This site has moved to the integrated Appfire documentation and information site for our apps.
From February 2024 this site is no longer updated.
Take a look here! If you have any questions please email support@appfire.com
Use metadata to increment a content version
- Robert Alexander Marshall
Overview
Different events can be used to increment a composite version number.
The workflow uses the following trigger actions
initialize a version value using the set-metadata macro
increment the version value using the increment-metadata macro using different triggers for each element of a composite version number
You will need to refresh the page content to view changes in the metadata value if you use the get-metadata macro on the page to display the metadata value.
These examples only work when the workflow is applied as a space workflow. The space workflow must be active to listen for the pagecreated event to initialize the metadata value.
Published version
Confluence versions change on each page update. You can use a metadata value and the increment-metadata macro to keep track of the number of times your document transitions to the final state - effectively using this metadata value as your published version value.
{workflow:name=Increment a Metadata Version}
{description}
A simple approval workflow with use of metadata to identify the published versions. The simple version is incremented on approval of content
{description}
{pageheader}
||Type|| Version||Version Number||
|Page metadata|Publishedversion value|@publishedversion@|
|Confluence metadata|Confluence version value|@version@|
{pageheader}
{state:Review|approved=Approved|taskable=true}
{approval:Review}
{state}
{state:Rejected|submit=Review|taskable=true}
{state}
{state:Approved|final=true|updated=Review|hideselection=true}
{state}
{trigger:pagecreated}
{set-metadata:publishedversion}0{set-metadata}
{trigger}
{trigger:pageapproved|approval=Review}
{increment-metadata:publishedversion}
{trigger}
{workflow}The workflow is added and enabled as a space workflow in the space tools Document Management dashboard for the space.
On creating a page in the space, the value for the metadata publishedversion is set as”0”.
The metadata publishedversion value is set using the set-metadata macro.
In the workflow page header added to the page as a table the publishedversion metadata value is retrieved by the workflow using @publishedversion@.
The page has not yet been approved as there has been no transition to the final state - the Approved state in our workflow.
Each page edit updates the Confluence version.
Approving the page in the Review state, transitions the workflow on the page to the Approved state.
The workflow trigger listening for this page approval event increments the value of the metadata publishedversion.
Editing the page in the Approved state transitions the workflow on the page back to the Review draft state.
Each subsequent approval of the page and transition to the Approved state increments the publishedversion value.
Composite major-minor version content
{workflow:name=Increment a Metadata Version major minor}
{description}
A simple approval workflow with use of increment-metadata macro to set the major and minor versions. Major version incremented on approval of content, minor version on any update on the approved content
{description}
{state:Review|approved=Approved|taskable=true}
{approval:Review}
{state}
{state:Rejected|submit=Review|taskable=true}
{state}
{state:Approved|final=true|updated=Review|hideselection=true}
{state}
{trigger:pagecreated}
{set-metadata:currentversion}0.0{set-metadata}
{trigger}
{trigger:pageupdated}
{increment-metadata:currentversion|increment=0.1}
{trigger}
{trigger:pageapproved|approval=Review}
{increment-metadata:currentversion|increment=1.0}
{trigger}
{workflow}Here's how each trigger action works.
Trigger Event | Action macro | Notes | Confluence and Metadata version displayed on content using |
|---|---|---|---|
|
| o | |
|
| Editing the page updates both the
| |
|
| On approving the page and transitioning to the Approved state the
| |
|
| Editing the page in the Approved state
| |
|
| Editing the page in the draft Review state, with a previously approved version
| |
|
| On approving the page and transitioning to the Approved state the
| |
An individual reviewer rejection decision on its own does not impact the metadata currentversion value.
Manage composite major-minor-patch version of the content
Additional triggers may be useful to initiate major-minor-patch value changes.
This second example below uses the increment-metadata macro to support the custom versioning of a page using a composite numeric metadata value.
The elements of the composite version are incremented when different specific events occur.
{workflow:name=Composite Increment Metadata}
{state:Draft|submit=Review}
{state}
{state:Review|approved=Approved}
{approval:Review|assignable=true}
{state}
{state:Approved|final=true|submit=Draft}
{state}
{trigger:pagecreated}
{set-metadata:comp-version}
0.0.1
{set-metadata}
{trigger}
{trigger:pageupdated}
{increment-metadata:comp-version|increment=0.0.1}
{trigger}
{trigger:statechanged|state=Review}
{increment-metadata:comp-version|increment=0.1.0}
{trigger}
{trigger:statechanged|state=Approved}
{increment-metadata:comp-version|increment=1.0.0}
{trigger}
{workflow}The metadata name and initial value are set on the creation of the page using a trigger macro and the set-metadata action macro.
{set-metadata:comp-version}0.0.1{set-metadata}
A version change will occur:
for every page edit (a PATCH version change)
on a state change to the Review state(a MINOR version change).
on a state change to the Approved state (a MAJOR version change).
Metadata value initialization
Page creation creates the metadata comp-version and sets the initial value as 0.0.1
{set-metadata:comp-version} 0.0.1 {set-metadata}
o
Minor element value update
A state change to the Review state will update the second numeric element (MINOR element)of the version by 1.
The workflow uses a trigger macro on the statechanged event for state=Review and the increment-metadata action macro.
{increment-metadata:comp-version|increment=0.1.0}
o
This also resets the final numeric element to zero e.g. a version value 2.1.3 will change to 2.2.0.
Major element value update
A state change to the Approved state will update the first numeric element (MAJOR element) of the version by 1.
The workflow uses a trigger macro on the statechanged event for state=Approved and the increment-metadata action macro.
{increment-metadata:comp-version|increment=1.0.0}
o
This also resets the second numeric element and the final numeric element to zero e.g. the version 2.2.5 will change to 3.0.0.
Patch element value update
A page edit will increase the final numeric element (PATCH element)of the version using a trigger macro on the pageupdated event and the increment-metadata action macro.
{increment-metadata:comp-version|increment=0.0.1}
o
The final numeric element of the version will increment by 1 for a page edit in any of the workflow states.