The resolution is to add a human step, for instance Translate
after Generate Translation Kit
. Since the WSXZStudio
package is exported for users to be downloaded and opened in SDL Trados Studio
, it is recommended that the human step is added right after Generate Translation Kit. Here is an example of a simple workflow:
Workaround: configure the Generate Translation Kit
in the Workflow to use the Kit Exporter Type: Assets
instead of Tasks
as displayed here:
Save the change in the Workflow and re-submit the project. The project with the tasks in Autoerror will need to be canceled.
Warning: if you select Kit Exporter Type
, the exported WSXZ package will be named after the project, for instance: project_Test Generate Translation Kit_1_1529_Dutch (Netherlands)_workbench.wsxz.
However, once you open the package in SDL Trados Studio, it will
display with a generic project name isuch as Adhoc_Project_xxxxxxx_xxxxxx"
(where the first 8 digits stand for the date of the export and the last 6 digits are random). This might be confusing as the translator will not be able to see the actual project name in Studio. Here is an example:
More information about how to configure the Generate Translation Kit
workflow step can be found in this article:How to configure the Generate Translation Kit Automatic Action and add it to your Workflow