Smartling job names now match the AEM translation project title
When you request a translation outside the Smartling dialog (for example, from the References panel), the connector now names the Smartling job after the AEM translation project. A project titled "Spring Campaign" creates a job named "Spring Campaign - 1234567890123". The connector appends a number to keep job names unique.

A new optional feature lets you control access to the connector’s Translate button through a dedicated permission. The connector introduces the permission smartling:translationButton, which only manages the visibility of the button. Users can still request translation through the Reference Panel. By default, the permission is set to allow on the path /content for the Smartling Project Owner group.
​

​How to use the feature
First, your AEM administrator must enable the feature in OSGi. It is off by default.

After that, an administrator can assign the permission to a specific user or group. For example:

In this example the Translate button will not be available for Experience and Products.
​

This feature works for Sites, DAM, Forms, and Page Editor UIs.

The connector has a new OSGi configuration option, Pseudo delivery Smartling locales. Here you can specify a list of Smartling locales for pseudo translation.
​

This option turns on the Pseudo translation option in the Smartling dialog if the set of target languages matches the list of languages in the OSGi configuration.
​

It only works if you haven't manually changed the Pseudo translation option.

Fixed an issue where the connector used a hyphen instead of an underscore in the Smartling namespace on AEM 6.5 LTS SP2 and newer, which could cause existing content to be treated as new and retranslated unnecessarily.

The connector shows a dialog with a message on every failed validation, meaning that when content is submitted for translation and there is nothing new to translate, it will block the translation request.
​

Also, the Smartling dialog prevents submitting content that is already up to date with the latest translations.
​

The connector resolves translation rules and property mappings the same way AEM does. It prioritizes specific-component property mappings over general/child-node mappings. See the notes below.

In the Translation Rules configuration UI (component / property editor): choose the value from the Parser dropdown — Auto, Html, Text, or Markdown. The UI saves the selected value.

In the property_mappings.json file (if you edit it directly): use the exact lowercase value — "auto", "html", "text", or "markdown".

Applies to pages, Experience Fragments (XFs), and Content Fragments (CFs) only.

Automatic resubmission only applies to content that was originally requested after this setting was enabled.

Introduced a new option for the Move strings setting. The Move strings dropdown replaces the deprecated checkbox and controls which strings are added to the requested job on each file upload. Three options are available:

Add to Job tab displays up to 100 jobs. This limit can be adjusted in the OSGi configuration.
​

User is now added to the smartling-projects-owners group as a project owner/observer when a workflow error occurs or the polling limit is exceeded during translation request processing.

The connector now uses an updated approach to preprocessing source XML files. The property mapping algorithm recreates XML nodes rather than renaming them, avoiding XML namespace validation entirely.

Fixed an issue where the connector was incorrectly detecting the AEM version when multiple products are installed on the same AEM instance.

It is now possible to select multiple Experience Fragments and create a translation request for them.

Smartling's AUTO parser option now detects and parses markdown.

When requesting context information for non-content entries (such as ASSETMETADATA, TAGMETADATA, or I18NDICTIOARY), no error is shown.

Connector does not check AEM content for XML errors.

Namespace resolution algorithm compares AEM and ISO 639 language codes regardless of whether a hyphen or underscore is used.

Upgraded Apache Commons Collections to version 4.4.

The connector now supports an instant translation option, allowing you to generate translations without creating a translation job or routing content through a translation workflow. Instead, content is translated immediately using Smartling’s Instant MT service. This option can be selected as a translation method.
​

The Instant Translation dialog was introduced to support this feature. It appears if the translation provider is set to smartling-instant in the Cloud configuration for the selected content.
​
​

The connector now supports the directive <characterLimit>none</characterLimit> for XML properties that should not inherit the character limit from a previous string in the file.

Fixed an issue related to saving property mappings.

A new Smartling workflow parameter, localeWorkflows, has been added. It stores associations between a Smartling targetLocale and a workflowUid, for example:

The specified workflow will be used for content sent for translation in the corresponding target language. For additional context, please see AEM Touch/Cloud Connectors Technical Resources.

When requesting additional locales for Experience Fragments, files are no longer duplicated.

Character limit feature now works with Auto parser option.

You can now set a character limit for a property mapping. We recommend using this feature with plain text strings. The limit will be shown to the translator/linguist working on the translation in the CAT Tool.
​

Alternatively, you can specify the limit in the property_mappings.json file. For example:

Several fixes have been implemented for the context feature. The connector now respects the language set for a language root and takes the language into account for resolving source content for taking context. The native context renderer composes proper URL for the context. This URL is then displayed in the Smartling dashboard within the Context tab of your AEM project.

Previously, ambiguous language mapping could cause the connector to generate an incorrect namespace for uploaded files. This issue has been resolved. The connector does not use language mappings for file namespaces.

Introduced context feature for Adaptive Forms.

Context for a page and an experience fragment can be taken from source page/fragment.
​

Multiple pages can be sent for translation. Users should open the Sites view, select several pages, and click the Translate button in the action bar. The Smartling Dialog will appear. There is only one difference from the usual Smartling Dialog shown in the page editor: users cannot manage subpages if several pages were selected.
​

Implemented support for Adaptive Forms.
​

Fixed the connector's validation for strings sent for translation. It now validates all strings for a text and/or for valid XML subnodes.

The connector now supports the Markdown content type. You can map a property to Markdown either through the Translation Rules UI or in the property_mappings.json file.
​

The connector now supports AEM 6.5 LTS.

The connector now matches properties to translation rules for nodes and all subnodes. Components in AEM may store their data in subnodes and descendant nodes in the repository. The AEM Translation framework matches translation rules not with the component itself, but with all subnodes. The connector can now match the Smartling parser in the same manner.

In the event of a rendering error, the context image will be taken from the repository.

The connector makes HTTP connections to Smartling with socket timeout set to 40000 milliseconds by default. If you experience errors related to SocketTimeoutException, you can adjust this value in the OSGi settings.
​

The connector waits until AEM has fully prepared a translation project. Once AEM completes this process, the connector overwrites the Auto * project options.

The connector can now work with the AEM Translation Framework's upload call, even when the source language parameter is not provided.

Auto option for Smartling parser was introduced in the Translation Rules UI.

Fixed missing MIME type for an asset retrieved directly from AEM for context.

Added check for existing locale mapping for the source locale in the Smartling Dialog.
​

The connector captures context directly from AEM in a native way using SlingRequestProcessor. This is the default behavior. To switch back to HTTP based rendering, use the option Use direct rendering in the Smartling - Context Preview Settings (Touch) OSGi config.
​

Smartling Dialog validates translation method and provider applied to the content.

If the user does not specify a parser, the connector will detect a Smartling parser (Text or HTML) for the property content. If the property string does not contain an HTML tag, &, or ", the connector assumes it is just text and not HTML.

The connector takes context from the target page/XF/DAM, not from the source. It ensures that the context matches the styles and JavaScript set for the target content.

Smartling credentials can be set in OSGi configuration. Credentials cannot be changed in UI in this case.
​

Fixed updating payload of workflow form on page editor.

Connector allows you to request a DAM folder and all its descendants. By default, it includes the folder’s children.
​

Pseudo translation default option was added to OSGi configuration Smartling - Dialog configuration (Touch)
​

AEM Translation Configuration UI correctly displays the Smartling parser for context with inherited rules.

Connector applies Smartling parser (HTML/Text) according to inheritance of translation rules context.

The validator for AEM-created XML files was updated to allow XML string as a property value.

Minor refactoring to fix AEM warnings. Changed the main package's type to container.

Connector checks translation rules for AEM components taking into account inheritance between them.

Connector trims whitespaces in Smartling job name and page/experience fragment title before initiating the translation flow. This ensures that registered AEM repository namespaces are not used as job or page names.

Context is taken from source content.

Connector uses the latest Smartling Java API.

Connector checks if the target content prepared (exists) for translation request.

AEM translation job Id was shortened to 12 alphanumeric symbols ([a-zA-Z0-9]). You will see a shorter file name in the Smartling dashboard.
Example: 62f1a6b0-eb31-4cb5-9ac5-c2b7b70b3a4e:/content/launches/2021/08/26/men2/content/we-retail/language-masters/de/men will be d4p56Lsew2m9:/content/launches/2021/08/26/men2/content/we-retail/language-masters/de/men

Pseudo option is added to Create Job in Smartling Dialog. If Pseudo translation checkbox is checked, connector will retrieve pseudo translation for the content.
​

Fixed reset of UI form after closing the dialog.

DOM mutation events are replaced with JS Observer.

Fixed language options set in the Smartling dialog for cases where the dialog is reopened on one Experience Fragment and then on another Experience Fragment later.

The Connector now trims any extra spaces that a user may accidentally add to their Smartling credentials while configuring the Connector.

A new OSGi option Custom Directives list was introduced. All the directives added to this configuration will be applied when translatable content is uploaded to Smartling.

A new OSGi Enable Legacy Config Validation option has been introduced. It allows you to disable or enable the validation of a legacy configuration applied for a page.
​

The Callback Host URL option has been replaced with a Callback URL option. Customers should specify the full callback URL, e.g. http://my-aem.host.com/services/smartling/sync-translation.
For backward compatibility, the previously specified option Callback Host URL is not shown, but exists internally and it is used if no Callback URL option has been specified.

Context is enabled for Author AEM instance only.

Updated Auto Authorize option in OSGi configuration. When enabled in OSGi configuration, it is enabled by default in the Smartling Translate dialog.

Fixed validators for proper processing of several assets or content fragments.

You can now configure AEM Translation project with automatic options.

Fixed bug with DITAMAP files.

Fixed bug with polling AEM when a translation project is created.

Siblings languages only option specified for Smartling - Page language copy manager (Touch) configuration works for assets too.

Fixed error for loading projects on non-content or service pages.

Improved security of the Callback.

Added support of web callbacks.

Added a toggle Only sibling language roots for narrowing a list of languages on Smartling dialog.
​

Smartling job locale validator checks locales available for the current page/XF/CF only.

You can now search by locale code in the Target Language field of the Translate dialog, as shown:
​

Connector installs a new security group Smartling Projects Owners. Every user assigned to the group gets Owner and Observer roles for every translation project created via Smartling Dialog.

The target language selector on the translation dialog now shows country and locale for each language option.
​

Fixed issues with a workflow for multiple translation projects created by AEM 6.4 SP4 for selected subpages.

Variants for i18n dictionary are now set from i18n-keys/property names.

Fixed permissions for overlay of the list of custom languages.

Fixed processing of blank text sent for translation.

AddedMove stringsoption to handle updates to translations
​

Translation project folder name is created properly from long page title.

Language selector shows languages in alphabetic order.

Fixed scroll of language selector showed many languages.

You can now include Job Custom Fields if enabled in Smartling and the connector's configuration

Fixed showing a validation failed message on the Smartling Dialog.

Metadata in images and documents (DAM assets) can be sent for translation.
​

You can now choose which Smartling project to send content for translation to.
​

Connector checks for new content in subpages. Excluded subpages are no longer checked for updates.

Fixed error on taking Smartling custom fields for a page without any language assigned.

A set of subpages can be configured for pages and Experience Fragment. CheckedInclude Sub-pagesoption shows additional buttonConfigureon Smartling dialog
​

Clicking on the button opens a dialog for selecting a particular subpages
​

Removed wrong information message about missed locale mappings for duplicate languages, e.g. [fr, de, fr, de, fr]

Fixed Force resubmission option for Content fragment translation request.

Smartling Job shows language display name provided by AEM instead of ISO 3166.

Fixed error in traversing over cycle of referenced content

Added new Smartling Dialog validator. The validator checks is there any updates on a content after the last translation.

Fixed bug with reconnect error in context connection. Test connection checks context for the whole multiconfiguration.

Fixed bug with unclosed HTTP client that loads context

AEM Touch Connector now supports the translation of attached Microsoft Office Documents

Fixed multi-configuration authentication for context upload

We added a new content upload configuration option in com.smartling.aem.connector.automation.impl.wcm.project.TranslationProjectResourceManager: polling.upload.complete="{Long}20"
It manages the waiting period of connector for upload in selected minutes: 10 mins is minimum, 20 mins is default, 30 mins is maximum. Your content will upload in this period after the translation request has started.

Fixed caching context connection with wrong user typed credentials.

Adjusted error message for missed service user mapping. We made OSGi configuration in a standard format. OSGi configs are applied for all modes: author and publish. We made a log to be written into standard error.log. We made indices to be merged upon deployment.

Removed unnecessary check for overridden language properties for a source root page

Improved search for a Smartling configuration

Fixed error message about missed language mapping

Introduced a hotfix for this AEM Cloud issue

Fixed processing bug when a custom field UID started with a digit

Property mapping configuration moved to /conf/global/settings/smartling/configuration/property_mappings.json.

Force resubmission option works for related assets on both AEM on-premise and AEM Cloud environments.

Fixed checking translation rules for inherited context.

Removed Log4j dependency from connector package.

Force resubmission option works for related assets. (AEM on-premise only)

WCMMODE for context preview is configurable

Fixed Smartling client library issue for missed dialog on a specific editor page, e.g. AEM template editor

Smartling Job name can now be found by name in Translation Dialog (AEM on-premise only)
​

Fixed the infinite loop for cloud configuration validation

Connector supports additional configuration for a particular AEM source locale

Now content creators can continue to write content in their native language, and this can be submitted for translation, once that language is configured as a secondary source language.

The secondary configuration should include the secondary source languages as an AEM locale code
​

Added an option to show locales without respecting Langauge Root properties.
​

Smartling Translation Dialog shows a short info about configuration is used for translation.
​

Locale of a page or experience fragment is built respecting site structure, e.g. /content/site/ch/fr/page is for French (Switzerland) locale.

Added index for cq:cloudservicename property of Smartling configuration

Connector no longer uses user repository session for the most cases

Fixed error when uploading tag metadata.

Fixed duplicate locales in language selector.

Fixed bug when using locale mappings for all Smartling API requests (upload content; checking translation status; deliver translations)

Connector shows Smartling custom fields in Smartling Translation Dialog. New OSGi configuration allows to add a list of custom fields names that should be shown on the dialog.
​

Connector is able to deliver Pseudo translation instantly. User should set up a locale where pseudo translation should be delivered in newly added OSGi configuration.

AEM Connector now polls AEM for created a translation project. New polling configuration is available in OSGi now.

Fixed warning about invalid Smartling service user mapping.

Closed unreleased resource resolver in Smartling Workflow Process.

Fixed translation search issue within a project. There are some rare cases when AEM asks for translation earlier than translation project is saved in repo. The connector waits until the translation is saved now.

Fixed locale mapping validation message

Made indexes to be lucene type

Introduced language properties support for a page.

Fixed issue to stop Connector from starting "Sync Translation WF" for a Job on AEM 6.4.8+

Introduced support of DITA files. AEM XML-Documentation plugin uses these type of content for translating a topic.

The force resubmission option is now selected by default.

Fixed failing Smartling workflow on creating a language copy of a root live copy.

Fixed failing Smartling workflow on creating a language copy inside non-orderable folder.

Fixed issue with locale codes containing underscores in the Smartling Job details page.

Added configuration for context timeouts

The Token secret field on Smartling configuration page is now empty by default, meaning the user must input the token for each update before saving.

There are cases when created language copy is a subpage of live copy. Fix causes connector to force detach from blueprint and to exclude subpage from the live copy.

Fixed validator for cloud configuration. The validator is successful if there was a configuration applied on a page directly and there was no target page created yet.

The AEM Touch Connector now detaches the language copy from the blueprint by default. You can revert to previous behavior (light end relationship) in new OSGi configuration Smartling - Live Copy Manager Settings (Touch)
​

You can now force the AEM Touch Connector to authorize all translations by setting Auto Authorize option in the new OSGi configuration Smartling - Smartling Facade (Touch)
​

Added a new OAK index for searching AEM translation project.

SVG images are skipped on upload without any errors.

No errors are logged for missed property mappings file.

Fixed locale selector in Smartling dialog for single/multiple selected payloads.

Fixed bug with empty language selector list for several selected Content Fragments.

Added a validator that compares Smartling configuration applied for source and target pages.

Made Smartling workflow model step Checking target locales to be auto-advanced.

Replaced using of suffix URL Sling segment for language selector suggestion with query parameter.

Fixed deploying of locale mappings for AEM Cloud. Added version for AEM Cloud package.

Added workaround for AEM fickle issue when translation job object may not contain MIME type for a file. The connector will use text/html MIME type for AEM translation job in this case

Fixed encoding for property mapping processing
Fixed user permissions for translation project

Fixed compatibility with AEM Cloud by replacing reflection on TranslationObject with JCR query solution

Added a sanitization of Translation Project name. Now names will contain only: letters, numbers, dash, underscore, and spaces.

Fixed displaying of validation errors on Smartling Translation dialog in AEM Cloud.

Improved Smartling parser configuration for components with multifield.

Language selector in Smartling dialog now supports languages with underscore/dash in language codes

Improved configuring permissions for a new AEM translation project. By default, the current user is configured as a project owner and observer, but if Smartling translation workflow is requested by another automation then this step is skipped

Update UI of Smartling Connector setting page

Fixed language selector component on Request Translation dialog for AEM Cloud

Fixed missed "Translation Configuration" options on Cloud Services page

Implemented Smartling Translation dialog for Experience Fragments

Fixed variations for uploaded properties

Fixed a typo in workflow model dialogs. The Process class is also now defined properly.

Fixed translation workflow model dialogs, which are now editable via Touch UI. The workflow model panel is also shown properly.

Added the special property Command endpoint heartbeat for Context Preview connections. Users can set the period in ms between keep-alive pings.

Command endpoint heartbeat is minimum 15000 ms and default 40000 ms.

Fixed loading of a resource with spaces in the path.

Fixed dialog rendering on pages with a missing resource.

You can now submit content fragments through the new Translate menu item.
​
​

Fixed the encoding that the connector uses for grabbing page HTML for context. If a server doesn't return encoding in Content-Encoding or Content-Type headers, it uses UTF-8.

Improved translated file upload. The connector will no longer send XML files with no translatable content.

Added protection in the "Smartling Translate as Job" workflow model for cases where the engine ran completed instances multiple times or ran the previous successful workflow step after a step failed.

Improved how the connector detects when AEM successfully creates and uploads projects. There should be fewer cases where files are uploaded but the job is unauthorized.

Improved the workflow step where the connector creates target language copies. If the original page is a live copy then new copies don't have a relationship with the blueprint.

Added validation that the parent page in a target folder exists and the connector can create a language copy there.

Fixed issue where a Smartling job was authorized even when not all AEM translation jobs were created. The translation workflow's polling of uploaded files is only for 20 minutes. After that, the job will be authorized for successfully uploaded files.

For how translation projects in 6.4 are created, we delegate the creation of AEM multi-language translation projects to translate content instead of doing it programmatically. Projects that were created via the "Translate as a Job" Smartling pop-up is now the same as those created through the AEM Reference panel. One project includes one-per-language job translation.

Changed automated launch promotion feature to disable by default. AEM in 6.4 provides a built-in automated promotion. The same Smartling functionality is disabled by default.

Fixed context issue. Context connection(s) was not automatically established due to the issue with getting a list of Smartling configurations.

Fixed getting Smartling configuration by page path.

Fixed Smartling UI styles: Translate as Job menu item

Added the new security group: projects-smartling-default-project-translationreviewer

Added the special property Command endpoint heartbeat for Context Preview connections. Users can set the period in ms between keep-alive pings.

Command endpoint heartbeat is minimum 15000 ms and default 40000 ms.

Fixed loading of a resource with spaces in the path.

Fixed dialog rendering on pages with a missing resource.

Fixed locale format check provided by Smartling using locale mapping.

Fixed removal of live relationships on the target translation resource.

Added property mappings for translated properties, which allows you to specify how Smartling should parse each property’s content.
​
​

The Test connection button now checks the context connection, which simplifies troubleshooting by letting you know when context is not configured.

We now prevent a stuck page in the workflow if one of the workflow steps has a validation error, or if no AEM translation project was created.

Resolved an issue where the connector was unable to upload all requested languages.

Fixed the encoding that the connector uses for grabbing page HTML for context. If a server doesn't return encoding in Content-Encoding or Content-Type headers, it uses UTF-8.

Improved translated file upload. The connector will no longer send XML files with no translatable content.

Added protection in the "Smartling Translate as Job" workflow model for cases where the engine ran completed instances multiple times or ran the previous successful workflow step after a step failed.

Improved how the connector detects when AEM successfully creates and uploads projects. There should be fewer cases where files are uploaded but the job is unauthorized.

Improved the workflow step where the connector creates target language copies. If the original page is a live copy then new copies don't have a relationship with the blueprint.

Added validation that the parent page in a target folder exists and the connector can create a language copy there.

Added capability to configure Custom Placeholder.
​

Improved the behavior for when something went wrong while creating jobs for translation via AEM. Now, the connector waits 20 minutes for the new job, and if all AEM translation jobs aren't created, then an error is written to the log summarizing what was and wasn't created.

Fixed the behavior of the Force resubmission (Required if page is unchanged) option when Include all Sub-pages is also checked.
​

Fixed page submission in Smartling popup. (Previously, the page could be submitted regardless of validator status. Now, the connector allows page submission only if all validators have no errors.)

Fixed resetting validation errors icon on the Smartling popup when it's opened multiple times. Validation error icons are cleared when the Smartling popup is reopened, or when a user switches between the Create Job and Add to Job tabs.

Sync a label text on the submit button when user switches between Create Job and Add to Job tabs.

Fixed issue with Smartling namespaces for Content Fragments. When you update original content and resubmit it to Smartling, AEM generates unique file names. The connector uses the same namespace in order to share strings of the same asset in different files.

Fixed length of auto-generated Smartling job name (when you submit pages via References panel instead of Smartling popup). Previously, it could be too long and was rejected by Smartling.

Added the new validator to the Smartling pop up that validates that the checkbox Auto-execute is set in the Translation Integration configuration.
​

Implemented a workaround for the inconsistency bug in AEM. You may notice this bug when you submit a brand new page for translation, but sometimes it doesn't appear in Smartling. If you check your AEM projects, then you may see that a submitted page is present in a randomly generated translation project instead of a project that was passed to an AEM translation framework. In a nutshell, the Touch connector creates non-existing language copies before asking AEM to translate pages. It's done by the new step in the Smartling workflow. If you want to revert this improvement, then you can just remove the workflow step.
​

Improved package installation behavior for customized language mapping. Previously, if you installed a new version of the AEM Touch Connector, it would overwrite your custom language mapping. With this new version, the connector will try to merge your custom language mapping with the default language mapping.

Added workaround for the issue when AEM tried to re-execute a completed translation workflow instance, more specifically when components such as ExternalProcessJob* are restarted. For unknown reasons, AEM took all instances of the workflow steps that implement WorkflowExternalProcess interface and tried to re-execute them. As a result, the Smartling workflow steps tried to resubmit pages. The connector now tries to detect multiple incorrect executions and do nothing with adding them into the log. Example: wfStep="Send Page for Translation" has been already executed.

You can now you can use https in context configuration.
​

Added a new option which allows resubmission of original page to Smartling, even if it was not modified. By default, the AEM translations framework does not allow this.
​

Attach files to Smartling jobs when submitting pages from the References panel. It's not recommended to use the References panel, but if you have to submit pages, then the Touch connector will take care of it, and will create a Smartling job with the attached files.
​

Improved stability of Automated Launch Promotion. (Previously, it would try to promote the same launch twice when it received multiple concurrent events from AEM.)

Restored functionality of notifying user as soon as upload is completed or failed. The connector creates task in the inbox.
​

Connector now always uses TLS1.2 for HTTPS connections regardless of Java version. (It was TLS1.0 for Java 7.)

Improved error handling edge case when AEM translation project is created and configured but then the Smartling configuration gets deleted.

Removed Adobe Consulting Services as it brings several dependencies that can't be satisfied in a variety of AEM instances.

Fixed validation for target locales. Previously, target locale validation was case sensitive, so if a page was submitted for 'de_DE locale' and language mapping was configured for 'de_de locale', validation would fail.

Added possibility for providing callback URI.
​

Enabled Launch Promotion by default.
​

Extended parse JSON configuration by providing possibility to add fields that will be sent to Smartling along with 'smartling.translate_paths' directive.
​

Added test connection button, so the user can test whether the provided credentials are suitable for configuration.
​

Added validation within the submitting page, so now the error is shown right after the submission.
​

Added inbox notifications. From now on, you will receive an email notification when a request is completed. The notification will either contain a link to a Smartling job, or a reason as to why the submission request failed. For example, if all locales are filtered in the initial step due to the fact that the appropriate language copies are up to date, or missing language mapping configurations, then you will see an error. In screenshot below, the results of three submissions are shown: one successful, and two with errors (see from bottom to top).
​

Fixed issue with missing folder title. When you a submit page for translation, the Touch connector creates folders for storing AEM translation projects. Before, these folders didn't have a title.

Fixed issue with how connector detects that the translated page is up to date and should not be submitted to Smartling. Fixed comparison source page, last modified date, and language copy last modified dates.

Modernized flow in order not to create AEM translation project for up to date language copies. If nothing has changed in a source page, content shouldn't be submitted and project shouldn't be created for those locales, for which content has been sent.

Extended String Duplicates processor in order to allow user to configure name space that is sent along with the file. When Use legacy namespaces is checked, strings will be shared across files on the same page, otherwise, content for each language will be uploaded as a unique string.
​

Integration was migrated from Jobs API v2 to v3.
Pages now can be attached to existing job in any state (Awaiting Authorization, In Progress, Completed).

Job may contain files that are authorized for different locales.

Authorize job checkbox in the New Job dialog is now unchecked by default.

Translation Job Support: Allows submitting of pages even if they were not modified after the last translation.

Automation: Fixed an issue that caused pages to be deleted when a launch is promoted.

Got rid of the deprecated API usage: All background operations are performed on behalf of smartling-touch-connector user instead of admin. To achieve this, a new service user is created with ID smartling-touch-connector. This user is granted Read-Write access to /content and Read access to /etc (as well as, Read-Write access to the connector's internal folders, under /apps and /etc).

Fixed issues with HTTP proxy support

Fixed issue with submitting content when the target locale is disabled in Smartling.

The connector now uses Smartling API v2 and is not backwards compatible with earlier versions. After installing you must create v2 credentials and add them to each Cloud Configuration.

Improved context capture performance.

Fixed issue with missing context on some configurations of AEM.

A separate log file smartling.touch.log has been created to capture all the log messages coming from the Connector.

Improved performance of the connector under heavy loads.

Due date on a translation job is not supported even if set on the AEM side.

Reject translation from AEM is not fully supported: once translation is rejected in AEM, the only option is to cancel all the translation job manually, wait until translation is corrected and request translation once again as a new job in AEM.

Added the ability to configure an HTTP proxy in a single place to be used by the connector - via Felix OSGi Console, Smartling - Network Settings configuration entry.

Support anonymous proxy configuration via Java System properties.

Fixes to translation context to improve quality and make troubleshooting easier.

Improved string sharing behavior for the case where multiple versions of the same page are being translated at the same time. As of the version 2.0.0 strings have been shared within a page, but if the page was copied into one or more launches then strings in these copies were considered completely different. As of 2.1.0, strings are shared among the page and all its versions in different launches.

The connector package has been renamed from “Smartling Translation Connector” to the “Smartling-Translation-Connector”. We recommend to manually remove the old package after installation.

Identical strings on different pages are treated as unique strings in Smartling.

If a page was submitted more than once as part of different Jobs, Smartling continues to share translations along all copies of the page.

Users can now control how Smartling should treat identical strings on the same page. Duplicates can be ingested as a single string or as unique strings. This feature is disabled by default but can be enabled from the Configuration Console.
​