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

Please check that you have workflow templates that will work with your project (i.e. the names of any Content Groups in the project exactly match those in the workflow).

NOTE: You will need one workflow template for each target language that you are importing.

NOTE: The names are case-sensitive.

1. Select a project from which you exported your translation file.
2. In the project's option menu, click Translation > Import Translations.

This will open the dialog: Import Translations

NOTE: You must import translations to the project from which the translation file was exported.

1. Click Upload Translations to select and upload your translated XML files.

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

2. The uploaded translation files will appear in the dialog's left-hand column.

1. Drag each translation file to the right. Each of these rows will become a version document.

NOTE: You can select and drag multiple translation files at once. Each will automatically be assigned to a new version document.

2. Rename a version document by clicking in the Version Name column.
3. Clicking the X to the right of a version document will remove it. The imported translation will reappear in the left-hand area if this is done.

4. Click a [No workflow] button to open the Select Workflow dialog.
5. Choose the appropriate workflow template and click Select to assign it to that version document.

6. By default, the workflows will start as soon as you create the version documents. If you do not wish for a workflow to automatically start, uncheck this box beside the workflow. The version will be created, but you can choose when to start the workflow.
7. Click Create Version Documents.

NOTE: The translations will still be imported to the document, even if the workflow is not started at this point.

8. The import tasks will be displayed in your notifications menu.
9. The Import Translations dialog will remain open, in case you wish to perform further imports for this project. You may close it manually via the Cancel button or the X in the top-right corner.

NOTE: You can define the status of imported translations in your Client Workspace Settings. By default, the Default Translation Import Job Status setting is set to Translation Finished, which will automatically commit your imported translations for review.

Your version documents, containing your imported translations, have now been created.

NOTE: It takes time for the system to write all of the translations into the version documents. Therefore, jobs will not appear instantaneously in a user's Jobs list.

NOTE: Any text that was not changed in the translation file will not be marked as translated.

If you have a multi-lingual document, you will have a Content Group for each target language.

In such a case, you must ensure that you assign the correct languages to the correct version documents, so that the target languages match those in the assigned workflow.

NOTE: Each row will result in a single Version Document.

A version document cannot be edited without a workflow. Therefore, the translations cannot be imported.

If you have not assigned a workflow to a version document, this Warning message will appear. Clicking Yes will create the version documents that have workflows assigned to them, and ignore those that do not.

NOTE: Your workflow must contain tracks for all Content Groups of type Translation that are in the project.

The chosen workflow must contain tracks that have the same name as the Content Groups in your project (see the Note at the start of this lesson).

If the names of the Content Groups in your project do not match those in the workflow, you will see this Error message.

NOTE: The names are case-sensitive.