Trados Enterprise

On the Trados Cloud side

The Trados Cloud configuration requires a Trados Administrator.

On Trados Enterprise, Trados Accelerate, and Trados Team, depending on your integration, an integration application must be set up for Localyzer to connect.

Integration Application

The Administrator on the Trados Side must set up

• a Service User: under the Users > Service Users tab
• an Application: Navigate from the account drop down in the upper right corner to Integration, then Application
  • for the Webhook, use the CommandCenter URL and a Command Center API User/token in this fashion:
  • https://<URL>/command-center/callback/tradoscallback?apiusername=<API_USER>&apitoken=<TOKEN>

Gather the following information:

• Client ID: see the Integration Application > API Access
• Client Secret: see the Integration Application > API Access
• Tenant ID: Navigate to Manage Account from the Account drop down, use Trados Account ID
• Template ID: See the last 24 numbers of the URL when clicking on the template name in Trados Enterprise/Accelerate/Team, in Resources/Project Templates.

These may need to be gathered by a Trados Administrator, who is likely not a Command Center administrator.

Workflow Configuration

The correct configuration for the integration to be able to communicate the requests requires to:

• Enable Final Check stage in the workflow, and have a user/group assigned (user will need to manually action/complete this task)
• Enable File Delivery stage
• Enable Hold for Feedback stage in the workflow, assign this stage to a Group that contains the connector service user
• Ensure the Hold for Feedback stage retains its default outcome: "Send to Final Check"

Localyzer expects the Trados Webhook (set up in the Application section above) to push a PROJECT.TASK.CREATED event with the following key:

• "key": "final-check"

For those files that are moved back into the workflow for Final Check stage (either because of import errors or a re-import), then the 'final-check' task will be created again triggering the 'PROJECT.TASK.CREATED event.

Special Handling

Comments

1. Comments should not be translated. Some comments are specific to Localyzer, such as the top comments in a file. To prevent comments from being translated, navigate to Resources > File Type Configuration and the Configuration used by the template. Click on the file type of interest. In the example below, we use Java Resources, i.e. properties. Make sure the 'Translate Comments' checkbox is unchecked:

2. View Comments in the right hand side In general, to see the comments and the context in Trados Online Editor, click on the Show Document Structure Outline button on the right hand side:

3. By default, the raw file can be shown in the Preview window. This feature can be useful to check the comments and file structure directly in the Editor view.

The Preview window can also be configured to show a context captured on the Localyzer side. In that case, the Preview will show the screen where the string to be translated was captured.

Parameters

Nake sure that parameters are not translated on the resources. The filtering for parameters can vary for different projects. The template should use the appropriate file type. As for Comments above, the Resources > File type configuration may need to be configured.

In the example above, a minor change is made to the {userName} parameter: it does not keep the casing and changes it to {username}. This change is an error. The file type needs to identify {someparametername} and preserve it exactly.

JSON Files

Localyzer sends JSON files with comments: comments are indicated by key/value pairs where keys start with _ (underscore).

If JSON files those types of comments cannot be parsed, Localyzer can send instead .properties files with # comments, as shown in the project above.

Note on Online Editor

Localyzer will create a new project in the Trados Cloud product. The files to be translated into a target locale may need to be assigned to a linguist.

The linguist should be able to open the file in Online Editor, and Accept to translate, translate/verify the MT/AI translation, and 'Complete' the task. For each file, that will send a Webhook call with a final-check event. See below the Webhook section.

On the Command Center side

Once the above is set,

• navigate to General Settings,
• put the system in Maintenance Mode,
• Click on to the Translation Management Systems and Machine Translation tile
• Select the Trados tile of choice

Information from the Trados Side

• API User: This user must be first created on the Command Center side

• Client ID: Provide by the Trados Administrator (See above)
• Secret Key: Provide by the Trados Administrator (See above)
• Tenant ID: Provide by the Trados Administrator (See above)

Template

Enter which template to use:

• Template ID: Provide by the Trados Administrator (See above)

• Non supported file type: JSON is supported by Trados products. However, you may want to send JSON files are properties depending on the configuration of the filters on the Trados side
• Import Schedule: enter how often to check for imports. For instance, to check every 2 hours, enter 2. Left blank, checking for imports will be done only manually from a project's Localyzer page or from the TMS Configuration
• Callback URL: This is for information only, and to make sure that the configuration set up by the Trados Administrator does match (see above)

Context Server

Enter which Context Server to use. This step only matters if you are using InContext See: About InContext Translation

Locales and Locale Codes

By default, the list of locales are those supported by Trados at large. Some templates only allow certain locales, so you may want to match the template locales and the locales of this configuration. This is not necessary. If a Localyzer project locale is not part of the Trados Template locales, Localyzer will show an error.

Name your connection

Save your configuration. This configuration can now be used for Localyzer projects.

Webhook check

In the System Log, files can be downloaded only when the Webhook calls into Localyzer with a final-check event. Once a translation has been completed in the Trados Online Editor, the log should show:

Payload: {"eventId":"677d44c8f89ce7776300fed3","accountId":"6759daa43fc4433cadd2211c","data":{"taskType":{"automatic":false,"id":"676096321d5fb27e3bc8f07e","key":"final-check"},"project":{"id":"677d4426a764526e3797d090"},"assignees":[{"type":"user","user":{"id":"6759daaf1d6799656c114924"},"vendorOrderTemplate":null,"group":null}],"location":{"id":"b7847b146c2148b988eac9a8db87fec1"},"id":"677d44c8378bc2451a6dbf96","dueBy":"2025-01-09T15:11:32.379Z","status":"created"},"eventType":"PROJECT.TASK.UPDATED","version":"1.0","timestamp":"2025-01-07T15:14:16.645765051Z"}

Getting events like the above means that Localyzer is download the associated file and if all the files for a target locale are translated and downloaded, the import process can proceed.