Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

CategoryEnvironment VariableDescriptionAdjustable by ScriptDefault Value
ControllerJS7_CONTROLLER_IDIdentification of a Controller as specified during initial operation.n/an/a





InventoryJS7_JOB_NAMEThe name of the job as specified with the workflow configuration.n/a

JS7_ORDER_IDThe order identification as returned when creating an order.n/a

JS7_WORKFLOW_NAMEThe name of the workflow.n/a

JS7_WORKFLOW_LABELThe label assigned the workflow instruction for the job. Consider that the same job can be used a number of times in a workflow and that its assignment to an instruction is additionally specified by a label.n/a

JS7_WORKFLOW_POSITIONThe indicator for the position of the order in the current workflow.n/a





Scheduled DateJS7_SCHEDULED_DATE

The date for which an order originally was scheduled. The date format includes yyyy, MM, dd, hh, mm, ss and the time zone offset, e.g. 2020-12-03 09:13:59+0100

n/aScheduled Date

JS7_SCHEDULED_YEARThe year of the scheduled date padded by 2 digits, e.g. 2020, 2021, 2022 etc.n/aYear of Scheduled Date

JS7_SCHEDULED_MONTHThe month of the scheduled date padded by 2 digits, e.g. 01, ..., 12n/aMonth of Scheduled Date

JS7_SCHEDULED_DAYThe day of the scheduled date padded by 2 digits, e.g. 01, ..., 31n/aDay of Scheduled Date

JS7_SCHEDULED_HOURThe hour of the scheduled date padded by 2 digits, e.g. 00, ..., 24n/aHour of Scheduled Date

JS7_SCHEDULED_MINUTEThe minute of the scheduled date padded by 2 digits, e.g. 01, ..., 59n/aMinute of Scheduled Date

JS7_SCHEDULED_SECONDThe second of the scheduled date padded by 2 digits, e.g. 01, ..., 59n/aSecond of Scheduled Date





Job Start DateJS7_JOBSTART_DATEThe date at which the job was started. The date format includes yyyy, MM, dd, hh, mm, ss and the time zone offset, e.g. 2020-12-03 09:13:59+0100n/aStart Date of the task for a shell job or Start Date of the processing of an order by a JVM job

JS7_JOBSTART_YEARThe year of the job start date padded by 2 digits, e.g. 2020, 2021, 2022 etc.n/aYear of Job Start Date

JS7_JOBSTART_MONTHThe month of the job start date padded by 2 digits, e.g. 01, ..., 12n/aMonth of Job Start Date

JS7_JOBSTART_DAYThe day of the job start date padded by 2 digits, e.g. 01, ..., 31n/aDay of Job Start Date

JS7_JOBSTART_HOURThe hour of the job start date padded by 2 digits, e.g. 00, ..., 24n/aHour of Job Start Date

JS7_JOBSTART_MINUTEThe minute of the job start date padded by 2 digits, e.g. 01, ..., 59n/aMinute of Job Start Date

JS7_JOBSTART_SECONDThe second of the job start date padded by 2 digits, e.g. 01, ..., 59n/aSecond of Job Start Date

JS7_JOBSTART_EPOCHMILLISThe number of milliseconds since January 1st 1970 UTC until the job start daten/aEpoch milliseconds for Job Start Date

Explanation:

  • Consider that the Scheduled Date is available only for orders that have been scheduled for a start time. 
    • This applies to scheduled orders created by JS7 - Schedules.
    • This applies to Ad Hoc orders created from the JS7 - Workflows that are assigned a start time
    • This does not apply to Ad Hoc orders that are created for immediate start.

Environment Variables from Job Properties


Explanation:

  • Users are free to choose the names of environment variables. Such names are automatically converted to uppercase letters.
  • Environment variables can be assigned values from order variables and from node arguments. Such variables are preceded by a $ and consider the spelling of the respective variable or argument.
  • Caveat: Any existing environment variables with the same name will be overwritten from the job configuration. You can e.g. specify a PATH environment variable if the intention is to modify this OS environment variable for use with a specific job.

...