When approval activities are grouped by category, they auto-complete when one of the items is rejected 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 expected behavior. However, if U2 logs in and rejects X1, then Y1 should not be automatically approved (auto-completed.) The defect is that it does autocomplete same as if entitlement X1 had been approved.
Cause
Resolution
