...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Overview
Transitions are the paths between states.
If you tested the workflow we made in Lesson 2 - States, you will have noticed that every state could transition to every other state. That's the default behavior of states – unless you specify otherwise.
...
Before you start this lesson, transition to the Editing state of your workflow via the
...
Submit transition
We'll start with the transition from the Editing state to the Review state.
When we're in the Editing state, we only want a single choice – go to the Review state. For that, we need a submit transition.
Edit your workflow, as shown in the previous lesson, and add submit=Review parameter to the Editing state:.
| Code Block | ||||
|---|---|---|---|---|
| ||||
{workflow:name=Simple Content Production Process}
{state:Editing|taskable=true|submit=Review}
{state}
{state:Review|taskable=true}
{state}
{state:Published|final=true|taskable=true}
{state}
{workflow} |
...
| Info |
|---|
We put a | (a pipe character – that vertical, sometimes split, line near the Enter key on your keyboard) between the |
You can also add this using workflow builder to edit the transitions for the Editing state.
...
| Tip |
|---|
If you wanted to add a condition for the transition from the Editing state to the Review state to be active, for example, you only want the transition to be available if a specific label is present on the page. For this, you can use a |
...
This generates the following markup notation for the Editing state and the transition.
| Code Block |
|---|
{state:Editing|taskable=true}
{state-selection:states=Review|haslabel=projecta}
{state} |
What are parameters?
Most Macros can have settings, called parameters.
Usually, parameters look like name=value – for example, taskable=true. However, some macros support a special Unnamed first parameter that only needs the value part. You can see both types in the markup above.
...
In our Review state, we want two possible transitions:
If the content is
approved, we want to go to the Publish stateIf the content is
rejected, we want to go back to the Editing state
These must be used with an approval added to the state
name the approval
Review
Let's make those changes to our workflow:
| Code Block | ||||
|---|---|---|---|---|
| ||||
{workflow:name=Simple Content Production Process}
{state:Editing|taskable=true|submit=Review}
{state}
{state:Review|taskable=true|approved=Published|rejected=Editing}
{approval:Review}
{state}
{state:Published|final=true|taskable=true}
{state}
{workflow} |
Workflow builder can be used to add an approval to the Review state.
...
Once the approval is added, the Approved and Rejected transitions can be added to the state using the workflow builder Transitions editor for the Review state.
...
| Info |
|---|
The Approved and Rejected transitions are only available after an approval has been added to the state. |
Published transition
Once content is Published, we generally leave it in that state. However, what happens if someone edits it?
We can use the updated transition to automatically move to another state – like the Editing state – if someone edits the content. Here's our updated workflow:
| Code Block | ||||
|---|---|---|---|---|
| ||||
{workflow:name=Simple Content Production Process}
{state:Editing|taskable=true|submit=Review}
{state}
{state:Review|taskable=true|approved=Published|rejected=Editing}
{approval:Review}
{state}
{state:Published|final=true|taskable=true|updated=Editing}
{state}
{workflow} |
In workflow builder, add an Updated transition to the the Published state.
...
Test it
Now, try testing the transitions in your workflow.
...
It's time for the next lesson:.