Specifications

DescriptionData typeElement name
An indication of the origin of the processed job
before it was injected in the flow; for example, a
TextJobOrigin
Submit point writes the absolute path of the original
job (on the client machine) in this field
The absolute file or folder path for the processed job
as it resided in the input folder before being
processed, including unique filename prefix
TextJobPath
The job priority assigned to the processed job as a
signed integer number
IntegerJobPriority
The unique filename prefix used for the processed
job, without the underscores; for a job called
“_0G63D_myjob.txt” this would be “0G63D”
TextJobUniqueNamePrefix
The user name associated with the processed job, if
any
TextJobUserName
The date-time when the operation was completed
(in the ISO 8601 format also used for Switch date
variables)
DateProcessingEnded
The date-time when the operation started (in the
ISO 8601 format also used for Switch date variables)
DateProcessingStarted
The name or IP address of the destination serverTextServerAddress
The user name used to login at the destination serverTextServerLoginName
The port of the destination serverIntegerServerPort
Defining metadata fields
The Submit point and Checkpoint tools allow defining metadata fields which can be viewed
and/or edited by the SwitchClient user when submitting or moving along a job. The values of
display-only fields are determined by evaluating a script expression so that they can depend on
metadata associated with the job. After a user submits a job or moves it along, the values of
editable fields (as entered by the user) are associated with the job as metadata (with the client
fields schema).
Defining metadata fields
322
Enfocus Switch 10