Have you ever wondered why "unrelated" records
got processed in workspaces review when using
one of the mass actions?
Simply because the workspace JavaScript component
is using an internal array, holding all selected records.
This internal array however was only reset on leaving
the module.
Therefore, all records which had been selected since
the module was accessed were taken into account
when a mass action was executed. This did not only
affect records which were unchecked prior to mass
action execution, but also records which were no
longer visible at this time, e.g. due to an applied
filter. In the worst case, that led to completely
unrelated records got published to a live workspace.
This is now fixed by resetting the mass action state
whenever the listing gets updated. This way, only
the selected records in the current view are taken
into account when executing a mass action.