Manually Added Approver In BPM Approval Flow Disappears If Participant Is Of Single Type
(Doc ID 2547797.1)
Last updated on MARCH 12, 2021
Applies to:
Oracle Fusion Enterprise Contracts Management Cloud Service - Version 11.13.19.01.0 and laterInformation in this document applies to any platform.
Symptoms
A manually added approver to a BPM human workflow ,when the corresponding workflow participant type is Single , is removed from the approval workflow in either of the below use cases:
- The initiator adds the approver, saves it and then submits the transaction to approval
- One of the workflow participants, having the privilege to add approvers to it, adds a new approver, saves it and then acts upon the transaction
Even though the application allows the new approver to be saved, it is removed afterwards from the approval chain with no notification or error thrown to users.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |