Three years ago I wrote about what I call the "Back to the Web" pattern. This week that pattern came up twice and we added some functionality related to it. Read on to refresh your memory.

In last month's post we discussed two approaches to the Force Steps Pattern based on business maps. This month we study the third option commented there based on the Process Flow modules with a very complete guest post from one of our team members Franceska who has been testing and implementing it for the past weeks.

On occasions, we want to force our users to follow all steps defined in a business process. There are many variations on this idea and many ways to implement it. In this post, we will see a validation and business map solution based on steps defined in a picklist.

Do you need the ability for clients to click a button in an email and have it automatically change the Status of an associated Ticket? If so, you have come to the right place to learn how to implement what I call the Get back into the web pattern.

A very common use case in business software applications is to have a set of defined steps or a procedure to follow when an event happens. The implementation pattern explained here shows how to do this in coreBOS.