Custom workflow and workflow templates
Custom workflows are the workflows that you create if the default workflows cannot cater for your localization needs in terms of tasks, review cycles or transitions.
Custom workflows are derived from a custom workflow template, namely a sequence of workflow tasks, workflow phases, and workflow transitions.
Tasks
- Default Human tasks (provisioned by the system )
- Custom Human tasks ( that you create based on the default types)
- Default Automated tasks (provisioned by the system)
- Custom Automated tasks (that you develop yourself or purchase from RWS)
Tasks are connected through transitions which control the overall progress of the workflow.
Phases
A workflow phase is a collection of workflow tasks that work together to perform a localization goal as a subsection of the full workflow.
Transitions
- Most of the default Automated tasks have one transition (outcome = DONE), with the exception of the Translation Automated QA Check task and the Linguistic Review Automated QA Check task which have two transitions (outcomes = REJECTED and DONE).
- Custom Automated tasks are tailored for your specific needs and can have any number and type of transitions.
- All the task types based on which Custom Human tasks are created have one default transition (outcome = DONE), with the exception of the Linguistic Review task which has 2 transitions (outcomes = APPROVED and REQUEST CORRECTIONS).
- You can add custom transitions for any Custom Human task, except those that are based on the Customer Quote Approval or Customer Review type. The maximum number of default and custom transitions combined, per task, is 10.
Workflow templates
A custom workflow template is a sequence of required workflow tasks mapping the business process of translating your content. A custom workflow template consists of: tasks, phases, and transitions.