translate5 offers two workflow types out of the box:
- the Standard workflow and
- the Complex workflow
For both workflow types, only those jobs that are required in the project need to be assigned. Unassigned jobs are automatically skipped by translate5. At the same time, as many users as required can be assigned to each task. For example, with a text of 1000 segments, the first 500 segments could be assigned to one translator and the other 500 segments to a second translator.
The two workflow types are described below.
| Please note that it is possible to configure individual workflows per client at database level. Get in touch with us if you are interested. |
|---|
Standard workflow
This workflow type contains the following jobs:
- Translate
- Review
- Second review
- View only: User is not involved in the workflow, but can look at the various jobs in read-only mode at any time.
Complex workflow
This workflow type contains the following jobs:
- Translate
- 1st revision - language
- 1st revision - technical
- 2nd revision - language with editable 100% matches
- 2nd revision - technical
- Text approval
- External DTP (read-only inside translate5)
- Final text approval
Multiple users – allocation and collaboration modes
translate5 offers the following collaboration modes:
- Simultaneous work: All assigned users of a workflow step can work on the same file at the same time. This mode is currently the pre-selected standard. If several users are assigned to the same workflow step, it is advisable to coordinate with them on who will work on which part of the source file(s).
- Competing assignment: “First come, first served” – only the first user to confirm/open the task is allowed to work on it. In this collaboration mode, acceptance of the job must always be confirmed. From this moment on, the other requested users no longer have access to it.
- Sequential work: All assigned users can work on the task, but only one after the other, not simultaneously.
| Within a project, only one collaboration mode can be used for all tasks. |
|---|
Completion of a task
A task can be finished when all users assigned to the task have completed their jobs.
Request confirmation of acceptance of a task
When assigning users to the individual workflow steps, the project manager can request a confirmation from the users. This is possible in the “Users” tab of the project overview: If you select the status “unconfirmed” in the drop-down here, the “Confirm task?” window will appear for the requested users when they open the task in the Editor, which must be used to confirm acceptance of the job. Editing of the task will only be possible after this has been done.
For workflows with the collaboration modes “simultaneous work” and “sequential work”, the confirmation is only used to provide feedback to the project manager that the assigned users accept the work. Only in the “competing assignment” collaboration mode, the confirmation of jobs ensures that the other requested users no longer have access to the task.
| The “initial task state” configuration field can be used to set the initial status of the tasks to “unconfirmed”. This can either be done in the system configuration, in the client profile or during project creation. This means that the very first workflow step is always assigned as “unconfirmed” and must be confirmed by the requested user. |
|---|---|
| If confirmations are requested for second and subsequent workflow steps, these can only be confirmed when the workflow jumps to the relevant step, i.e. when the preceding jobs have been finished. |
