SharePoint workflow solution (1): ordered workflow and state machine Workflow

SharePoint workflows are based on the Workflow Foundation. Let's talk about WF first. Only by having a correct understanding of WF can we find the SharePoint workflow solution.

Two of the most notable features of the Workflow Foundation

Directly supporting the State Machine Model

State machines are the theoretical basis of workflows, but in the past few workflow products directly support state machines, because most workflow products have direct commercial purposes and the goal is to apply them, the technology of the state machine is very difficult. To reduce the difficulty of the application, the state machine is encapsulated so that the process can be redirected in a flowchart. Sacrifice features in exchange for ease of use.

The objective of WF is a basic architecture. Therefore, it can directly support the state machine model. Although development is difficult, it implements a complete flow function. On WF, different platforms can be built to meet the needs of different applications.

Our workflow platform implements nearly business processes, all of which adopt state machines. None of them can be implemented through sequential flows. Therefore, state machines are the basis of WF applications, complex process logic can be implemented only through the state machine. Some people roll back the process by adding loops to the Sequential stream. This style greatly increases the complexity of the process and limits the functions of the process.

Fine-grained Activity

The basic component of WF is activity, which has a large number of activities and very detailed functions. Almost all the flow-related statements required in coding have corresponding activities. through inheritance of existing activities, you can easily expand functions, and use codeactivity to conveniently implement business logic.

However, some WF and SharePoint workflow solutions encapsulate the activity and no native activity is supported, which may be helpful for process development, however, it brings a lot of trouble to the development of business logic.

Relationship between SharePoint workflows and WF

WF is a workflow engine that implements the process-driven function and provides a process-driven interface to the outside. It can be applied to human-computer interaction flows or industrial control flows. However, WF is technically difficult,CodeComplex; developing the simplest human-computer interaction process on WF also requires understanding of its complex mechanism, implementing process-driven interfaces, and writing a large amount of code.

Sharepoint is a workflow platform. It is applied to human-computer interaction processes. It implements process-driven functions by roles or personnel on the WF process-driven interface. Therefore, in Sharepoint, a simple human-computer interaction process can be implemented without understanding the mechanism of the WF process-driven interface or writing code.

Existing Solution Problems

I have seen several workflow products and solutions in SharePoint that have been completed and under development, but they do not support state machines and native activities. If they do not support state machines, it is very difficult to implement the rollback and redirect functions of processes; native activity is not supported, and it is difficult to implement business logic.

The WF workflow solution has high requirements on experience. Only when other workflow products are used and lack of knowledge can the WF be realized. Only a deep understanding of WF can be realized, only applications that have been successfully applied can have confidence in SharePoint workflows. Although the design of those SharePoint workflow products and the technical level of developers mentioned above are still relatively high, there are some deficiencies in experience. Even complex WF applications have not been successfully implemented, how to design and develop SharePoint workflow products and solutions.

A successful solution can meet functional requirements, and its application should also be a simple task.

Basic of SharePoint workflow solution

In conclusion, to successfully apply a Sharepoint workflow, the following two aspects are the basis:
1. Adopting the WF State Machine Model
2. Supports WF native Activity