01must proveProposed | The public interface changes status through Close, Reopen, Archive, Unarchive, Post and Unpost rather than a status field edit. | lifecycle | api, service | test |
02must proveProposed | Close accepts an Open batch and rejects other starting states. | lifecycle | service | test |
03must proveProposed | Reopen accepts Closed, Verified and Error, clears recorded errors, and leaves posted and archived batches to their separate Unpost and Unarchive actions. | lifecycle | service | test |
04must proveProposed | Archive accepts Open or Closed, stops document intake and posting, and clears the automatic close. | lifecycle | service | test |
05must proveProposed | Unarchive opens the batch without restoring the state it had before archive. | lifecycle | service | test |
06must proveProposed | The action catalogue offers Post, Close and Archive for Open; Post, Reopen and Archive for Closed; Reopen for Verified; Post and Reopen for Error; Unarchive for Archived; and Unpost for Posted, Downloaded or posting work unchanged for over an hour. | lifecycle | service | test |
07must proveProposed | Lifecycle actions require update permission, Post requires posting permission and Unpost requires unposting permission, with unauthorized actions omitted and execution refused before mutation. | permission | api, service, console | test |
08must proveProposed | An update-locked batch lists the applicable actions as disabled with a lock explanation and rejects their execution. | policy | service, console | test |
09must proveProposed | System batches offer no ordinary action and reject every such action because fiscal close and reopen control them. | policy | service | test |
10Proposed | Post, Archive and Unpost require confirmation, and Post warns when an Open batch will stop accepting documents. | policy | service, console | test |
11must proveProposed | Action execution rejects an unknown action or an extra batch reference, and accepts a reason or note without retaining it. | validation | api | test |