R12: AME: First responder Wins Method Not Effective With Two Approval Groups In Sequence (Doc ID 1532248.1)

Last updated on APRIL 28, 2023

Applies to:

Symptoms

When using voting method as "First Responder Wins" (or "Beat By First Responder") and one of the approver approves, then AME does NOT close the notification to the other users of the current approval group, before notifying the users of the next approval group.
  
Consider the following simple scenario:

• If 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	AAA	Group 2
  2	XXX	Group 2

• AAA, BBB and CCC are notified initially.
  
  
• Two(2) problems arise:
  1. 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.
  2. Only XXX is notified and AAA is NOT notified as his notification from previous step is not cancelled yet.
     
     

The Expected Behavior:

Group 1 is set to "First Responder Wins" so we expect the notifications of all approvers of Group 1 to be Closed / Cancelled, except for BBB who approved.
 
After applying <patch 8490741:R12.OIE.B>, the notifications for all other approvers of the same group get cancelled if one approver responds as expected but that only works fine if the "First Responder Wins" group is the final level and has no following approval group after it.  In our example, if approver Group 2 is NOT there, then things work fine and we do not face the 2 issues mentioned above).

Changes

This issue occurs even if the <patch 8490741:R12.OIE.B> has been applied.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.