This documentation supports the 22.1 version of BMC Service Request Management.To view an earlier version, select the version from the Product version menu.

Localizing the application

You can localize all BMC Service Request Management content that the users can view in the Request Entry console. Service Request Management leverages the robust internationalized environment of Action Request System 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 Service Request Management objects (for example, navigational categories or SRDs) are displayed based on the locale fallback mechanism of AR System. If AR System finds at least one localized object for the client locale, it does not display the other localized objects defined in other locales.

Related topics

Configuring-locale-fallback-mechanism

Localizing-navigational-categories

Localizing-AOTs-PDTs-and-AIFs

Localizing-SRDs-and-surveys

Deploying-and-verifying-localized-content

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 Service Request Management sample data is defined with null locale values. If you do not localize any Service Request Management 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 Service Request Management object, you must also localize the sample data. Users see only those Service Request Management objects that match their client locale. Objects with empty locale are not displayed.