When a document is sent to multiple users in the same approval sequence, and one approver approves it, the document is correctly marked as Released, but it still shows up in the "Request to Approve" page for the others in that sequence.
This can be confusing for the remaining approvers, who think they still need to take action. It often leads to unnecessary reviews, follow-ups, or questions, even though the document is already approved and done.
It would be helpful if:
-- The approval request was automatically removed from the other same-sequence users once one person approved.
OR
--The system showed a clear status or tag like "Already Approved" or dimmed the entry to indicate no further action is needed.
This small change would really improve clarity, reduce confusion, and save time for teams. Rejection already removes the request from everyone, so it would make sense for approvals to behave similarly.
Comments
If I understand correctly, you've setup a workflow where you have multiple approvers getting the same approval notification at the same time, but only 1 person needs to approve. If this was the case, you had to alter the standard condition and made the step where the document is released to Always run. The problem here is that the standard response expects the pending approval condition to be zero hence it doesn't run a critical step "Approve the approval request for the record." What this step does is, it'll go through each open approval entry for the record and close them out as if approved. This same step will also notify the approver that the record has been approved. Edit your workflow and add the missing step to the line where the release document resides and you should be good to go.
Category: Development
I encountered a similar issue while working with one of our clients.
Category: Development