Using message keys in Bundle sysDescriptions

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Hello ,

We are using SailPoint IdentityIQ and message keys from a .properties file to manage translated labels and descriptions.

For example, message keys work correctly in objects such as ObjectConfig attribute :

<ObjectAttribute displayName="custom_attribute_label" ... />

The corresponding value is correctly resolved from the language .properties file.

We would like to use the same approach for bundle descriptions.

For example:

<entry key="sysDescriptions">
  <value>
    <Map>
      <entry key="en_US" value="custom_bundle_description"/>
    </Map>
  </value>
</entry>

With the following entry in the .properties file:

custom_bundle_description=This is the bundle description.

However, IdentityIQ displays custom_bundle_description directly instead of resolving the message key.

Is it possible to use a message key from a language .properties file directly inside Bundle.sysDescriptions?

If yes, what is the supported configuration or syntax to make IdentityIQ resolve the message key?

Thanks
Best Regards

2

Hello Alshahim. I do not see a documented syntax to resolve a message key directly inside Bundle.sysDescriptions.

sysDescriptions stores the description text for each locale, for example:

<entry key="sysDescriptions">
  <value>
    <Map>
      <entry key="en_US" value="This is the bundle description."/>
    </Map>
  </value>
</entry>

IIQ then uses the appropriate localized description based on the user’s language.

If you want to maintain the text in a .properties file, one practical approach would be to resolve the message key in your import or custom code first, then set the resolved text on the Bundle:

bundle.addDescription(locale, resolvedText);

If you are updating the Bundle directly in custom code, persist the change using the appropriate SailPointContext save/transaction handling.

So in your current example, value="custom_bundle_description" would normally be treated as the description value itself rather than automatically resolved as a message key.

3

@alshahim04 System UI Labels (Buttons, menu headers, dialog titles, validation errors) live in .properties files and are looked up via native APIs. While Roles and Entitlements are Business Data stored in the database (spt_bundle table). When IdentityIQ renders a role in the Access Request catalog or Role Management, it calls bundle.getDescription(). It does not run the string through the message catalog

The best way is to define the different locale in the role xml itself like @punna0001 said. Here is an example of description with Dutch description.:

     <entry key="sysDescriptions">
        <value>
          <Map>
            <entry key="en_US" value="Manager access to the PRISM financial management system."/>
            <entry key="nl" value="Managertoegang voor het financiële beheersysteem PRISM."/>
          </Map>
        </value>
      </entry>

Based on browser language, it’ll pick the desciption. Here it is in Dutch:

image
image2064×742 26.2 KB