Intensive Business Processing System and Method

Abstract

The present application provides an intensive service processing system and method, including: a front-end unit, a gateway configuration unit, an engine unit, and a data layer; the front-end unit is connected to the gateway configuration unit, the gateway configuration unit is further connected to the engine unit, and the engine unit is further connected to the data layer; the engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter; the special zone engine is used to perform the functions of special zone component configuration, special zone permission management, and special zone operation data statistics; the form engine is used to perform the functions of business component library, form controls, form rule configuration, and data rule configuration; the workflow engine is used to perform the functions of process components, process configuration, process processing, form engine integration, and special zone engine integration; the workflow engine adapter is used to perform the function of integrating the workflow engine with the existing enterprise workflow engine.

Description

Technical Field

[0001] This application relates to the technical field of servers, and particularly to an intensive service processing system and method. Background Art

[0002] Intensive management is the basic orientation for modern enterprise groups to improve efficiency and effectiveness. The "intensive" in intensive management means concentration, gathering production factors such as human resources, material resources, financial resources, and management for unified allocation. The "restraint" in intensive management means that in the process of centralized and unified allocation of production factors, thrift, restraint, and high efficiency are taken as the value orientation, so as to achieve cost reduction and efficient management, and then enable the enterprise to concentrate its core strength and gain sustainable competitive advantages. In the intensive service processing systems of large and medium-sized group enterprises, there are differences in the actual management processes of subsidiaries and branches. Subsidiaries and branches can build private service systems to achieve personalized processes. When business requirements and management processes change, both the group system and the private systems of subsidiaries and branches need to change the processes.

[0003] Currently, business changes are usually achieved by manually collecting and changing business data, or developers need to modify the process model and data model according to the latest business logic and release the version before it can be used.

[0004] However, in the intensive service processing systems in the prior art, the business change time is long and the efficiency is low, and rapid and unified business changes cannot be achieved. Summary of the Invention

[0005] This application provides an intensive service processing system and method to solve the technical problems that in the intensive service processing systems in the prior art, the business change time is long, the efficiency is low, and rapid and unified business changes cannot be achieved.

[0006] In a first aspect, this application provides an intensive service processing system, including: a front-end unit, a gateway configuration unit, an engine unit, and a data layer;

[0007] The front-end unit is connected to the gateway configuration unit, the gateway configuration unit is further connected to the engine unit, and the engine unit is further connected to the data layer;

[0008] The engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter;

[0009] The special zone engine is used to execute the functions of special zone component configuration, special zone permission management, and special zone operation data statistics;

[0010] The form engine is used to execute the functions of business component library, form controls, form rule configuration, and data rule configuration;

[0011] The workflow engine is used to execute the functions of process component, process configuration, process processing, form engine integration, and zone engine integration;

[0012] The workflow engine adapter is used to execute the function of integrating the workflow engine with the existing workflow engine of the enterprise;

[0013] The front-end unit is used to execute the function of Internet pages;

[0014] The gateway configuration unit is used to execute the function of routing configuration for the data interface of the front-end unit;

[0015] The data layer is used to execute the functions of data persistence, caching, and statistics.

[0016] Here, the present application provides an intensive business processing system, including a front-end unit, a gateway configuration unit, an engine unit, and a data layer. Among them, the engine unit includes a zone engine, a form engine, a workflow engine, and a workflow engine adapter. The workflow engine is a basic component for enterprise process management. To support the operation of enterprise business, enterprise business systems all implement process management through open-source or self-developed workflow engines; the form engine is a component that realizes form configuration, form rules, and data filling functions, and is generally applied to data collection scenarios; the form engine realizes form self-configuration by defining form controls and form rules, and after the form is published, data filling is realized through the page provided by the form engine; the zone engine is a component that provides different organizational scope zones and permission management functions. Generally, the zone engine realizes zone self-configuration by defining zone components, and realizes permission management by setting zone members and administrators. Through the above engines and workflow engine technologies, the process page configuration function can be realized. At the same time, the intensive business processing system includes the workflow engine adapter, which can integrate the existing (current) workflow engine of the enterprise, reduce the risk of engine process migration, realize the rapid and unified change of business, reduce the time of business change, and improve the efficiency of business change.

[0017] Optionally, the zone engine includes a zone interface layer, a zone permission layer, a zone service layer, a zone component management module, and a zone engine sub-unit;

[0018] The zone interface layer is used to execute the functions of application programming interfaces and microservice interfaces;

[0019] The zone permission layer is used to execute the functions of data request and operation permission verification;

[0020] The zone service layer is used to execute the function encapsulation of the zone engine;

[0021] The zone component management module is used to execute the functions of definition, function management, and component version management of the zone component library;

[0022] The dedicated area engine sub-unit is used to execute functions such as dedicated area configuration, dedicated area permission management, and dedicated area operation data.

[0023] Among them, the dedicated area engine can provide dedicated area and permission management functions for different organizational scopes, realize self-service configuration of dedicated areas by defining dedicated area components, and realize permission management by setting dedicated area members and administrators, which is conducive to targeted unified changes through different dedicated areas, and further improves the efficiency and accuracy of business changes in the intensive business processing system.

[0024] Optionally, the dedicated area engine executes the function of integrating the workflow engine through the dedicated area interface layer.

[0025] Optionally, the dedicated area permission layer is also used to execute the user permission identification function, and the user permission identification function is used to identify dedicated area administrators.

[0026] Here, the dedicated area permission layer of the present application can execute the user permission identification function, manage the process by setting up permission modules, and ensure the security and stability of process changes when integrating the workflow engine and the dedicated area engine.

[0027] Optionally, the form engine includes a form interface layer, a form permission layer, a form service layer, a form component management module, a form rule management module, and a form engine sub-unit;

[0028] The form interface layer is used to execute the function of form field rule verification and also the function of integrating the workflow engine;

[0029] The form permission layer is used to execute the function of data request and operation permission verification;

[0030] The form service layer is used to execute the function encapsulation of the form engine;

[0031] The form component management module is used to execute functions such as business component library definition, business component library online, form control management, and component version management;

[0032] The form rule management module is used to execute functions such as form rule management, field rule management, and data rule management;

[0033] The form engine sub-unit is used to execute functions such as form configuration, form filling, and data statistics.

[0034] Here, in order to manage components, the form engine provided by this application includes a form interface layer, a form permission layer, a form service layer, a form component management module, a form rule management module, and a form engine subunit. By defining form controls and form rules, form self-configuration is achieved. When there are business changes in the intensive business processing system, the process main form and node forms can be configured accurately and quickly through the form engine, further improving the process change efficiency of the intensive business processing system.

[0035] Optionally, the form engine performs the function of integrating with the workflow engine through the form interface layer.

[0036] Optionally, the form engine performs the function of integrating with the workflow engine through the form interface layer, including:

[0037] The form engine configures the process main form and node forms, and configures the process main form and the node forms to the workflow engine through the form interface layer;

[0038] The workflow engine determines the transfer rules according to the process main form and the node forms;

[0039] The workflow engine executes the transfer rules.

[0040] Optionally, the workflow engine includes a workflow interface layer, a workflow permission layer, a workflow service layer, a process definition module, a runtime module, a workflow engine subunit, and a bottom-layer workflow engine integration module;

[0041] The workflow interface layer is used to perform the functions of application programming interfaces and microservice interfaces;

[0042] The workflow permission layer is used to perform the functions of data request and operation permission verification;

[0043] The workflow service layer is used to perform the function encapsulation of the workflow engine;

[0044] The process definition module is used to perform the functions of process node component management, process transfer rule management, and process definition version management;

[0045] The runtime module is used to perform the functions of process initiation, task processing, message notification, and workbench;

[0046] The workflow engine subunit is used to perform the functions of process creation, zone engine integration, form engine integration, process monitoring, and process operation statistics;

[0047] The bottom-layer workflow engine integration module is used to perform the functions of process definition, process deployment, process initiation, and process transfer.

[0048] Optionally, the workflow engine subunit performs the function of shielding the underlying workflow engine through the workflow engine adapter.

[0049] Here, in this application, the workflow engine adapter is used as an information interface to interact with the business system. To achieve the integration of enterprise workflow engines, the existing enterprise workflow engines are integrated through the workflow engine adapter, reducing the risk of process engine migration and further improving the efficiency of the process table of the intensive business processing system.

[0050] In a second aspect, this application provides an intensive business processing method, which is applied to an intensive business processing system and includes a front-end unit, a gateway configuration unit, an engine unit, and a data layer;

[0051] The front-end unit is connected to the gateway configuration unit, the gateway configuration unit is further connected to the engine unit, and the engine unit is further connected to the data layer;

[0052] The engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter;

[0053] The special zone engine performs the functions of special zone component configuration, special zone permission management, and special zone operation data statistics;

[0054] The form engine performs the functions of business component library, form control, form rule configuration, and data rule configuration;

[0055] The workflow engine performs the functions of process component, process configuration, process processing, form engine integration, and special zone engine integration;

[0056] The workflow engine adapter performs the function of integrating the workflow engine with the existing enterprise workflow engines;

[0057] The front-end unit performs the function of Internet pages;

[0058] The gateway configuration unit performs the function of routing configuration for the data interface of the front-end unit;

[0059] The data layer performs the functions of data persistence, caching, and statistics.

[0060] The intensive business processing system and method provided by this application. The intensive business processing system includes a front-end unit, a gateway configuration unit, an engine unit, and a data layer. Among them, the engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter. The workflow engine is a basic component of enterprise process management. To support the operation of enterprise business, enterprise business systems all implement process management through open-source or self-developed workflow engines; the form engine is a component that realizes form configuration, form rules, and data filling functions, and is generally applied to data collection scenarios; the form engine realizes self-service form configuration by defining form controls and form rules, and after the form is published, data filling is realized through the page provided by the form engine; the special zone engine is a component that provides special zone and permission management functions for different organizational scopes. Generally, the special zone engine realizes self-service configuration of the special zone by defining special zone components, and realizes permission management by setting special zone members and administrators. Through the above engines and workflow engine technologies, the process page configuration function can be realized. At the same time, the intensive business processing system includes the above-mentioned workflow engine adapter, which can integrate the existing workflow engines of the enterprise, reduce the risk of engine process migration, realize the rapid and unified change of business, reduce the time of business change, and improve the efficiency of business change. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] In order to more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0062] Figure 1 It is a schematic structural diagram of an intensive business processing system provided by an embodiment of this application;

[0063] Figure 2 It is a schematic diagram of the relationship among process data, form data, component definition, and group business data of an intensive business system provided by an embodiment of this application;

[0064] Figure 3 It is a schematic structural diagram of a special zone engine provided by an embodiment of this application;

[0065] Figure 4 It is a schematic structural diagram of a form engine provided by an embodiment of this application;

[0066] Figure 5 It is a schematic structural diagram of a workflow engine provided by an embodiment of this application.

[0067] Through the above-mentioned accompanying drawings, specific embodiments of the present disclosure have been shown, and will be described in more detail hereinafter. These drawings and the written description are not intended to limit the scope of the concept of the present disclosure in any way, but to illustrate the concept of the present disclosure to those skilled in the art by reference to specific embodiments. Detailed Description of the Embodiments

[0068] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0069] The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and above-mentioned accompanying drawings of the present application are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence. It should be understood that such data may be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0070] Branches and subsidiaries can build private business systems to achieve personalized processes. When the group's business requirements change, the private systems of branches and subsidiaries cannot quickly respond to the changes, increasing the R & D, operation and maintenance, and operation costs of the systems of branches and subsidiaries, and causing the problem of data dispersion. When the group conducts unified business data collation and analysis, the private systems need to report data to the group system. Usually, there are two methods: manual collection and system docking, and both of these methods have defects. Among them, the method of manual collection has difficulties in data integration, low efficiency, cannot process ultra-large-scale data, and cannot be automatically processed; in the method of system docking, when the business requirements and management processes change, both the group system and the private systems of branches and subsidiaries need to carry out process changes and system docking joint debugging, which affects the efficiency. In summary, it is necessary to find a balance between the intensive business system and the personalized process to save the R & D, operation and maintenance, and operation costs of enterprise informatization.

[0071] Existing open-source workflow engines can perform process flow according to the process models designed by developers. When the business requirements of the group change, developers need to modify the process models and data models according to the latest business logic and can use them only after releasing the versions. According to the software life cycle, it takes a long time to complete. Therefore, in the intensive business processing systems in the prior art, the business change time is long and the efficiency is low, and the rapid and unified change of the business cannot be achieved.

[0072] To solve the above technical problems, the embodiments of the present application provide an intensive business processing system and method. Through the front-end unit, gateway configuration unit, engine unit, and data layer, wherein the engine unit includes a special zone engine, form engine, workflow engine, and workflow engine adapter, the problems of unified business change, unified data management, personalized process configuration, and personalized operation in the group intensive business system are solved; the problem of integration with the existing workflow engine of the enterprise is solved.

[0073] Optionally, Figure 1 It is a schematic structural diagram of an intensive business processing system provided by an embodiment of the present application. As Figure 1 shown, the intensive business processing system includes: a front-end unit 101, a gateway configuration unit 102, an engine unit 103, and a data layer 104.

[0074] Among them, the front-end unit 101 is connected to the gateway configuration unit 102, the gateway configuration unit 102 is further connected to the engine unit 103, and the engine unit 103 is further connected to the data layer 104.

[0075] Among them, the engine unit 103 and the data layer 104 are also connected through a data source adapter.

[0076] Optionally, when the signal is transmitted in the system, when it is transmitted from the gateway unit to the engine unit, Json web token (JWT) request authentication can be performed.

[0077] Among them, the engine unit 103 includes a special zone engine 1031, a form engine 1032, a workflow engine 1033, and a workflow engine adapter 1034.

[0078] The special zone engine 1031 is used to execute the functions of special zone component configuration, special zone permission management, and special zone operation data statistics.

[0079] The form engine 1032 is used to execute the functions of business component library, form control, form rule configuration, and data rule configuration.

[0080] Optionally, configure the process main form and node forms through the form engine and configure them into the workflow engine; when a user initiates a process instance, fill in the process main form according to the configuration; when a user processes a task, fill in the process node form, modify the process main form and historical step form data according to the configuration; control the flow rules of process execution through field rules; when the process flows, the workflow engine determines which flow rule to execute based on the boolean value of verifying whether the data filled in by the user matches the field rules.

[0081] Optionally, the form engine implements the unified business data requirements of the group through the business component library. Branches and subsidiaries must use relevant business components to implement business support processes; branches and subsidiaries add other form controls to implement differentiated business data requirements; when a business component changes, a new component version number is generated, and the zone administrator dependent on this component is notified to verify whether a process definition change is required.

[0082] The workflow engine 1033 is used to execute the functions of process components, process configuration, process processing, form engine integration, and zone engine integration.

[0083] The workflow engine adapter 1034 is used to execute the function of integrating the workflow engine with the existing workflow engine of the enterprise.

[0084] In some possible implementation manners, the workflow engine adapter includes an abstract configuration interface of the workflow engine, an abstract interface of the workflow engine adapter, a tool class for process deployment of the underlying workflow engine, a runtime service tool class of the underlying workflow engine, and a task tool class of the underlying workflow engine.

[0085] Optionally, in the abstract configuration interface (FlowProcessEngineConfiguration) of the workflow engine, the underlying workflow engine to be used can be configured through the getProcessEngineAdapter() method, and the corresponding workflow engine adapter can be obtained.

[0086] Optionally, when applying the abstract interface (ProcessEngineAdapter) of the workflow engine adapter, the tool classes of the underlying workflow engine can be obtained through this interface for process deployment, process initiation, obtaining the current node of the process, obtaining the process task list, and processing task operations. Exemplarily, the getProcessDeployHelper() method is used to obtain the deployment tool class; the getProcessRuntimeServiceHelper() method is used to obtain the runtime tool class; the getProcessTaskServiceHelper() method is used to obtain the task tool class.

[0087] Optionally, when applying the tool class (ProcessDeployHelpe) for process deployment of the underlying workflow engine, the method deploy(FlowProcessDefinitionInstance instance):String is used to deploy the process configured by the user. After successful deployment, the process definition identifier is returned, and the user can initiate the process. Among them, the parameter instance is the encapsulated object of the process data configured by the user.

[0088] Optionally, when applying the runtime service tool class (ProcessRuntimeServiceHelper) of the underlying workflow engine, the Long method is used to initiate a process based on the process definition id. After successful process initiation, the initiated process id is returned. The String method is used to obtain the current node identifier of the process.

[0089] Optionally, when applying the task tool class (ProcessTaskServiceHelper) of the underlying workflow engine, the TaskInstanceEntity method is used to process user tasks. After successful processing of the user task, the processed user task data object is returned. Through getTasks(ProcessInstance processInstance):List <taskinstanceentity>The method is used to obtain the current user task list of the process. Among them, the parameter processInstance represents the data encapsulation object of the process instance initiated by the user.

[0090] Among them, one end of the workflow engine adapter is connected to the workflow engine, and the other end is connected to the existing enterprise work engine. It is used to integrate the existing enterprise workflow engine.

[0091] The front-end unit 101 is used to execute the functions of the Internet page.

[0092] Optionally, the front-end unit part provides a Web page, which can be directly deployed in the server.

[0093] The gateway configuration unit 102 is used to execute the function of performing routing configuration on the data interface of the front-end unit.

[0094] Here, the gateway configuration unit provides the routing configuration of the front-end part data interface.

[0095] The data layer 104 is used to execute the functions of data persistence, caching, and statistics.

[0096] Here, the data layer can be used to store the process instance data generated by the process tasks.

[0097] Optionally, the data layer 104 may include at least one of a Structured Query Language (SQL) cluster, a data structure server (Remote Dictionary Server, Redis) cluster, and an Elasticsearch (ES) cluster.

[0098] Exemplarily, Figure 2 For the schematic diagram of the relationship between the intensive business system process data, form data, component definition, and group business data provided by the embodiments of this application, in some possible implementation manners, through Figure 1 the intensive business processing system, based on Figure 2 the relationship between the process data, form data, component definition, and group business data in

[0099] (1) The form engine provides unified business components to implement the unified business data requirements of the group and implement the business data adapter of this version.

[0100] (2) The branches and subsidiaries must use relevant business components to implement the business support process to meet the unified business data requirements.

[0101] (3) The branches and subsidiaries can add other form controls to meet the differentiated business data requirements.

[0102] (4) Personalized processes are configured for subsidiaries and branches.

[0103] (5) When a business component changes, a new component version number is generated, and the zone administrators depending on this component are notified to verify whether process definition changes are required.

[0104] (6) Processes depending on the old version can flow as usual according to the old version.

[0105] Here, an embodiment of the present application provides an intensive business processing system, including a front-end unit, a gateway configuration unit, an engine unit, and a data layer. Among them, the engine unit includes a zone engine, a form engine, a workflow engine, and a workflow engine adapter. The workflow engine is a basic component for enterprise process management. To support the operation of enterprise business, enterprise business systems all implement process management through open-source or self-developed workflow engines; the form engine is a component that realizes form configuration, form rules, and data filling functions, and is generally applied to data collection scenarios; the form engine realizes self-service form configuration by defining form controls and form rules, and data filling is realized through the page provided by the form engine after the form is published; the zone engine is a component that provides zone and permission management functions for different organizational scopes. Generally, the zone engine realizes self-service zone configuration by defining zone components and realizes permission management by setting zone members and administrators. Through the above engines and workflow engine technologies, the process page configuration function can be realized. At the same time, the intensive business processing system includes a workflow engine adapter, which can integrate the existing workflow engines of the enterprise, reduce the risk of engine process migration, realize fast and unified business changes, reduce the time of business changes, and improve the efficiency of business changes.

[0106] Optionally, Figure 3 is a schematic structural diagram of a zone engine provided by an embodiment of the present application. The zone engine here is the Figure 1 zone engine 1031 in Figure 3 As shown, the zone engine includes a zone interface layer 10311, a zone permission layer 10312, a zone service layer 10313, a zone component management module 10314, and a zone engine subunit 10315.

[0107] The zone interface layer 10311 is used to execute the functions of application programming interfaces and microservice interfaces.

[0108] Optionally, the zone interface layer 10311 may include an application programming interface (Application Programming Interface, API) interface layer and a microservice interface layer, providing zone engine API interfaces and microservice interfaces. The API interface layer provides RESTful APIs, and the microservice interface layer provides microservice interfaces.

[0109] The zone permission layer 10312 is used to perform data request and operation permission verification functions.

[0110] The zone service layer 10313 is used to execute the functional encapsulation of the zone engine.

[0111] Optionally, the functions encapsulated in the zone service layer may include zone management, member and permission management, homepage configuration and operation data.

[0112] The zone component management module 10314 is used to perform the functions of defining the zone component library, function management and component version management.

[0113] Optionally, the functions that can be implemented in the zone component management module include component definition, function management and version management.

[0114] The zone engine subunit 10315 is used to perform the functions of zone configuration, zone authority management and zone operation data.

[0115] Optionally, the zone engine subunit can implement functions including zone component configuration, zone permissions and autonomous operation services.

[0116] Among them, the zone engine can provide zone and permission management functions for different organizational scopes, realize self-service configuration of zones by defining zone components, and realize permission management by setting zone members and administrators. It is conducive to targeted unified changes through different zones, further improving the efficiency and accuracy of business changes in the intensive business processing system.

[0117] In some embodiments, the zone engine can be based on Figure 3 Provide zone permission verification function through the interface layer for workflow engine integration; provide personal to-do, completed, initiated, and draft query functions through the zone workbench component; provide process initiation function through the zone process entry component. Optionally, the zone engine executes the function of workflow engine integration through the zone interface layer.

[0118] Optionally, the zone permission layer is also used to perform a user permission identification function, which is used to identify zone administrators.

[0119] Here, the zone permission layer of the embodiment of the present application can perform the user permission identification function, realize the management of the process by setting the permission module, and ensure the security and stability of the process change when the workflow engine and the zone engine are integrated.

[0120] In some possible implementations, the workflow engine and zone engine are integrated as follows:

[0121] Only zone administrators can configure processes through the zone management module.

[0122] A special zone administrator can only view and modify all the processes configured under this special zone.

[0123] The special zone administrator can view and export all the data of a certain process and can delete the process instance.

[0124] Only members of the special zone can become process-related persons and perform operations such as process initiation and user task processing.

[0125] Optionally, Figure 4 FIG. is a schematic structural diagram of a form engine provided for an embodiment of the present application. Here, the form engine is Figure 1 the form engine 1032 in Figure 4 As shown in, the form engine includes a form interface layer 10321, a form permission layer 10322, a form service layer 10323, a form component management module 10324, a form rule management module 10325, and a form engine subunit 10326.

[0126] The form interface layer 10321 is used to perform the function of form field rule verification and is also used to perform the function of workflow engine integration.

[0127] The form interface layer 10321 is used to perform the functions of application programming interface and microservice interface.

[0128] Optionally, the form interface layer 10321 may include an API interface layer and a microservice interface layer, providing a form engine API interface and a microservice interface. The RESTful API is provided by the API interface layer, and the microservice interface is provided by the microservice interface layer.

[0129] The form permission layer 10322 is used to perform the function of data request and operation permission verification.

[0130] The form service layer 10323 is used to perform the function encapsulation of the form engine.

[0131] The form component management module 10324 is used to perform the functions of business component library definition, business component library online, form control management, and component version management.

[0132] The form rule management module 10325 is used to perform the functions of form rule management, field rule management, and data rule management.

[0133] Optionally, the rule management module provides functions of form rule management, field rule management, and data rule management. Among them: form rules refer to the display logic of each control and component in the form. Field rules refer to the Boolean expressions configured through comparison operators and logical operators. Data rules refer to the data length, options, and statistical rules of form controls.

[0134] The form engine sub-unit 10326 is used to perform functions such as form configuration, form filling, and data statistics.

[0135] Optionally, the form engine performs the function of integrating the workflow engine through the form interface layer.

[0136] Optionally, the form engine performs the function of integrating the workflow engine through the form interface layer, including:

[0137] The form engine configures the process main form and node forms, and configures the process main form and node forms to the workflow engine through the form interface layer; the workflow engine determines the transfer rules according to the process main form and node forms; the workflow engine executes the transfer rules.

[0138] Optionally, the form engine provides functions such as form configuration, form filling, and data statistics, provides a form field rule verification function through the form interface layer for workflow engine integration. The group's unified business requirements are realized through the business component library. The form engine can run independently.

[0139] In some embodiments, based on Figure 4 the form engine in, the integration method of the workflow engine and the form engine is as follows:

[0140] Configure the process main form and node forms through the form engine and configure them to the workflow engine.

[0141] When the user initiates a process instance, fill in the process main form according to the configuration.

[0142] When the user processes a task, fill in the process node form according to the configuration.

[0143] When the user processes a task, modify the process main form and historical step form data according to the configuration.

[0144] Control the transfer rules of process execution through field rules.

[0145] Optionally, when configuring the transfer rules, field rules can be set according to the controls in the already configured process main form and step forms. When the process flows, the workflow engine decides which transfer rules to execute by verifying whether the data filled in by the user matches the field rules.

[0146] Here, in order to implement the management of components, the form engine provided by the embodiments of the present application includes a form interface layer, a form permission layer, a form service layer, a form component management module, a form rule management module, and a form engine sub-unit. Through the definition of form controls and form rules, form self-configuration is realized. When the business of the intensive business processing system changes, the process main form and node forms can be configured accurately and quickly through the form engine, further improving the process change efficiency of the intensive business processing system.

[0147] Optionally, Figure 5 FIG. 3 is a schematic structural diagram of a workflow engine provided by an embodiment of the present application. The workflow engine here is Figure 1 the workflow engine 1033 in Figure 5 As shown in FIG. 3, the workflow engine includes a workflow interface layer 10331, a workflow permission layer 10332, a workflow service layer 10333, a process definition module 10334, a runtime module 10335, a workflow engine subunit 10336, and a bottom-layer workflow engine integration module 10337.

[0148] The workflow interface layer 10331 is used to execute the functions of application programming interfaces and microservice interfaces.

[0149] The workflow permission layer 10332 is used to execute the functions of data request and operation permission verification.

[0150] The workflow service layer 10333 is used to execute the function encapsulation of the workflow engine.

[0151] The process definition module 10334 is used to execute the functions of process node component management, process transition rule management, and process definition version management.

[0152] Optionally, the process node components include: start event, user task, subprocess, end event, etc. The transition rules include: button type, field rule type, etc.

[0153] The runtime module 10335 is used to execute the functions of process initiation, task processing, message notification, and workbench.

[0154] The workflow engine subunit 10336 is used to execute the functions of process creation, zone engine integration, form engine integration, process monitoring, and process operation statistics.

[0155] The bottom-layer workflow engine integration module 10337 is used to execute the functions of process definition, process deployment, process initiation, and process transition.

[0156] Optionally, the bottom-layer workflow engine integration module provides function abstractions for process definition, process deployment, process initiation, and process transition, and the bottom-layer workflow engine provides specific function implementations.

[0157] Optionally, the workflow engine shields the implementation details of the bottom-layer workflow engine through a workflow engine adapter, and focuses on user self-service configuration of processes, process version management, and transition of enabled processes, etc. The specific details of process initiation, task processing, and process transition are the responsibility of the bottom-layer workflow engine to implement.

[0158] Optionally, the workflow engine subunit executes the function of shielding the bottom-layer workflow engine through a workflow engine adapter.

[0159] Here, in the embodiments of the present application, the workflow engine adapter is used as an information interface to interact with the business system. To achieve the integration of the enterprise workflow engine, the existing enterprise workflow engines are integrated through the workflow engine adapter, reducing the risk of process engine migration and further improving the process table efficiency of the intensive business processing system.

[0160] Optionally, the embodiments of the present application further provide an intensive business processing method, which is applied to an intensive business processing system and includes a front-end unit, a gateway configuration unit, an engine unit, and a data layer.

[0161] The front-end unit is connected to the gateway configuration unit, the gateway configuration unit is further connected to the engine unit, and the engine unit is further connected to the data layer.

[0162] The engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter.

[0163] The special zone engine executes the functions of special zone component configuration, special zone permission management, and special zone operation data statistics.

[0164] The form engine executes the functions of business component library, form controls, form rule configuration, and data rule configuration.

[0165] The workflow engine executes the functions of process components, process configuration, process processing, form engine integration, and special zone engine integration.

[0166] The workflow engine adapter executes the function of integrating the workflow engine with the existing enterprise workflow engines.

[0167] The front-end unit executes the function of the Internet page.

[0168] The gateway configuration unit executes the function of performing routing configuration on the data interface of the front-end unit.

[0169] The data layer executes the functions of data persistence, caching, and statistics.

[0170] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces, and the indirect coupling or communication connection of devices or units can be in electrical, mechanical, or other forms.

[0171] In addition, in each embodiment of the present application, each functional unit can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0172] After considering the specification and practicing the present application disclosed herein, those skilled in the art will readily conceive of other embodiments of the present disclosure. The present application is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0173] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.< / taskinstanceentity>

Claims

1. An intensive business processing system, characterized in that, including: a front-end unit, a gateway configuration unit, an engine unit, and a data layer; the front-end unit is connected to the gateway configuration unit, the gateway configuration unit is further connected to the engine unit, and the engine unit is further connected to the data layer; the engine unit includes a special zone engine, a form engine, a workflow engine, and a workflow engine adapter; the special zone engine is used to perform functions such as special zone component configuration, special zone permission management, and special zone operation data statistics. The special zone engine provides different organizational scope special zones and permission management functions. The special zone engine includes a special zone interface layer, a special zone permission layer, a special zone service layer, a special zone component management module, and a special zone engine subunit; the special zone interface layer is used to perform functions of application programming interfaces and microservice interfaces; the special zone permission layer is used to perform functions of data request and operation permission verification; the special zone service layer is used to perform function encapsulation of the special zone engine; the special zone component management module is used to perform functions such as definition of the special zone component library, function management, and component version management; the special zone engine subunit is used to perform functions such as special zone configuration, special zone permission management, and special zone operation data; the form engine is used to perform functions such as business component library, form controls, form rule configuration, and data rule configuration; the workflow engine is used to perform functions such as process components, process configuration, process processing, form engine integration, and special zone engine integration; the workflow engine adapter is used to perform the function of integrating the workflow engine with the existing enterprise workflow engine; the front-end unit is used to perform the function of Internet pages; the gateway configuration unit is used to perform the function of routing configuration for the data interface of the front-end unit; the data layer is used to perform functions such as data persistence, caching, and statistics.

2. The intensive service processing system according to claim 1, wherein The special zone engine performs the function of workflow engine integration through the special zone interface layer.

3. The intensive service processing system according to claim 1, characterized in that The special zone permission layer is further used to perform a user permission identification function, and the user permission identification function is used to identify special zone administrators.

4. The intensive service processing system according to claim 1, wherein The form engine includes a form interface layer, a form permission layer, a form service layer, a form component management module, a form rule management module, and a form engine subunit; The form interface layer is used to perform the function of form field rule verification and is also used to perform the function of workflow engine integration; the form permission layer is used to perform functions of data request and operation permission verification; the form service layer is used to perform function encapsulation of the form engine; the form component management module is used to perform functions such as business component library definition, business component library going online, form control management, and component version management; the form rule management module is used to perform functions such as form rule management, field rule management, and data rule management; the form engine subunit is used to perform functions such as form configuration, form filling, and data statistics.

5. The intensive service processing system according to claim 4, wherein The form engine performs the function of workflow engine integration through the form interface layer.

6. The intensive service processing system according to claim 5, wherein The form engine performs the function of workflow engine integration through the form interface layer, including: The form engine configures the process main form and the node form, and configures the process main form and the node form to the workflow engine through the form interface layer; The workflow engine determines the transfer rules according to the process master form and the node form; The workflow engine executes the transfer rules.

7. The intensive service processing system according to claim 1, wherein The workflow engine includes a workflow interface layer, a workflow permission layer, a workflow service layer, a process definition module, a runtime module, a workflow engine subunit, and a bottom-layer workflow engine integration module; The workflow interface layer is used to execute the functions of application programming interfaces and microservice interfaces; The workflow permission layer is used to execute the functions of data request and operation permission verification; The workflow service layer is used to execute the function encapsulation of the workflow engine; The process definition module is used to execute the functions of process node component management, process transfer rule management, and process definition version management; The runtime module is used to execute the functions of process initiation, task processing, message notification, and workbench; The workflow engine subunit is used to execute the functions of process creation, zone engine integration, form engine integration, process monitoring, and process operation statistics; The bottom-layer workflow engine integration module is used to execute the functions of process definition, process deployment, process initiation, and process transfer.

8. The intensive service processing system according to claim 7, wherein The workflow engine subunit executes the function of shielding the bottom-layer workflow engine through the workflow engine adapter.

9. An intensive service processing method, characterized in that, Applied to an intensive business processing system, including a front-end unit, a gateway configuration unit, an engine unit, and a data layer; The front-end unit is connected to the gateway configuration unit, the gateway configuration unit is also connected to the engine unit, and the engine unit is also connected to the data layer; The engine unit includes a zone engine, a form engine, a workflow engine, and a workflow engine adapter; The zone engine executes the functions of zone component configuration, zone permission management, and zone operation data statistics. The zone engine provides zone and permission management functions for different organizational scopes. The zone engine includes a zone interface layer, a zone permission layer, a zone service layer, a zone component management module, and a zone engine subunit; The zone interface layer is used to execute the functions of application programming interfaces and microservice interfaces; The zone permission layer is used to execute the functions of data request and operation permission verification; The zone service layer is used to execute the function encapsulation of the zone engine; The zone component management module is used to execute the functions of defining the zone component library, function management, and component version management; The zone engine subunit is used to execute the functions of zone configuration, zone permission management, and zone operation data; The form engine executes the functions of business component library, form controls, form rule configuration, and data rule configuration; The workflow engine executes the functions of process components, process configuration, process processing, form engine integration, and zone engine integration; The workflow engine adapter executes the function of integrating the workflow engine with the existing enterprise workflow engine; The front-end unit executes the function of Internet pages; The gateway configuration unit executes the function of routing configuration for the data interface of the front-end unit; The data layer executes the functions of data persistence, caching, and statistics.

Images