This article is for Account Owners and Project Managers on the New Experience - Beta.
Dynamic Workflows are designed to help you achieve translation cost savings and faster time to market by intelligently routing your content based on parameters you choose.
Make your workflow dynamic by configuring Decision Steps and Workflow Branches.
Decision Steps and Workflow Branches
The Decision step is a new workflow step type that evaluates a string’s properties and automatically chooses between multiple steps to send them to. Decision steps are different from other workflow steps in that:
- Can point to multiple steps: other workflow steps can only be followed by one workflow step. Decision steps can be followed by several parallel workflow steps
- Fully automated: users do not need to submit strings from a Decision step
Once a Decision step is defined, you can create multiple workflow branches from it. A workflow branch can consist of multiple workflow steps. This effectively allows you to have a single workflow that has the functionality of multiple workflows. Each branch can be configured to best translate the content that moves through it.
Decision steps can be used to support complex translation needs effortlessly and within the same workflow. Some examples:
- Send strings with high fuzzy scores to human translators (to leverage TM and SmartMatch) and strings with low fuzzy scores to machine translation (for cost savings and velocity).
- Split content by File URI to different agencies, then have all translated content reviewed together in an Internal Review step.
- Combine multiple different workflows for different locales into a single workflow.
Currently, only one Decision step is allowed in a dynamic workflow and it must be in pre-translation. However, you can create as many workflow branches as you’d like.
Creating a Dynamic Workflow
- Go to Projects (select a project) > Gear Icon > Project Settings > Workflows
- Scroll to the workflow you’d like to configure, then click Add Steps. Click on the + icon before a Translation step
- Select the Decision (New Branch) step type, then click Next. Enter a name for the step, then click Create
- The new Decision step will show up in the workflow as . Now you can create a second workflow branch to send strings to. Click on the + icon to begin building the second branch
- Choose the Workflow step type, and choose a step for this workflow branch to merge back into.
- Define your new Translation step. You can read here for more information on step settings. Click Create when you are done configuring the step
- Repeat steps 4-6 to create as many workflow branches as you need
- Now you have to define the rules to route content to your workflow branches. Click on the Decision step to configure your rules.
- Decision steps contain the rules for sending strings to different workflow branches. A Decision step always has a default rule, which automatically sends strings to the first Translation step if no other rules apply. Click Add New Rule to define a new rule
- A rule consists of an action (where the string should go) and a condition (why it should go there). Choose a branch to send strings to, then choose a condition and define the value for it. The following conditions are currently supported:
- Fuzzy score is greater than or equal to X%
- Fuzzy score is less than X%
- String word count is greater than or equal to X
- String word count is less than X
- File URI contains “X”
- File URI does not contain “X”
- Target language is in the list “X,Y,Z” (must use locale IDs, like “fr-FR” and “pt-BR”)
- Target language is not in the list “X,Y,Z” (must use locale IDs, like “fr-FR” and “pt-BR”)
- String key contains “X”
- String key does not contain “X”
- Has string tags “X”
- Does not have string tags “X”
- Repeat steps 9-10 to define all your rules
- Click Save when you are done defining rules
- When you are done adding steps to the workflow, click Done on the workflow toolbar
To ensure that content is translated correctly, all possible paths through a workflow must have exactly one Translation step and end at the same Published step. A workflow branch does not have to merge back to the Published step, but it must merge with a step that will eventually lead it to Published.