Skip to content

Workflow Forms

Standard work item forms are available for presenting approval or other data requests to approvers. However, some installations prefer to use custom forms for these activities. Based on the type of the data collection effort, a custom form might be required. You can build a custom form using a

element in the XML that is embedded within the element.

Note

The element can be used to collect data from a user, even if the workflow is not an approval. You generally use custom forms for these activities because the normal approval forms do not apply. However, you can also use custom forms for traditional approval activities when you need a different presentation format.

The basic elements in a Form definition are:

<Form>
   <Attributes>    (map of name/value pairs that influence the form renderer)
   <Button>     (determine form processing actions)
   <Section>    (Subdivision of form; may contain nested Sections and Fields)
     <Field>    (may contain Attributes map, Script to set value, Allowed Values Definition script, and Validation Script)

For detailed information about working with forms, see Forms(LINK IN DOC).

Process Variable and Step Forms

You use forms added to steps on the Process Designer tab in the Business Process Editor to request data that a process needs from a user. For example, you can add a form to a step to request a value for a missing attribute.

However, to present information on the Basic Views of the Process Variables tab and the Arguments tab of the Step Editor, you use process variable and step forms.

To simplify the information displayed on the Process Variables tab:

  • Variables are displayed in more logical groups.

  • Variables that are rarely, if ever, modified are hidden.

Changes made in the Basic View are persisted to the Advanced View and more complex configuration can be performed there if needed.

The step forms are referenced from the workflows or stepLibraries. These forms define the form that is presented on the Arguments tab of the Step Editor panel and works similar to the process variable forms.

Both of these forms are referenced from workflows using the configForm variable. The forms can be defined, viewed and edited on the IdentityIQ debug page.