Step Libraries

Step libraries are designed to offer a group of common functions that can be added to existing workflows from the Add a Step panel Business Process Editor. Step libraries are a collection of steps encapsulated by a workflow with the template attribute marked true. The steps do not have any transitions and they are not executable. A Step Library must be defined. See the following example.

Note: The type does not have to be StepLibrary. However, using the StepLibrary type ensures that these workflows do not appear in other parts of the product.

Copy
<Workflow name="Provisioning Step Library"
                  type="StepLibrary"
                  template="true">

When you edit a new or existing workflow, you can include a list of step libraries by including a comma separated list in the stepLibraries attribute. See the following example.

Copy
<Workflow name="LCM Provisioning"
                  type="Provisioning"
                  taskType="LCM"
                  libraries="Identity,Role,PolicyViolation,LCM,BatchRequest"
                  stepLibraries="Common,Provisioning"
                  handler='IIQ.api.StandardWorkflowHandler'>

In the example above, when you edit a business process with the LCMProvisioning type, the Common and Provisioning steps are available in the Add a Step panel of the Business Process Editor.

Steps within a step library workflow can also include a soft reference to a step form that provides a simplified form-based interface that you can use to add arguments to some steps in the workflow. This form-based interface adds a Basic view option to the Arguments tab of the Step Editor. The Basic view is built using the information contained in the referenced form. The Advanced view is a list of all possible arguments and is built using the list of arguments that the step library references.

When you add a step form reference to a step library, use the configForm attribute, See the following example.

Copy
<Workflow name="Provisioning Step Library" 
                     template="true" 
                 type="StepLibrary">
 <Step configForm="Provisioning Approval Step Form" 
                 icon="Task" 
                 name="Account Approval">
<Arg name="approvalMode"/>
<Arg name="approvalScheme"/>
<Arg name="approvalSet" value="ref:approvalSet"/>
...

In the example above, when you edit an approval step in the Step Editor, the Basic and Advance Views of the Arguments tab are displayed.

Built-in Steps

IdentityIQ includes several built-in steps. The Start, Stop, and Generic steps apply to all workflow types. The following table lists the names, descriptions, and associated workflow types of additional built-in steps.

Step

Description

Process Type

Notify

Allows users to select categories of recipients to notify, the specific recipient, recipients for each category, and the specific email template to use for each category.

Identity Lifecycle

LCM Provisioning

Account Approval

Used for provisioning request approvals. The process assumes many of the Provisioning Workflow structures exist.

Identity Lifecycle

LCM Provisioning