Order Management (OM) / Approvals Management Engine (AME) Not Working As Expected When Using Approval Group With Action Type 'First Responder Wins'
(Doc ID 2890089.1)
Last updated on OCTOBER 03, 2022
Applies to:
Oracle Order Management - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Approvals Management Engine (AME) has been enabled for OM RMA. Where there exists a Parallel approval - First responder wins action type is not working as expected
when there is an approver in Level1 and also found in next Level approval group(level 2) approved,
Workflow is getting stuck and not cancelling the other child workflows.
When using voting method as "First Responder Wins" and one of the approver 'approves', then AME does NOT close the notification to the other users .
EXPECTED BEHAVIOR
-----------------------
Expect workflow to progress with approval and cancel other child workflows.
It's working as expected when a different approver(s) who don't come up in subsequent levels approves.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super User
2. Navigate: Use RMA and AME Approval setup is like this:
Two dynamic approval groups are set up as follow:
Order Approver (Person) Approval Group
1 AAA Group 1
1 BBB Group 1
1 CCC Group 1
2 XXX Group 2
2 YYY Group 2
AAA, BBB and CCC are notified initially.
When BBB approves, AAA and CCC are beaten by first responder in the front end
but, their notifications are NOT cancelled in the backend for AAA and CCC and order is still stuck at approval.
Expectation is that approval should cancel AAA and CCC for Order 1, and approval should proceed to Order 2 for further approval.
Changes
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 |
Changes |
Cause |
Solution |
References |