Tasks Are Not Escalating To Managers After Completion Of Expiry Period After Migrating Project From 11g to 12g
Last updated on OCTOBER 05, 2017
Applies to:Oracle Business Process Management Suite - Version 184.108.40.206.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.
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