updateMultipleTasks
- Description
- This transaction modifies the details of one or more task instances at the same time. Details that can be updated include TaskDueDate, Priority, TaskOwnerRole, TaskAction, and TaskStatus. The rules for updating tasks are applied to each of the task instances in the request. If one instance fails validation, the entire transaction fails.
- Web Services
- Operation name: updateMultipleTasks
- Example
- Change the due date and priority of five existing tasks.
Assign three tasks to a specific task owner.
Send all tasks belonging to a task owner who is on vacation back to the unassigned list.
Approve all the new subcategories in the "Electronics" category.
- Usage information
- This transaction is used in the same manner as the updateTask transaction. Almost all
attributes of an active task instance can be updated directly, with
the following exceptions:
- The Creator and CreationDate of the tasks cannot be updated.
- The TaskStatus can only be changed by providing an appropriate TaskAction.
- TaskOwnerRoles can only be updated if the tasks are not assigned to any TaskOwner.
The following are optional input:- TaskDueDate
- Priority
- TaskOwnerRole
- TaskOwner (must be accompanied by TaskActionType)
- TaskAction (for updating TaskStatus)
- CommentText
- Preconditions
- The task instance being updated must exist.
The task instance being updated must be active.
- Mandatory input
- For each task instance included in the request:
- TaskId
- TaskLastUpdateDate, if applicable
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- This transaction behaves the same way as updateTask. Since there are multiple
task instances involved in a single transaction request, if the update
for one task instance fails then the whole transaction request fails.
Input for the update, optionally including a task comment, must be provided for each task individually, even if the same value or text is intended for all the task instances in the request. The input is not automatically repeated for multiple instances.
- Request message
- <TCRMTxType> addTask
<TCRMTxObject> TaskBObj
<TCRMObject> List of TaskBObj
with optional business objects: list of TaskCommentBObj
- Response objects
- TaskBObj and, where applicable, WorkbasketBObj with a list of WorkbasketEntityBObj, and TaskCommentBObj
- Special note
- For related information, refer to the updateTask transaction.