Forms & UI config
Quick answer
Building forms in SailPoint IdentityIQ: provisioning policy forms, workflow forms, field types and dynamic behaviour.
Key takeaways
- Forms capture data in policies, workflows and requests
- Fields have types and live in sections
- Dynamic show/hide/require and refresh behaviour
- Validation keeps input clean before provisioning
Where forms appear
Forms drive data capture in IdentityIQ: provisioning policy forms at account creation, workflow forms during a process, and request forms in Lifecycle Manager.
Fields and sections
Forms are built from fields with types (string, boolean, select), organised into sections, with values sourced from attributes, allowed-value rules or field value rules.
Dynamic behaviour
Fields can be hidden, required or refreshed based on other fields, giving a responsive experience without custom UI code.
Validation
Field validation and rules keep input clean before it reaches provisioning, reducing downstream errors.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What computes a form field’s default value?
- A. A correlation rule
- B. A field value rule
- C. A connector
- D. An audit event
Show answer
B. A field value rule
Field value rules compute defaults or derived values for form fields.