Use Form Designer to define how object information is arranged in a form. The application also refers to this tool as Form Builder. It helps administrators choose fields and organize a reusable presentation for a particular type and context. Designing a form changes its definition; entering or updating a particular object’s values is a separate task.
Choose the definition context
- Open Form Designer with an account permitted to manage form definitions.
- Review the form category or intended context, then select the relevant object type. Where a universal definition is appropriate and supported, use the corresponding option.
- Load an existing form to review it, or choose Create New Form to begin a separate definition.
- Check the definition’s identity and context before arranging its fields. For a relationship-specific form, confirm the relevant relationship as well.
Arrange fields
Use the available attribute area to find fields supported by the chosen context. Add the fields required for the form and arrange them in a useful order. Group related information where the designer supports grouping.
Use names and labels that help the intended reader understand the information. Review each field’s available display and layout settings. The field choices depend on the selected type and category, so changing that context can change what is available.
An object attribute and a relationship attribute describe different things. For example, a value attached to a connection belongs in the relevant relationship context. Confirm the intended data source before placing the field in a form.
Preview and save
Use the view-mode control to inspect the form’s presentation. Review field order, grouping, labels, and the space available for longer values. Preview helps you check the layout before saving; it does not publish or save the definition by itself.
Choose Save and wait for confirmation. Reopen the definition to verify that the intended fields and arrangement persisted. Then check it in the application context where it will be used, selecting the form there when applicable.
Understand shared definitions
A saved definition can be used by other views and users. Review the effect of changing an existing form before saving. Changing form layout does not grant access to object data or replace the platform’s attribute validation and lifecycle rules.
Troubleshooting
If an attribute is missing, check the selected type, category, and relationship context. If the preview differs from the intended form, review field settings and grouping before saving again.
If Save is unavailable, confirm that there are unsaved changes and that you have definition-management permission. If a saved form is not offered in the intended view, check its type and category and refresh the available definitions.
