Revision Management Pane v2
The Workflow designer's Manage revisions pane displays saved source revisions for the selected Environment and contains the control used to save a new revision.
Revision history is available when the Tenant includes Revision Management.
Open Manage revisions
Open a Workflow in Design, then use either of these controls:
- Click
Savein the top bar. The pane opens and focuses the commit-message field. - Click
Manage revisionsin the right action bar.
Saving is enabled only in the first Environment. When Release Management is enabled and you select a later Environment, its design is read-only and the top-bar Save control is unavailable.
Revision rows
Revisions are shown as a timeline. Each row can display:
| Item | Description |
|---|---|
| Time | The revision timestamp in yyyy/MM/dd HH:mm:ss form. |
| Message | The supplied commit message, or No commit message. for older records without one. |
| File hash or revision | The first eight characters of the content FileHash, falling back to the commit ID. |
| User | The account that created the revision, including its avatar and account link when available. |
| GitHub | Opens the backing commit in a new tab when the revision supplies a commit URL. |
| Open revision | Opens that Environment and commit in a new designer tab. |
Opening a historical revision does not replace the latest source. It loads that snapshot for inspection. If you open it in Test and save it, Flowgear uses the latest update hash and records the loaded content as a new latest revision. This is the supported rollback pattern.
Search the history
Search matches the revision's commit hash, message, username, and formatted timestamp.
The search control has two modes:
- Match mode keeps the timeline visible and highlights matching revisions.
- Filter mode shows only matching revisions.
The result summary reports the number of matches and the number of loaded revisions searched. Revision history is loaded in pages. Click Fetch earlier when it appears to add older results; a search only covers revisions that have been loaded so far.
If there are no matches, clear or adjust the search, or fetch earlier revisions when that action is available.
Save a revision
At the bottom of the pane, Save a new commit contains:
- An optional
Commit messagefield. - A clear button when text has been entered.
- A ✓ button that saves the Workflow.
Press Enter to save or Escape to clear the message. If the message is empty, the new revision uses (No description).
The Console saves and publishes the revision to Test. A new Workflow is also enabled automatically in Test. If the source is saved but publish fails, the Console preserves the new FileHash and reports the publish problem under Problems.
The pane refreshes with the new revision and normally closes shortly after a successful save. If the content hash did not change, no new history entry is added.
You do not need to save before a designer Debug run. Debug can execute the current unsaved design; saving is what makes the source durable and publishes the Test revision.
See also
See Revisions and Releases for the lifecycle and Release Management Pane for promotion.