(Doc ID 1079054.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version 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.

Example given;

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.

Example of Routing Slip
<participants isAdhocRoutingSupported="false">
<stage name="Stage1">
<participant name="Reviewer">
<resource type="XPATH" identityType="user">oraclesystemuser</resource>
<participant name="Vendor">
<resource type="XPATH" identityType="user">USER2</resource>
<participant name="FinalReviewer">
<resource type="XPATH"identityType="user">USER3</resource>

The issue is that the task completes prior to overriding.
If you login to worklist as weblogic user, the task is displayed as completed.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms