Workflow is a very important part of the enterprise application development process. Almost common management and business systems are inextricably linked with workflow.
Workflow, as a part of the application system, is a core solution to solve the problems of information transmission routing and content level according to different roles, division of labor and conditions.
Commonly used workflows should include basic functions such as node management, flow management, and process samples.
Excellent enterprise applications, its beautiful system interface is the most basic part; information exchange between databases is a necessary condition; and ensuring the functionality, fit, stability and easy maintenance of the application system is the top priority weight.
Taking into account the maintenance of the later period, modular and structured applications can be adopted, so that when the business process changes (decision rights change, organizational structure changes), a new business logic can be quickly generated. Moreover, if the application lacks a complete and efficient logic layer (usually implemented by a workflow engine), it will be prone to information routing errors and low operating efficiency.
In terms of architecture, a service-oriented architecture is a component model that connects different functional units of an application through interfaces and contracts defined between these services. The interface definition is carried out in a neutral way, which is independent of hardware, system and programming language. The workflow engine enables services built in such systems to interact in a unified and common way.
In the early days, many companies urgently needed a flexible OA workflow mechanism, so more and more people began to use Domino to build. Later, when ASP.NET appeared, everyone seemed to be enlightened, and all group executives started It is required to use a workflow engine to realize the informatization of enterprise process approval.
Based on the actual needs of the market, we first developed a standard ASP.NET enterprise-level workflow engine (LeaRun) and obtained relevant certifications. Various indicators and customer feedback were good, so the subsequent java platform also continued its design ideas :
First define the process steps, which mainly include: the interface address of the operation, operation parameters, and operation type (initial operation, intermediate operation). Its purpose is to set up the relevant relationship for each operation, and the set process steps can be selected when defining the process.
Secondly, define the parameters of the operation, which is another necessary item besides the interface address.
The third is to define the relationship between the process steps. That is, define the predecessor and subsequent operations of each operation step in a process.
Then define the process, its content includes basic information and the operation steps and circulation rules in the process definition. The basic information of the process does not need to be repeated. The process step definition is more complicated, setting the definition step type (start, middle, end), entry step, exit step, notification mode, personnel, role, and notification content.
After defining the situation involving skipping, if you need to submit it to the corresponding step for approval according to different parameters, here is called the process step change rule setting. The content that needs to be set: original step, target step, direction of change (positive/negative), conditional rule (judgment "and", "or" operation). Then set the parameters, values, and comparison conditions.
Finally manage authorization. This item is relatively simple, and it is judged whether the person being submitted is in an authorized state, so that relevant processing can be carried out.
The above is the general logic of the process. The situation considered in the actual writing process will be more complicated. You can refer to the mature cases in the current market.
Windy.