Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Introduction

XTM Cloud offers quite a vast flexibility in terms of building up XTM workflow definitions as well as transition between particular workflow steps. This article presents ins and outs of how transition marks work in XTM workflow, especially in the context of working on a particular workflow step by multiple linguists.


Transition marks

What are they?

Transition marks, or blocking mechanisms, are tools which allow you to impose rules on when specific workflow steps are available to work on by assigned linguists in the XTM UI.

When are they used? – splitting a job into bundles

Transition marks gain their actual significance and effect mainly when XTM jobs are split into multiple smaller bundles, whose primary purpose is to enable different linguists to work on a single workflow step simultaneously.

IMPORTANT!

A common misconception about splitting an XTM job into bundles is that it enables linguists to work on the exact same segments in XTM Workbench, in the same workflow step, by multiple linguists. It works quite the opposite. In this case, linguists have a certain, different, scope of segments assigned within a single workflow step. Other segments which are not assigned to a specific linguist are locked for them in XTM Workbench.

Types of transition marks

There are three types of transition marks available for inserting in between workflow steps in XTM Cloud:

comma.svg

  • Comma → Bundles in the neighboring workflow steps can be processed at the same time, which means that the first workflow step does not necessarily have to be finished first:

uuid-9fc8626c-7337-758c-7d28-c9342876fa6c.svg

  • Arrow → A specific bundle in the next workflow next step cannot be started until the previous workflow step for that bundle is finished first.

uuid-d3746982-6903-054b-94f7-83ff55e64c16.svg

  • Hashtag → Any bundle in the next workflow step cannot be started until all the bundles from the previous step are finished.

  • No labels