Before you start, you should check that you have a workflow template that will work in your project (i.e. the content groups in the project exactly match the track names in the workflow).

Without a valid workflow, no translation job can be created. Therefore, you will need to provide a workflow during this process in order to create the jobs from the translated XML files.

NOTE:
It is important to make sure that the workflow track names match the names of the existing content groups (the names are case sensitive). Check your master document if you are unsure.

Click 'Project > Translation > Import Translations' to start the process.

The 'Import Translations' window is where you will do the importing and setting up of the translation jobs.

1. You will be able to name your version documents in this column.
2. Any translation content groups in the project are listed as columns into which the appropriate translated XML files will be placed.
3. The workflow column is where you will assign your workflow template to any created translation jobs.
4. The checkmark column gives you the option to automatically start the workflows upon creation of the jobs.

Click the 'Upload Translations' window to select and upload your translated XML files.

NOTE:
You can select multiple translated XML files for upload at once.

All imported files will be listed in the 'Imported Translation Files' column on the left of the window.

Drag each translation into the appropriate content-group column, as shown.

NOTE:
Each row in the 'Version Documents to Create' section will result in a single 'Version Document'. If you have multiple content groups across multiple version documents, care must be taken to ensure that the correct translations are in the same row.

If more than one content group has been exported from a single project, you will need to ensure that the translated content groups are imported into the same version document.

This is done by ensuring that they are dragged to the same row in the 'Version Documents to Create' section.

Unassigned content groups can be identified by a '[No file]' placeholder.  

NOTE:
You can select and drag multiple translations into a column at once.

1. You can rename your version documents by clicking in the 'Version Name' column.
2. You can empty a row by clicking on the red 'X' in the right-hand column. If this is done, the imported translation will reappear in the 'Imported Translation Files' area.

Click the '[No workflow]' button to open the 'Select Workflow' window. This window displays all workflow templates and folders in your 'Workflows' tab.

Select a translation workflow for that version document and click 'Select'.

You have now set up the following:

• assigned the translated XML files to their correct content groups
• assigned a workflow to the version document that will be used to create the jobs ]

Clicking 'Create Version Documents' will start the process that creates the version documents, applies the workflows to those documents, replaces the source-language segments with the translated segments, and starts the workflow (for any version where the checkbox is checked).

Any translations in the translated XML files will be marked as 'Done' in the first workflow step. Therefore, if all translations are done in the XML file, the first review task will appear in the reviewers 'Jobs' tab.

NOTE:
It is still possible for a reviewer to 'reject' a job item back to the edit/translation step, so it is important to add a user to that step of the workflow even if it is initially skipped by this process.

NOTE:
The 'Import Translations' window will not close by default. Click the 'Cross' symbol in the upper right corner to close the window.

If you click the 'Create Version Document' button before selecting a suitable workflow, this 'Warning' message will appear.

You must have a workflow that contains workflow tracks for all translated content groups.

All version documents are then created.

NOTE:
It will take time for the system to write all of the translations into the version documents (like with a pre-translation action). Therefore, jobs may not appear instantaneously in a user's 'Jobs' tab.