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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

If you want to show different versions of metadata depending on if your users are viewing the draft or published  versions when using same-space publishing you can use the view parameter of the {set-message} macro together with a metadata variable.

The value of the metadata ReleaseVersion is set when the transition to the Approved state occurs using the set-metadata macro.


Workflow template

{workflow:name=Using set message published and draft view}
    {description}
        The Simple Approval Workflow
    {description}
    {state:In Progress|approved=Approved|taskable=true}
        {approval:Review|assignable=true}
    {state}
    {state:Approved|final=true|updated=In Progress|hideselection=true}
    {state}
    {trigger:statechanged|state=Approved}
        {set-metadata:ReleasedVersion}@version@{set-metadata}
        {set-message:view=published}
        Published view
        ||Released Version |{get-metadata:ReleasedVersion}|
        {set-message}
        {set-message:view=draft}
        Editor view
        ||Released Version|{get-metadata:ReleasedVersion}|
        {set-message}
    {trigger}
    {trigger:statechanged|state=In Progress}
        {set-message:view=draft}
        Draft view
        ||Version |{get-metadata:version}|
        {set-message}
    {trigger}
{workflow}

Related Pages

First trigger

The published content will display the view=published message on the public URL for the content

  • <hostname>/display/public/<spacekey>/<pagename>



(info) A user with edit permission viewing content in the Approved state will, by default, not see the public URL content.  To avoid this confusion, the first trigger has a second set-message action to cater for this scenario so that a user with edit permission will see a message in the Approved state.



Second trigger

The draft content will display the view=draft message. 


  • No labels