Using AEM translation workflow to localize adaptive forms and document of record using-aem-translation-workflow-to-localize-adaptive-forms-and-document-of-record

Adobe recommends using the modern and extensible data capture Core Componentsfor creating new Adaptive Formsor adding Adaptive Forms to AEM Sites pages. These components represent a significant advancement in Adaptive Forms creation, ensuring impressive user experiences. This article describes older approach to author Adaptive Forms using foundation components.

Localized forms help you serve a wider audience across geographies. Adobe Experience Manager translation workflow helps you localize adaptive forms and their documents of record . You can use machine translation or human translators to localize an adaptive form.

This article explains the process to use AEM translation workflow with adaptive forms and documents of record.

Localizing an adaptive form and document of record using machine translation localizing-an-adaptive-form-and-document-of-record-using-machine-translation

The machine translation service immediately translates your content in adaptive form and document of record. AEM Forms is pre-configured to use a trial version of Microsoft Translator for machine translation. Perform the following steps to enable machine translation for your adaptive forms and document of record:

  1. On the AEM Forms UI, select a form, and select the Add Dictionary option.

  2. In Add Dictionary to Translation Project screen, select the Create a new translation project or Add to an existing translation project option.

  3. In the Project Title field, specify the title. For example, Government Reference Site - German locale.

  4. In the Target Languages field, specify a locale (For example, German(de)), and click Done. You can specify multiple locales. The form is translated to all the locales specified in the Target Languages field.

  5. In the Dictionary Added dialog box, click Open Projects. In the Projects screen, open the newly created project.

  6. Click the ellipses at the bottom of the Translation Summary tile. The Translation Summary screen opens.

  7. Click the Edit icon at the top of the Translation Summary screen. Open the Translation tab and select Machine Translation in the Translation Method screen. Select the appropriate Translation Provider and Cloud Configuration. Click the Done icon at the top of the screen.

  8. On the Translation Job tile, click the aem62forms_downarrow icon, and click Start. The status of the tile changes to Draft. On completion of the translation, the status changes to Ready for review. Refresh the page after a few minutes and verify the status.

  9. After the status changes to Ready for review on the Translation Job tile, open the form in a browser window. A localized version of the form is displayed.

    note note
    • Before opening the localized version of form in the browser window, ensure that the locale of the browser is set to match the locale of the form. For example, if the form is translated to German(de) language then set the locale of the browser to German(de).
    • Adaptive form components do not support right to left (RTL) languages. For example, Hebrew.

    Along with the Adaptive form, the auto-generated document of record is also localized.

    For more information on Document of Record settings and configuration, see:

    Document of Record Template Configuration

    Document of Record settings

  10. Customize the branding information of the document of record and ensure that the browser locale is set to the same language to which you have localized the Adaptive Form using machine language. The browser locale helps localize the branding information in the document of record.

  11. To view the localized document of record, select Generate Preview. The document of record PDF is generated and opened in a new tab in your browser.

Localizing an adaptive form and its document of record using Human Translation localizing-an-adaptive-form-and-its-document-of-record-using-human-translation

In Human translation the content is sent to a translation provider and translated by professional translators. When complete, the translated content is returned and imported into AEM. When your translation provider is integrated with AEM, content is automatically sent between AEM and the translation provider.

For translation, a dictionary containing files in XLIFF format is shared with the professional translators. The dictionary includes a separate XLIFF file for each locale. Each XLIFF file contains text that will be displayed to the end users and placeholders for the corresponding localized text.

Perform the following steps to localize a form and its document of record using Human Translators:

  1. Connect AEM with your translation service provider and create translation integration framework configurations.

  2. Associate the pages of your language master with the translation service and framework configurations.

  3. Identify the type of content to translate.

  4. Prepare the content for translation by authoring the language master and creating the root pages of language copies.

  5. Create translation projects to gather the content to translate and to prepare the translation process.

  6. Use the translation projects to manage the content translation process.

  • Adaptive form components do not support right to left (RTL) languages. For example, Hebrew.