Resolves to the agent hostname.

${ops_agent_hostname}

Resolves to the agent IP address {see ${ops_agent_ip}, below.

${ops_agent_ipaddr}

Resolves to the agent IP address.

${ops_agent_ip}

Resolves to the agent operational mode {Active, Offline}.

${ops_agent_mode}

Resolves to the agent name.

${ops_agent_name}

${ops_agent_id}

Resolves to the agent hostname.

${ops_agent_hostname}

Resolves to the agent IP address {see ${ops_agent_ip}, below.

${ops_agent_ipaddr}

Resolves to the agent IP address.

${ops_agent_ip}

Resolves to the agent name.

${ops_agent_name}

Resolves to the sys_id of the agent.

${ops_agent_id}

Resolves to the Name of the credential defined in the Agent Details section of the task definition (Utility Credential or Credential).

If a credential is defined on the agent and not in the Agent Details section of the task definition, it will be the agent’s credential Name.

${ops_agent_queue_name}

Resolves to the agent cluster name.

${ops_agent_cluster_name}

Resolves to the Distribution type for the agent cluster.

${ops_agent_cluster_distribution}

${ops_agent_cluster_distribution} → Any

Resolves to the type of Task Execution Limit for the agent cluster.

${ops_agent_cluster_limit_type}

${ops_agent_cluster_limit_type} → Unlimited

Resolves to the current suspension status of the agent cluster.

${ops_agent_cluster_suspended}

${ops_agent_cluster_suspended} → true

Resolves to the maximum number of tasks that can be running at the same time by Agents in this agent cluster.

${ops_agent_cluster_limit_max}

${ops_agent_cluster_limit_max} → 5

Resolves to the current number of tasks currently being run by the Agents in this agent cluster.

${ops_agent_cluster_limit_current}

${ops_agent_cluster_limit_current} → 3

Resolves to the Network Alias of this agent cluster.

${ops_agent_cluster_network_alias}

Resolves to the Agent Port of this agent cluster.

${ops_agent_cluster_network_alias_port}

Resolves to the Notification State for which the notification matched.

${ops_agent_cluster_notification_state}

${ops_agent_cluster_notification_state} → Suspended

Resolves to the base file name.

${ops_trigger_file_name_simple}

Resolves to the directory where the new file was created, but not the file itself. If the existence or non-existence of the final directory separator is a requirement, we recommend the use of ${ops_trigger_file_fullpath} and ${ops_trigger_file_fullpath_no_separator}, respectively.

${ops_trigger_file_path}

${ops_trigger_file_path} → C:\stonebranch

Resolves to the directory where the new file was created, but not the file itself; includes the final directory separator.

${ops_trigger_file_fullpath}

${ops_trigger_file_fullpath} → C:\stonebranch\

Resolves to the directory where the new file was created, but not the file itself; does not include the final directory separator.

${ops_trigger_file_fullpath_no_separator}

${ops_trigger_file_fullpath_no_separator} → C:\stonebranch

Resolves to the file extension of a file.

${ops_trigger_file_name_extension}

${ops_trigger_file_name_extension} → dat 

Resolves to the separator appropriate to the platform where the agent is running. For Windows, resolves to a backslash { \ }; for Linux/Unix, resolves to forward slash { / }. This variable may be useful if you want to piece together a pathname using a combination of text and variables.

${ops_trigger_file_separator}

Resolves to the file date of the file that fired the trigger.

${ops_trigger_file_date}

Resolves to the file group of the file that fired the trigger.

${ops_trigger_file_group}

Resolves to the name of the file that fired the trigger.

${ops_trigger_file_name}

${ops_trigger_file_name} → C:\stonebranch\file.dat

Resolves to the name of the file that fired the trigger, but without any path information.

${ops_trigger_file_name_nopath}

${ops_trigger_file_name_nopath} → file.dat

Resolves to the file owner of the file that fired the trigger.

${ops_trigger_file_owner}

${ops_trigger_file_owner} → Administrator

Resolves to the result of the file scan: FOUND or NOT_FOUND.

${ops_trigger_file_scan}

Resolves to the file size of the file that fired the trigger.

${ops_trigger_file_size}

${ops_trigger_file_size} → 141085

Resolves to the name of the Application being monitored by the trigger.

${ops_trigger_appl_name}

Resolves to the status of the Application being monitored by the trigger.

${ops_trigger_appl_status}

${ops_trigger_appl_status} → Starting

Resolves to the sys_id of the application.

${ops_trigger_appl_id}

Resolves to the type of Application being monitored by the trigger, as defined by the Application Type field.

${ops_trigger_appl_type}

${ops_trigger_appl_type} → Windows Service

Resolves to the hostname of this cluster node.

${ops_cluster_hostname}

Resolves to the cluster node's internally-generated build ID.

${ops_cluster_id}

Resolves to the IP address of this cluster node.

${ops_cluster_ipaddr}

Resolves to the current mode of this cluster node: Offline, Active, Passive.
 
For more information, see Viewing Node Status.

${ops_cluster_mode}

${ops_cluster_name} is an alias for the ${ops_cluster_id} variable.

${ops_cluster_name}

Resolves to the numbers of days, hours, and minutes that this cluster node has been running since it was last started.

${ops_cluster_uptime}

Resolves to the value of the System Identifier Universal Controller system property.

${ops_system_identifier}

${ops_system_identifier} → QA UC6

Resolves to the time when a Composite Trigger component fired.

${<prefix>_trigger_component_event_time}

${filetrigger_component_event_time} → 2024-10-21 14:38:29 -0400

${timetrigger_component_event_time} → 2024-10-21 14:38:29 -0400

Resolves to the Name of the Task’s credential.

Resolves to the Body field of the Email.

${ops_trigger_email_body}

Resolves to the Cc field of the Email.

${ops_trigger_email_cc}

Resolves to the From field of the Email.

${ops_trigger_email_from}

Resolves to the HTML Body field of the Email.

${ops_trigger_email_body_html}

Resolves to the Received Date field of the Email.

${ops_trigger_email_received_date}

${ops_trigger_email_received_date} → 2024-10-16 13:01:33 -0700

Resolves to the Reply-To field of the Email.

${ops_trigger_email_reply_to}

Resolves to the Sent Date field of the Email.

${ops_trigger_email_sent_date}

${ops_trigger_email_sent_date} → 2024-10-16 13:01:27 -0700

Resolves to the Subject field of the Email.

${ops_trigger_email_subject}

Resolves to the To field of the Email.

${ops_trigger_email_to}

Resolves to the source password.

${ops_src_cred_pwd}

Resolves to the source user ID.

${ops_src_cred_user}

Resolves to the destination password.

${ops_dst_cred_pwd}

Resolves to the destination user ID.

${ops_dst_cred_user}

Resolves to the Primary password.

$(ops_primary_cred_pwd)

Resolves to the Primary user ID.

$(ops_primary_cred_user)

Resolves to the Secondary password.

$(ops_secondary_cred_pwd)

Resolves to the Secondary user ID.

$(ops_secondary_cred_user)

Resolves to the Primary File{s} field values.

If the Primary File{s} field is empty, it resolves to empty string/blank.

${ops_primary_filename}

${ops_primary_filename} is an alias for ${ops_local_filename}.

${ops_primary_filename} → file.dat

Resolves to the Secondary File{s} field values.

If the Secondary File{s} field is empty, it resolves to empty string/blank.

${ops_secondary_filename}

${ops_secondary_filename} is an alias for ${ops_remote_filename}.

${ops_secondary_filename} → file.dat

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 *.

${ops_primary_agent_hostname}

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.

${ops_secondary_agent_hostname}

Resolves to the Local Filename field values.

If the Local Filename field is empty, it resolves to empty string/blank.

${ops_local_filename}

${ops_local_filename} is an alias for ${ops_primary_filename}.

${ops_local_filename} → file.dat

Resolves to the Remote Filename field values.

If the Remote Filename field is empty, it resolves to empty string/blank.

${ops_remote_filename}

${ops_remote_filename} is an alias for ${ops_secondary_filename}.

${ops_remote_filename} → file.dat

Resolves to the last OMS Server connected to the Controller in an OMS HA cluster.

${ops_oms_last_connected}

Resolves to the last time that the OMS Server connected to the Controller in an OMS HA cluster.

${ops_oms_last_connected_time}

${ops_oms_last_connected_time} → 2024-10-17 10:18:06 -0400

Resolves to the OMS Server IP address.

${ops_oms_server_address}

Resolves to the current status of the OMS Server.

${ops_oms_status}

${ops_oms_status} → Connected

Resolves to the sys_id of the OMS server.

${ops_oms_id}

Resolves to the current status of the OMS Server messaging sessions {heartbeat, input, output}: Operational, Impaired, None.

${ops_oms_session_status}

Resolves to the PeopleSoft task instance Distribution Status.

${ops_distribution_status}

Resolves to the PeopleSoft Main Job Name.

${ops_main_job_name}

Resolves to the PeopleSoft task/task instance Main Schedule Name.

${ops_main_schedule_name}

Resolves to the PeopleSoft task instance Process Instance.

${ops_process_instance}

Resolves to the PeopleSoft task/task instance Process/Job Name.

${ops_process_name}

Resolves to the PeopleSoft task/task instance Process Type.

${ops_process_type}

Resolves to the PeopleSoft task instance Run Status.

${ops_run_status}

Resolves to the time when the Recurrence task next runs.

${ops_next_recurrence_time}

${ops_next_recurrence_time} → 2024-10-18 11:46:28 -0400

Resolves to the current count of task recurrences.

${ops_recurrence_count}

${ops_recurrence_count} → 3

Resolves to the ID of the Recurrence task instance.

${ops_source_instance_id}

Resolves to the name of the Recurrence task instance.

${ops_source_instance_name}

Resolves to the ID of the target task.

${ops_target_task_id}

Resolves to the name of the target task.

${ops_target_task_name}

Resolves to the base file name.

${ops_trigger_file_name_simple}

${ops_trigger_file_name_simple} → file

Resolves to a comma-separated list of files that matched the wildcard, if one was specified in the Remote Filename field in the Remote File Monitor task.

${ops_trigger_files}

Resolves to the remote file name.

${ops_trigger_file_name}

${ops_trigger_file_name} → file.dat

Resolves to the remote file name without any path information.

${ops_trigger_file_name_nopath}

${ops_trigger_file_name_nopath} → file.dat

Resolves to the directory where the remote file is located, but not the file itself. ${ops_trigger_file_path} is an alias for ${ops_trigger_file_fullpath_no_separator}.

${ops_trigger_file_path}

Resolves to the directory where the remote file is located, but not the file itself; includes the final directory separator.

${ops_trigger_file_fullpath}

Resolves to the directory where the remote file is located, but not the file itself; does not include the final directory separator.

${ops_trigger_file_fullpath_no_separator}

Resolves to the file extension of the file.

${ops_trigger_file_name_extension}

${ops_trigger_file_name_extension} → dat

Resolves to the contents of the Remote Filename field in the Remote File Monitor task.

${ops_trigger_wildcard}

Resolves to the path only, with the final slash but without the file name, from the Remote Filename field in the Remote File Monitor task.

${ops_trigger_wildcard_path}

Resolves to the path only, without the final slash and without the file name, from the Remote Filename field in the Remote File Monitor task.

${ops_trigger_wildcard_path_no_separator}

Resolves to the SAP InfoPackage Request ID.

${ops_sap_requestid}

Resolves to the SAP job ID.

${ops_sap_jobid}

Resolves to the SAP job name.

${ops_sap_jobname}

Resolves to the SAP Process Chain ID.

${ops_sap_chainid}

Resolves to the SAP Process Chain Log ID.

${ops_sap_logid}

Resolves to the Name of either the Task’s credential or the Database Connection's credential. Task credential is higher precedence.

Resolves to any error message generated by the database.

${ops_sql_error_msg}

Resolves to the number of rows processed.

${ops_sql_rows}

Resolves to a return code that indicates the outcome of the most recently executed SQL statement.

${ops_sql_state}

Resolves to the value of the SQL Command field.

${ops_sql_command}

Resolves to the value from the Stored Procedure Name field.

${ops_stored_proc_name}

Actual size determined by the agent.

${ops_sm_actual_size}

${ops_sm_actual_size} → 36.11

Same as ops_sm_actual_size, except rounded to the nearest integer.

${ops_sm_actual_int_size}

${ops_sm_actual_int_size} → 36

Scale of the actual size determined by the agent.

${ops_sm_actual_scale}

${ops_sm_actual_scale} → GB

Scale specified in the By Scale field for Resource Available of the System Monitor task definition.

${ops_sm_scale}

${ops_sm_scale} → MB

Size specified in the Resource Available field of the System Monitor task definition.

${ops_sm_size}

${ops_sm_size} → 5.0

Same as ops_sm_size, except that ops_sm_int_size is rounded to the nearest integer.

${ops_sm_int_size}

${ops_sm_int_size} → 5

Resolves to the hostname of the Active cluster node.

${ops_cluster_hostname}

Resolves to the Active cluster node's internally-generated build ID.

${ops_cluster_id}

Resolves to the IP address of the Active cluster node.

${ops_cluster_ipaddr}

Resolves to the current mode of the cluster node: Offline, Active, Passive.
 
For more information, see Viewing Node Status.

${ops_cluster_mode}

${ops_cluster_name} is an alias for the ${ops_cluster_id} variable.

${ops_cluster_name}

Resolves to the numbers of days, hours, and minutes that the Active cluster node has been running since it was last started.

${ops_cluster_uptime}

Resolves to the date and time the Active cluster node {server} was started.

${ops_cluster_start_time}

For tasks that launch a command on a Windows or Linux/Unix machine; resolves to the task command.

${ops_cmd}

For tasks that launch a command on a Windows or Linux/Unix machine; resolves to the task command parameters.

${ops_cmd_parms}

Resolves to the value of user-defined field #1.

${ops_custom_field1}

Resolves to the value of user-defined field #2.

${ops_custom_field2}

Resolves to the value of the Task Description field.

${ops_description}

Resolves to the task instance Duration.

${ops_duration_text}

${ops_duration_text} → 2 Minutes 10 Seconds

Resolves to the task instance Duration In Seconds.

${ops_duration}

${ops_duration} → 130

Resolves to the task ending time.

${ops_end_time}

${ops_end_time} → 2024-10-14 10:05:48 -0400

Resolves to the Average Estimated End Time in the server's time zone.

${ops_avg_estimated_end_time}

${ops_avg_estimated_end_time} → 2018-10-16 15:01:45 -0400

Resolves to the Highest Estimated End Time in the server's time zone.

${ops_highest_estimated_end_time}

${ops_highest_estimated_end_time} → 2018-10-16 15:01:45 -0400

Resolves to the Lowest Estimated End Time in the server's time zone.

${ops_lowest_estimated_end_time}

${ops_lowest_estimated_end_time} → 2018-10-16 15:01:44 -0400

Resolves to the User Estimated End Time in the server's time zone.

${ops_user_estimated_end_time}

${ops_user_estimated_end_time} → 2018-10-16 15:01:54 -0400

Resolves to the ID of the user who launched the task or to the ID of the user who enabled the trigger that launched the task.

${ops_execution_user}

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.

${ops_instance_number}

Resolves to the task launch time. For workflows, all descendants will have the same launch time as the top-level workflow.

${ops_launch_time}

${ops_launch_time} → 2024-10-14 10:05:33 -0400

Resolves to the maximum retry count.

${ops_retry_maximum}

Resolves to the sys_id of the parent workflow task instance.

${ops_workflow_id}

Resolves to the name of the parent workflow.

${ops_workflow_name}

Resolves to the projected end time of workflow, based on its critical path calculations.

${ops_projected_end_time}

${ops_projected_end_time} → 2024-10-21 11:18:13 -0400

Resolves to the date and time that the task was queued for processing.

${ops_queued_time}

${ops_queued_time} → 2024-10-15 08:25:12 -0700

${ops_task_ref_count}

Resolves to the current retry count.

${ops_retry_count}

Resolves to the retry interval {seconds}.

${ops_retry_interval}

${ops_retry_interval} → 60

For Windows, Linux/Unix, and SAP tasks where a Script or SAP Definition from Scripts is specified; resolves to the Controller system ID of the script.

${ops_script_id}

For Windows, Linux/Unix, and SAP tasks where a Script or SAP Definition from Scripts is specified; resolves to the Controller name of the script.

${ops_script_name}

For tasks that run a script on a Windows or Linux/Unix machine; resolves to the task script parameters.

${ops_script_parms}

Resolves to the task starting time.

${ops_start_time}

${ops_start_time} → 2024-10-14 10:05:33 -0400

Resolves to the current task instance attempt count. Each Re-run operation increments the attempt. Initial attempt is 1.

${ops_attempt}

Resolves to the task instance definition ID.

${ops_task_definition_id}

Resolves to the task instance exit code, if any.

${ops_exit_code}

${ops_exit_code} → 0

Resolves to the task instance name.

${ops_task_name}

Resolves to the current task instance status.

${ops_status}

${ops_status} → SUCCESS

Resolves to the task instance status description.

${ops_status_description}

${ops_status_description} → State was cancelled from RUNNING to CANCELLED

Resolves to the sys_id of the task instance.

${ops_task_id}

${ops_task_security_name}

Resolves to the task type.

${ops_task_type}

${ops_task_type} → Windows

Resolves to the value of the task’s vertex id in a workflow.

${ops_vertex_id}

${ops_vertex_id} → 5

Resolves to the time zone of the task instance, as specified by the Time Zone Preference field.

${ops_task_time_zone}

${ops_task_time_zone} → America/New_York

Resolves to the time zone of the trigger that launched the task. If the task was launched by the Trigger Now/Launch Task command, the built-in variable will resolve to the command's time zone option, or if no time zone option was specified, the server time zone.

${ops_time_zone}

${ops_time_zone} → America/New_York

Resolves to the name of the top-level workflow task instance.

${ops_top_level_workflow_name}

Resolves to the sys_id of the top-level workflow task instance.

${ops_top_level_workflow_id}

Resolves to the value of the task instance field Virtual Resource Priority.

${ops_resource_priority}

${ops_resource_priority} → 10

Resolves to the name of the task instance that matched the Task Monitor conditions and fired the trigger.

${ops_trigger_task_name}

${ops_trigger_task_status} → SUCCESS

Resolves to the sys_id of the task instance that matched the Task Monitor conditions and fired the trigger.

${ops_trigger_task_id}

${ops_trigger_task_type}

${ops_trigger_task_type} → Windows

Resolves to the uuid of the workflow instance containing the task instance that matched the Task Monitor conditions and fired the trigger.

This variable is available only if the task instance that matched the Task Monitor conditions and fired the trigger is invoked by a workflow.

${ops_trigger_workflow_name}

Resolves to the value of user-defined field #1.

${ops_trigger_custom_field1}

Resolves to the value of user-defined field #2.

${ops_trigger_custom_field2}

Resolves to the name of the trigger that launched the task instance.

${ops_trigger_name}

Resolves to the scheduled time of the trigger or, if the trigger is not scheduled, the actual trigger time.

If the task is triggered by date/time, it resolves to that specified date/time.

${ops_trigger_time}

${ops_trigger_time} → 2024-10-14 10:34:38 -0400

Resolves to the trigger time in the time zone of the trigger.

${ops_trigger_time_tz}

${ops_trigger_time_tz} → 2024-10-14 10:34:38 -0400

${ops_trigger_uac_task_status_changed_launch_source} → Trigger Monitor

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.

Name of the Universal Event.

${ops_trigger_universal_event_name}

UUID of the Universal Task Instance that published the Universal Event, if applicable.

${ops_trigger_universal_event_publisher_id}

Time To Live {in minutes} for the Universal Event.

${ops_trigger_universal_event_ttl}

${ops_trigger_universal_event_ttl} → 15

UUID of the Universal Template, if applicable.

${ops_trigger_universal_template_id}

UUID of the Universal Template Event Template, if applicable.

${ops_trigger_universal_template_event_template_id}

UUID of the Universal Event Template, if applicable.

${ops_trigger_universal_event_template_id}

Resolves to the name of the variable being monitored.

${ops_trigger_variable_name}

Resolves to the current value of the variable being monitored.

${ops_trigger_variable_value}

Resolves to previous value of the variable being monitored.

${ops_trigger_variable_prev_value}

Resolves to the Name of the Task’s credential.

Resolves to the entire encoded URL containing the host, port, path and query.

${ops_url}

${ops_url} → http://localhost:8080/uc/resources/task?taskname=web-service-test

Resolves to the raw value of the URL field.

${ops_url_raw}

${ops_url_raw} → http://localhost:8080/uc/resources/task

Resolves to the URL host.

${ops_url_host}

${ops_url_host} → localhost

Resolves to the URL port.

${ops_url_port}

${ops_url_port} → 8080

Resolves to the encoded URL path.

${ops_url_path}

${ops_url_path} → /uc/resources/task

Resolves to the unencoded URL path.

${ops_url_path_unencoded}

${ops_url_path_unencoded} → /uc/resources/task

Resolves to the URL query.

${ops_url_query}

${ops_url_query} → taskname=web-service-test

Resolves to the unencoded URL query.

${ops_url_query_unencoded}

${ops_url_query_unencoded} → taskname=web-service-test

${ops_webhook_uac_task_status_changed_payload} →

{
  "attributes" : {
    "attempt" : 1,
    "calendar_id" : "77171434c0a801c9016d5b2b5d17ddee",
    "created" : "2024-10-21 12:17:16 -0400",
    "critical" : false,
    "current_retry_count" : 0,
    "early_finished" : false,
    "execution_user" : "ops.admin",
    "exit_code" : "0",
    "halt" : false,
    "instance_id" : "1729522829077855314PTRR635YO2WOS",
    "instance_name" : "sample",
    "instance_number" : 48,
    "invoked_by" : "Webhook: webhook-test",
    "late_finished" : false,
    "late_started" : false,
    "launch_source" : "Webhook",
    "launch_time" : "2024-10-21 12:17:16 -0400",
    "maximum_retries" : 0,
    "retry_indefinitely" : false,
    "security_name" : "sample",
    "simulate" : false,
    "source_version" : 4,
    "state_changed_time" : "2024-10-21 12:17:16 -0400",
    "status" : "Defined",
    "status_value" : 0,
    "task_id" : "65c18b06e420403191c9cf9c5da5b428",
    "type" : "Windows",
    "type_value" : 3,
    "updated" : "2024-10-21 12:17:16 -0400"
  },
  "businessServices" : [ ],
  "name" : "uac_task_status_changed",
  "templateId" : "7fda9c3f452e4fe78a4f9dc3afad8353",
  "webhookName" : "webhook-test"
}

Resolves to the file and member name containing the JCL script.

${ops_jcl_location}

Resolves to the job number assigned to the job by JES.

${ops_job_id}

Resolves to the file and member name of the JCL location containing a potential override JCL script.

${ops_override_jcl_location}

Resolves to the file and member name of the JCL location that was actually used for job submission.

${ops_submitted_jcl_location}

Resolves to the name of the Job Event being monitored.

${ops_trigger_job_event}

${ops_trigger_job_event} → Step End

Resolves to the value of the Job Event being monitored.

${ops_trigger_job_event_value}

${ops_trigger_job_event_value} → 4

Resolves to Job Id of the Job that was matched by the monitor.

${ops_trigger_job_id}

Resolves to Job Name of the Job that was matched by the monitor.

${ops_trigger_job_name}

Resolves to Step Name of the Job that was matched by the monitor.

${ops_trigger_step_name}

Resolves to User Id of the Job that was matched by the monitor.

${Resolves to Step Name that was matched by the monitor.}

Resolves to Condition Code of the Job that was matched by the monitor.

${ops_trigger_condition_code}

${ops_trigger_condition_code} → 0001