Previous Topic: Define Approvers for Approval Tasks

Next Topic: Attribute Value and Sequence Order

How Approval Tasks are Triggered

An Option Pack Workflow approver is defined at the value level. For a specific process, the new values added are checked against the approvers' configuration, and each results in an approver if necessary. New values are those that are now in the triggering attribute and do not yet exist in the target attribute (before the change).

A triggering attribute starts a workflow process and the target attribute starts the approver selection. For example, if attribute RACF group is defined as a triggering attribute and there is a change in RACF group for a selected user, a defined workflow process starts.

During the approval chain, an approver may reject some of the groups requested. The target attribute will hold the accumulated approved values until the chain of approval completes.

Example

There is an Active Directory group approval process configured. The ADGroups attribute is both the trigger and the target. Two new groups are added to the user. These groups are now in the trigger (ADGroups attribute) which starts the workflow process, but are not in the target (ADGroups again, before the change). Therefore, these two new groups are recognized as new values, and are checked against the approvers' configuration.

Example

There is a logical attribute to which new Active Directory group values are added. This is the trigger to the Active Directory workflow process. The target is the ADGroups attribute, which is synchronized with the endpoints. Adding two groups to the logical attribute will cause the workflow to trigger. Those groups may or may not already exist in the ADGroups physical attribute, so only those that did not exist are checked.


Copyright © 2009 CA. All rights reserved.