Public Forms should support dynamic prefilled / default values

[sleidig]

Public Forms (PublicFormConfig based views) should support the same default value system as normal FormComponents of the Entity Details view.

Previous system:

• PublicFormConfig.prefilled: { "remarks": "added through public form" }

New system:

• PublicFormConfig.prefilled --> removed (write config-migration method in ConfigService)
• PublicFormConfig.columns --> change type from string[][] to FieldGroup[] (support full FormFieldConfig format to overwrite default values if needed; also support field group headers)
  • e.g. PublicFormConfig.columns: [ { fields: [ { id: "remarks", defaultValue: { mode: "static", value: "special default value" } } ]} ]
• use defaultValue definitions from the underlying EntitySchema of the entity, if it exists and is not overwritten in this PublicFormConfig object

The "default" prefilled values of a field in a Public Form (PublicFormConfig.prefilled) currently only allows fixed values and is a separate system from the "standard" default values approach, which is implemented via the EntityFormService and its use of the DefaultValueService. We should only rely on a single implementation of such similar logic. Remove custom implementation of "prefilled" values for public forms and work out a solution how to rely on the same DefaultValueService or EntityFormService methods there.

[aam-digital-ci]

🎉 This issue has been resolved in version 3.43.0-master.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[aam-digital-ci]

🎉 This issue has been resolved in version 3.43.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀