My Oracle Support Banner

SOA 11g: Limit Allocation Duration Checkbox in Edit Participant not Working for Rule Based User Allocation (Doc ID 1589966.1)

Last updated on MARCH 27, 2020

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


In SOA there is a difference in handling task expirations when assignments are done using values or using rules.

A Human Task in a composite is of type serial and needs to be handled by a number of users, say <USER_NAME1> and <USER_NAME2> for example. When using the following task settings:

the task is assigned to <USER_NAME1> for 10 minutes. If <USER_NAME1> does not act within that time, the task is expired. If <USER_NAME1> acts (say approves), then task is assigned to <USER_NAME2> (as type is serial) who has again 10 minutes to act.

This is working as expected.

But when using rules for the assignment, e.g.

the task is assigned to first user <USER_NAME1> and waits there indefinitely if <USER_NAME1> doesn't act. If <USER_NAME1> approves, the task goes to <USER_NAME2> and waits there indefinitely again.

The above Rule-based scenario must work in the same way as the Value-based scenario.


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

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