Skip to content
Taking it back: void, undo and discard · presentation 4 of 4 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Taking it back: void, undo and discard · presentation 4 of 4

Undo to Draft is not a rewind

You know exactly what taking a finalised document back to Draft does and does not undo, why re-finalising will not post it again…

One subscriber

Step 1 — Know how small the undo actually is

You will know what the button really does.

What this step names
  1. The source order gets its outstanding quantity back
  2. The document stops holding it
  3. The links between them are released

Step 2 — Know what stays posted

You will know what is still true about a document that says Draft.

Where this step sits
    flowchart TD
  s1["1. Know how small the undo actually…"]
  s2["2. Know what stays posted"]
  s3["3. Understand why re-finalising will not post…"]
  s4["4. Know what happens if you edit…"]
  s5["5. Know what the button was actually…"]
  s6["6. Know how Discard differs…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

The part nobody expects

Step 3 — Understand why re-finalising will not post it again

You will avoid the one mistake this whole presentation exists to prevent.

Where this step sits
    flowchart TD
  s1["1. Know how small the undo actually…"]
  s2["2. Know what stays posted"]
  s3["3. Understand why re-finalising will not post…"]
  s4["4. Know what happens if you edit…"]
  s5["5. Know what the button was actually…"]
  s6["6. Know how Discard differs…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — Know what happens if you edit in between

You will have the rule in one sentence.

What you do
  1. Pull a finalised invoice back to Draft, change a quantity or a price…

Step 5 — Know what the button was actually built for

You will read the design rather than the label.

Where this step sits
    flowchart TD
  s1["1. Know how small the undo actually…"]
  s2["2. Know what stays posted"]
  s3["3. Understand why re-finalising will not post…"]
  s4["4. Know what happens if you edit…"]
  s5["5. Know what the button was actually…"]
  s6["6. Know how Discard differs…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Know how Discard differs, and the route with no fan-out at all

You will have the last two operations straight.

What you do
  1. Ask before anyone wires it into a workflow

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.