Tasks Are Not Escalating To Managers After Completion Of Expiry Period After Migrating Project From 11g to 12g
(Doc ID 2312892.1)
Last updated on FEBRUARY 05, 2020
Applies to:Oracle Business Process Management Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The issue takes place in the migrated project APBPM (which was originally created in 11g). The task NonPORequester has an escalation configured with a parameter coming from the instance.
When the escalation triggers, the task, instead of being escalated to the manager, the instance seems to move ahead and a new task is created because of the logic in the process (there is a flag to check whether the task is escalated and this flag returns false, in which case, the instance returns to the activity). As a result, the customer ends up with a list of tasks for the same activity... all of these tasks assigned to the same user.
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