Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Retrieves comments and status history for the specific job.

NOT IMPLEMENTED

URL

(GET) /jobs/{id}/traces

PARAMETERS

URL parameters are:

id

The job ID. Also see jobs/{id}/summary

string, Mandatory


RESULTS

The resulting JSON object has these properties:

count

Total number of traces.

int
items

Array with the list of traces, see below.

object[]
persons

An object containing the persons referred to by the traces. Note:

  • Excludes persons that the user cannot see. There is an access right to prevent a user from viewing user and company names.

See Persons List (Object) for details.

object

 

Each trace has these properties:

ctyAlways "job"string
cmidThe ID of the trace.int
txtOptional message with the trace. Typically used with traces that are messages.string
locThe locale to which the comment is attached. This can be a source or target locale.string
loctThe language name.string
dtThe date of the trace.datetime
uidThe user who triggered this event. Null if the user was deleted.int?
tskThe task code to which this event is attached: RV, TR, PROOFstring
tsktThe task name. 
status

The job status at the time. Numeric status, see Job Status

int
statustThe job status title.string
editTrue if the user is allowed to edit or delete the item. False, if no change is permitted.bool

 



The job property has these elements:

idThe globally unique ID of the job (which encodes jobid + iscodyt)string
jobidThe numeric job id (unique for Standard and Codyt respectively)int
iscodytTrue: A Codyt job. False: A standard job.bool
referenceThe reference of the job. With Codyt jobs this is the job's document name.string
taskThe task code of the job (TR, RV...)string
tasktThe task title (Translation, Revision...)string
src / srctSource language code and namestring
trg / trgtTarget language code and namestring
branch / brancht

Branch language code and name. In general the branch locale is identical to the target locale.

It may be different where a workflow involves a back translation or translation into pivot languages.

string
statusThe job status as a number.int
statustThe job status name.string

 

EXAMPLES

 

 

 

 

  • No labels