Ask for Approval did not update group member's approval state to 'no longer required' immediately after first approver approved approval - Known Error

Ask for Approval did not update group member's approval state to 'no longer required' immediately after first approver approved approval Description Ask for Approval did not update group member's approval state to 'no longer required' immediately after first approver approved approval

Steps to Reproduce

1. Create a flow in Flow Designer: (screenshot attached) 1.1 In TIGGER 1.1.1 Table: incident 1.1.2 Condition: short description starts with DEF0399604 1.2 In ACTIONS 1.2.1 Choose Ask for Approval and add the following conditions - Record: Trigger - Record Created > Incident record - Rules: Reject when: Anyone rejects: Database, Network, CAB Approval OR Approve when: Anyone approves: Database AND Anyone approves: Network AND Anyone approves: CAB Approval 2. Activate the flow 3. Create an incident with short description starts with "DEF0399604". Make sure it triggers the flow. There should be 12 sysapproval_approver records and 3 sysapproval_group records created and associated with the incident record. 4. Approve cab approver's approval.

Expect: the state in the approval records of other group members in group 'CAB Approval' should be updated to 'no longer required'. Actual: the state in the approval records of other group members in group 'CAB Approval' remains 'required'

Workaround No workaround for this defect on Utah Patch 0 through Utah Patch 4.

Starting in Utah Patch 5, customers can revert back to previous behavior using the following:

create sys property "com.glide.hub.flow.approval.function.early_terminate" and set it to true to make this work, this is not a workaround, this is the fix for this defect.

With the property (the fix in place) users should be able to see the behavior of Ask for Approval changed back to pre-Utah when they approved/rejected the approval records.