AEM Touch | AEM Cloud Connector

Translating with the AEM Cloud Connector

The Smartling Adobe Experience Manager (AEM) Cloud Connector allows you to translate AEM content with context. Translations are requested from within AEM, and translated content is automatically sent back to your environment.

The AEM Cloud Connector supports the translation of pages, Content Fragments, Experience Fragments, i18n dictionaries, and tags via AEM Translation Projects.

i18n can be translated only by manual uploading (drag & drop)

Request Translations

Once you have installed and configured the AEM Cloud Connector, you can begin submitting content to Smartling for translation.

In the AEM Cloud Page Editor, the Smartling: Translate as Job menu item will allow you to submit the current page and child pages for translation.

Translate Pages

  1. From the Sites view, open the page for translation in the AEM Cloud Page Editor by selecting it and clicking Edit.
  2. Select Smartling: Translate as Job from the Page Information menu to bring up the Smartling - Translate dialog.
  3. Type in a Job Name for this submission and select a Due Date for translation, if applicable, or select an existing job to add this submission from the Add to Job tab.

    • Check Authorize Job if you'd like to authorize the content for translation automatically.
    • Check Include all Sub-pages to include all of the current pages' sub-pages in the submission.
    • Check Force resubmission (Required if page is unchanged).
    • Select the languages to translate in this submission.

If your page contains Content Fragments and/or Experience Fragments, they will automatically be included in the page translation job. Occasionally, you may want to translate Content Fragments and Experience Fragments exclusively.

Translate Content Fragments

  • Go to your Content Fragments in AEM
  • Select the Content Fragments for translation
  • Click the 3 dots on the top panel > Translate


  • This will open the Smartling - Translate dialog 
  • Complete the fields and click Add to job
    • As content fragments do not contain sub-pages, the "Include all sub-pages" checkbox is removed from the Smartling - Translate dialog.


Translate Experience Fragments

  • Go to your Experience Fragments in AEM
  • Navigate through the source folders to Experience Fragments
  • Click the 3 dots on the top panel > Translate


  • This will open the Smartling - Translate dialog 
  • Complete the fields
    • If your Experience Fragments contains variants that you want to include for translation, select the "Include all sub-pages" checkbox
  • click Add to job.

Translate Content in Bulk

The Include all Sub-pages option in the Smartling - Translate window allows bulk submission of a page and all of its sub-pages.

Not seeing all of your page content available for translation in Smartling? Check that all of the relevant Properties are included for translation in Tools > General > Translation Configuration for the context path being submitted in AEM.

Resubmit Options

The Force resubmission (Required if page is unchanged) option in the Smartling - Translate window allows you to submit an original page to Smartling even if there are no changes after the last submission. By default, AEM doesn't submit such pages, but if for some reason you need to resubmit an original page, you can enable this option and the Smartling connector will make AEM think that the original page was modified, and should be submitted for translation.

Include Visual Context with your Translation Request

A Visual Context capture tool is built into the AEM Cloud Connector, helping linguists get your translations right the first time - reducing translation cost and time to market.

If Visual Context is not displaying properly in Smartling, your AEM Administrator should check the Smartling settings in AEM's Web Console Configuration page, or enable a Proxy Connection in Smartling - Network Settings

Check the Status of Translations

The Smartling Connector creates a smartling-auto Project folder in AEM, with subfolders for each date content is submitted. To check the status of a Job, go to the corresponding folder within the smartling-auto Project and open the Translation Project. Click the ellipses on the Job to view the contents and State of each page in the Job.  For more detailed translation progress information, check the Job status in the Smartling Dashboard.

Check Translation Status More Frequently - Configuration

By default, the AEM Translation Framework checks translation progress once per day, but you can set it to check more frequently in the AEM configuration. 

Add the following OSGi configuration file to your AEM customization project with required values

File name - com.adobe.cq.wcm.translation.impl.TranslationPlatformConfigurationImpl.config:

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling=""

          xmlns:jcr="" jcr:primaryType="sling:OsgiConfig"

          syncTranslationState.schedulingFormat="0 0 1 1/1 * ? *"

          schedulingRepeatTranslation.schedulingFormat="0 0 0/1 1/1 * ? *"


          export.format="xml" />

`syncTranslationState.schedulingFormat` is responsible for check AEM translation projects periodically.

Download Translations

AEM will download translations automatically after all the content in the Translation Project is published in Smartling. There may be a delay after content has been translated as the download process runs in accordance with the Scheduler Cron (once per day). The AEM Cloud interface does not allow for manual download of translations from Smartling.

Handle Updates to AEM Content

The AEM Connector does not automatically resubmit pages with updates. To resubmit a page with updates, use Smartling: Translate as Job once again to submit the page and create a new job. Only new strings that were not previously submitted will be added to the new job.
When a page is resubmitted for translation, AEM creates a launch for the language copy. When translations have been downloaded, they are applied to the launch, then AEM promotes the launch to the language copy.

Handle Updates to Translations

You can make the updates to translations in Smartling, then use the Force resubmission (Required if page is unchanged) option to create a new AEM Translation Project to pull back updated translations.

Request Translations by References Panel

Smartling does not recommend using the default AEM submission flow via the References panel, nor manually creating translation projects.

When you submit pages via the References panel, the Smartling connector will do the following:

  • Create a Smartling job with a name that consists of the current date, page path, and unique identifier.
  • Attach uploaded file to the job above.
  • Job will not be authorized automatically. You can decide when to authorize the job as needed.

Additional Notes

  • A Smartling job is created for every AEM project. For example, you might submit a page for three languages. AEM will then create three translation projects (one per language), and in turn, the Smartling connector will create three jobs.
  • All pages that are added to the same AEM project will be attached to the same Smartling job. For example, if you submitted "pageA" for "French", it will be added to the Smartling job "2018-01-01 - pageA - 1". Later on, if you submitted "pageB" also for "French", and used the existing AEM translation project, then "pageB" will be attached to the Smartling job "2018-01-01 - pageA - 1"
  • Smartling jobs are not authorized automatically.

How to troubleshoot if the title is not translated

Although you may have submitted a page and translated all content, including the title of the page, ("jcr:title" property), you may notice that the title didn't translate properly. This is because the Smartling Touch connector is responsible for submitting original content to the TMS and it pulls translations back. However, applying translations to page properties is handled by AEM.

For example, you wish to translate three properties: title, description, and alias. 



  • Go to CRX DE and browse to the /libs/msm/launches/rolloutconfigs/launch/contentUpdate node.
  • Open Package Manager
  • Create a package contained filter for /libs/msm/launches/rolloutconfigs/launch/contentUpdate 
  • Build and download the package
  • Extract package content into `ui.apps` module of  your AEM customization project
  • Replace:
  • Replace:
  • Add filter for a new content 
  • Update `ui.apps`’s structure module

So, `contentUpdate` action for launches will be overlaid and deployed with your AEM customization project.

How to Translate Component Strings (i18n dictionaries)

The translation of component strings, such as i18n dictionaries, is not supported in AEM Cloud in usual way because they are resided in immutable part of AEM repository under /apps. For this reason, it is recommended to uncheck the Translate Component Strings option:


How to exclude certain strings from a file

When a single page is submitted, the Smartling connector may upload more than one file. This is a result of tags/dictionaries/assets being included. If you wish to exclude these types of strings from files such as these:


The type of translatable content and scope should be configured for the AEM translation framework.

Go to Tools > Cloud Configuration - Translation Configuration and adjust your settings.




For more details, consult Adobe AEM documentation.

Was this article helpful?