How approval activity behaves when change request items are grouped by category in RSA Identity Governance & Lifecycle
Originally Published: 2019-09-24
Article Number
Applies To
RSA Version/Condition: 7.1.1
Issue
For example, given an activity workflow where changes are grouped by category under Process Properties as shown below:
and entitlements are requested from two applications: Application X and Application Y, the following change request is created:
| Parent WF | Sub WF | Entitlement | Category | Assigned approvers |
|---|---|---|---|---|
| WFX | SWFX1 | X.X1 | Accounting | U1,U2 |
| WFX | SWFX2 | X.X2 | HR | U3,U4 |
| WFY | SWFY1 | Y.Y1 | Accounting | U5,U6 |
| WFY | SWFY2 | Y.Y2 | HR | U7,U8 |
Entitlements X1 and Y1 are grouped in the Accounting category for approval. If user U2 logs in and approves X1, then X1 and Y1 approvals are auto-completed as follows:
Approval 'Accounting' completed by U2 on <date/time>
Approval 'Accounting' completed by System (because of category manager) on <date/time>
Approval 'Accounting' completed by System (because of category manager) on <date/time>
This is current product behavior. However, there are times when you may not want items in the same category to be automatically approved. This article discusses a new product feature which will allow you to configure this behavior.
Resolution
When you edit the workflow (Requests > Workflows > Approval/Fulfillment tab > {name of workflow}> and select the grouping of changes under Process Properties and then choose category as your grouping, a new check box will display called Auto Complete Category. Choosing this option will auto complete change request items in the same category. Below is a sample screenshot of the new option:
NOTES:
- This change will take effect for new processes and new jobs only. This will not effect existing jobs.
- The Resource Assignment on any Approval/Activity Nodes in the workflow must be set to ANY.
