Workflow Variables under the Resource section of Workflow Nodes cannot resolve Roles and Groups after being imported in RSA Identity Governance & Lifecycle
Originally Published: 2020-08-18
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
For example, when navigating to Requests > Workflows > {Workflow tab} > {Workflow name} > {Node name}, there is a RESOURCES section under Activity Node Properties on the right-hand side. In this section under Include, Workflow Variables may be included as a Resource. If the Workflow Variable references a Role or Group name from the other system, it may not resolve correctly on the system to which it was just imported.
Cause
This problem is caused by the underlying internal reference ID. The internal reference ID for a Role or Group on one system may not be same as on another system. User do not have this issue because they can be based on other options besides the internal ID such as the User ID or email address as noted in the example below.
Resolution
The product has been enhanced to allow the user to define the values used for Roles and Groups in workflows. Note below the additional Resource options available in 7.2.0
Workaround
Related Articles
RSA Identity Governance and Lifecycle 7.1.1.1 Release Notes 26Number of Views RSA Identity Governance and Lifecycle 7.2 Upgrade and Migration Guide 6Number of Views Change Request generated by Role Review shows as Rejected in RSA Identity Governance & Lifecycle 31Number of Views HTTP 401 Unauthorized occurred while changing the password in the webservice node in the workflow in RSA Governance and Li… 16Number of Views RSA Identity Governance and Lifecycle 7.1.0.6 Release Notes 19Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme… How to import CA signed console cert from AM 8.x primary into a new primary with same FQDN
Don't see what you're looking for?