Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle
Originally Published: 2024-04-29
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
Attribute Change Rule reverts to a previous version after making changes in RSA Identity Governance & Lifecycle 23Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle 105Number of Views How to upgrade to Sentry CA 3.6 from a previous version of Sentry CA. 3Number of Views Important information on upgrading to Sentry CA 3.7 from a previous version. 3Number of Views What is Schema.Mitigator.pruneAttributes in SilverTail v4.x 7Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?