The translate5 basic workflow knows three workflow roles:

• translator (translator, if it is a translation task)
• proofreader (first or only editor),
• translatorCheck (second editor, if needed),
• and visitor (not part of the workflow chain; can only view content).

Segment autostates created by the workflow roles

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

• Role independent:
  • "blocked": segments which are not editable / translatable are marked as blocked by the import process.
  • "not translated": non translated segments are set to this state by the import process.
  • "translated": already translated segments are set to this state by the import process.
• translator
  • "translated": if an untranslated segment will be translated, it is set to translated. This is the initial autostate of already translated segments for proofreading tasks.
  • "translated auto": if an untranslated segment was translated by using the repetition editor in the frontend

• proofreader

  • "reviewed": if the proofreader modifies and saves a segment.

  • "reviewed auto" if the proofreader modifies and saves a segment by using the repetition editor.

  • "reviewed untouched" if all proofreaders are finishing the task, all segments not opened by proofreaders are getting automatically this autostate.

  • "reviewed unchanged" if a proofreader opens and saves a segment without modification.

  • "reviewed unchanged auto" if a proofreader opens and saves a segment without modification by using the repetition editor.

• translatorCheck
  • "reviewed translator": if the translator opens and saves the segment, regardless if he changed anything.
  • "reviewed translator auto": if the translator opens and saves the segment, regardless if he changed anything, triggered by repetition editor.
• Projectmanager (editing a segment without any workflow role)

  • "reviewed pm": if the pm modifies and saves a segment.

  • "reviewed pm auto" if the pm modifies and saves a segment by using the repetition editor.

  • "reviewed pm unchanged" if a pm opens and saves a segment without modification.

  • "reviewed pm unchanged auto" if a pm opens and saves a segment without modification by using the repetition editor.

• visitor
  • Since segments are readonly no autostate is changed

Workflow Steps

The translate5 basic workflow knows three workflow steps:

• "Translating" (1st step allocated by the role as an translator)
• "Proofreading" (2st step allocated by the role as an proofreader)
• "checking of editing" (3nd Step allocated by the role as a translatorCheck)

It is possible to allocate only users with the role as an editor (proofreader) 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:

• All users of one role (other roles are not considered then) are finishing their workflow step (by setting the task to finish). The next step in the workflow chain is chosen.
• If a user association is added, changed or deleted, the combination of all user state and roles of that task is used to determine the workflow step of the task. This enables the PM to start an untranslated task in the "translator check" step, even if this makes no sense.

The valid status combinations to match a workflow step are:

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:

• Open: The task can be currently processed by the user. For API usage use the value "open".
• Waiting: The user can process the task as soon as it is his turn in the workflow (he can view it, though). For API usage use the value "waiting".
• Finished: The user completed the processing of the task and thus cannot open it for processing anymore (he can view it, though). For API usage use the value "finished".
• Unconfirmed: The user first have to confirm the task before working on it. For API usage use the value "unconfirmed".
  To confirm a task, just open the userState with state "edit". That implies if the user should open the task for reading only before confirmation, the userState "view" should be used.

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