• If the client locale is set in the localization property and the translations for display name are available in that locale, the display name of the administrative objects is seen in the client locale.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” When the value for display name is available, then in the Integrity Lifecycle Manager client, the display name value from the German locale is seen.

• If the client locale is not set in the localization property, or if the translations for display name are unavailable in the client locale, then the display name of the administrative objects is seen in the server locale.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set to “en.” When the display name value in the English locale is available, then in the Integrity Lifecycle Manager client, the display name value from the English locale is seen, as the German locale is not set in the property.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” The display name value in the English locale is available but is unavailable for the German locale. In the Integrity Lifecycle Manager client, the display name value from the English locale is seen.

• If the server locale translations for the display name value are not available, the Name of the administrative object is seen. The changes for the administrator operations create and edit are recorded in the language matching the client that is used (provided that it is set in the property).

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” When the display name value in the English locale and the German locale is unavailable, then in the Integrity Lifecycle Manager client, the name is seen.

• If the client locale is set in the localization property and the translations for description are available, the description is seen in the client locale.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” When the value for description is available, then in the Integrity Lifecycle Manager client, the description value from the German locale is seen.

• If the client locale is not set in the localization property, or if the translations for description are unavailable, the description for the administrative objects is seen in the server locale.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en.” The description value in English locale is available, then in the Integrity Lifecycle Manager client, the description value from the English locale is seen (as the German locale is not set in the property).

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” The description value in the English locale is available but is unavailable for the German locale. In the Integrity Lifecycle Manager client, the description value from the English locale is seen.

• If the server locale translations are unavailable, the description is seen as blank.

◦ For example, consider that the server locale is English and the client locale is German, and in the server the localization property is set as “en;de.” The description value is unavailable for both the locales, then in the Integrity Lifecycle Manager client, the description value is seen as blank.