In this article we will discuss about difference between sequential and state machine workflow in SharePoint. You can also check my last article on how to create SharePoint sequential workflow using Visual Studio 2010 in SharePoint 2010 here
. It is really depends on the business process whether we have to go for Sequential workflow or State Machine workflow.
- It looks very simple like flow chart.
- Steps within the workflow execute sequentially, one after another in the particular order.
- A sequential workflow always progresses forward, never going back to a previous step.
- Sequential workflows are definitely much easier to design and maintain.
- A sequential workflow executes in no particular order and these are based on events like OnTaskCreated, OnTaskDeleted etc.
- A sequential workflow moves from one state to another until the logic concludes the workflow has completed.
- Compared to Sequential workflows State machine workflows are difficult to design and maintain.
- In order to move to another event, the workflow needs to meet another state.
- The workflow doesn’t really have to end. It can stay in the same state for weeks.
Visual studio provides both Sequential workflow and State Machine workflow. But in SharePoint designer you can only make sequential workflows.