(Workflow) Steps
Workflows are composed of steps.
Default workflow steps
The following drop-downs describe the default workflow steps available in XTM:
In this step, users can enter and edit translations and add comments.
The comments entered here are typically meant as issues for a project manager to resolve.
In this step, users can edit translations and enter comments.
Edits made by the corrector are automatically registered under their username and shown in the comments section of the segment in Workbench (CAT). Each change (translation or correction) in the segment is included in the comments for each change to the translation that is made.
In this step, users can only enter comments about translations.
Users can't edit the translation.
The typical next step after a review is a correction.
Allows you to automatically approve the TM of changed segments, segments set to done (completed), or ICE and leveraged matched segments.
Without this step only reviewed, corrected or LQAd strings (the next step described below) enter the TM.
This can be overwritten in the workflow configuration. Workflows consist of individual workflow steps that are tied together. Within the workflow checking the "Approve TM" box automatically approves TM for a given step in the workflow.
In this step, users can check translation errors.
This is exactly like a review step except errors can be categorized into one of the many predefined error types XTM provides.
Along with being able to enter comments, this allows for better traceability and continuous improvement initiatives.
Typically a correction step follows.
The linguist in this case then tags translation errors with one of these LQA error codes for easier tracking.
Translation errors marked with LQA codes are stored against the translator in XTM and can be viewed by opening the rating section for each user under their Quality tab, and reports can be generated on a project level or across multiple projects.
These categorized reasons can be modified by an administrator, using this procedure.
Workflow step types
Each workflow step is assigned a type (category).
The step types in XTM are:
In this step, users can enter and edit translations and add comments.
The comments entered here are typically meant as issues for a project manager to resolve.
In this step, users can edit translations and enter comments.
Edits made by the corrector are automatically registered under their username and shown in the comments section of the segment in Workbench (CAT). Each change (translation or correction) in the segment is included in the comments for each change in the translation that is made.
In this step, users can only enter comments about translations.
Users can't edit the translation.
The typical next step after a review is a correction.
In this step, users can check translation errors.
This is exactly like a review step except errors can be categorized into one of the many predefined error types XTM provides.
Along with being able to enter comments, this allows for better traceability and continuous improvement initiatives.
Typically a correction step follows.
The linguist in this case then tags translation errors with one of these LQA error codes for easier tracking.
Translation errors marked with LQA codes are stored against the translator in XTM and can be viewed by opening the rating section for each user under their Quality tab, and reports can be generated on a project level or across multiple projects.
These categorized reasons can be modified by an administrator, using this procedure.
Files can be downloaded but not updated.
Example entering cost details, approving cost and proposals, printing files, sending files to client
Files can be downloaded and updated in XTM, but the TM and project segments will not be modified.
Example DTP (Desktop Publishing)
Allows you to automatically approve the TM of changed segments, segments set to done (completed), or ICE and leveraged matched segments.
Without this step only reviewed, corrected or LQAd strings (the next step described below) enter the TM.
This can be overwritten in the workflow configuration. Workflows consist of individual workflow steps that are tied together. Within the workflow checking the "Approve TM" box automatically approves TM for a given step in the workflow.
Also sets the minimum XLIFF:doc status for segments at a specific point in the workflow.
Workflow steps are assigned to:
Workflows, globally by an administrator using this procedure.
Workflows by a project manager within a project. Edit the project then click on the workflow tab to the left, then the edit workflow button at the top.
Tip
Workflow steps are assigned to workflows globally by an administrator.
A project manager, however, can overwrite the global configuration within any project that they have access to.
The following can be assigned to workflow steps:
Workflow steps are assigned to users with the linguist role in the user configuration screen. Typically this represents the job function that a linguist has.
An administrator can create custom workflow steps using the procedure indicated here.