Attributes
Forms can include a map of attributes that are used by the renderer. These are applicable only to workflow forms and, in a limited way, to the identity provisioning policy form.
Attributes are specified with the following keys:
Key |
Description |
pageTitle |
Title to render at top of page, typically larger and a different color than the form title; also displayed in browser window header bar in some cases |
title |
FormTitle, shown at top of form body |
subtitle |
Form subtitle, shown below title |
readOnly |
|
hideIncompleteFields |
This does not create dynamically displayed fields on forms. Fields are not displayed on a form after their dependency values on the same form are entered. Use the new hidden attribute on Fields and Sections to achieve this dynamic display functionality. |
Note: The Boolean attributes are only specified if they are true; they default to false when omitted.
Attributes maps are specified as shown here:
<Attributes>
<Map>
<entry key="pageTitle" value="Review Non-Employee Request"/>
<entry key="readOnly" value="true"/>
</Map>
</Attributes>
Attributes do not apply to report forms because the sections in a report form are pulled out of the report's form definition and combined into the Report Form Skeleton for display in the user interface. Even if they are specified in the report form, these attributes are never applied to the resultant form that is displayed to the user.
On an identity provisioning policy form, the pageTitle attribute is ignored because the main page title is programmatically set based on the other action being performed (Create New Identity, Edit Identity Attributes for [Username], or New User Registration). The title and subtitle attributes are displayed in the user interface when specified in the form's attributes map. The readOnly and hideIncompleteFields function on this form type should not be used because they do not provide useful functionality for this type of form.