Skip to main content

Improve Playbook / Checkpoint UX + Settings

Feature ideasSend and sign

Improve the Interface to follow a central “Approvals” Logic, i.e. Approvals are the leading topic and the requirement for an approval can be either triggered by a stage (checkpoint), a metadata (conditional checkpoint, see Implement Conditional Checkpoints) or the content (playbook, triggering a checkpoint).

This needs to be re-structured so it is clearer for the user.

+ autoapply
+ cancel (e.g. when document's content has changed, playbook should be canceled)
+ rerun

2 comments

Log in to comment and vote

Comments2

  • Aquamarine Astronomer

    Team•

    Oct 30

    •

    Merged request

    •

    3 votes

    Playbook column in documentlist

    Add a Playbook column to the document list that displays the number of flags (red, yellow, green) as well as the current progress of the playbook.

    DE:

    Füge der Dokumentliste eine Playbook-Spalte hinzu, die die Anzahl der Flags (Rot, Gelb, Grün) sowie den aktuellen Fortschritt des Playbooks anzeigt.

  • Teal Astronaut

    Team•

    May 14

    •

    Merged request

    •

    4 votes

    Delete / archive / deactivate playbook runs on a document

    Problem: During playbook setup, the user repeatedly runs → tweaks → re-runs. All runs remain visible on the document, cluttering the view; only the latest run is relevant.

    Benefit: keeps the document clean; avoids confusion for other internal viewers.

    Potential solutions: delete playbook runs, archive old runs, or add a “show only latest run” toggle.