Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle
Originally Published: 2024-04-29
Last Modified: 2025-10-24
Article Number
Applies To
- RSA Governance & Lifecycle 8.0
Issue
Using multiple activity nodes or sub-processes that include activity nodes similar to the below screenshot will result in excluding the previous approvers, even though no exclusion options have been set up under the 'Exclude' section.
If one user (who is a designated member in the group/role completed the assigned activity) completes their activity before another parallel workflow reaches the activity node or any other Activity Node within the same workflow, then the user gets excluded from the assignment in the other activity nodes.
Resolution
This is known behavior in the following versions:
- RSA Governance & Lifecycle 8.0 P05
Related Articles
How to exclude files based on a regular expression in RSA Access Manager Agents 26Number of Views SSOAgent - SAMLConfiguration - Teem RSA Ready SecurID Access Implementation Guide 2Number of Views Attribute Change Rule reverts to a previous version after making changes in RSA Identity Governance & Lifecycle 27Number of Views How to exclude a range of IPs from analysis with whitelists in RSA Web Threat Detection 31Number of Views RSA Identity Governance and Lifecycle Attribute change rule not detecting changes in terminated users 90Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?