A method for configuring event operations in workflow nodes of multi-organization enterprises based on dynamic codes

Abstract

The present invention relates to a multi-organization enterprise workflow node event operation configuration method based on dynamic code, comprising: using an online programming tool to edit and select a process node for custom operation and a corresponding node custom operation module, online programming the business logic of the node custom operation according to the comments and prompts of the online webpage, and selecting the object role for configuring the custom operation; generating parameters for the node custom operation; online compiling the business logic code; dynamically injecting the ID number and the unique identification class name of the node custom operation as a unique identification combination into a system container; running a workflow engine, loading a workflow template, opening a process, triggering an event when the process is reversed to the node of the custom operation, and automatically completing the event operation according to the business logic of the custom operation. The present invention realizes the custom function of the event operation of the process node of the enterprise office automation system, and increases the flexibility and functional complexity of the enterprise information system.

Description

Technical Field

[0001] The invention belongs to the technical field of workflow, and in particular relates to an online configuration method for customized operations of enterprise workflow node events including subsidiaries. Background Art

[0002] Workflow management systems use computer technology to define, execute and manage workflows, and coordinate information interactions between workflow execution processes and between group members.

[0003] The workflow management system contains predefined process templates. The system instantiates the process when it is running. The workflow engine uses frequent node event operations to realize the automation of office business. Corresponding node events are generated when a node task is created, when a node task is assigned to a role object, when a node task is completed, and before a task is deleted.

[0004] When a node event occurs, corresponding event operations are triggered according to business needs, such as sending text messages, emails, etc. In the workflow management system of the prior art, the business operations triggered by these node events need to be configured when setting up the module, and the business operations cannot be customized in the form of configuration. Summary of the invention

[0005] The purpose of the present invention is to provide a multi-institution enterprise workflow node event operation configuration method based on dynamic code in view of the above problems, so as to realize the customization function of event operation of process nodes in the workflow template of the enterprise office automation system. Office personnel edit the business logic of event operation in a pre-defined node custom operation template through an online web page, introduce node monitoring events in the form of aliases, and automatically generate codes online and complete compilation before injecting them into the enterprise office automation system for operation.

[0006] The technical solution of the present invention is a multi-organization enterprise workflow node event operation configuration method based on dynamic code, comprising the following steps:

[0007] Step 1: Use the online idea tool to edit and select the process node for custom operation and the corresponding node custom operation module. According to the comments and prompts on the online webpage, program the business logic of the node custom operation online, and select the object role for configuring the custom operation;

[0008] Step 2: Generate the parameters of the node custom operation according to the object role of the custom operation selected in step 1; use the SnowFlake algorithm to generate an ID number as a unique identifier for the business logic code obtained in step 1, and set the container unique identification class name by setting an alias;

[0009] Step 3: Compile the business logic code obtained in step 1 online. If the compilation is successful, go to step 4. Otherwise, the reason for the compilation failure will be prompted and go to step 1.

[0010] Step 4: Dynamically inject the node custom operation ID number and unique identification class name as a unique identification combination into the system container;

[0011] Step 5: Run the workflow engine, load the workflow template, start the process instance and event listener program, trigger the event when the process turns to the node of the custom operation, and automatically complete the event operation according to the business logic of the custom operation.

[0012] Furthermore, in step 1, corresponding node custom operation data is generated according to the node custom operation and stored in the process node custom operation information table. The process node custom operation information table includes task_id, task_user, form_key and form_json fields, where task_id represents the task ID, task_user represents the user who creates the node event custom operation, form_key represents the key value of the form of the node custom operation, and form_json represents the form data of the node custom operation.

[0013] Furthermore, in step 3, the online compilation of the business logic code includes the following steps:

[0014] 1) Get the compilation environment;

[0015] 2) Get a Java compiler;

[0016] 3) Determine the type of the compilation environment. If the compilation environment is a Linux system, execute step 4), otherwise execute step 5);

[0017] 4) Execute the Linux compilation process;

[0018] 4.1) Get the Java file management class;

[0019] 4.2) According to the Java file management class in step 4.1), obtain a Java file object iterator;

[0020] 4.3) Set compilation parameters;

[0021] 4.4) Get the compilation task;

[0022] 4.5) Execute the compilation task. If a compilation error occurs, output the error message;

[0023] 5) Execute the Windows compilation process;

[0024] 5.1) Obtain the compiled file according to the compiled file path;

[0025] 5.2) Execute the compilation process. If a compilation error occurs, an error message will be output.

[0026] Compared with the prior art, the beneficial effects of the present invention include:

[0027] 1) The present invention realizes the customization function of event operations of process nodes of enterprise office automation systems. Office personnel can edit the business logic of workflow node event operations according to business needs, that is, customize the operations. After automatically generating codes and completing compilation, the codes are injected into the enterprise office automation system for operation, thereby increasing the flexibility and functional complexity of the enterprise information system. The informatization and automated operation of the business have little dependence on professional software developers, and the operation and maintenance costs of the information system are greatly reduced.

[0028] 2) Office staff using the workflow platform can edit business logic and customize operations online, which has little dependence on office computer equipment and environment, and is convenient and practical.

[0029] 3) The present invention generates parameters of the object role according to the selection of the object role of the node custom operation. The parameters include the specific organization to which the object role belongs, so as to accurately distinguish the roles of multi-level organizational structures and realize the precise control of user rights.

[0030] 4) The user role of the node customization task and the specific organization parameters to which it belongs in the method of the present invention are encrypted and stored in the database. Other personnel other than the node customization operator, including software development and testing personnel, are unaware of the user object of the node customization task and its affiliated organization, thereby preventing other personnel from tampering with or affecting business reversals, thereby improving the security of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0032] Figure 1 The present invention is a flowchart of a method for configuring a node event operation in a multi-organization enterprise workflow according to an embodiment of the present invention.

[0033] Figure 2 A schematic diagram of the code of a node customized operation template according to an embodiment of the present invention.

[0034] Figure 3 This is a diagram of the editing interface of the node custom operation template according to an embodiment of the present invention.

[0035] Figure 4 A schematic diagram of a code for obtaining parameters of a custom operation according to an embodiment of the present invention.

[0036] Figure 5 A schematic diagram of online compiled code according to an embodiment of the present invention.

[0037] Figure 6 This is a diagram of the management interface of the event listener according to an embodiment of the present invention.

[0038] Figure 7 The flowchart of the workflow of the embodiment of the present invention is shown in FIG.

[0039] Figure 8 A schematic diagram of the code of the AES encryption algorithm according to an embodiment of the present invention. DETAILED DESCRIPTION

[0040] The system environment of the embodiment is shown in Table 1.

[0041] Table 1 System environment information table

[0042] System environment Backend Java service application Java JDK1.8 database Mysq18 Front-end deployment application Nginx

[0043] The hardware devices of the embodiment are shown in Table 2.

[0044] Table 2 Hardware parameters

[0045] name quantity system Memory VCPU System disk size Data disk size Virtual graphics card Application Server 1 Linux 16G 8 cores and 8 threads 80G 100G no Database Server 1 Linux 16G 8 cores and 8 threads 80G 100G no

[0046] The node custom operation template of the embodiment is designed and coded by a software designer. The code of the node custom operation template is as follows: Figure 2 As shown in the figure, the editing interface of the node custom operation template is as follows Figure 3 As shown, the interface provides the functions of "code rollback", "test compilation", "save template" and "exit template".

[0047] like Figure 1 As shown, a multi-organization enterprise workflow node event operation configuration method based on dynamic code includes the following steps:

[0048] Step 1: Use the online programming tool to edit and select the process node for custom operation and the corresponding node custom operation template, program the business logic of the node custom operation online according to the comments and prompts on the online webpage, and select the object role of the custom operation and the specific organization to which the role belongs;

[0049] According to the node custom operation, the corresponding node custom operation data is generated and stored in the process node custom operation information table. The process node custom operation information table includes task_id, task_user, form_key and form_json fields, where task_id represents the task ID, task_user represents the user who creates the node event custom operation, form_key represents the key value of the form of the node custom operation, and form_json represents the form data of the node custom operation, as shown in Table 3.

[0050] Table 3 Process node custom operation information table

[0051] Fields type Not required illustrate id bigint(255) Y Primary key snowflake id task_id varchar(255) Y Task id task_user bigint(20) Y Event Node Create User form_key varchar(255) Y The key snowflake id stored in the event form form_json longtext Y JSON data of event form

[0052] Step 2: Generate the parameters of the node custom operation according to the object role of the custom operation selected in step 1; generate an ID number as a unique identifier for the business logic code obtained in step 1, and set the container unique identification class name by setting an alias.

[0053] According to the object role of the selected custom operation and the specific organization to which the role belongs, the user data of the task corresponding to the node custom operation is generated and stored in the user data table of the node custom task, as shown in Table 4.

[0054] Table 4 Node custom task-user data table

[0055]

[0056]

[0057] The GROUP_ID_ field is used to distinguish the user role and the organization to which the user belongs. The value of GROUP_ID_ is obtained by concatenating the role type code role_cod and the organization type code dept_code. In the embodiment, dept_code=1 represents the headquarters, dept_code=2 represents the branch company, dept_code=3 represents the project department, dept_code=4 represents the department, and dept_code=5 represents the virtual organization type. The role types in the embodiment are shown in Table 5.

[0058] Table 5 Role information table

[0059] Institutional Level Role Name Role coding Headquarters Headquarters - General Manager headquarters_gmd Headquarters Headquarters - Technology Department - Deputy Manager in Charge headquarters_scientific_amg Branches and subsidiaries General Manager, Branch and Subsidiary - Technology Department company_scientific_gmd Branches and subsidiaries Branch and Subsidiary - Technology Department - Manager in Charge company_scientific_mg Project Department Project Department-Finance project_finance Project Department Project Department-Scientific Research Leader project_scientific_user department Project Department-Manager project_user

[0060] In the embodiment, the AES encryption algorithm is used to encrypt the value of GROUP_ID_ and then store it in the database to prevent other personnel other than the node customization operator, such as software developers and testers, from modifying or affecting the business changes in the workflow. Figure 8 As shown, the AES encryption algorithm adopted in the embodiment refers to the AES algorithm disclosed in Chai Chuanjiang's paper "Design of Network Information Data Encryption Transmission Method Based on AES Algorithm" published in the 2nd issue of "Modern Transmission" in 2022.

[0061] The TYPE_ field has three values: TYPE_=assignee indicates the user assigned to the task; TYPE_=candidate indicates the candidate user for task processing. This type of task only requires one of the candidate users to handle it; TYPE_=owner indicates the designated and irreplaceable user for task processing. This type of task can only be handled and completed by a specific and unique user.

[0062] The code for obtaining parameter data according to the user operation in step 1 is as follows Figure 4 shown.

[0063] Step 3: Compile the business logic code obtained in step 1 online. If the compilation is successful, go to step 4. Otherwise, the reason for the compilation failure will be prompted and go to step 1.

[0064] The specific process of compilation includes:

[0065] 1) Get the compilation environment;

[0066] 2) Get a Java compiler;

[0067] 3) Determine the type of the compilation environment. If the compilation environment is a Linux system, execute step 4), otherwise execute step 5);

[0068] 4) Execute the Linux compilation process;

[0069] 4.1) Get the Java file management class;

[0070] 4.2) According to the Java file management class in step 4.1), obtain a Java file object iterator;

[0071] 4.3) Set compilation parameters;

[0072] 4.4) Get the compilation task;

[0073] 4.5) Execute the compilation task. If a compilation error occurs, output the error message;

[0074] 5) Execute the Windows compilation process;

[0075] 5.1) Obtain the compiled file according to the compiled file path;

[0076] 5.2) Compile the obtained compilation file. If a compilation error occurs, an error message is output.

[0077] like Figure 5 As shown, the online compiled code includes:

[0078]

[0079]

[0080] Step 4: Dynamically inject the node custom operation ID number and unique identification class name as a unique identification combination into the system container;

[0081] Step 5: Run the workflow engine, load the workflow template, start the process instance and event listener program, trigger the event when the process turns to the node of the custom operation, complete the event operation according to the business logic of the custom operation, generate the corresponding task, and complete the business reversal.

[0082] The event listener in the embodiment is pre-coded by the software designer and compiled and tested. The management interface of the event listener is as follows: Figure 6 shown.

[0083] The workflow of the embodiment is as follows Figure 7 As shown, the payment approval process is selected as an example in the embodiment for explanation. At the "branch subsidiary-technology department-manager in charge" node, after the approval task of this node is completed, it is necessary to notify the project department-handler that the approval process has been completed at the branch subsidiary-technology department-manager in charge, and send a message to the branch subsidiary-technology department-general manager to explain that this payment approval process is very important.

[0084] In the embodiment, low-code development is performed on the process node of "branch subsidiary-technology department-manager in charge". The branch subsidiary-technology department-manager in charge uses the node custom operation template to customize the system operation triggered by the approval task completion event, and edits the business logic to be implemented in the node custom operation interface, that is, notifying the project department-handler and sending a message to the branch subsidiary-technology department-general manager. After the user edits the custom operation of the event, save the written low-code, generate the file and the unique file number and ID number and hand it over to the platform personnel.

[0085] The platform staff enters the server and injects the file with the file number and unique id into the container. Run the workflow engine, load the workflow template, start the payment approval process instance and event listener program, and trigger the event when the process turns to the "approval by the deputy manager of the science and technology department" node, notifying the science and technology department's person in charge that the approval process has been completed at the deputy manager of the science and technology department, and send a message to the general manager of the science and technology department to explain that this payment approval process is very important.

Claims

1. A method for configuring event operations of workflow nodes of multiple organizations and enterprises based on dynamic codes, characterized in that: Provides the function of customizing the event operation of the process node in the workflow template of the enterprise office automation system. The office staff can edit the business logic of the event operation in the pre-defined node custom operation template through the online web page, introduce the node listening event in the form of an alias, automatically generate the custom operation code online, compile it, and inject it into the enterprise office automation system for operation; The event operation configuration method comprises the following steps: Step 1: Use the online programming tool to edit and select the process node for custom operation and the corresponding node custom operation module, program the business logic of the node custom operation online according to the comments and prompts on the online webpage, and select the object role of the custom operation and the specific organization to which the role belongs; Step 2: Generate the parameters of the node custom operation according to the object role of the custom operation selected in step 1; generate an ID number as a unique identifier for the business logic code obtained in step 1, and set the container unique identification class name by setting an alias; Step 3: Compile the business logic code obtained in step 1 online. If the compilation is successful, go to step 4. Otherwise, the reason for the compilation failure will be prompted and go to step 1. Step 4: Dynamically inject the node custom operation ID number and unique identification class name as a unique identification combination into the system container; Step 5: Run the workflow engine, load the workflow template, start the process and event listener program, trigger the event when the process turns to the node of the custom operation, and complete the event operation according to the business logic of the custom operation; The node custom operation template is pre-designed and coded by the software designer. The editing interface of the node custom operation template provides the functions of "code rollback", "test compilation", "save template" and "exit template"; In step 2, according to the object role of the selected custom operation and the specific organization to which the role belongs, user data of the task corresponding to the node custom operation is generated and stored in the user data table of the node custom task. The user data table of the node custom task includes ID_, REV_, GROUP_ID_, TYPE_, USER_ID_, TASK_ID_, PROC_INST_ID_ and PROC_DEF_ID_ fields, where ID_ is the primary key, REV_ indicates the data version, GROUP_ID_ indicates the user group ID, TYPE_ indicates the relational data type, USER_ID_ indicates the user ID, TASK_ID_ indicates the task ID, PROC_INST_ID_ indicates the process definition ID, and PROC_DEF_ID_ indicates the attribute ID; wherein the GROUP_ID_ field is used to distinguish the user role and the organization to which the user belongs, and the value of GROUP_ID_ is obtained by splicing the role type code and the organization type code in a front-to-back manner; The value of GROUP_ID_ is encrypted using the AES encryption algorithm and then stored in the database to prevent modification by personnel other than workflow users or business changes that affect the workflow.

2. The event operation configuration method according to claim 1, characterized in that: In step 1, according to the node custom operation, the corresponding node custom operation data is generated and stored in the process node custom operation information table. The process node custom operation information table includes task_id, task_user, form_key and form_json fields, where task_id represents the task ID, task_user represents the user who creates the node event custom operation, form_key represents the key value of the form of the node custom operation, and form_json represents the form data of the node custom operation.

3. The event operation configuration method according to claim 2, characterized in that: The TYPE_ field has three values: TYPE_=assignee indicates the user assigned to the task, TYPE_=candidate indicates the candidate user for task processing, and TYPE_=owner indicates the designated and irreplaceable user for task processing.

4. The event operation configuration method according to claim 3, characterized in that: In step 3, the online compilation of the business logic code obtained in step 1 includes the following steps: 1) Obtain the compilation environment; 2) Get a compiler; 3) Determine the type of the compilation environment. If the compilation environment is Linux system, go to step 4), otherwise go to step 5); 4) Execute the Linux compilation process; 4.1) Get the Java file management class; 4.2) According to the Java file management class in step 4.1), obtain the Java file object iterator; 4.3) Set compilation parameters; 4.4) Get the compilation task; 4.5) Execute the compilation task. If a compilation error occurs, the error message will be output; 5) Execute the Windows compilation process; 5.1) Get the compiled file according to the compiled file path; 5.2) Execute the compilation process. If a compilation error occurs, an error message will be output.

Images