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
State content transitions
- Robert Alexander Marshall
State content transitions
These transitions are actioned by changes to the content e.g. page edits; reaching the state expiry date; content approval or rejection, or the completion of added tasks.
See also: States, Administrator state override, Tasks, Content reviews
Content review transitions
Similar to a state selection transition, but the focus is on reviewing content rather than choosing a state (the workflow determines which state to go to depending on outcome of the review).
The user chooses to Approve or Reject, and the workflow transitions to the appropriate state (as defined in the approved and rejected parameters). Approve and Reject buttons in the Workflow Popup.
{workflow:name=Content review}
{state:A|approved=C|rejected=B}
{approval:Review}
{state}
{state:B}
{state}
{state:C}
{state}
{workflow}
In workflow builder, the approved and rejected transitions for the content review are only available when a content review (approval) has been added to the state.
If the approval is added to the state but the Approved and Rejected transitions are not added
the workflow popup will still display the Approve and Reject buttons
if a user rejects or approves the content the workflow will simply remain in the current state
no transition will occur
any approval decision will still be recorded in the page activity report
You do not need to add both the Approved and the Rejected transition.
A content review transition may also occur when a trigger listens for an event and uses one of the following action macros to approve or reject the content.
Action macros related to approvals:
The following events are related to approvals:
pageapproved,Ânewsapproved,Âpagerejected,Ânewsrejected,Âpageapprovalassigned,Ânewsapprovalassigned,Âapprovalunassigned
Other related macros:
Related documentation:
Content expiry transition
A state can be given an expiry date, after which a transition can occur.
If the state expires whilst it is active
theÂ
duedate parameter determines the expiry datetheÂ
expired parameter specifies which state to transition toÂ
An expiry indicator appears in the workflow popup.
{workflow:name=State expiry}
{state:A|duedate=P1W|expired=C}
{state}
{state:B}
{state}
{state:C}
{state}
{workflow}The state expiry transition can be added to the state in the transition editor using workflow builder.
The transition only occurs if a due date has been added to the state and the Expired transition was added before the due date.
Any other of the state transitions can be added with the Expired transition.
Related macros:
The following events are related to expiry:
stateexpired
Related documentation:
Updated content transition
States can automatically transition should content be updated (edited).
The updated parameter specifies the state to transition to if the content is updated.
If used on a state that has final=true parameter, the workflow popup will show a message about the publishing process, otherwise, it will be empty.
{workflow:name=Content update}
{state:A|updated=C|final=true}
{state}
{state:B}
{state}
{state:C}
{state}
{workflow}The state Updated transition can be added to the state in the transition editor using workflow builder.
The transition occurs when the content is edited and the changes saved.
Any other of the state transitions can be added with the Updated transition.
Related macros:
Related events:
Â
pageupdated,Ânewsupdated,Âpagemoved,Âattachmentschanged,Âattachmentadded,Âattachmentupdated,Âattachmentremoved,attachmentversionremoved
Related documentation:
Tasks completed transition
States can automatically transition should all workflow tasks be completed.
The completed parameter specifies the state to transition to when all tasks are completed. Tasks are listed in the Tasks popup.
The task popup will need to be accessed to complete one or more workflow assigned tasks.Â
On completion of the task(s) the workflow will transition from state B to state C.
The state Tasks Completed transition can be added to the state in the transition editor using workflow builder.
This includes any uncompleted tasks added in other workflow states and still awaiting completion when the workflow transitions into this state.
Any other of the state transitions can be added with the Tasks Completed transition.
Related macros:
Related events:
- taskcreated, taskassigned, taskcompleted, taskexpired
Related documentation: