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.

Enabling records

Updated on April 5, 2022

If your original installation of Pega Platform was before Pega 7 and you have never translated it, you can enable the Localize setting for each record in an unlocked ruleset so that the rule can be translated. Although records in Pega Platform are set by default to be translatable, older rules might not be.

If you did not select an unlocked ruleset in the Select Rulesets topic, this option is not available and you can proceed to the next topic.

  1. Click Enable records for translation to update the Localize setting for the selected records.

    Result: A report displays the results of the enablement process.
    • Successfully enabled – Number of records that are now ready for translation export.
    • Already enabled – Number of records that were already prepared for translation.
    • Errors while enabling – Number of errors encountered during the enablement process.
  2. If errors are listed, click a row to open the associated rule form in Dev Studio.

  3. Click Next.

  • Selecting application rulesets

    Specify one or more unlocked application rulesets and versions that contain field value rules that you want to translate. The field value rules are used to display application elements such as user forms and portal displays.

  • Downloading the translation package

    Create a compressed translation package for each language and save it to a local directory so that you can send it to a translator. The package includes an XML file that contains the text strings and other files that the translator needs.

  • Localization wizard

    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.

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