11G HUMAN TASK: OVERRIDEROUTINGSLIP MARKS TASK AS COMPLETED
(Doc ID 1079054.1)
Last updated on JUNE 18, 2018
Applies to:Oracle(R) BPEL Process Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Oracle Business Process Execution Language (BPEL)Process Manager is a part of the Oracle SOA Suite.
In Oracle BPEL after initiating a human task, you override its routing slip to place routing rules dynamically for the task.
You are using overrrideRoutingSlip operation
provided by task service .
However, the operation marks the task as completed without any outcome.
This means the workflow cannot go ahead with this new routing slip.
User "weblogic" is the initator of the task.
You have defined a routing rule to assign the task to user "oraclesystemuser".
In the routing slip, you have provided users and the task assignment should be overridden by the routing slip, i.e the task will not be assigned to"oraclesystemuser" but should be assigned to first user defined in the routing slip.
<resource type="XPATH" identityType="user">oraclesystemuser</resource>
<resource type="XPATH" identityType="user">USER2</resource>
If you login to worklist as weblogic user, the task is displayed as completed.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|