XTM Cloud v 13.1

Workflow definitions

XTM default workflows include:

  • translate

  • translate # review

  • translate # review # review

  • translate > correct

  • translate > correct > correct

  • translate , correct

  • translate , correct > review

  • translate , review

  • translate , review > review

  • translate # correct

  • translate > correct # review

Table 45. Blocking mechanism between workflow steps

Symbol/ special character

Description

comma.svg

steps can be processed at the same time

greater-than-solid.svg

the next step cannot be started until the previous step for that bundle is finished

hashtag-solid.svg

the next step cannot be started until the previous step for all the bundles is finished


For each task, a linguist can choose to:

  • finish the task

  • reject the task

  • decline the task: the PM will have to assign it to another person

Table 46. Default workflow steps in XTM Cloud

Step name

User functionality

Translate

Edit target text. Manually add comments.

Correct

Edit target text.

Manually add comments. If the target text is changed a new comment is automatically created to record the change made.

Review

Manually add comments

LQA

Check translation errors

Management task

Files can be downloaded but not updated.

Example entering cost details, approving cost and proposals, printing files, sending files to client

Non-CAT tool process

Files can be downloaded and updated in XTM, but the TM and project segments will not be modified.

Example 14. Example

DTP (Desktop Publishing)


Automatic

  • Approve the TM of segments

  • Set the minimum XLIFF:doc status of segments

  • Set the XTM status of segments.


Note

The system Administrator can also create custom steps.

When creating a new project by default each job contains all the segments from the file (e.g., if a document has 150 segments XTM creates the tasks for segments 1-150).

The project manager can then split the default tasks into smaller parts.

Each bundle in the project follows the same steps in the workflow.

Example 15. Example 1
Table 47. Workflow example 1

Translate 1

comma.svg

Review 1

greater-than-solid.svg

Review 2

Bundle 1

Task

(translate1,bundle1)

comma.svg

Task

(review1,bundle1)

greater-than-solid.svg

Task

(review2,bundle1)

Bundle 2

Task

(translate1,bundle2)

comma.svg

Task

(review1,bundle2)

greater-than-solid.svg

Task

(review2,bundle2)


In this workflow example:

  • once the workflow has been started, Translator 1 and Reviewer 1 can work simultaneously

  • the tasks in Review2 are initially not active

  • When Reviewer1 has finished reviewing bundle1, the task Review2 for bundle 1 becomes active and Reviewer2 can start work, irrespective of the status of bundle 2


Example 16. Example 2
Table 48. Workflow example 2

Translate 1

hashtag-solid.svg

Correct 1

Bundle 1

Task

(translate1,bundle1)

hashtag-solid.svg

Task

(review1,bundle1)

Bundle 2

Task

(translate1,bundle2)

hashtag-solid.svg

Task

(review1,bundle2)


In this workflow example:

  • once the workflow has been started, only Translator 1 can start work

  • the tasks in Correct1 are initially not active

  • when Correct1 only became active when both bundles 1 and 2 have been finished in Translate.


workflow_stages__apply_roles.png

Applying roles to Workflow stages