When using the 'Import Translations' wizard to import a translated XML file, it is necessary to assign a workflow in order to create a version document.

However, you may see the warning 'Workflow has no matching content groups' appear in the bottom-right corner of your window. This is shown because the content group(s) in the workflow do not match the content group(s) in your master document.

There are two things to check in this case: the content group name and type.

One reason for this warning to appear is when the name of the content group in the document does not match the name of the content group in the workflow.

In the example above, the content group in the document is named "New Content Group" (the default value), while the workflow content group is named "Edit Group".

NOTE:
If there are multiple content groups in the document and/or the workflow, the system will use the names of these groups for matching purposes.

Another reason for this warning to appear is when the type of content group in the document does not match the type of content group in the workflow.

There are two types of content group in one2edit™: 'Edit Group' or 'Translation Group'. The difference between these is that a translation content group must have a source language defined in the master document, and a target language defined in the workflow.

In the example above, there is a source language defined in the master-document content group, but no target language defined in the workflow content group. This means that the type of content group in the workflow is an 'Edit Group', not a 'Translation Group'.

This mismatch causes the warning to appear.