Skip to main content
Matrix42 Self-Service Help Center

Localizing Configuration Packages

Learn how the resources introduced by the Configuration Package can be localized to supported Languages.


The article explains how the resources introduced by the Configuration Package can be localized to supported Languages.


The default DWP installation has all provided resources already localized to all supported languages. Adding non-localized resources to this Environment, either manually, via User Defined Localization, or by Package installation, could be easily detected in the Administration Localization area


Install the Configuration Package on a clean DWP environment

  1. Install the DWP from scratch
  2. Install the Configuration Package

Export not-localized Resources

  1. Proceed to Administration → User Interface → Localization  Management Area;
  2. In the View Options, select columns with the Target Languages;
  3. Filter Grid to display strings with no translations;
  4. Run Search;
  5. Click Export All to export results to Excel file:


Translate the Localization Strings

  1. Open the exported Excel file and make sure that all accumulated Strings are related to the Configuration Package. Remove those which have no relation to the Package.
  2. Translate the Localization String on your own or send it to Translation Agency.

Import Translations 

  1. Proceed to the UUX Administration Home page and start the "Configuration Recording";
  2. Follow back to  Administration → User Interface → Localization Management Area and start action "Import localization";
  3. In the wizard provide the excel file with the translations and select the target language, preview the detected changes and submit the wizard;
  4. Repeat the import for each additional language you would like to apply.

Update the Configuration Package with localizations

  1. On the Administration Home page run "Download Recorded Changes";
  2. Migrate the Schema Scripts with localizations from the generated archive to the Install folder of the Configuration Package;
  3. Add references to added Schema Scripts to the Package install.xml file;
  4. Generate a new version of the Configuration Package.


For further information, see also Solution Builder Development Process page.