My Oracle Support Banner

TaskService.updateTask() Operation Changed Functionality In 12.2.1.3 (Doc ID 2545565.1)

Last updated on FEBRUARY 07, 2020

Applies to:

Oracle Business Process Management Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, Orchestration Engine

ACTUAL BEHAVIOR
---------------
TaskService.updateTask() operation changed functionality in 12.2.1.3

When updating the task using TaskService.updateTask() operation in the API

If a task's (which is assigned to a particular Group and User) details/Payload is updated by the Process Owner/Admin (or any other user having the permission); then the task is also getting acquired by the process Owner/Admin. Overwriting the current assignment and/or acquisition. This is happening in SOA/BPM version 12.2.1.3.0 version and not in 12.2.1.2.0 and earlier versions.


For e.g. If a task with task number 12345 is assigned to Group XXX and user YYY; and that task’s payload value, say document Id is being updated by an admin ZZZ; then the task 12345 is getting acquired by ZZZ. Hence, YYY cannot see it in his/her list.
 

EXPECTED BEHAVIOR
-----------------------
That the task will remain assigned to the original assignee

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use REST API methods as admin user to update a task assigned to a user other than the admin user
2. Use the taskdetails method and notice that the task has now been acquired by the admin user.




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.