System properties
- Synopsis
- Full Details
In briefSystem properties are values Continuum supplies itself — dates, the job's name and
status, the schedule date, the agent. Write the token, such as [[$SCHEDULE DATE]] or
[[JI.$JOB NAME]], and the platform fills it in. Names start with $ and ignore case; a bare $
name is routed to the scope that owns it.
WhereSelect Insert property on a field that has the picker: notification actions, a job's Events tab, a workflow's Event Trigger tab, Self Service button events and rules, and Vision trigger actions. The groups are Global, Job, Schedule, Agent and Card. Job parameters, the command line and expressions have no picker; type the token.
When
- A job parameter needs the schedule date, the job's name or today's date.
- An event or notification should say which job, workflow or agent it is about.
- A Self Service request should record who submitted it, with
${SM.USER.EMAIL}.
For your own values, use a global or instance property — see Properties.
How
- Open the field and select Insert property, or type the token.
- Pick the group: Job for
JI, Schedule forSI, Agent forMI, Global forOI. - For a date, add a format or an offset if you need one:
[[$SCHEDULE DATE(-1dd)]]. - Check the result after a run — in the job's Summary tab, or the Event log.
The full steps are in Manage properties, calendars, and tags.
$MAX RUN TIMEand$EST RUN TIMEareHH:mm:sstext, not numbers.$EST RUN TIMEcomes from the Estimated Run Time (in min) on the job's frequency.$JOB STATUSuses its own wording, such asJob Running— see Status text.- A date format suffix needs a global property of the same name holding the mask.
${SM.USER.LOGIN}is the requester's email address;${SM.USER.COMMENTS}is always empty.
- An unresolved token in a job parameter puts the job in Initialization Error; in a submitted event it fails the event. In a fired event or a notification it is left in the text, and the tokens around it still resolve.
- Some tokens are offered but never fill in:
$START COMMAND,$MACHINE NET STATUS,$MACHINE RUNNING JOBSand$NOTIFYID.$RESTART STEPfills in only after a restart on a step, and$TRIGGER MESSAGEonly in an LSAM Feedback event. - Only the current instance can be read; naming another one is refused. Another agent's machine
property is the exception:
[[MI.Name.AGENT01]].
Task walkthrough: Manage properties, calendars, and tags. This page is the full catalog of the built-in tokens.
A system property is a value OpCon Continuum supplies itself — today's date, the job's name,
the schedule date, the agent a job ran on. You do not create one; you write its token, and the
platform fills it in. System names start with $, are written in upper case with spaces
($JOB NAME), and are matched case-insensitively.
[[$SCHEDULE DATE]] the schedule date of the current workflow instance
[[JI.$JOB NAME]] the current job's name
[[$DATE]] today's date
The token grammar — delimiters, your own properties, expressions — is on Properties. This page lists what the platform itself supplies, and where.
- Scopes
- Job and Schedule Tokens
- Other Tokens
- Formats and Offsets
- Where Tokens Work
- Troubleshooting
Scopes
A token can name the scope it reads from: [[Scope.Name]]. A bare $ name is routed to the scope
that owns it, so [[$JOB NAME]] and [[JI.$JOB NAME]] are the same token.
| Scope | Shown in the picker as | What it reads |
|---|---|---|
OI | Global | Your global properties, and the clock tokens $DATE, $TIME and $NOW. RI.<instance>.Name reads the same as OI.Name |
JI | Job | The current job instance |
SI | Schedule | The current workflow (schedule) instance |
MI | Agent | The agent the job runs on: the $MACHINE … names below, and the machine properties set on the agent. The picker offers only the $MACHINE … names; type a machine property's token |
TH | — | A threshold's current value: [[TH.<name>]] |
RM | — | A resource's total units: [[RM.<name>]] |
RU | — | A resource's units in use, across every environment: [[RU.<name>]] |
CI | Card | A Vision card's values, in a Vision action only. See Card tokens |
TH, RM and RU are not offered in the picker; type them. SSI and SJI are not offered
either. As a token, in a job parameter or an expression dependency, they read the parent workflow
instance or the container job of a sub-workflow — see Scopes. In the
Property Name of a $PROPERTY event they name the parent of a sub-workflow to write to — see
Writing a property onto a running instance.
Only the current instance can be read. Naming another instance — another job or another
schedule — is refused with Cross-instance addressing is not yet supported, rather than quietly
resolving to the current one. The agent scope is the exception for your own values:
[[MI.EMAIL.PROD01]] reads the machine property EMAIL of the agent PROD01. A system name is
read only for the job's own agent, so [[MI.$MACHINE NAME.PROD01]] does not resolve.
Job and Schedule Tokens
The catalog
Job (JI)
| Token | Resolves to | Format |
|---|---|---|
$JOB NAME | The job's name | Text, trimmed |
$JOBID | The job instance's identifier | A UUID |
$JOBID CMP | The job name followed directly by $JOBID | Text |
$JOBID LONG | The job name cut or padded to 12 characters, five spaces, then $JOBID | Text |
$JOB STATUS | The job's status, as text. See Status text | Text, such as Finished OK |
$JOB STATUS CATEGORY | RUNNING in a job's parameters and expression dependencies; nothing in events or notifications | Text |
$JOB TERMINATION | The job's termination description — empty until it ends, and empty when it finished OK with none. See Exit codes and machine messages | Text |
$JOB STARTTIME | When the job started; N/A if it has not | Date and time, default yyyy/MM/dd hh:mm:ss |
$JOB ENDTIME | When the job ended; N/A if it has not | Date and time, default yyyy/MM/dd hh:mm:ss |
$ACTUAL RUN TIME | How long the run took; N/A while a start or end time is missing | HH:mm:ss |
$MAX RUN TIME | The job's maximum run time | HH:mm:ss text; 0 reads 00:01:00 |
$EST RUN TIME | The job's estimated run time: the Estimated Run Time (in min) of the frequency the job was built from. Supplied in the job's parameters, expression dependencies, events and notifications, on every built job and every job a $JOB:ADD event adds. A job instance built by an earlier release has none until it is rebuilt or its estimate is edited | HH:mm:ss text; 0 reads 00:01:00 |
$FREQUENCY NAME | The frequency the job was built from | Text |
$MASTER JOB NAME | The job's definition identifier, in an expression dependency only | Text |
$MACHINE NAME | The agent the job is going to, or ran on. Also MI.$MACHINE NAME | Text |
$ARRIVED FILE NAME | The whole path a File Arrival job matched | Text |
$ARRIVED FILE PATH | Its directory | Text |
$ARRIVED SHORT FILE NAME | Its last segment | Text |
$ARRIVED BASE FILE NAME | Its last segment without the extension | Text |
$ARRIVED FILE EXTENSION | Its extension, leading dot included | Text |
$RESTART STEP | The step the job was last restarted on — a UNIX Command, SAP R/3 Job, SAP BW Process Chain, z/OS Batch Job or z/OS Started Task only. For a z/OS job restarted on a range it is the whole range as given, such as STEP2|STEP4. Nothing when no step is stored: the job has never been restarted on a step, was last restarted from the beginning, or has since finished OK. Supplied in the job's own events and notifications and in its parameters as it is dispatched; not in an expression dependency | Text, as the agent reported the step |
$START COMMAND | Nothing: offered in the picker, but no value is supplied | — |
The five $ARRIVED … names, and which job types supply all five, are described in
The file a File Arrival job found.
$MAX RUN TIME and $EST RUN TIME render as HH:mm:ss, so compare them as text in an expression:
> "00:10:00", never > 10. From 100 hours, text order is no longer time order. The picker's hover
text says the same.
Schedule (SI)
| Token | Resolves to | Format |
|---|---|---|
$SCHEDULE NAME | The workflow's name | Text |
$MASTER SCHEDULE NAME | The workflow's name, in a job's parameters and in events and notifications | Text |
$SCHEDULE ID | The workflow's identifier | A UUID |
$SCHEDULE INST | Which run of the instance this is for the date — 1 unless it was built again. Not the build number | A whole number |
$SCHEDULE DATE | The schedule date | Date, default dd-mmm-yy (30-Sep-26) |
$SCHEDULE DATEMS | The schedule date as a date serial number | Default ##### |
$SKD STATUS | The workflow instance's status: Building, Wait to Start, Wait Container Job, In Process, On Hold, Parent Hold, Started by User, Completed, Cancelled or Unknown | Text |
$SKD STATUS CATEGORY | Nothing: no value is supplied | — |
InstanceName | Not a $ name, but supplied on every build: the instance's name, or Default. Write [[SI.InstanceName]] | Text |
Status text
$JOB STATUS uses its own wording, which is not always the status name used on these pages:
| Status | $JOB STATUS text |
|---|---|
| Finished OK, Marked Finished OK, Failed, Marked Failed, Initialization Error, Cancelled, Missed Start Time, Skipped, Under Review, Fixed, On Hold, Released, Late to Start, Start Attempted, Still Attempting Start, Lost in Failover | The same words |
| Running | Job Running |
| Late to Finish | Job Running; Late to Finish |
| Running (To Be Terminated) | Job Running; To be terminated |
| Attempting to Start | Attempt to Start |
| Pre-run Active, Pre-run Failed | Prerun Active, Prerun Failed |
| Job to Be Skipped | Job to be Skipped |
| Wait to Start, Wait to Start (Forced) | Wait to Start, Wait to Start; Forced |
| Waiting: Job Dependency, …: Job Conflict, …: Start Time, …: Expression Dependency, …: Machine | Wait Job Dependency, Wait Job Conflict, Wait Start Time, Wait Expression Dependency, Wait Machine |
| Waiting: Threshold Dependency, Waiting: Resource Dependency | Both Wait Threshold/Resource Dependency |
| Finished OK (Pending) and the other (Pending) statuses | The status followed by ; Processing Events, such as Failed; Processing Events |
In a job's own parameters $JOB STATUS is always Start Attempted, because the job is being
started. In an event it is the status that fired the event.
Other Tokens
Agent (MI)
| Token | Resolves to |
|---|---|
$MACHINE NAME | The agent's name, wherever the platform knows which agent the job is on. In an expression dependency it reads Undetermined when the job has no single agent |
$MACHINE OPER STATUS | The operator mark — Active, Marked Offline or Marked Draining — in an Agent notification about an operator mark only |
$MACHINE NET STATUS, $MACHINE RUNNING JOBS | Nothing: offered in the picker, but no value is supplied |
Any MI name that does not start with $ is a machine property, a value you set on the agent.
See Machine properties in a token for where each form
resolves.
Global (OI)
| Token | Resolves to | Default format |
|---|---|---|
$DATE | Today's date | Short Date |
$TIME | The time now | Long Time |
$NOW | The date and time now | General Date, such as 10/16/2026 2:30:05 PM |
$TRIGGER MESSAGE | In an LSAM Feedback event, the feedback value that fired it. Nothing anywhere else | Text |
$OPCONVER, $NOTIFYID | Nothing: Continuum supplies no value for them, though the picker offers them | — |
$DEPARTMENT NAME is recognised so that it is never mistaken for a property of yours, but it never
resolves and the picker does not offer it.
Card tokens (CI)
Seven tokens, filled in only in a Vision trigger action: [[CI.$CARD NAME]],
[[CI.$CARD FREQUENCY NAME]], [[CI.$CARD STATUS]], [[CI.$CARD START TIME]],
[[CI.$CARD END TIME]], [[CI.$SCHEDULE DATE]] and [[CI.$REMOTE INSTANCE NAME]]. They take no
format or offset, and any other CI name is refused when the card is saved. $CARD START TIME and
$CARD END TIME show their own token name while the time is only a forecast, and
$REMOTE INSTANCE NAME shows its token name when the card has no target environment. See
Triggers.
Self Service variables (SM.)
A Self Service button's events can carry four ${…} variables about the person who submits the
request, offered under Submitting user in the button's insert menu:
| Variable | Resolves to |
|---|---|
${SM.USER.EMAIL} | The requester's email address |
${SM.USER.NAME} | The requester's display name, or their email address when they have none |
${SM.USER.LOGIN} | The requester's email address — sign-in is by email |
${SM.USER.COMMENTS} | Always empty |
Any other SM. name is refused when the request is submitted. The button's own inputs and the
SM. variables are filled in first, then any [[…]] global tokens, resolved as the requester. See
Events and variable substitution.
Formats and Offsets
Date and time formats and offsets
The seven date and time tokens — $SCHEDULE DATE, $SCHEDULE DATEMS, $JOB STARTTIME,
$JOB ENDTIME, $DATE, $TIME and $NOW — accept a format and an offset after the name:
[[$SCHEDULE DATE mm/dd/yy]] the schedule date in that format
[[$SCHEDULE DATE(-1dd)]] the day before the schedule date
[[$JOB STARTTIME(+2hh)]] two hours after the job started
A format suffix is looked up as a global property of that exact name, whose value is the mask:
to use $SCHEDULE DATE mm/dd/yy, create a global named $SCHEDULE DATE mm/dd/yy. Without one, the
token fails with No date format is defined for property …. Defining a global named exactly
$DATE (or another bare name) changes that token's format everywhere — except in an event's
Schedule Date and Dates fields, which always use the built-in format. Offsets, their units,
and the rule that working-day offsets are refused are on
Date and time tokens.
Where Tokens Work
Where a token can be used
The Insert property button opens the picker on the fields that have one. It offers different groups on each surface:
| Surface | Groups offered |
|---|---|
| A notification action — the Email, SMS body, In-App and OpCon Event fields | Global, Job, Schedule, Agent |
| A job's events (job editor › Events) | Global, Job, Schedule |
| A workflow's completion events (Event Trigger tab) | Global, Schedule |
| A Self Service button's events | Global |
| A Self Service button's Hidden and Disabled rules | Global |
| A Vision trigger action | Global, Card |
Job parameters and the command line, dependency expressions and completion expressions have no picker: type the token.
When a token is filled in, and what a failure does, depends on where it is:
| Where the token is | Filled in | What resolves | If it cannot be filled in |
|---|---|---|---|
| A job parameter or the command line | As the job is dispatched | Job, schedule, agent and global tokens, thresholds and resources | The job goes to Initialization Error, with the reason as its termination description |
| An expression dependency | Each time it is checked | As a job parameter, plus $MASTER JOB NAME | The job goes On Hold, with the reason as its termination description |
| An event a job fires | As the event fires | Job, schedule, agent and global tokens, thresholds and resources | The event still fires; that token stays exactly as written, and the other tokens in the field still resolve |
| An event a workflow fires | As the event fires | Schedule and global tokens, including $SKD STATUS, and a machine property of an agent named in the token | As above |
| A notification template | As it is sent | What the triggering event captured, plus globals; thresholds and resources for Job and Workflow groups | The notification still goes out, with the token shown as its bare name |
| A notification's OpCon Event action | As it is sent | As a notification | The delivery fails |
| An event submitted from Self Service, the API or a legacy agent | As the event is processed | Global tokens and $DATE, $TIME, $NOW only | The event fails, naming the token — for example no global property with that name exists |
| A Self Service Hidden or Disabled rule | When the button list loads and when the form opens | Global tokens and $DATE, $TIME, $NOW only; encrypted properties are refused | The button shows as visible and enabled |
The full rules for each — encrypted properties, retries, commas a value carries into an event — are on When tokens are resolved. Which tokens a notification can answer is on Template tokens.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| A job goes to Initialization Error with Property could not be resolved: … | A token in a parameter names something that has no value there | Correct the name, or create the global property |
A job's parameter containing [[ fails, such as a shell [[ -f x ]] test | Any [[ in a parameter is read as a token | Write the test another way, such as test -f x |
An event field arrives with [[…]] still in it | The token did not resolve when a job or workflow fired the event | Check the name against the catalog and the surface's row in Where a token can be used |
A notification shows JI.$JOB NAME as text | The group type captured no job — an Agent or Relay group | Use a Job or Workflow group for job tokens |
$START COMMAND, $MACHINE NET STATUS, $MACHINE RUNNING JOBS or $NOTIFYID never fill in | No value is supplied for them | Do not rely on them |
$RESTART STEP does not fill in | No restart step is stored: the job was not restarted on a step, or has finished OK since | Use it only in a job that was restarted on a step |
| No date format is defined for property … | A date token with a format suffix, and no global of that name | Create the global named after the token, with the mask as its value |
| Cross-instance addressing is not yet supported | The token names another job or schedule | Read the current instance, or pass the value through a property |
A [[MI.Name]] token does not fill in | The agent has no property of that name, or there is no agent to read: a Universal Agent pool job at dispatch, a workflow's event, a submitted event | Check the agent's Machine Properties, or name the agent: [[MI.Name.AGENT01]]. See Machine properties in a token |
A global you named $… cannot be read as [[$NAME]] | A bare $ name is routed to a system scope | Rename it without $, or write [[OI.$NAME]] |
Related topics
- Properties — the token grammar and your own properties
- Using expressions with dependencies and properties — computing a value with
[[= … ]] - Events — the events whose fields carry tokens
- Notifications (groups, triggers, channels) — template tokens
- Service requests — Self Service variables
- Exit codes and machine messages — what
$JOB TERMINATIONholds