Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printabletrue
Page Properties
hiddentrue

Introduction

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

...

Transition marks

What are

...

transition marks?

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

They are set up in the XTM Workflow editor:

...

When are they used? – splitting a job into bundles

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

...

Note

IMPORTANT!

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

Types of transition

...

mark

There are three types of transition marks available mark for inserting in insertion 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:

greater-than-solid.svgImage Removeduuid-9fc8626c-7337-758c-7d28-c9342876fa6c.svgImage Added

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

hashtag-solid.svgImage Removeduuid-d3746982-6903-054b-94f7-83ff55e64c16.svgImage Added

  • Hashtag Any bundle No bundles in the next workflow step cannot can be started until all the bundles from the previous step are have been finished first.