Method, device and equipment for realizing process security based on Activiti workflow and readable storage medium

Abstract

The invention relates to the technical field of artificial intelligence, in particular to an Activiti workflow-based process security implementation method, device and equipment and a readable storage medium, and aims to effectively perform process nesting combination on Activiti workflows and transform an original two-dimensional flow chart into a three-dimensional mode so as to support complex business processes and improve the security of the process security. Meanwhile, the data security of the process information is ensured; in addition, the invention provides a number brushing script for flow chart change, so as to ensure the process safety of the in-transit process of changing the Activiti flow chart when the business process is changed; meanwhile, the invention provides a process log and business flow chart viewing component, has an isolation function of nested workflow, and upgrades an existing Activiti workflow engine into a functional component which is more powerful, flexible and easy to change and gives consideration to process data security.

Description

Technical Field

[0001] The present application relates to the field of computer technology, in particular to the application field of the financial technology industry, and in particular to a method, device, equipment and readable storage medium for implementing process security based on Activiti workflow. Background Art

[0002] At present, with the development and popularization of Internet office, the banking industry and many other industries will process their own business processes or internal processes online, which not only improves the timeliness of process processing, saves the time of relevant personnel, but also ensures the security and readability of process data (such as OA leave process). With the promotion of online business processes, a componentized tool called Activiti workflow engine has been widely developed and used. This functional component solves the problem of standardization of process nodes and node trends, and realizes document information transmission or task execution promotion between multiple participants according to predetermined rules, so as to achieve the expected business goals. However, under the existing technology, the Activiti workflow engine still has many limitations, such as the inability to handle complex business processes and the inability to ensure the data security of business processes; at the same time, with the rapid development of business, the business party is likely to change the existing process (such as adding a new node), and the current functional components cannot effectively support changes in business process diagrams and in-transit processes.

[0003] Therefore, a technical solution that can effectively handle complex business processes while ensuring the data security of business processes and can effectively support changes to business process diagrams and in-transit processes is a technical problem that needs to be urgently solved by technical personnel in this field. Summary of the invention

[0004] The purpose of this application is to solve at least one of the above technical defects. The technical solution adopted by this application is as follows:

[0005] In a first aspect, an embodiment of the present application provides a method for implementing process security based on Activiti workflow, the method comprising:

[0006] Create a main workflow with multiple nodes, each of which is associated with one or more sub-processes;

[0007] Each node in the main process is associated with a corresponding sub-workflow in a configured manner;

[0008] Set trigger conditions for each sub-process associated with the main process node, including forward drive and reverse drive conditions;

[0009] Through nested workflows, we can implement business process rules such as multi-process parallelism, multi-person processing on a single node, and multi-result-oriented business process rules on process nodes.

[0010] Optionally, the business process rules for implementing multi-process parallelism, single-node multi-person processing, and process node multi-result orientation through nested workflows include:

[0011] The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

[0012] Optionally, by configuring the association relationship between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

[0013] Optionally, after using the nested workflow,

[0014] The workflow engine includes a main process, which includes at least three nodes;

[0015] Node 1 and node 2 in the main process are each associated with at least one sub-process;

[0016] The main process node and the sub-process are bound through a configured association relationship;

[0017] The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process;

[0018] When the process returns to node 1, the condition triggers the corresponding sub-process;

[0019] If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1;

[0020] If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions;

[0021] You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time;

[0022] The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

[0023] In a second aspect, an embodiment of the present application provides a device for implementing process security based on Activiti workflow, the device comprising: a creation module, a configuration module, a setting module and an output module, wherein:

[0024] Creation module: used to create a main workflow containing multiple nodes, each of which is associated with one or more sub-processes;

[0025] Configuration module: used for each node in the main process, and associated with the corresponding sub-workflow in a configured manner;

[0026] Setting module: used to set trigger conditions for each sub-process associated with each main process node, including forward drive and reverse drive conditions;

[0027] Output module: used to implement multi-process parallelism, single-node multi-person processing, and multi-result-oriented business process rules for process nodes through nested workflows.

[0028] Optionally, the business process rules for implementing multi-process parallelism, single-node multi-person processing, and process node multi-result orientation through nested workflows include:

[0029] The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

[0030] Optionally, by configuring the association relationship between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

[0031] Optionally, after using the nested workflow, the output module includes:

[0032] The workflow engine includes a main process, which includes at least three nodes;

[0033] Node 1 and node 2 in the main process are each associated with at least one sub-process;

[0034] The main process node and the sub-process are bound through a configured association relationship;

[0035] The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process;

[0036] When the process returns to node 1, the condition triggers the corresponding sub-process;

[0037] If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1;

[0038] If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions;

[0039] You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time;

[0040] The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

[0041] In a third aspect, an embodiment of the present invention provides an electronic device, including a processor and a memory;

[0042] The memory is used to store operation instructions;

[0043] The processor is used to execute the above-mentioned method for achieving process safety based on Activiti workflow by calling the operation instruction.

[0044] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for implementing process security based on Activiti workflow is implemented.

[0045] The solution for realizing process security based on Activiti workflow disclosed in the embodiment of the present application creates a main workflow containing multiple nodes, wherein each node is associated with one or more sub-processes; each node in the main process is associated with the corresponding sub-workflow in a configured manner; trigger conditions are set for the sub-processes associated with each main process node; and multi-process parallelism, single-node multi-person processing, and multi-result-oriented business process rules for process nodes are realized through nested workflows. The beneficial effects brought by the technical solution provided in the embodiment of the present application are: the Activiti workflow is nested and combined, and the original two-dimensional flowchart is transformed into a three-dimensional mode (viewing the flowchart is changed to splitting multiple two-dimensional diagrams), so as to support complex business processes while ensuring the data security of process information; in addition, the present application provides a flowchart change brushing script to ensure the process security of the in-transit process of the Activiti flowchart when the business process changes; at the same time, the present application provides a process log and a business process diagram viewing component, which has the isolation function of the nested workflow, and upgrades the existing Activiti workflow engine into a more powerful, flexible and easy to change functional component that takes into account the security of process data. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0047] Figure 1 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0048] Figure 2 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0049] Figure 3 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0050] Figure 4 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0051] Figure 5 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0052] Figure 6 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0053] Figure 7 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0054] Figure 8 A flowchart of an embodiment of a method for implementing process security based on Activiti workflow provided in this application;

[0055] Fig. 9 A schematic diagram of the structure of an embodiment of a device for implementing process safety based on Activiti workflow provided by this application;

[0056] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.

[0058] It will be understood by those skilled in the art that, unless otherwise stated, the singular forms "a", "an" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0059] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0060] Activiti Workflow: An open source software tool that can be used to design and manage workflows, helping users automate various tasks and processes. For example, when a new order comes in, Activiti can automatically send a confirmation email, update inventory, generate invoices, etc. It is easy to use and has standardized support. It supports the BPMN2.0 standard, a common business language model, which helps developers to clearly design processes in a graphical way; it has a powerful tool set, including Activiti Modeler, Explorer, Engine and other functional components. The usage scenarios are usually approval processes, order processing and reimbursement processes.

[0061] In order to make the objectives, technical solutions and advantages of the present application more clear, the specific implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0062] The core of this invention is to provide a method for realizing process security based on Activiti workflow. Figure 1 The flowchart of the method for implementing process security based on Activiti workflow provided in this embodiment is shown in FIG. Figure 1 The technical solution of this embodiment is described in detail:

[0063] S101, creating a main workflow including multiple nodes, wherein each node may be associated with one or more sub-processes;

[0064] S102, for each node in the main process, associate the corresponding sub-workflow in a configured manner;

[0065] S103, setting trigger conditions for each sub-process associated with each main process node, including forward drive and reverse drive conditions;

[0066] S104. Implement complex business process rules such as multi-process parallelism, multi-person processing on a single node, and multi-result orientation of process nodes through nested workflows.

[0067] In the embodiment of the present application, the business process rules for implementing multi-process parallelism, single-node multi-person processing, and process node multi-result orientation through nested workflows include:

[0068] The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

[0069] In an embodiment of the present application, by configuring the association relationship between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

[0070] In an optional implementation of this embodiment, after using the nested workflow,

[0071] The workflow engine includes a main process, which includes at least three nodes;

[0072] Node 1 and node 2 in the main process are each associated with at least one sub-process;

[0073] The main process node and the sub-process are bound through a configured association relationship;

[0074] The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process;

[0075] When the process returns to node 1, the condition triggers the corresponding sub-process;

[0076] If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1;

[0077] If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions;

[0078] You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time;

[0079] The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

[0080] For example:

[0081] Figure 2The diagram shows the main process. The nested workflow is like a hierarchical tree. All nodes are in the main process or in the sub-process associated with the main process. Figure 2 As shown in the figure, the main process contains 3 nodes, among which node 1 and node 2 have associated sub-processes. The main process node and the sub-process can be bound through the association relationship, and the driving and reverse driving conditions can be set at the same time, such as Figure 2 In the main process node 1, you can set the sub-process to be triggered when the process returns to node 1. At this time, if it is a newly initiated business process, the corresponding sub-process will not be triggered after reaching node 1. If a node is associated with multiple workflows, you can also set trigger restrictions under different conditions, such as Figure 2 In node 2, you can set sub-process 2 as a must-trigger process. If the approval is rejected, sub-process 3 will be triggered at the same time. The main process is the top level of the entire nested process tree. All related processes and nodes can be traced back to the corresponding nodes in the main process.

[0082] Figure 3 The following is a schematic diagram of the sub-process. The difference between the sub-process diagram and the main process diagram is the nested workflow main process. Figure 1 There must be at least one node associated with a sub-process, but sub-workflows do not have this restriction, so Figure 3 As shown in the figure, assuming that the main process node 1 is associated with the sub-process 1, when the trigger condition of the corresponding node of the main process is met, the sub-process is triggered. At this time, the sub-process can be regarded as a separate workflow, unless the sub-process node is associated with other processes, which will trigger the associated process when specific conditions are met; otherwise, only when specific conditions are met will the main process be reversely driven. Figure 3 As shown, if the reverse driving condition is set to drive the main process node 1 to invalidation after the approval of the sub-process node 1, when the processor of the sub-process node 1 chooses to invalidate the business, the main process also goes to invalidation. Figure 3 The figure shows a two-layer nested workflow. If the business process is more complex, the sub-process nodes can be associated with the process to achieve a process tree with more levels.

[0083] Process change script: In the past, the workflow was a whole flowchart. Business process changes required modifying the entire diagram, and all business processes would be affected. After using the nested workflow component, the flowchart is divided into multiple modules. Only the corresponding workflow needs to be changed (most of the time, the sub-workflow node process is changed), and the processes involved in the flowchart are governed at the same time. The script involves 25 forms generated by linking to the database when the Activiti engine is deployed, among which GE is general data, hi is historical data, act_id is the user table, re is the process definition table, and ru is the running instance table (in-transit data). The specific script content is as follows:

[0084] / / Deployed process definition, check the latest deployed process ID_, and refresh the PROC_DEF_ID_ of the in-progress process to the latest ID_

[0085] SELECT ID_FROM Activiti.act_re_procdef WHERE KEY_='process name' ORDER BY VERSION_DESC LIMIT 1;

[0086] / / View the process definition ID corresponding to the in-transit process

[0087] SELECT PROC_DEF_ID_FROM Activiti.act_ru_task WHERE PROC_DEF_ID_LIKE '%process name%';

[0088] / / Tasks running in transit, if PROC_DEF_ID_ is multiple, where in is displayed.

[0089] UPDATE Activiti.act_ru_task SET PROC_DEF_ID_='latest deployed PROC_DEF_ID_' WHERE PROC_DEF_ID_='on the way PROC_DEF_ID_';

[0090] / / Historical process node instance

[0091] UPDATE Activiti.act_hi_taskinst SET PROC_DEF_ID_='latest deployed PROC_DEF_ID_' WHERE PROC_DEF_ID_='on the way PROC_DEF_ID_';

[0092] / / Historical process instance (main process)

[0093] UPDATE Activiti.act_hi_procinst SET PROC_DEF_ID_='latest deployed PROC_DEF_ID_' WHERE PROC_DEF_ID_='on the way PROC_DEF_ID_';

[0094] / / Historical workflow node instance

[0095] UPDATE Activiti.act_hi_actinst SET PROC_DEF_ID_='latest deployed PROC_DEF_ID_' WHERE PROC_DEF_ID_='on the way PROC_DEF_ID_';

[0096] / / In-transit process execution instance

[0097] UPDATE Activiti.act_ru_execution SET PROC_DEF_ID_='latest deployed PROC_DEF_ID_' WHERE PROC_DEF_ID_='on the way PROC_DEF_ID_';

[0098] Flowchart and business log viewing component: In the prior art, flowcharts and logs are viewed by displaying the entire business process diagram and the entire business processing log. Because they are all associated with a workflow ID, after using nested workflows, the scope of different inspections can be displayed according to conditions, such as only displaying the current sub-process or main process diagram, or displaying the current sub-process and the corresponding main process diagram. At the same time, all log information will be associated with the corresponding main process, and the role node condition can be used to limit the display of the current sub-process log or the main process log, or all process log information.

[0099] The following will use the entire process of production events in the integrated development and operation platform as an example to introduce the method of implementing process security based on Activiti workflow described in the embodiment of this application to implement complex business process logic such as multi-process parallelism, single-node multi-processor, and multi-result orientation of process nodes; at the same time, it has been verified that the process change brushing script can be widely used in the flowchart change requirements of deployed processes, reducing the development resources and change risks of business process changes; and after process separation, the business process diagram and production log can flexibly configure the query range to ensure business information security. The implementation process of the solution to achieve process security based on Activiti workflow is as follows:

[0100] Step 1: Confirm the business logic and divide the process;

[0101] Before drawing the Activiti flowchart, you need to confirm the overall business logic, clarify the overall business process diagram, node direction, and trigger logic. If the process logic is more complex and you need to consider the application of nested functional components in the process, you need to split the process nodes according to the sorted business logic and divide the process into the main process and the following sub-processes. Figure 4 As shown, the nodes involved in the overall process are too complex, and the existing Activiti workflow cannot meet the business logic requirements, so the overall process needs to be split. Figure 4 The entire production process has been segmented into business processes. Figure 4 It can be seen that in addition to the main process, there are several sub-processes, namely transfer, appeal, project review, test review, soliciting field opinions and arbitration sub-processes.

[0102] Step 2: Draw the main flow chart and process logic;

[0103] After clarifying the business process and dividing the process, you need to confirm the main process diagram first, and then you can draw the associated sub-processes and set the logic under each node of the main process.

[0104] See also Figure 5 As shown in the figure, it is the main flow chart after the split design. Except for the start and end nodes, only the first pending node is a separate node, and all other nodes are associated with nested sub-processes, such as the project team review associated with the project review sub-process, and the test review associated with the test review sub-process. According to the process shown in the figure, when the process moves from the pending node to the subsequent node, the corresponding sub-process will be triggered, so the complex logic required by the business side can be realized.

[0105] Step 3: Draw sub-flow chart and process logic;

[0106] After the main flow chart is drawn, according to the previously divided associated process relationships, sub-flow charts are drawn for the nodes in the main flow chart that involve associated sub-flow charts, and the associated relationships and sub-flow logic development settings are set. Since there are many sub-flows associated with the main process nodes of production events, only the project review and test review sub-flows are displayed here.

[0107] See also Figure 6As shown in the figure, there are two sub-processes associated with the main process nodes of production events, which have different triggering, process running flow, and reverse driving main process logic. First of all, when the main process runs from the first pending node to the next node, after selecting the project review, the main process node will flow to the project review node, and the project review sub-process will be triggered at the same time. According to the rules of the business side, the project review process can be triggered in parallel. At the same time, each process can choose to initiate a new project review process at the quality team approval node. Therefore, the project review sub-process realizes the technical difficulty of multi-process parallelism that cannot be achieved in the original Activiti workflow. When the quality team chooses to approve the end of the test review, if there is no project review process in progress, the main process will be reversed to the test review node, and the test review sub-process will be triggered at the same time. The test review process is a multi-process serial according to the needs of the business side. As shown in the figure, when the test review process is driven, three business process lines will be triggered, that is, there will be three processors at the test review node. When the three processors complete the processing at the same time, it will flow to the domain CTO approval node, which is also the three CTO serial approval. After all are passed, they will be summarized to the section interface person. After passing, it will be submitted to the quality team for approval. The quality team can choose to pass and reverse drive different main process nodes, such as ending the process, arbitration, and soliciting opinions from the field. If the latter two are selected, the main process will trigger the corresponding sub-process after going to the corresponding node. At the same time, the quality team and the section interface person can choose to return the operation, and can select three test reviewers individually or select multiple ones to return and re-test the review. Such complex and special business logic is difficult to draw directly from the Activiti flowchart, and it can be better implemented by using the workflow nesting method.

[0108] Step 4: View components and permission settings in the log flow chart;

[0109] After the flowchart and associated business logic are drawn and set, you can develop and set auxiliary components, such as flowchart display components, log display components, etc. Associated nested workflows can more intuitively display business logic and process trends.

[0110] See also Figure 7 The main flow chart of a completed production event process is shown in Figure 7 We can clearly see the direction of the business process, from pending to project review to test review, soliciting field opinions, and the arbitration process ends. When we want to view the process information of a specific sub-process, we can also view it separately.

[0111] Figure 8 The figure shows the flow chart of the test process in the previous production event process. It can be seen that in the test review, after the quality team approved it, they chose to solicit opinions from the field. As shown in the main process, the test review node flows to the node for soliciting opinions from the field.

[0112] By setting business logic and flowchart log components, information isolation can be perfectly achieved. For example, in a project review sub-process, the reviewer can only see his own review log process information, and cannot see the review information of other project teams or the process information of the entire production event process.

[0113] The solution for achieving process security based on Activiti workflow provided in the embodiment of the present application realizes the process nesting and combination of Activiti workflow, and transforms the original two-dimensional flowchart into a three-dimensional mode (viewing the flowchart is changed to splitting into multiple two-dimensional diagrams), so as to support complex business processes while ensuring the data security of process information; in addition, the present embodiment provides a flowchart change brushing script to ensure the process security of the in-transit process of changing the Activiti flowchart when the business process changes; at the same time, the present embodiment provides a process log and a business process diagram viewing component, which have the isolation function of nested workflows, and upgrades the existing Activiti workflow engine into a more powerful, flexible and easy to change functional component that takes into account the security of process data.

[0114] based on Figure 1 The embodiment shown provides a method for implementing process security based on Activiti workflow. Fig. 9 A device for implementing process security based on Activiti workflow provided by an embodiment of the present application is shown. Fig. 9 As shown, the device may mainly include: a creation module 201, a configuration module 202, a setting module 203 and an output module 204, wherein:

[0115] Creation module 201: used to create a main workflow including multiple nodes, wherein each node is associated with one or more sub-processes;

[0116] Configuration module 202: used for each node in the main process, and associated with the corresponding sub-workflow in a configured manner;

[0117] Setting module 203: used to set trigger conditions for sub-processes associated with each main process node, including forward driving and reverse driving conditions;

[0118] Output module 204: used to implement multi-process parallelism, single-node multi-person processing, and process node multi-result-oriented business process rules through nested workflows.

[0119] In the embodiment of the present application, the business process rules for implementing multi-process parallelism, single-node multi-person processing, and process node multi-result orientation through nested workflows include:

[0120] The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

[0121] In an embodiment of the present application, by configuring the association relationship between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

[0122] In an optional implementation of this embodiment, after using the nested workflow,

[0123] The workflow engine includes a main process, which includes at least three nodes;

[0124] Node 1 and node 2 in the main process are each associated with at least one sub-process;

[0125] The main process node and the sub-process are bound through a configured association relationship;

[0126] The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process;

[0127] When the process returns to node 1, the condition triggers the corresponding sub-process;

[0128] If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1;

[0129] If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions;

[0130] You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time;

[0131] The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

[0132] It can be understood that the above modules of the device for realizing process safety based on Activiti workflow in this embodiment have the function of realizing Fig. 9The functions of the corresponding steps of the method in the embodiment shown in . The function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above functions. The above modules can be software and / or hardware, and the above modules can be implemented separately or integrated with multiple modules. For the functional description of the above modules, please refer to Fig. 9 The corresponding description of the method in the embodiment shown in will not be repeated here.

[0133] The solution for achieving process security based on Activiti workflow provided in the embodiment of the present application realizes the process nesting and combination of Activiti workflow, and transforms the original two-dimensional flowchart into a three-dimensional mode (viewing the flowchart is changed to splitting into multiple two-dimensional diagrams), so as to support complex business processes while ensuring the data security of process information; in addition, the present embodiment provides a flowchart change brushing script to ensure the process security of the in-transit process of changing the Activiti flowchart when the business process changes; at the same time, the present embodiment provides a process log and a business process diagram viewing component, which have the isolation function of nested workflows, and upgrades the existing Activiti workflow engine into a more powerful, flexible and easy to change functional component that takes into account the security of process data.

[0134] An embodiment of the present application provides an electronic device, including a processor and a memory;

[0135] A memory, used for storing operation instructions;

[0136] The processor is used to execute the method for achieving process security based on Activiti workflow provided in any implementation mode of the present application by calling operation instructions.

[0137] As an example, Fig.10 A schematic diagram of the structure of an electronic device applicable to the embodiment of the present application is shown. Fig.10 As shown, the electronic device 2000 includes: a processor 2001 and a memory 2003. The processor 2001 and the memory 2003 are connected, such as through a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that in actual applications, the transceiver 2004 is not limited to one, and the structure of the electronic device 2000 does not constitute a limitation on the embodiments of the present application.

[0138] The processor 2001 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter. The transceiver 2004 is applied in the embodiment of the present application to implement the function of the electronic device of the embodiment of the present application communicating with other devices when executed.

[0139] Processor 2001 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 2001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0140] The bus 2002 may include a path to transmit information between the above components. The bus 2002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 2002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0141] The memory 2003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0142] Optionally, the memory 2003 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 2001. The processor 2001 is used to execute the application code stored in the memory 2003 to implement the method for realizing process security based on the Activiti workflow provided in any embodiment of the present application.

[0143] The electronic device provided in the embodiment of the present application is applicable to any embodiment of the above method and will not be described in detail here.

[0144] The solution for achieving process security based on Activiti workflow provided in the embodiment of the present application realizes the process nesting and combination of Activiti workflow, and transforms the original two-dimensional flowchart into a three-dimensional mode (viewing the flowchart is changed to splitting into multiple two-dimensional diagrams), so as to support complex business processes while ensuring the data security of process information; in addition, the present embodiment provides a flowchart change brushing script to ensure the process security of the in-transit process of changing the Activiti flowchart when the business process changes; at the same time, the present embodiment provides a process log and a business process diagram viewing component, which have the isolation function of nested workflows, and upgrades the existing Activiti workflow engine into a more powerful, flexible and easy to change functional component that takes into account the security of process data.

[0145] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for implementing process security based on the Activiti workflow shown in the above method embodiment is implemented.

[0146] The computer-readable storage medium provided in the embodiments of the present application is applicable to any embodiment of the above method and will not be described in detail here.

[0147] The solution for achieving process security based on Activiti workflow provided in the embodiment of the present application realizes the process nesting and combination of Activiti workflow, and transforms the original two-dimensional flowchart into a three-dimensional mode (viewing the flowchart is changed to splitting into multiple two-dimensional diagrams), so as to support complex business processes while ensuring the data security of process information; in addition, the present embodiment provides a flowchart change brushing script to ensure the process security of the in-transit process of changing the Activiti flowchart when the business process changes; at the same time, the present embodiment provides a process log and a business process diagram viewing component, which have the isolation function of nested workflows, and upgrades the existing Activiti workflow engine into a more powerful, flexible and easy to change functional component that takes into account the security of process data.

[0148] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the specific device can be divided into different functional modules to complete all or part of the functions described above.

[0149] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0150] In several embodiments covered by the present application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. For example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, or it can be an electrical, mechanical or other form of connection.

[0151] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0152] In addition, each functional module in each embodiment of the present application can be implemented in the form of hardware or in the form of software functional modules. If these functional modules are implemented in the form of software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or part of the prior art that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a computer program product, which includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program product is stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, a computer instruction can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)).

[0153] The above contents are merely examples and explanations of the structure of the present invention. The technicians in this technical field may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the structure of the invention or exceed the scope defined by the claims, they should all fall within the protection scope of the present invention.

Claims

1. A method for implementing process security based on Activiti workflow, characterized in that: The method comprises: Create a main workflow with multiple nodes, each of which is associated with one or more sub-processes; Each node in the main process is associated with a corresponding sub-workflow in a configured manner; Set trigger conditions for each sub-process associated with the main process node, including forward drive and reverse drive conditions; Through nested workflows, we can implement business process rules such as multi-process parallelism, multi-person processing on a single node, and multi-result-oriented business process rules on process nodes.

2. According to the method for realizing process safety based on Activiti workflow according to claim 1, it is characterized in that: The business process rules for implementing multi-process parallelism, multi-person processing on a single node, and multi-result orientation on process nodes through nested workflows include: The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

3. The method for realizing process safety based on Activiti workflow according to claim 2 is characterized in that: By configuring the association between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

4. The method for realizing process safety based on Activiti workflow according to claim 1 is characterized in that: After using the nested workflow, The workflow engine includes a main process, which includes at least three nodes; Node 1 and node 2 in the main process are each associated with at least one sub-process; The main process node and the sub-process are bound through a configured association relationship; The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process; When the process returns to node 1, the condition triggers the corresponding sub-process; If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1; If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions; You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time; The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

5. A device for implementing process safety based on Activiti workflow, characterized in that: The device comprises: a creation module, a configuration module, a setting module and an output module, wherein: Creation module: used to create a main workflow containing multiple nodes, each of which is associated with one or more sub-processes; Configuration module: used for each node in the main process, and associated with the corresponding sub-workflow in a configured manner; Setting module: used to set trigger conditions for each sub-process associated with each main process node, including forward drive and reverse drive conditions; Output module: used to implement multi-process parallelism, single-node multi-person processing, and multi-result-oriented business process rules for process nodes through nested workflows.

6. The device for realizing process safety based on Activiti workflow according to claim 5 is characterized in that: The business process rules for implementing multi-process parallelism, multi-person processing on a single node, and multi-result orientation on process nodes through nested workflows include: The process node of the main workflow is associated with one or more different sub-workflows through configuration, and the process node of the sub-workflow can be reconfigured as the process node of the main workflow to be associated with other processes.

7. The device for realizing process safety based on Activiti workflow according to claim 6 is characterized in that: By configuring the association between the process nodes of the main workflow and the process nodes of the sub-workflow, when the main workflow reaches the corresponding process node, the generation of the sub-workflow process is driven; wherein the sub-workflow is regarded as a separate business process, or as an additional process associated with the main process; at the same time, after the sub-process after the association relationship is configured reaches a specific node condition, it reversely drives the main process to promote the business process.

8. The device for implementing process safety based on Activiti workflow according to claim 5 is characterized in that: After using the nested workflow, The workflow engine includes a main process, which includes at least three nodes; Node 1 and node 2 in the main process are each associated with at least one sub-process; The main process node and the sub-process are bound through a configured association relationship; The configured association relationship allows setting the conditions for driving the sub-process and the conditions for the sub-process to reversely drive the main process; When the process returns to node 1, the condition triggers the corresponding sub-process; If the business process is newly initiated, the corresponding sub-process will not be triggered after reaching node 1; If the node is associated with multiple sub-processes, trigger restrictions can be set according to different conditions; You can set sub-process 2 as a must-trigger process, and if the approval is returned, sub-process 3 will be triggered at the same time; The main process is the top layer of the entire nested process tree, and all associated processes and nodes can be traced back to the corresponding nodes in the main process.

9. An electronic device, characterized in that: including a processor and a memory; The memory is used to store operation instructions; The processor is used to execute the method according to any one of claims 1 to 4 by calling the operation instruction.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images