About Field Organization

Field sections are provided for organizing fields on state and transition forms. Organizing fields in sections provides a way to group fields for display, as well as to limit user accessibility to certain fields. When quick forms are used, field sections are used to control security and field layout. When custom forms are used, field sections are used to control security only.

In SBM Composer, you assign fields to privilege sections when you create them in tables. You can also override privilege sections for each field for workflows, states, and transitions. These settings apply to quick forms and custom forms.

In Application Administrator, you can override inherited field order fields for projects and for individual states and transitions.

There are three ways to control access to fields in sections:

Roles
Grant field section privileges to roles in your application in SBM Composer.
Groups
Grant privileges to field sections for your application to groups in Application Administrator.
Users
Grant privileges to field sections for application users in Application Administrator.

Tip: You may want to restrict access to the Owner, Secondary Owner, Project, and State fields from most users. These fields are generally handled automatically by the system; therefore, most users should not have access to change the field values. There may be situations, however, where a manager or administrator might want to manually change the values in these fields.

For details on changing field order, refer to Reordering Fields.

Provided Field Sections

Provided field sections enable you to control access to fields through role-based privileges and user and group privileges.

Note: On-premise customers can change the names of all field sections in your system on the Labels tab in the Settings dialog box in the SBM System Administrator. Field section names can also be changed for each primary or auxiliary table in SBM Composer. These custom field section labels appear on forms.

The following set of field sections are provided:

Standard Fields
The fields contained in this section are always visible to users who have privileges to submit, view, update, or transition items for a particular project. On quick forms, the Standard Fields section and set of fields are displayed at the top of each form.
Tip: Place required fields in this section to ensure users can provide values as they work with items.
User Fields
Advanced Fields
Manager Fields
System Fields
Use this section to store fields that are visible to users with privileges to fields in this section. Typically, this section is used to store fields that are automatically populated by the system, such as the Owner or State fields. You can then limit access to this section so that users cannot inadvertently change your process.
Hidden Fields
Provides a place to store fields that you may not want users to view or update for a particular workflow, state, transition, or project.
Not Used Field Section
Provides a place to store fields that are not used in a particular workflow or auxiliary table. Fields placed in this section for tables or workflows are not available for modifications for projects, states, or transitions.
Deleted Field Section
This field section contains fields that have been deleted, allowing you to restore them at any time using SBM Composer. For example, you can reuse deleted fields by restoring them and then renaming them and resetting properties. Reusing deleted fields helps with database table field limits.
Note: The Not Used and Deleted field sections are not visible in Application Administrator.