| Panel | |
|---|---|
|
Overview
...
- Agent Variables
- Agent-Based Task Instance Variables
- Agent Cluster Variables
- Agent File Monitor Task Instance/Trigger Variables
- Application Monitor Trigger Variables
- Cluster Node Variables
- Common Variables
- Composite Trigger Variables
- 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 Variables
- Task Monitor Task Instance/Trigger Variables
- Trigger Variables
- Universal Event Monitor Task Instance/Trigger and Universal Event Variables
- Variable Monitor Task Instance/Trigger Variables
- Web Service Task Instance Variables
- Webhook Variables
- z/OS Task Instance Variables
...
| Note | ||
|---|---|---|
| ||
Although they have the same syntax, ${ops_agent_id}, this 206420808 Agent Queue Name Agent variable resolves to a different value than the 206420808 Agent sys_id Agent-based task instance variable. |
...
| Note | ||
|---|---|---|
| ||
Although they have the same syntax, ${ops_agent_id}, this 206420808 Agent sys_id Agent-based task instance variable resolves to a different value than the Agent Queue Name 206420808 Agent variable. |
Agent Queue Name
...
Description | If UDM Agent Option = UDM Agent Hostname; Resolves to the specified hostname. If UDM Agent Option = UDM Agent or UDM Agent Cluster; Resolves to the IP address of the referenced Agent definition. If UDM Agent Option = --None–; Resolves to empty string/blank. If UDM Agent Option = Utility Agent; Resolves to *. |
|---|---|
Syntax | $({ops_primary_agent_hostname)} |
Example |
| Anchor | ||||
|---|---|---|---|---|
|
Description | If UDM Agent Option = UDM Agent Hostname; Resolves to the specified hostname. If UDM Agent Option = UDM Agent or UDM Agent Cluster; Resolves to the IP address of the referenced Agent definition. If UDM Agent Option = --None–; Resolves to empty string/blank. |
|---|---|
Syntax | $({ops_secondary_agent_hostname)} |
Example |
For Transfer Protocol = FTP/SFTP/FTPS
...
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 |
...
Description | Resolves to the task type. |
|---|---|
Syntax | ${ops_task_type} |
Example |
Task Vertex ID
Description | Resolves to the value of the task’s vertex id in a workflow. |
|---|---|
Syntax | ${ops_vertex_id} |
Example | Ops_vertex_id = 5 |
Time Zone (Task time zone)
...
Description | Resolves to the uuid of the workflow instance containing the task instance that matched the the Task Monitor conditions and fired the trigger. This variable is available only if the task instance that matched the the Task Monitor conditions and fired the trigger is invoked by a workflow. |
|---|---|
Syntax | ${ops_trigger_workflow_id} |
Example |
...
| Anchor | ||||
|---|---|---|---|---|
|
Universal
...
Monitor Task Instance/Trigger and Universal Event Variables
| Anchor | ||||
|---|---|---|---|---|
|
Description | Name of a Universal Event Attribute. Facilitates the passing of matched Universal Event attributes to downstream instances within a workflow or to instances launched by a Universal Monitor Trigger. |
|---|---|
Syntax | ${ops_trigger_eventName_attributeName} |
Example |
Universal Event Business Services
| Description | Business Services of the Universal Event. If the Universal Event is published from a universal task instance, the Universal Event inherits the business services from the task instance. If the Universal Event is a system-published event, it inherits the business services of the object the event is being published for. If the Universal Event is published via our publish web service API, the business services are specified as part of the request body. If the Universal Event is published via our push web service API, the business services are specified as part of the request query parameters. |
|---|---|
| Syntax | ${ops_trigger_universal_event_business_services} |
| Example |
| Anchor | ||||
|---|---|---|---|---|
|
...
Universal Event Payload
| Description | Resolves to same JSON payload for the matched Universal Event that would be used for a URL action. |
|---|---|
| Syntax | ${ops_webhook_eventName_payload} |
| Example |
Webhook Name
| Description | Resolves to the name of the Webhook that launched the Task Instance. |
|---|---|
| Syntax | ${ops_webhook_name} |
| Example |
| Anchor | ||||
|---|---|---|---|---|
|
...