Workflow Element

The Workflow tag identifies the name and type of the workflow.

Copy 
<Workflow  explicitTransitions="true" name="WF-Training Hello World Workflow" type="IdentityUpdate">

The attributes of a workflow element including the following:

Workflow Attribute

Purpose

configForm

A soft reference to a process variable form presented in the Basic View of Process Variables tab, or a step form presented in the Basic View of the Arguments tab on the Step Editor panel accessed from the Process Designer tab of the Manage Business Process page.

name

Short descriptive name for the workflow this is displayed in user interface selection list-boxes and list of existing business processes on the Process Editor window.

type

Workflow type. Type is used to filter workflow selection lists in configuration windows where you select the workflow based on system activities.

explicitTransitions

Boolean value indicating that transitions between steps are explicitly specified and workflow should not resort to implicit, fall-through, transitions when no transition conditions evaluate to true.

The default setting is false. If you so omit this argument and the specified transition conditions all evaluate to false, the workflow uses implicit transitions and launches the next sequential step in the XML. However, if you edit a workflow using the Business Process Editor, the value is changed to true.

If the developer makes the last transition in any set unconditional, which is considered best practice, the transitions between steps are smoother.

libraries

Lists workflow libraries the workflow needs.

If this attribute is not specified, workflows automatically have access to Identity, Role, PolicyViolation, and LCM libraries.

stepLibraries

Lists workflow step libraries the workflow can access.

If this attribute is not specified, workflows automatically have access to the Generic Step Library, which provides access to the Start, Stop and Generic steps.

handler

The default workflow handler is sailpoint.api.StandardWorkflowHandler. This attribute does not need to be specified when the default is used. In this case, the best practice is to omit it.

If you use a custom workflow handler, the custom handler must EXTEND the default handler and not replace it. The custom handler must be specified in the workflow Handler argument.