Workflow management system design instructions
Workflow management system positioning and its application is currently two ways to run in the workflow system, one is the business system with workflow nature developed by our work engine and third-party development tools. The system is running on the workflow engine, the workflow engine is responsible for the interpretation of the process monitoring and control, and the part of our third-party tool development is mainly the processing of the transaction, completing the processing of the business point. This way is well solved the process of developing the process control of the business system with workflow and its process change. Another advantage of this way is that the business function module developed by third-party development tools will not be functional. Restrictions can be complex business processing. The workflow engine and the low coupling of the business function module we develop have enabled the use of this approach to design a complicated business processing system with flow control. Disadvantages: All business processing systems must be customized and developed, and the flexible business processing points are quickly customized. The other is the workflow engine and form combination. We call it "Workflow Management System". At present, most of the workflow systems on the market use this way, which can basically solve most of the business process processing. The advantage of this way is to complete a business processing system with process nature through the establishment of the model, the design of the form, without the development of the business module, thereby implementing zero code programming, change in user requirements or With new demand, you can quickly make adjustments to meet user needs. Disadvantages: This method is mainly suitable for flow processing similar to the approval nature, because in business processing points, it is not suitable for complex operations, the current workflow system has also taken many ways to solve this problem, such as using some embedded Plug-in, controls, etc., doing this to some extent, some of the complex business can be resolved, but this approach is more complex and more complicated, and more complicated, and more complicated, and the business process is more complex. So we don't recommend this way. Is there a very difficult way to play the advantages of both, avoid your own shortcomings? Preliminary ideas combine two ways to use their respective advantages, make up for their drawbacks, create a flexible, powerful workflow management system. However, due to the current combination of workflow and application, the experience is not a lot, so temporarily take the second way, to achieve our workflow system, it is to complete the combination of workflow engines and forms, can do more in the process of implementation Some interfaces and pay attention to his extension ability so that the next step is smooth. After the workflow management system is completed, you can handle the business process relatively simple in the transaction point, mainly in the following aspects: the transaction point does not have a complex business logic; all information is performed by a form or an attachment; a single transaction point processing Information is single, and there is no complex contact structure in the underlying layer. Workflow management systems, throughout the extension of some transaction point functions, can basically meet the needs of most business processes. Detailed description of each system combination method and system operation
How do workflow engines combine with forms, identity authentication, mail systems, and document systems to jointly solve business processes in different fields, perhaps the difficulty of system design. The current authentication, mail system and document system provide corresponding APIs. It can be said that the difficulty of workflow is not very difficult. The system is difficult to combine the workflow engine and form, how to solve different business process transaction points. Operational differences. After studying some business processes and some workflow products, it is more important to feel this importance, because the side focus in different business processes, mode of operation, performance form may not be the same, if each type is The business process is designed to achieve customization, and there is also the meaning of realizing zero coding with our form unified design. How to find the commonality of different business processes, abstract the workflow management system suitable for most business processes, Our current difficulties are not easy to grasp. Take Live Flow, from his example, it may feel that his function is more powerful, almost solves most business processes, but for various business processes. Features, in Live Flow, it does not reflect it. It takes place to take his sents and receives. If the customer is willing to use, it will lose the meaning of the application. Through a period of learning, I feel that the workflow management system has two more important places. Of course, it is to control the process, how to achieve the flexible control of the process, this most workflow management system has been made, we The original design workflow engine can be said to be better in the support of process control, and another is the service processing, which is the business process of the transaction point, how to abstract the commonality of business process transaction processing, how to deal The characteristics of business process transactions may be a problem that most workflow management systems need to face, I think it is also what we face. When I mentioned the workflow at the last time, he mentioned a question. "What is your system in this area?", I think he is a question raised by this difficult point we mentioned above. Since our original idea is a workflow engine and a third-party development tool, there is only the top one of the two key issues, and there is no problem with business process transaction point operation, so our workflow engine is also There is no problem for that field. After studying some business processes, we will abstract the vectors of four transaction-processing point information, namely lists, text, file list, business reports. Since our reporting services are not yet implemented, the business report is not considered. The form list completes the acquisition of information in the business process. For the text of the business process that requires the text, you can implement complex body editing and extension, file list complete the addition, modification, deletion of attachments. Through these information, the vector can basically complete the requirements of the basic transaction point of the basic transaction point, basically solve the second problem existing in the workflow management system mentioned above. Here, the operation of the workflow management system will be described, see the figure below:
