SecurID® Governance & Lifecycle Knowledge Base
Find answers to your questions and identify resolutions for known issues with knowledge base articles written by SecurID Governance & Lifecycle experts.
Article Number
000036073
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.1 , 7.0.2
RSA Version/Condition: 7.0.1 , 7.0.2
Issue
Upgrading from 6.9.1 to the latest versions 7.0.1 or 7.0.2 have caused the parameter values in the workflow provisioning node to be misaligned.
The issue is that if we map hardcoded values to a parameter, and if that value has a character such as a comma (,), then when you save the node and open it again you will see the value after the comma is mapped to the next parameter in line and all other mappings are misaligned.
Image description
Once we save the changes and open the node again, the values are misaligned.
Image description
However, it is working properly; that is, the mapping is correct, as it should be and this is just a display issue.
The issue is that if we map hardcoded values to a parameter, and if that value has a character such as a comma (,), then when you save the node and open it again you will see the value after the comma is mapped to the next parameter in line and all other mappings are misaligned.
Image descriptionOnce we save the changes and open the node again, the values are misaligned.
Image descriptionHowever, it is working properly; that is, the mapping is correct, as it should be and this is just a display issue.
Cause
This is a bug reported and will be fixed in future release.
Workaround
To have the value aligned correctly to its parameter we can create an SQL SELECT node, pulling the values to the parameter that have multiple records and then map the Job or Public workflow variable to the provisioning node parameter.
Image description
Image description
Image descriptionImage descriptionIn this article
