Expiry For Second Level Of Parallel Approvers
Last updated on AUGUST 13, 2016
Applies to:Oracle SOA Platform - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Consider a Human Task use case , which is designed with multilevel approver, with the first level as "single participant" and the next level as "parallel participants".
The expiry for the second level is set to 5 minutes :
The task is initiated from a BPEL composite and approved by the first level participant.The task is then allowed to expire at the second level.
The expectation is for the state of the task to be "EXPIRED" However , it's observed that the overall state of the task is “COMPLETED“ instead of "EXPIRED".
This issue can be noticed from the "Audit Trail" of the composite.
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