System settings / Export and import localized business solutions

Export and import localized business solutions

You can localize components and resources of a developed business solution. This allows it to be installed in a company where users operate in a language different from the original language of the solution.  

начало внимание

To localize a solution, apply translations, and use it in a company, enable the configuration translation feature in the system. To activate this feature, contact BRIX technical support.

конец внимание

Translate a business solution

Localizing business solutions follows the same process as translating a custom configuration. For each workspace and module within the solution, generate a resource file, translate it using a third-party tool, and then upload the file back into the system.  

Translation of solution components can be prepared by:  

  • The developer company before exporting the solution — translations are included in the export and applied automatically after import.  
  • The foreign-language company after importing the solution — the installed solution interface will be in the original language until translations are uploaded.  

Add translations after updating a solution

When a new version of the solution is released, translations must be prepared for any added components, fields, etc. This can be done by the developer company after making changes or by the foreign-language company after updating the solution.  

To add new translations while preserving existing ones, regenerate the resource files, translate the new strings, and replace the translation files in the system.  

Export a localized solution

Transferring a localized solution to a foreign-language company differs from the standard export process. If the original language of the workspaces included into the solution does not match the language of the importing company, the settings of those workspaces will be inaccessible. To prevent this, change the language of the workspace before exporting.

For example, you developed a solution in English and are preparing to install it in a German-language company:  

  1. Ensure your company has German interface language available by adding a Language package module.
     
    When preparing the solution for export, change the language of its workspaces to German. Their settings will become temporarily inaccessible. To regain access and restore the original language after export, temporarily switch your interface language.  
  2. Prepare translations for workspaces and modules if your company is handling localization.  
  3. Navigate to the settings of each workspace included in the solution and change its language to German.
     
    Workspace settings will be temporarily unavailable because the administrator's language must match the language of this workspace to edit it.
     
    If you export a solution with a changed language, the administrator will be able to configure workspaces and the components included in them in a foreign-language company after import. For example, set access to apps and add users to groups.
  4. Export the solution to an .e365 file.
  5. Provide the file to the administrator of the foreign-language company.
  6. To restore access to workspace settings in your company, revert their language to the original developer language by switching your interface language to German and then setting each workspace back to English.  

Import a localized solution

начало внимание

If you use BRIX On-Premises, disable user and workspace language comparison for proper translation of solutions by contacting BRIX technical support.

конец внимание

To install the solution in a company:  

  1. Import the solution. If translations were prepared by the developer company, they will be applied automatically.  
  2. Prepare translations for workspaces and modules if the solution is not localized. You can also refine existing translations by downloading, editing, and re-uploading resource files.  
  3. Unlock the solution if you plan to adapt it to your needs: extend app forms, add steps to business processes, or configure modules. Unlocking is also required to edit or upload translations for modules.  

Once completed, administrators can configure the solution, and employees can use its features.