They are used for defining and saving the extended attributes of selected entities:
SysSystem - linked to the systems IdmIdentity - identitiesExtended attributes are saved in the individual tables according to the entity which they are linked to ⇒ which is their owner (e.g. the entity SysSystemFormValue').
FormService serves for working with the extended attributes on the back-end.
On the front-end, the editing of dynamic forms is done by the component EavForm.
Dynamic forms support these data types with properties:
obligationreadonlymulti values - represented on the front-end by a textarea, where a line is a value (a new line separates the values)confidential - the values are stored in an encrypted storage). Stored values of these attributes - substitute characters only - are loaded on the front-end. The value can only be changed and determined whether it is filled in.So far, the agenda for managing form definitions has not been implemented, therefore the procedure will be changed (and possibly simplified with regard to usage from the FE, which is now linked to a predefined form definition).
On the FE, there is not an agenda of forms - their definition and attributes. Each definition can contain zero or more attributes. To maintain the integrity, an interface UnmodifiableEntity has been created, which allows adding a flag that the entity has been created by the system and cannot be modified (or some of its attributes) and deleted (this logic now needs to be implemented manually into the relevant controllers), for example in IdmFormAttributeController.
It is necessary to be cautious when editing individual form attributes as the logic linked to this form can be rendered non-functional