Task and sub-task APIs

Companies that own or link to Agile Process Teams use these APIs to add, update, and complete tasks. Tasks are based on pre-defined task templates, which determine the default values that populate for the task, any sub-tasks that automatically generate, and the extent to which the task can be modified by users.

Tasks are split into one or more sub-tasks, which are smaller, assignable portions of work that are completed as part of of the parent task. Sub-tasks are attached to tasks and managed by separate APIs.

Use the Template APIs to manage the task templates and any template-defined sub-tasks for your company.

Add Task

Owners and Partners use this API to add a new task to the Owner's company network, including any initial comments or file attachments. The response returns a generated identifier for the new task.

New tasks are assigned the ToDo base state by default.

Edit Task

Owners and Partners use this API to do the following: 

  • Modify an existing task with new, updated, or corrected information (e.g. adding a description, updating the responsible party, fixing a typo).
  • Update the workflow state (e.g. manually transitioning the base state from ToDo to InProgress to indicate that the work assigned in the task has started).
Use the following APIs to modify other portions of the task process:

Copy Task

Owners use this API to copy an existing task. Boolean fields determine which section values are copied to the new task (e.g. copy all values from the General section but not the related processes from the original task). The new task is created with a new identifier and automatically set to the ToDo base workflow state.

Close Task

Owners use this API to close a task to indicate the work is complete. The closed task transitions from its current base state (either ToDo or InProgress) to a Closedstate. Closed tasks can be edited or reopened by users with the requisite permissions.

Reopen Task

Owners use this API to reopen a closed task with all information intact. Returns the identifier for the reopened task with the base workflow state updated from from Closed to InProgress. Reopened tasks cannot be manually transitioned back to the ToDo state.

Add Sub-Task To Task

Owners and Partners use this API to add a new sub-task to an existing task. Partners can only add sub-tasks to tasks that contain at least one sub-task that they have already been assigned to.

Sub-tasks can be added only if isAddRemoveSubtaskAllowed is set to true in the task template .

Edit Sub-Task On Task

Owners and Partners use this API to do the following: 

  • Modify a sub-task associated with a parent task with new, updated, or corrected information (e.g. adding Partner information, fixing a typo, updating the assigned users).
  • Update the workflow state (e.g. manually transitioning the base state from ToDo to InProgress to indicate that the work assigned in the sub-task has begun).
Use the comment APIs to add, edit, or delete comments and file attachments from an existing task or sub-task.

List Sub-Task For Task

Owners and Partners use this API to view all sub-tasks associated with a specified task. Returns all sub-tasks currently attached to the task (isDelete = false). Partner users can only view sub-tasks that they are assigned to.

Submit Sub-Task To Partner

Owners use API to manually submit a sub-task to the Partner specified in the sub-task partnerId. This cannot be undone.

Upon successful response:

  • isSubmittedToPartner updates to true.
  • The Partner is notified of the sub-task on their network.
  • The parent task and sub-task becomes visible to the Partner.
Submitting the sub-task to Partner does not update the sub-task workflow state. Use the Edit Sub-Task On Task API to manually transition the sub-task from one workflow state to another.

Close Sub-Task

Owners and Partners use this API to close a sub-task to indicate the assigned work is completed or no longer applicable. The closed sub-task transitions from its current base state (either To Do or In Progress) to a Closed state. Closed sub-tasks can be edited or reopened by users with the requisite permissions.

Reopen Sub-Task

Owners and Partners use this API to reopen a closed sub-task with all information intact. Returns the identifier for the reopened sub-task with the base workflow state updated from Closed to InProgress. Reopened sub-tasks can only be returned to the InProgress base state; they cannot be manually transitioned back to ToDo.

A sub-task cannot be reopened if the parent task is already closed. The parent task must be reopened first using the Reopen Task API.

Remove Sub-Task From Task

Owners use this API to remove a sub-task from a task. Upon successful removal, the sub-task cannot be re-added and will display as a deleted (isDelete = true) in the activity history.

The following must be true to remove a sub-task: 

  • The task template must allow sub-tasks to be modified (isAddRemoveSubtaskAllowed must be true in the task template).
  • The sub-task cannot already be submitted to a Patner (isSubmittedToPartner must be false in the sub-task).

Add Comment

Owners and Partners use this API to add comments and attach files to an existing task or sub-task.

Edit Comment

Owners and Partners use this API to modify or remove existing comments and files attached to an task or sub-task. Comments and attachments can only be edited by the user that created the comment or attachment.

Upon successful removal, the attachment is marked deleted (isDelete = true) and will display as a deleted comment in the activity history for the task or sub-task.

List Comments

Owners and Partners use this API to return all comments and attachments for a specified task or sub-task. Return includes all comments and attachments associated with the task or sub-task that the user is authorized to view. Comments and files are listed with additional information (e.g. comment identifier, AWS S3 location of the file), and any deleted items are marked as isDelete = true.

Toggle User Follows Process

Owners and Partners use this API to start or stop following a task or sub-task. Users that follow a task or sub-task receive notifications on updates to the request based on the APT notification settings for their profile. When users stop following the task or sub-task, notifications will cease.

Get Activity History

Owners and Partners use this API to return the full activity history for a specified task or sub-task. The response includes all recorded audit activities and updates to the record.