Find out more about our consulting services. McLean. Boston. New York.
While developing websites and web apps is never an easy proposition, some parts of the process are getting easier and fulfill the promise of next generation platforms that trumpet easier application development. I have always been dubious about these claims, and the Adobe CQ5 Web Experience Platform defiantly offers up some challenges to even the most seasoned developers. Yet one aspect I have found really easy was building basic, but highly relevant and useful workflows.
I thought a step-by-step guide to building a workflow could benefit all developers using Adobe’s new suite of applications.
A new window will pop up with the workflow editor. It looks like this:
The next step is to define a participant step that represents the content editor who is starting the workflow after editing or creating content. This first step is a ‘Workflow Initiator Participant Chooser’ and looks like this:
These are the properties of the workflow initiator you just created:
Once you have created a workflow initiator you could have the workflow go directly to an approver or you could define a more complex approval process, while keeping it simple to implement. For example, let’s say that your content editor needs to have his or her work approved by their manager, the legal department and the marketing department. All we need to do to facilitate this is drag ‘And Split’ from the Workflow menu onto the canvas.
Now add the approvers to the 3 new slots on the canvas. Those approvers are represented as ‘Participant Steps’. For each Participant step you will need to define a user or group of users to conduct the action required. Each user or group of users identified for a workflow step will receive an email notice when action is required, if the ‘Notify user by email’ checkbox is selected.
As seen above, I have set a 24 hour timeout and the ‘Send Email’ as the ‘Timeout Handler.’ There dozens of other stock handlers, but your developers can obviously script something custom as well.
Now that we have added a couple of parallel approvers (which incidentally could also be organized in a sequential structure, but I figured that was obvious and didn’t show off as much of CQ5’s workflow capability), this is what our workflow looks:
Some organizations will add another approver at the end of the ‘And Split’ but for simplicity’s sake, let’s start wrapping this thing up. First we will version our content modification and then publish it. CQ5’s workflows come with versioning and publishing steps as built in functionality.
From the ‘WCM Workflow’ menu in Sidekick I added a ‘Create Version’ step and an ‘Activate Page’ step to complete the workflow. Don’t forget to save your work by clicking save in the upper left corner of the workflow editor. Now let’s have a quick look at how to use this workflow and what the notifications look like.
The content editor is done making their changes. Now they need to:
The options available are to ‘Complete’ (approve), ‘Step Back’ (reject) or delegate the workflow approval to another user.
Workflow approvers get to the page they are trying to review by going to the CQ5 inbox which is accessible from the main page once a user logs into CQ5. The inbox looks like your standard email inbox. A double click on the row will launch the page to be reviewed.
There it is: a workflow you could create in less time than it took me to type this blog post.
As always, feel free to drop a comment below and I’ll respond promptly.