...
Built-in variables are listed alphabetically within the following categories on this page:
- Agent Variables
- Agent-Based Task Instance Variables
- Agent Cluster Variables63733890
- 63733890
- 63733890
- Agent File Monitor Task Instance/Trigger Variables
- Application Monitor Trigger Variables
- Cluster Node Variables
- Common Variables
- Composite Trigger Variables63733890
- 63733890
- 63733890
- 63733890
- Email Monitor Task Instance/Trigger Variables
- File Transfer Task Instance Variables
- OMS Server Variables
- PeopleSoft Task Instance Variables
- Recurring Task Instance Variables
- Remote File Monitor Task Instance Variables
- SAP Task Instance Variables
- SQL and Stored Procedure Task Instance Variables
- SQL Task Instance Variables
- Stored Procedure Task Instance Variables
- System Monitor Task Instance Variables
- Task Instance Variables63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- 63733890
- Task Monitor Task Instance/Trigger VariablesTrigger Variables
- 63733890
- Variable Monitor Task Instance/Trigger Variables
- Web Service Task Instance Variables
- z/OS Task Instance Variables63733890
- 63733890
| Anchor | ||||
|---|---|---|---|---|
|
...
| Note | ||
|---|---|---|
| ||
Although they have the same syntax, ${ops_agent_id}, this 63733890 Agent Queue Name Agent variable resolves to a different value than the 63733890 Agent sys_id Agent-based task instance variable. |
...
| Note | ||
|---|---|---|
| ||
Although they have the same syntax, ${ops_agent_id}, this Agent sys_id 63733890 Agent-based task instance variable resolves to a different value than the 63733890 Agent Queue Name Agent variable. |
Agent Queue Name
...
Description | Resolves to the sequentially assigned number, maintained per task, representing the creation order of the instance. For example, if you launch a task twice, the first task instance will have instance number 1, and the second task instance will have instance number 2.
| |||||
|---|---|---|---|---|---|---|
Syntax | ${ops_task_ref_count} | |||||
Example |
...
Trigger Task Name
Description | Resolves to the name of the task instance that matched the Task Monitor conditions and fired the trigger. |
|---|---|
Syntax | ${ops_trigger_task_name} |
Example |
Trigger Task Status
Description | Resolves to the status of the task instance that matched the Task Monitor conditions and fired the trigger. |
|---|---|
Syntax | ${ops_trigger_task_status} |
Example |
Trigger Task sys_id
Description | Resolves to the sys_id of of the task instance that matched the Task Monitor conditions and fired the trigger. |
|---|---|
Syntax | ${ops_trigger_task_id} |
Example |
Trigger Task Type
Description | Resolves to the type of the task instance that matched the Task Monitor conditions and fired the trigger. |
|---|---|
Syntax | ${ops_trigger_task_type} |
Example |
Trigger Workflow Name
Description | Resolves to the name of the workflow instance containing the task instance that matched the Task Monitor conditions and fired the trigger. This variable is available only for a Task Monitor task specified specified. If a workflow condition is specified, ${ops_trigger_workflow_name} will resolve to the name of the workflow instance that the workflow condition matched. |
|---|---|
Syntax | ${ops_trigger_workflow_name} |
Example |
...