...
Depending on the project configuration, the operation will typically do everything needed to get translation workflows runningready and going: Save files to project, mark online, pre-translate and word count, create and assign jobs.
...
PARAMETERS
The URL parameters are:
| The invoice project’s ID. | int, Mandatory |
The request BODY contains a JSON payload object with the new invoice’s these properties:
properties | Optional. Use if you want to update any of the properties. Refer to Invoice Properties Record and notable the section “UPDATING” | object, Optional | ||||
lines | Optional. Use if you want to replace the existing invoice lines with a new set of lines. An array if invoice lines. You must submit at least 1 line. See Invoice Line Record and make sure to read the notes on Inserting and Updating lines. | object[], Optional | ||||
distribution | This is optional. It will be populated with the presets configured in the client record by default (which usually is what is wanted). If you want to customize this section, submit this object: Invoice Distribution Record | object?, Optionalfiles | An array with one or more records, each describing a file to be uploaded. The records include the token referencing an uploaded a file. Example:
See detailed description further down. | object[], Mandatory | ||
src | The source language code. This must be a valid project language. | string, Mandatory | ||||
trgs | The languages to translate to. These must be valid project languages. Example:
| string[], Mandatory | ||||
deadline | Optional deadline for completion of work. Deadlines are assigned to the jobs that are created with the workflow. Example:
| datetime?, Optional | ||||
workflow | Optional, selects
| string, Optional | ||||
allowUpdates | Optional. Default is true.
| bool?, Optional | ||||
jobsCfs | Optional custom fields to assign to all jobs created for a file’s workflow. See Custom Field Collection Record for details. Example:
|
RESULTS
The result is the updated invoice document.
...