| Table of Contents |
|---|
...
On the Contractor side:
Go to Configuration → Settings → Workflow → Workflow steps, and Add a new step.
...
| Info |
|---|
In the project workflow, the LSP will see the name of the assigned step as Translate (in this example) because it is a default step name on the LSP side. |
Go to Configuration → Settings → Workflow → Workflow steps, and check the Show contractors online translation steps checkbox. You will see the workflow steps created by the Contractor.
...
| Info |
|---|
The Refer to option allows you to decide to which of your workflow steps this contractor’s workflow step should refer to. In general, if it is set up to Choose, the name of the step in the workflow will be the same as it is on the contractor side. Those steps (the ones with a red asterisk) are not active because the contractor has not sent off any project that includes those steps yet. |
...
On the Contractor side:
Go to Project editor → Workflow, and edit it in some way (for example, update the due date).
| Info |
|---|
Updating the project workflow on the LSP side does not have the same effect: it does not change the name. |
On the LSP side:
Go to Project editor → Workflow, and see the result: the workflow step is displayed with its new name.
| Tip |
|---|
From now on, every time the Contractor makes use of that particular workflow step in their subcontracted projects (whether it is an isolated workflow step or is incorporated into a particular workflow definition), the LSP shall see the relevant custom name defined by the Contractor in the Project editor → Workflow. |