Goal
Improve the usability of EDM-generated applications by preventing confusion around auto-generated fields during entity creation and API usage.
Scope
- In Scope
- Hide auto-generated fields (e.g. IDs, timestamps, system-managed values) from the “Creation” UI in EDM-generated applications.
- Exclude these fields from mandatory validation in REST API requests during entity creation.
Description
Currently, EDM Templates generate UI and REST APIs that include auto-generated fields in the “Creation” flow. These fields are not editable by users, yet they appear in the UI and are part of validation rules in the REST API.
This leads to:
- Confusion in the UI, as users see fields they cannot modify.
- Validation errors in REST API requests, since users are expected to provide values for fields they cannot control.
The expected behavior is that auto-generated fields should be:
- Hidden in the “Creation” UI.
- Excluded from required validation in REST API create operations.
Acceptance Criteria
Goal
Improve the usability of EDM-generated applications by preventing confusion around auto-generated fields during entity creation and API usage.
Scope
Description
Currently, EDM Templates generate UI and REST APIs that include auto-generated fields in the “Creation” flow. These fields are not editable by users, yet they appear in the UI and are part of validation rules in the REST API.
This leads to:
The expected behavior is that auto-generated fields should be:
Acceptance Criteria