Official version macro

The Official version macro renders the page’s current official version as inline text — a semantic version number like 1.2.3 that sits in the page body wherever you embed it. The value is whatever the Create official version action last stamped on the page, so the macro is the public surface for that action’s output. The action itself is documented separately on the Create official version page; this page covers only how the displayed value behaves.

Adding the macro

In the page editor, open the macro picker and choose Aura Workflows Official Version. The macro lands inline at the cursor as a single-line element, fitting cleanly into prose, a heading row, or a table cell next to a page link. There are no configuration options. The macro reads from the workflow currently applied to the page, so dropping it into the editor is enough.

A natural placement is next to a page title or alongside the Page freshness macro, where the version number doubles as a “last good revision” reference for the reader.

Behavior

The macro renders the latest stamped version as major.minor.patch — plain text rather than a coloured badge, so it slots into a heading or sentence without competing visually with the Status badge next to it. There is no “Official” prefix or label; just the number.

On a page that has no official version yet — either because no workflow is applied, or because the applied workflow has never reached a state with the action — the macro renders 0.0.0 rather than disappearing or showing a placeholder. That’s the same starting point the action increments from on its first run, so a page sitting at 0.0.0 is genuinely “no official version yet” rather than a missing-data error. There’s no separate “draft” or “unversioned” label; the zeroed number is the empty state.

When the Create official version action runs, viewers looking at the page at that moment see the number update without a page reload. Other open tabs and freshly loaded pages pick up the new value on their next render. Pairing the macro with the action in a Published state means a reader who watches the approval go through sees the version tick up in place as the transition completes.

When a Confluence page is exported to PDF or Word, the macro exports as the version text. Viewing or exporting an older Confluence revision of the page resolves to the official version that was current at that revision rather than the latest one, so a printout from three months ago carries the version number from three months ago.

The macro respects page permissions and nothing more. Anyone with view access to the page sees the version, the same way they’d see any other content on the page. There are no separate controls to gate, and the macro is read-only — it only reflects what the action wrote, never edits it.

When to use it

The official version is also visible in the page’s workflow history under the Official version event type, with every from-version and to-version pair, actor, and timestamp. The macro is for the cases where a single, current number deserves to live in the page body itself: at the top of a policy document, in a release-notes header, or next to a download link where readers expect a clear version reference. If you want the full sequence of bumps, send readers to the history; if you want the latest one called out where they’re already reading, embed the macro.

For the broader set of in-page elements, see the other macros.