Task Web Services
Overview
Universal Controller supports the following RESTful-based web services for Task operations.
Formatting specifications for each web service, including details about parameter requirements, are provided.
Common Web Services
The following web services are common to all Task types:
Detailed information for each of these web services is provided on this page.
Task-Specific Web Services
The following web services are specific for each Task type:
Create a Task
Modify a Task
Read a Task
For detail information about these task-specific web services, see:
Delete a Task
| Description |
|---|---|
URI | |
HTTP Method | DELETE |
Description | Deletes the specified task. |
URI Parameters | See Delete a Task: URI Parameters, below. |
Example URI | |
Authentication | HTTP Basic |
Example Response |
|
Delete a Task: URI Parameters
Parameter | Description | Specifications | Required | Mutually Exclusive With |
|---|---|---|---|---|
| ID used within the Controller to identify this task. | String; URI parameter. | Y |
|
| Name used within the Controller to identify this task. | String; URI parameter. | Y |
|
Launch a Task
| Description |
|---|---|
URI | |
HTTP Method | POST |
Description | Launches the specified task. |
Example URI | |
Authentication | HTTP Basic |
Consumes Content-Type | application/xml, application/json |
Produces Content-Type | application/xml, application/json |
Example Request | |
Example Request for Task-Related Records | |
Request Properties | |
Request Task-Related Records Properties | |
Example Response |
Launch a Task: XML and JSON Examples
Examples | XML | JSON |
|---|---|---|
Example Request for Task | <task-launch>
<variables />
<virtual-resources />
<name>Timer 0</name>
<timeZone>America/Halifax</timeZone>
<virtualResourcePriority>10</virtualResourcePriority>
<hold>yes</hold>
<holdReason>Waiting for input</holdReason>
<launchReason>Testing</launchReason>
</task-launch> | {
"variables": null,
"virtual-resources": null,
"name": "Timer 0",
"timeZone": "America/Halifax",
"virtualResourcePriority": 10,
"hold": "yes",
"holdReason": "Waiting for input",
"launchReason": "test"
} |
Example Request for Task-Related Records | ||
Example Response |
|
|
Launch a Task: Request Properties
Property | UI Field Name | Description | Specifications | Required |
|---|---|---|---|---|
| Hold on Start | Indicates that when the task is launched, it appears in the Activity Monitor with a status of Held. The task runs when the user releases it. | Valid values = Yes,Y,true | N |
| Hold Reason | Information about why the task will be put on hold when it starts. |
| N |
| Launch Reason | Reason for the task launch |
| N (Y if Task Launch Reason Required system property is True.) |
| Task Name | Name of the task. |
| Y |
| Simulate | Specifies if the workflow should execute under simulation mode. | Boolean; Valid values: true/false. Default is false. | N |
| Time Zone | Time Zone in the which the task is launched. |
| N |
| Vertex Selection | Specifies Root Vertices and/or Specific Vertices to be included in the triggered workflow. A vertex can be specified by If you specify a To indicate a vertex selection is a Root Vertex, set the vertex root attribute to true. If vertex root attribute is unspecified or false, it indicates a vertex selection is a Specific Vertex. Duplicate vertex specifications are ignored and do not prevent the operation from completing. | XML
JSON
| N |
| Virtual Resource Priority | Priority for acquiring a resource when two or more tasks are waiting for the resource; applies to all resources required by the task. | Integer; Valid values: 1 (high) to 100 (low). Default is 10. | N |
Task-Related Records Properties: Variables
Task-Related Records Properties: Virtual Resources
The virtual resource dependencies specified in virtual-resources are merged with the default virtual resource dependencies:
If a default virtual resource dependency already exists for a specified virtual resource amount, the virtual resource dependency is updated.
Any virtual resource specified with an amount of 0 is dropped from the default virtual resource dependencies; if the virtual resource did not exist as a default dependency, the command will fail.
If a default virtual resource dependency does not already exist for a specified virtual resource amount, the virtual resource dependency is added. |
List All Workflows That a Task Belongs To
| Description |
|---|---|
URI | |
HTTP Method | GET |
Description | Retrieves a list of parent workflows that a task belongs to. |
URI Parameters | See List All Workflows That a Task Belongs To: URI Parameters, below. |
Example URI | |
Authentication | HTTP Basic |
Consumes Content-Type | n/a |
Produces Content-Type | application/xml, application/json |
Example Response | See List All Workflows That a Task Belongs To: XML and JSON Examples. |
Response Properties | See List All Workflows That a Task Belongs To: Response Properties. |
List All Workflows That a Task Belongs To: URI Parameters
Parameter | Description | Specifications | Required | Mutually Exclusive With |
|---|---|---|---|---|
| ID used within the Controller to identify this task. | String; URI parameter. | Y |
|
| Name used within the Controller to identify this task. | String; URI parameter. | Y |
|