Handler fields in forms

[teemukataja]

Is your feature request related to a problem? Please describe. Paper documents can have sections such as "applicant fills here" and "clerk fills here", it could be useful to have a similar feature in REMS forms.

Describe the solution you'd like When creating fields to a form, having to select if this field is for the applicant or the handler. The handler fields could optionally be invisible to the applicant, if they contain some internal data or automation configuration, or they could be visible, so that the applicant can see some important additions from the handler.

Describe alternatives you've considered It's already possible to do this by parsing remarks made on an application, but structured fields would be more efficient.

Additional context

• so that handlers can give structured configurations for automation
• so that handlers can fill in additional information on an application

[Macroz]

• Something I've considered before is having the ability to attach metadata to an application. Effectively, it would probably be like the "handler fields", if there is a UI for the handler and not just an API.
• It could be useful for integrations to be able to store some state in an application too (more than just setting an external id).
• Possibly this could be made to work better just extending the remarks too.
• The current form structure feels like it could be difficult to work so that some fields are for the applicant and some for handler. One of the assumptions it breaks is that the applicant fills the application and the handler doesn't touch it.

Let's discuss this in next planning.

[jaakkocsc]

Handler form could be an option for workflows.