Here is a four-and-a-half minute video that shows you how to generate a form from a class definition and how to customize the form.
Forms are composed of three main components:
-
Form purpose
The form purpose controls the form section's structure. Each form purpose is displayed as a tab on the View Form dialog box.
-
Sections
Sections define a collection of display items (properties or relations). Sections may be either created or re-used from the database. Once a section is created, display items can be added to the section.
A section can be attached to multiple forms with any changes to that section automatically updated on all forms where it is included.
-
Display items
Display items are used to present data or relationships on a form. After a display item is created, the display item can then be added to a section for inclusion on a form. A display item can be a member of multiple sections. If a display item is updated, the changes are automatically updated on the forms where it is included.
|
1 |
Purposes |
|
2 |
Sections |
|
3 |
Display items |
Forms can be created in three different ways:
-
Generating a form automatically base on class definition and its realized interfaces.
-
Using the New Form dialog box to manually create the form.
-
Copying and editing an existing form.
There can be minor differences in form sections and display items between forms created
for the Desktop Client and those created for the Web Client. This is to help maximize
performance in the Web Client, as well as to support responsive design and form configuration.
A classified object can have alternative forms for different classifications of the class definition. The form is related to a class definition and used for all GUI operations of objects of that class definition. The SPFObjClassForm relationship definition is used to navigate to the correct form.
Form section precedence
Because sections of a form can be related to roles, though access groups, to allow or prevent access to those sections and the display items associated with them, it is possible for a user with multiple roles selected to have access to multiple sections with different configurations. By creating a hierarchical order, or precedence, for the sections, you can determine which section users see when they have multiple roles selected.
The different versions of a section are related using the SPFFormSectionsPrecedence relationship definition.
For more information, see Setting precedence for form sections.