It is necessary to assign target-language workflows to Version Documents when using the Import Translations tool.

However, if the Content Groups in the chosen workflow do not match the Content Groups in your source-language document, you will see the above message: Workflow has no matching groups

In this case, you must check that both the Name and the Type of the Content Groups match.

One reason that this message appears is if the Name of the Content Group in the source-language document does not match the name of the Content Group in the workflow.

In the example above, the Content Group in the source-language document is named Translation, but the Content Group in the workflow is named New Content Group (the default value).

To resolve this, update the name in the workflow to match the one in the source-language document.

NOTE: one2edit™ uses the names of Content Groups to match them to the corresponding workflow tracks. This allows for workflows containing multiple Content Groups to be defined in a project (e.g. for a multi-lingual document, etc.).

Another reason that this message appears is if the Type of the Content Group in the source-language document does not match the type of the Content Group in the workflow.

In the example above, the Content Group in the source-language document is of type Translation, but no target language is assigned to the Content Group in the workflow. If no target-language is assigned to a Content Group, then it is treated as an Edit type, not a Translation type.

To resolve this, assign a target language to the Content Group in the workflow.

NOTE: Take care to assign the target language from the correct Language Set.