Perform an Action on a Task

put

/ic/api/process/v1/tasks/{id}

Performs an action based on payload on a given task Number.

Request

Supported Media Types
Path Parameters
Body ()
Payload
Root Schema : payload
Type: object
Show Source
Nested Schema : action
Type: object
Show Source
Nested Schema : comment
Type: object
Show Source
Nested Schema : identities
Type: array
Show Source
Nested Schema : activityChanges
Type: array
Show Source
Nested Schema : assignees
Type: array
Show Source
Nested Schema : correlationKeyChanges
Type: array
Show Source
Nested Schema : dataObjectChanges
Type: array
Show Source
Nested Schema : instanceAttributeChanges
Type: array
Show Source
Nested Schema : processes
Type: array
Show Source
Nested Schema : FlowChangeItemReq
Type: object
Show Source
Nested Schema : correlationKeyChanges
Type: array
Show Source
Nested Schema : dataObjectChanges
Type: array
Show Source
Nested Schema : instanceAttributeChanges
Type: array
Show Source
Nested Schema : DataVariable
Type: object
Show Source
Nested Schema : QName
Type: object
Show Source
Nested Schema : identity
Type: object
Discriminator: type
Show Source
Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : task
Type: object

400 Response

The tasknumber is invalid.No action will be performed.

401 Response

Unauthorized

404 Response

Task not found.

409 Response

Conflict.

500 Response

Internal Server Error
Back to Top

Examples

The following example shows how to reassign task to a different user by using PUT request on the REST resource.

Send Request

https://example.com/ic/api/process/v1/tasks/<taskId>

Where,

  • example.com is the host where Oracle Integration is running.

  • <taskId> is the ID of task on which you want to perform the action.

    To get the task ID of the current user, see Retrieve a Task List.

Note: When you reassign to another user, delegate to another user, or request more information from another user, you need to add the Identities element in the request. When you claim(acquire) the task, do not specify the Identities attribute in the payload. Only the current user can claim the task.

Example of Request Body

Example 1:

The following example shows the request body when you reassign a task ID:

{
    "identities":
  [{
    "id":"<userId>","type":"user" 
  }],
   "action":
  {
   "id":"REASSIGN", "type":"SYSTEM" 
  }
 }

Where, <userId> is the user ID.

Example 2:

The following example shows the request body when you escalate or approve the task ID with a comment:

{ 
   "identities":[{"id":"jstein","type":"user" }],
   "action":{"id":"ESCALATE","type":"SYSTEM"}, 
   "comment":{"commentStr":"Some comment","commentScope":"BPM"}
 }

Example 3:

The following example shows the request body when you approve a task:

{
   "action":{"id":"APPROVE"} 
}

Example of Response Header

Status Code: 200 OK
Date: Wed, 27 Apr 2016 00:53:16 GMT
Content-Type: application/json

Example of Response Body

{
   "totalResult": false, 
   "hasMore": false, 
   "items": 
 [
  {
   "href": "http://example.com/ic/api/process/v1/tasks/200002",
   "length": 0,
   "rel": "self",
   "title": "Approver to review request and approve, reject, or request additional information",
   "hasSubTasksFlag": false,
   "isDocsEnabledFlag": false,
   "isConversationEnabledFlag": false,
   "hasSubTasks": false
  }
 ],
 "user": 
  { 
		"href": "http://example.com/ic/api/process/v1/identities/user/jsmith", 
		"length": 0, 
		"rel": "user" 
	}
 }
Back to Top