About Forms
Each object has an associated form that defines its record-level interface. These forms are the default interface for creating and configuring objects. When you create a new object, its associated form is automatically generated. You can use Form Designer to add and remove sections and tabs, fields, and related lists to configure forms to meet your organization’s unique needs. For example, you can add related lists to Equipment forms to help identify installed products, reorder fields to change the information that appears in Quick View panes, or update form field metadata to make field values required or editable.
 |
Field properties specified at the metadata level, for example, in Field records, apply to both API and UI functionality. Form-level properties apply to the UI only, and cannot override metadata-level properties. You can modify fields that are defined as editable or as optional at the metadata level to be non-editable or required at the form level. However, you cannot make fields that are defined as non-editable or required at the metadata level editable or optional at the form level.
|
In addition, you can create multiple forms for individual objects for various purposes. For example, you can create multiple form versions for users assigned to specific Roles or Groups.
Forms are automatically selected for the current user based on the following criteria:
• The primary Role or Group assigned to the form.
• The custodian that defines and owns the form.
• The primary Role or Group assigned to the current user.
• The custodian for the current user.
|
|
The Custodian object controls which organizations can create and own records within a Max Platform application tenant. Max Platform users can have multiple roles and belong to multiple groups, but each user is assigned a single primary Role or Group.
|
Form selection logic is applied in the following order:
1. Users are assigned the forms designed for the primary Roles or Groups to which they are assigned in their user account records.
2. If multiple forms are configured for the same Role or Group, forms owned by the custodian for the current user are assigned. If multiple forms match this rule, the form with the earliest creation date is selected.
3. If no form matches the current user's primary Role or Group, the form configured for the Standard User role owned by the custodian for the current user is assigned. If multiple forms match this rule, the form with the earliest creation date is selected.
In cases where the predefined forms included with Max Platform applications require customization to meet your organization's unique needs, you can save existing forms with unique names, make modifications as needed in Form Designer, and set them as the default active forms.
|
|
Forms owned by the ServiceMax Applications custodian cannot be modified. To configure such a form, save it with a different name and make modifications as needed.
|
When you create custom forms based on predefined forms, be sure to retain the same form type. The following form types are available:
• Calendar Form: Contains fields and relations, without attachment support.
• Canonical Form: Contains fields only, without attachment or relation support.
• Dispatch Form: Contains fields only, without attachment or relation support. Used by the Dispatch Job dialog box in Service Board.
• Custom Form: Generic form with fields, attachments, and relations as configured in Form Designer.
• Quick Create Form: Contains fields in a one-column layout, without attachment or relation support. Used for quick record creation from related lists.
• Quick View Form: Contains fields in a one-column layout, without attachment or relation support. Used for read-only abbreviated record display.
For details on the predefined forms provided with your Max Platform application, consult product Help.