I noticed that when selecting the "approve all items" action in a workspace, it also updated several items that had previously been rejected to approved. This would have caused a lot of issues if it was not caught before publishing the workspace.
I would suggest that the approve all button should only effect items that are in the "review" state, and not override any previous choices.
the confirmation prompt would definitely help. One of the issues that prompted this was that I hit the approve all items by accident while trying to publish a workspace, and had to go back and redo a bunch of rejected items.
Hi Pearce, To further improve clarity and prevent unintended actions, we’ll be adding a confirmation prompt when the “Approve All” option is selected. The message will inform users that the action will include all items with updates, including any currently in a “Rejected” state.
Example:
“Are you sure you want to approve all items? This includes any items currently in the Rejected state.”
Hi Pearce,
The “Approve All” action is designed to approve all items that have updates, regardless of whether they are in “In Review” or “Rejected” state. It’s intended for use cases where the user is ready to move all unpublished changes forward, including previously rejected items.
If your intent is to approve only items in the “In Review” state, we recommend using the Advanced Filter to filter by workflow status. From there, you can select and approve only the relevant items. Screenshot attached.
In your specific case, since some items were rejected and then “Approve All” was triggered, both Rejected and In Review items were approved. To avoid this, a suggested approach is:
Reject the necessary items.
Publish the workspace — this discards rejected changes.
Then, use “Approve All” to approve the remaining items.
That way, you ensure only the appropriate changes are approved and published.