000039103 - The display names of the 'Contains Privilege Access' and 'Business Criticality' attributes fail to change after they have been modified in customerstrings.properties in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jul 16, 2020Last modified by RSA Customer Support Employee on Jul 16, 2020
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000039103
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
IssueAfter creating a customerstrings.properties file to modify the display names of the attributes Contains Privilege Access and Business Criticality found under the General tab of Directories, Applications and Role Sets, the new display name is not reflected under the General tab.


In the example below, the following changes were added to a customerstrings.properties file:
PRIVILEGED_FLAG=Contains EDITED Privileged Access.

and the file was uploaded to RSA Identity Governance & Lifecycle under Admin > User Interface > Files tab > Customer Strings from the drop down menu > Upload > customerstrings.properties > OK.

The expected behavior is that Contains Privilege Access will display as Contains EDITED Privileged Access and Business Criticality will display as EDITED Business Criticality. The actual behavior is that the attribute names remain unchanged as seen when viewing a Role Set (Roles  > Role Sets > {Role Set name} > General tab).
User-added image

The column names under Table Options correctly show the new attribute display name:
User-added image

The new attribute display names are also correctly reflected under the Admin > Attributes > Business Source tab 
User-added image

It is only under the General tab of Directories, Applications and Role Sets that the display name is not correctly reflected.

CauseThis is a known issue reported in engineering ticket ACM-104937.
ResolutionThis issue is resolved in RSA Identity Governance & Lifecycle 7.2.0 P02.
WorkaroundCurrently there is no workaround for this issue.