Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin UI for Public Forms should allow to overwrite details like field labels and required status just for that form #2872

Open
sleidig opened this issue Feb 20, 2025 · 0 comments

Comments

@sleidig
Copy link
Member

sleidig commented Feb 20, 2025

The Admin UI to manage a Public Form should be more flexible. At the moment all changes to a field there are applied to every form and the core profile (Entity Details view) of the entity. The user should also have the option to edit some details of the field only for the current Public Form, without changing the underlying entity's field. For example, I may want to make a certain field "required" for people filling that public form but when creating a new record within the app or editing records, that field shouldn't always be required for the team.

Use Case:

  1. Navigate to Children List
  2. "Edit Data Structure" (from the three dot menu at top right)
  3. section "Public Forms" in the Admin Entity UI
  4. open the "Example form" to edit the Public Form config
  5. in the "Configure Fields" tab, edit a field and mark it as required
  6. --> NEW: this change should only affect this public form; The Child Details view should not have this field as required after saving

Image


Implementation Considerations:

  • Related Component: EditPublicFormColumnsComponent
  • The PublicFormConfig entity can store a full FormFieldConfig instead of just the id of a field. This is then overwriting the base entity field's config. Changes in the Public Forms Admin UI should (probably?) only add an object defining these overwriting things in the PublicFormConfig without changing the entity type itself
    • However, adding new fields would require to write these to the entity instead
    • Also, changing the "Type" of a field should not be possible just for the form (this could lead to inconsistent data ...)
    • ❓ --> these edge cases need more discussion about the details of this requirement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Triage / Analysis
Development

No branches or pull requests

1 participant