It should be possible analogous to locking and unlocking segments for all segments in the current filtering to set the editing status of a segment to the respective final editing status of the current segment for the current workflow step.

Add in the dropdown for "All segments":

EN: Set to final processing status
DE: Auf finalen Bearbeitungsstatus setzen

If done so, also the segments should be saved in the same way, as they would be saved, if saved manually.

A warning pop-up should tell the user:

EN: All segments will be saved to the task and and the task-TM, as they would when opened individually.
Two Buttons: "Continue" / "Cancel"

DE: Alle Segmente werden in der Aufgabe und im Aufgaben-TM gespeichert, wie wenn sie einzeln geöffnet würden.

Two Buttons: "Weiter" / "Abbrechen"

Questions to handle

• Bulk user feedback in case of errors (for this TRANSLATE-3543 'Move "toast" messages and warnings to an extra tabular view' should be implemented. Since this is not the case so far, we need to collect the errors by other means for now and visualize them. But there should not be a problem, because with the new bulk-way of saving segments to TM (see below) there is only one save request to t5memory and not many.
• Validate that bulk background-saving of segments to TM works and handles errors correctly
  • Coordinate with Sanya about how he does buld-updating of segments now with https://jira.translate5.net/browse/TRANSLATE-3305. Should be done based on that technical foundation in your case.
  • TM not reachable: segments are then saved later; issue is communicated to the front-end;
  • if segments can not be saved to the TM after X tries, all such update workers to the TM should be defunct, the PM informed (by adding a task log error only? seperate mail?)
  • The repeated save to the TM and threshold to interrupt should be completely handled in the level of that worker