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

Last updated on NOVEMBER 03, 2016

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 "benmanager1" and "benmanager2" for example. When using the following task settings:

the task is assigned to benmanager1 for 10 minutes. If benmanager1 does not act within that time, the task is expired. If benmanager1 acts (say approves), then task is assigned to benmanager2 (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 benmanager1 and waits there indefinitely if benmanager1 doesn't act. If benmanager1 approves, the task goes to benmanager2 and waits there indefinitely again.

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


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