guides
TM per workflow step
A translation memory bound to a project, or associated with an org unit, is read and written by every workflow step by default, as its read and write say. To have a step behave differently, for example a translation step that reads the TM and a review step that also writes to it, list the steps in settings.workflows.
The settings
{
"atlasTmId": 1042,
"read": true,
"write": false,
"settings": {
"workflows": [
{ "workflowUuid": "5a1c7e2b-3d9f-4b86-a0e4-8f2d6c1b9e73", "read": true, "write": false },
{ "workflowUuid": "c2e8b4d1-6f3a-4c97-b5d0-1a9e7f3c2b48", "read": true, "write": true }
]
}
}
| Field | Meaning |
|---|---|
read, write | What the steps not listed in settings.workflows do with the TM. |
settings.workflows[].workflowUuid | A workflow step, as the workflowUuid of the project's work units (List Project Work Units). |
settings.workflows[].read | The step looks up matches in the TM, for pre-translation and in the editor. |
settings.workflows[].write | The step's confirmed translations are saved to the TM. |
A step listed in settings.workflows follows its own read and write; every other step follows the TM's.
Where to send them
- On a project: Bind TM to Project, one entry per TM. Send the TM's
atlasTmIdin each entry; Get Project Translation Memories returns the current entries with it. - On org units: Associate Translation Memory with Org Units takes the same
settingsin its body. Projects created afterwards in those org units start with them.