This documentation supports the 23.3 version of BMC Helix Innovation Suite (AR System and BMC Helix Innovation Studio).

To view an earlier version, select the version from the Product version menu.

Creating a localization package definition

The Localization Package Definition editor in Developer Studio, as shown in the following figure, makes it easy to create a localization package definition for your application and any other forms that you want in the package definition.

AR System supports the administration functions only in English. Therefore, application menu labels and fields are not localized. Also, in AR System, the admin-only forms are not localized. Only the user-facing forms are localized.


To create a package definition

  1. Close any objects that you want to process in the localization toolkit.
  2. In AR System Navigator, right-click Localization Package Definitions, and select New Package Definition.
    A new package definition is opened, and the Target Server and Localization Database fields are completed.
  3. Click the Browse button (...) next to the Locales field, and select the locales for which you want to translate.
    A comma-separated list is entered in the Locales field.
  4. In the Ignored Field Label Prefixes field, enter a comma-separated list of prefixes that are used in field labels of fields that you do not want to localize.
    For example, to ignore all of the fields with labels that begin with zTMP, enter zTMP.
  5. To localize currency codes, select the Localize Currency Code Labels check box.
    By default, this check box is not selected. If you want to localize currency code labels on a server, you need to select this check box in only one of the localization package definitions on the server. Then, all currency code labels are localized.
  6. In the Deployable Applications section, click Add, and add the applications that you want to localize.
  7. In the Independent Forms section, click Add, and add any independent forms that you want to localize with the application.
  8. In the Panel Fields to Skip section, add the field IDs for the panel fields that should be skipped (along with their child fields) during the localization process.
    You might want to skip a panel field because you do not want to localize it, for example, for debugging purposes. You can enter IDs from 0 to 2147483647.
  9. In the View ID Range section, enter a start and end range for generating view IDs when the localization toolkit creates a new localized view.
    View IDs are created from the same ranges as field IDs. For a list of the ranges reserved for BMC, see Reserved field ranges.
    The range can be from 0 to 2,147,483,647. Enter a range that is outside of the reserved ranges and that is large enough to hold the view IDs of all views. If you enter 0 in the Start and End fields, the view ID will be generated in the unreserved range.
  10. Save and name the package.
    An XML file containing the configuration information is created in your root folder. For more information, see Setting a root folder.

    Anything that is done outside Developer Studio is not refreshed immediately in UI. If you add or remove definitions outside of Developer Studio, the changes do not automatically appear. To view the latest definitions, close all of the editors, right-click Localization Package Definitions in the AR System Navigator, and select Refresh.

Was this page helpful? Yes No Submitting... Thank you

Comments