Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Localization wizard

Updated on April 5, 2022

Use the Localization wizard to make an application available in additional languages. The wizard automates many of the steps necessary to create language-specific rulesets.

The Localization wizard identifies field values and text strings that are used in your application ruleset user interface rules. However, the wizard might not detect rules that were created by unique application configurations. Some manual translation might be required for complex applications.

To track the status of translation work, the wizard creates a work item with the prefix PXL-.

The Localization wizard has three functions, which you access from Dev Studio by clicking ConfigureUser InterfaceApplication readinessLocalization :

  • Translate to New Language – Create a translation package, which is a .zip file that contains the values that are to be translated. A translator translates the package and returns the updated package to you.
  • Translations in Progress – List the translation projects that are still in progress, and optionally import a translated package.
  • Locale Settings – Change the locale for the current session so that you can test the translated package.

Translation package

The language translation package that is created by the Localization wizard includes the following files:

  • A TextToTranslate.xml file, which is the translator's worksheet. The Localization wizard import process uses the translated content of this file for updating field values.
  • A .htm file, which contains instructions for the translator.
  • A folder for each correspondence, correspondence fragment, and HTML paragraph rule that contains HTML text. The text is located and translated in a pair of .txt files within each folder. The .xml file contains hypertext links to the text files.
  • Folders that contain graphics and HTML, which provide context examples for the translator.

When you make updates to the translation package, always extract the .zip file contents first. Do not work directly inside the .zip file.

Translated HTML paragraphs and correspondence

The text that is used in HTML paragraphs, correspondences, and correspondence fragment rules is packaged in a pair of .txt files called Base.html and Translation.html. Both files initially contain the same text. The translator edits the Translation.html file to contain the translated text. HTML paragraphs are imported into the localized ruleset like normal text strings.

A localized application sends correspondence in the language of the recipient, rather than the language of the sender. Typically, these correspondence rules use circumstanced properties rather than a ruleset to identify the locale. After the translator updates the Translation.html files, you manually update the circumstanced correspondence rules by copying the translated text from the Translation.html files.

  • Internationalization and localization

    A single Pega Platform application can support users who work in different countries and time zones and who speak different languages.

  • Localizing your application

    Localize your application so that users can work in their preferred language. During the localization process, the text in field values is translated into the language that you specify and is imported into Pega Platform.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us