Localizing BMC Service Request Management content


You can localize all  content that the users can view in the Request Entry console. 

WarningSome content is unavailable due to permissions.

leverages the robust internationalized environment of  to support different character sets and a suite of features that enables administrators to produce localized applications. Additionally, users can specify their language and formatting preferences to have the application delivered in the style that is the most useful to them. With this model, the same application can be delivered simultaneously to different users in multiple languages.


The various 

WarningSome content is unavailable due to permissions.

objects (for example, navigational categories or SRDs) are displayed based on the locale fallback mechanism of . If  finds at least one localized object for the client locale, it does not display the other localized objects defined in other locales.

Success

Best practice
When you create your own navigational categories, AOTs, PDTs, and SRDs, we recommend that you localize them at the same time. 

By default, the

WarningSome content is unavailable due to permissions.

sample data is defined with null locale values. If you do not localize any

WarningSome content is unavailable due to permissions.

objects, the sample data (for example, the navigational categories) is displayed any user who logs in to the Request Entry console for the first time. 

When you localize a

WarningSome content is unavailable due to permissions.

object, you must also localize the sample data. Users see only those

WarningSome content is unavailable due to permissions.

objects that match their client locale. Objects with empty locale are not displayed. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Service Request Management 25.4