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

Localizing AOTs, PDTs, and AIFs

When you configure an application object template (AOT) or a process definition template (PDT), you can also include other locales. You can create additional sets of display properties for your users, based on other locales you specify. These display properties are automatically related to each other.

If you plan to deploy advanced interface forms (AIFs) in a localized environment, you should create localized views for them. The AIFs are installed with localized views for English, Japanese, French, Italian, German, Spanish, and Simplified Chinese. 

For information about localizing Action Request System forms, see Localizing form views.

Related topics

Localizing-the-application

Important

  • The parent AOTs and PDTs appear in the first locale created. As a result, if you first create an AOT in English and then localize it for French, you only see the parent English AOT shown in the PDT form.

To localize AOTs

  1. To create the AOT, on the Custom Configuration tab of the Application Administration console, select Service Request Management >Application Configuration > Define Application Object Template, and click Open.
  2. Search for a record and open it.
  3. Click Other Locales.
  4. In the Defined Locales dialog box, specify a new locale.
  5. Enter a user-friendly name of this AOT, based on your locale.
  6. Provide a summary, based on your locale.
  7. Click Add to save the display properties for this locale.
  8. Add more locales as needed.
  9. Close the dialog box, and click Save.
     The Service Catalog Manager can use this localized AOT when creating a PDT.

To localize PDTs

  1. Create the PDT.
  2. Add the localized AOT or localized nested PDTs to this PDT.
  3. Click Other Locales.
  4. In the Defined Locales dialog box, specify a new locale.
  5. Enter a name for this PDT, based on your locale.
  6. Provide a summary, based on your locale.
  7. Click Add to save the display properties for this locale.
  8. Add more locales as needed.
  9. Close the dialog box, and click Save.
    The localized PDTs appear in the Process View of the Service Catalog Manager Console.
    The localized PDTs have the same template ID as the original. The Service Catalog Manager can use these localized PDTs when creating an SRD.

To localize AIFs

  1. For each AIF that you want to localize, create a localized view of that form.
    You can use a copy of a view as the base for creating a localized view. The new view should have the Locale property set to match the appropriate locale.
  2. After you associate a view with a specific locale, select that view and localize the components that users see.
    For example, translate the field labels.
  3. After you translate the components, adjust the field and view size to better match the new labels.

If you create and localize your own advanced interface forms (AIFs) and they do not appear as expected, use the following procedure to reconfigure the AIFs.

To reconfigure AIFs

If the SRD includes an advanced interface form that is localized, users will see the correct localized version when they log into the Request Entry console.

  1. From the Application Settings list, select Service Request Management > Advanced > Configure Advanced Interface Data, and click Open.
  2. Search for a form record.
  3. Modify the information as needed.
  4. Specify the locale for your form.
  5. Click Save.

 

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