Before you start, you should check that you have a workflow template that will work with your project.

This means that:

1. the names of the Content Group(s) in the workflow template exactly match those in the project (i.e. in the master document).
2. It also means that there must be one workflow template for each target language (or set of target languages, if the document is multilingual).
3. Furthermore, the workflow template must contain users at the workflow steps (otherwise the workflow cannot run).

Without a valid workflow template, the translation job can be created via this process.

NOTE: It is very important to make sure that the Content Group name(s) in the workflow template match the names of the existing content groups in the project. These names are case sensitive. Check the Content Groups in your master document if you are unsure.

Click Translation > Import Translations in the Project's context menu to open the Import Translations dialog.

The Import Translations dialog assists with importing and setting up your translation jobs.

1. Your uploaded translation files will be shown here.
2. You will be able to name your version documents before they are created.
3. Any translation Content Groups in the project are shown as columns into which the appropriate translations will be placed.
4. The checkmark column gives you the option to automatically start the workflows upon creation of the version documents.
5. The Workflow column is where you will assign workflow templates.

NOTE: Even if you choose to not start the workflows, you will still be required to assign a workflow template to each version document.

NOTE: In our example above, there is a single translation-type Content Group in our project, which is named Translation Group.

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

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

All uploaded files will be listed in the Imported Translation Files column on the left.

Drag each translation into the appropriate Content-Group column, as shown.

NOTE: Each row in the Version Documents to Create section is 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 dropped into the correct rows.

NOTE: It is a good idea to ask your translators to put the target language code into the filename of the translated XML file. This makes it easier to figure out which translation goes where during this step.

Click in the Version Name column to rename your version documents.

1. Clicking the X at the end of a row will remove that row from the list of Version Documents to Create.
2. When a row is removed, any uploaded translations related to that row will appear back in the Imported Translation Files.

1. Click the [No workflow] button to open the Select Workflow dialog. This dialog displays the folders and templates from your Workflows section.
2. Select the appropriate translation workflow (i.e. the one with the correct target-language) for this version document and click Select.

NOTE: As mentioned above, the Content-Group name(s) must be the same in both the master document and the workflow template.

At this point, you have:

• assigned the translated XML files to their correct Content Groups
• assigned workflows to the version documents

Click Create Version Documents to start the creation process.
This will: create the version documents, import the translations, and start the chosen workflows (for any version document where the checkbox is checked).

NOTE: The Import Translations dialog will not close by default once the version documents are created. Click the X in the upper-right corner to close it.

You must assign workflows that contain tracks/groups for all imported Content Groups.

If you do not, this warning will appear when you click the Create Version Documents button, because no import can be performed without a workflow.

Version documents are created in the project.

The resulting progress of each job will depend on how many translated segments have been imported, as well as the number of steps in the workflows.

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

In the example above, the project contains two translation-type Content Groups:

• Translation A
• Translation B

In such a case, you will need to ensure that translated Content Groups are imported into the correct version documents by dragging them to the correct row in the Version Documents to Create section.

NOTE: Unassigned content groups can be identified by the placeholder text of: [No file]