Visualized workflow engine system

Abstract

The invention relates to a visualized workflow engine system, which comprises a flow configuration module, a form configuration module, a permission configuration module, an intelligent reminding module and a plurality of functional interfaces, wherein the flow configuration module is used for a needed business flow; the form configuration module is used for configuring a form needed by each business flow; the permission configuration module is used for configuring a corresponding operation permission respectively for each business flow; the intelligent reminding module is used for transmitting a reminding report to a role in each business flow; and the functional interfaces are used for other non-flow systems to call the visualized workflow engine system. Due to the adoption of the visualized workflow engine system, the flow can be defined by real business personnel in a hauling way according to the business requirement, the attribute and the permission of a movable node are edited, and thus the business flow can be adjusted and configured in time on the background only according to new requirement change for the changing of the flow requirement.

Description

technical field [0001] The invention relates to the field of workflow automation management, in particular to a visual workflow engine system. Background technique [0002] The concept of workflow originated in the fields of production organization and office automation, and its purpose is to decompose work into well-defined tasks and roles, perform these tasks according to certain procedures and rules, and monitor them. According to the definition of WfMC (Workflow Management Coalition, the International Workflow Management Alliance), workflow is an automatic business process, which is manifested by participants taking actions on files, information and tasks according to regulations, and allowing them to be carried out among participants. Delivery, to help enterprises standardize the management of processes, shorten process operation time, quickly respond to market customer needs, meet flexible control flow needs, effectively monitor work progress, strengthen internal infor...

AI Technical Summary

Problems solved by technology

[0003] In the traditional electronic workflow solution, the coupled method is usually adopted, that is, according to the actual business process, it is implemented with specific IT technology. However, the business process and technology of the electronic workflow application system realized in this way The means are highly coupled, requiring developers not only to have deep technical knowledge, but also to be familiar with business processes

Moreover, enterprises often have many business processes belonging to different application systems. If each application system implements such a workflow application system, there will inevitably be problems such as high cost, long cycle, and difficult maintenance. In addition, such a workflow The application system is often implemented according to the initial business process, so if the subsequent business process changes, the workflow application system may also face major adjustments

[0004] However, the management of tasks is ever-changing with different business needs, daily office automation can no longer cover everything, and the demand for data transmission and management is becoming increasingly urgent

In the traditional way, interface development technicians need to individually design the user interface for each workflow task step according to the needs of the workflow, which requires a lot of programming work, and once the process changes, it is difficult to modify or maintain the page at the same time

Although the existing workflow engine also provides technical personnel to customize the page through a proprietary interface, it is difficult to allow business personnel to participate in the interface design

The workflow engine is generally coupled with the business process, that is, the workflow engine obtained according to the business process in a specific field, that is to say, the nodes used to draw the business process are not completely independent of the business, and many are related to the business The nodes are not completely abstracted from the business process, which limits the scope of application of the workflow engine and makes it difficult to maintain. Moreover, the scalability of the workflow engine is not strong. In actual workflow applications Unable to meet the change of business process, or not well adapted to the change of business process, once the business process changes, the system also needs to be changed accordingly, thus increasing the development cost and maintenance cost of the system, etc.

Images