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.

Localizing your application

Updated on April 5, 2022

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.

Text that can be localized includes labels, captions, tooltips, and instructions that are displayed in user-facing rules such as harnesses, sections, flow actions, messages, and portals. The HTML text that is used in HTML paragraphs, correspondences, and fragments can also be localized.

  • Preparing your application for translation

    Before you use the Localization wizard, complete the following steps to ensure that your application is up to date.

  • Creating a translation package

    Create a translation package that lists the fields and values to be translated. You send this package to a translator, who returns it to you with the translated values.

  • Preparing a translation package for a translator

    Before sending the translation package to a translator, review the TextToTranslate.xml file to ensure that the package contains the correct field values.

  • Importing translations

    After the translator has updated the translation package with the translated values, import the translation package into your system.

  • Testing the translation package

    After you import a translation package, test your application with the new locale to ensure that the translated values are accurate and visually accessible.

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