Save a BPMN diagram
The modeller batches changes as you work rather than reacting to every keystroke. Saving flushes those pending changes first, then writes the BPMN XML.
In practice this is invisible. It matters only if you are trying to save within a fraction of a second of a change.
#What this is for
Understanding what happens when you press save.
Diagnosing a save that seems to have missed the last edit.
Knowing what is actually stored.
#How it works
Action | How |
|---|---|
Flush | Pending modeller changes are applied first. |
Write | The BPMN 2.0 XML is written. |
Version | Each save creates a version you can restore. |
Close without saving | Discards the session's changes. |
#A few things that catch people out
Click away from a field you are editing before saving, so the field commits.
The close button is a cancel, not a save.
Saved files are standard BPMN 2.0 and open in other tools unchanged.
#Related
Simulate it before you publish it.
