For file components, you can now select the documenttype for attachments on the component itself. This takes into account the selected ZGW API group/objects API group already if such a relevant registration plugin is selected.
However, this is still error-prone because you can select document types that are not related to the zaaktype that is configured in the registration backend.
Tightly coupling these component-configuration and registration backend concepts seems like a bad idea to me. I think it'd be nicer to be able to specify this at the registration-configuration level in the variables table. This would allow configuration and a better UI/UX specific to the particular registration backend, and is very similar to the "Objecttypes Contract" feature implemented recently.
This would move the registration tab of the file attachment component out of the builder and into the registration aspect.
Additionally, storing the omschrijving rather than the full URL would be more future-proof for when new versions are created.
joeribekker
commented
2 weeks ago
Thema / Theme
Plugins
Omschrijving / Description
For file components, you can now select the documenttype for attachments on the component itself. This takes into account the selected ZGW API group/objects API group already if such a relevant registration plugin is selected.
However, this is still error-prone because you can select document types that are not related to the zaaktype that is configured in the registration backend.
Tightly coupling these component-configuration and registration backend concepts seems like a bad idea to me. I think it'd be nicer to be able to specify this at the registration-configuration level in the variables table. This would allow configuration and a better UI/UX specific to the particular registration backend, and is very similar to the "Objecttypes Contract" feature implemented recently.
This would move the registration tab of the file attachment component out of the builder and into the registration aspect.
Additionally, storing the omschrijving rather than the full URL would be more future-proof for when new versions are created.
Added value / Toegevoegde waarde
Aanvullende opmerkingen / Additional context
No response