Localization of custom report templates

Report templates can be localized, so that translated into other languages by directly translating all actual text in the report template and then saving the report template with a different name – for example, DocumentReport_DK for the report in Danish and DocumentReport_US for the same report in English.

The localized reports are later referenced in the Report JSON file to differentiate between the languages.

Additionally, based on the Accept-Language header value or the WorkZone Content Server language setting, the generated XML model is localized as well, and this can be seen from the model's node names and default text inside Content Controls on the report template files (.docx or.xlsx).

Tip: It is advisable to create the original report first, update the Report JSON file, and verify that the report is correctly deployed and displayed in WorkZone Client before creating translated versions of the report. You will still have to update the Report JSON file for every translated report you create.

Localizing content controls

Do not translate the placeholder text in the content controls, as the placeholder texts will be overwritten when the report is run.