Please see the screenshots below for basic explanations.

Detailed explanations, how the workflow system works

If a user opened a task for editing, no other user can edit it as long as the session of the editing user is valid and he does not close the task.

Workflow Roles

The translate5 basic workflow knows three workflow roles:

These workflow roles can be combined as needed. They can be used on their own or in combination with the others. Only "translatorCheck" always has to be combined with "reviewer".

So you could

Segment autostates created by the workflow roles

On editing a segment the segment gets an autostate, depending on the role of the user:

Workflow Steps

The translate5 basic workflow knows three workflow steps:

It is possible to allocate only users with the role as an editor (reviewer) to a task in the workflow - then the first and third workflow steps are omitted.

In general the used workflow steps are depending on the chosen user roles, so if no translation is needed, no translators are chosen, no translation step is performed.

The workflow step of a task changes if:

The valid status combinations to match a workflow step are:

translationreview (reviewing)secound review
role translator has status openrole translator has status finishrole translator has status finish
role reviewer has status waitingrole reviewer has status openrole reviewer has status finish
role translatorCheck has status waitingrole translatorCheck has status waitingrole translatorCheck has status open

The role as a visitor is not allocated to any workflow step. It has no function in the workflow chain.

A user with the role as a project manager is able to open a task in the workflow for viewing at any time. He is able to edit any task, which is not currently opened by another user.

Workflow Status of Task Allocations

Each allocation of a user with a role to a workflow step has a workflow status. The translate5 basic workflow knows the following workflow statuses:

The project manager is able to change each task allocation for each user at any time.

Workflow Status of Tasks

Regardless of workflow status of task allocations, a task in itself has a status in the workflow. This status is affecting the task allocations:

Workflow Chain

For the workflow chain see the corresponding document.

API Usage

Via API jobs (task user associations) can be created to set-up the workflow in a task.

The following workflow step values has to be used via API:

Step in the UI / documentationvalue to be used via API
Second ReviewtranslatorCheck
View onlyvisiting

The values for the status fields are straight forward as in the documentation above, but all in lower case: