Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identity Governance & Lifecycle
Originally Published: 2020-09-22
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1
Issue
For example,
1. Make a copy of the default "On Hold Review" workflow but with the Review Status changed to Complete.
2. Edit the default user review to set the due date as 1 day.
3. To a default user review associate the escalations to change the review state to hold after 1 day and then change the state to complete after 2 days.
4. Run the review
5. You will see the OnHold escalation triggers but the next escalation does not get triggered.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P11
- RSA Identity Governance & Lifecycle 7.2.0 P05
- RSA Identity Governance & Lifecycle 7.2.1 P01
Related Articles
Review escalation workflows sometimes do not trigger in RSA Identity Governance & Lifecycle 93Number of Views Escalation Workflows randomly fail to trigger in RSA Identity Governance & Lifecycle 46Number of Views Entitlement View does not scope correctly when triggered via request buttons in RSA Identity Governance & Lifecycle 16Number of Views When multi-step review is generated, NewReviewGeneratedEvent is triggered twice for second step review sending duplicate e… 49Number of Views RSA Identity Management and Governance DB logs, task results, task progress are not available on run details of collection… 126Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?