A method, device, equipment and medium for dynamically adding approval nodes to a business process
By presetting events, rules and manual sign-up operations in the process engine, and dynamically adding approval nodes, the problem of inefficient approval caused by business process solidification in the existing technology is solved, flexible approval processes are realized, and corporate approval efficiency is improved.
Patent Information
- Application Number
- CN202410768116.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-14
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2044-06-14
AI Technical Summary
The existing business processes are solidified and cannot dynamically sign up, resulting in inefficient corporate approval and inability to meet the complex and changing approval needs.
Preset event sign-up, rule sign-up and manual sign-up operations in the process engine, dynamically add approval nodes through event feature values, sign-up rules and user manual operations, and configuration information is persisted to the database, so that the process engine can be implemented according to different permissions and The rules automatically or manually generate sign-up nodes.
A variety of flexible sign-up methods have been realized, which meets complex approval needs and improves the process approval efficiency of enterprises.
Smart Images

Figure CN118485408B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of business process engines, and in particular to a method, device, equipment and medium for dynamically adding approval nodes to a business process. Background Art
[0002] In the context of paperless office, process office is an important part of almost every enterprise office. However, the original process is solidified in the program, and it is impossible to implement dynamic signature according to business needs or it can only meet the signature in specific scenarios, which is in sharp contradiction with the complex and changeable approval business needs of large and medium-sized companies. Ultimately, due to the solidification and low flexibility of business processes, the approval efficiency of enterprises is low. Summary of the invention
[0003] The technical problem to be solved by the present invention is to provide a method, device, equipment and medium for dynamically adding approval nodes to a business process, and to solve the contradiction between relatively rigid business processes and complex and changeable approval requirements by implementing multiple flexible signing methods at the approval nodes, thereby improving approval efficiency.
[0004] In a first aspect, the present invention provides a method for dynamically adding an approval node to a business process, comprising:
[0005] Configuration process: Preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; obtain the signing authority of the specified node configured through the process designer, and then persist the node configuration information to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and corresponding signing node must be configured. The configuration of the signing rule depends on the specified form field.
[0006] Dynamic node addition process: When the process is initiated, a process running instance is created. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, a logical judgment is made based on the signing rule and the value of the corresponding form field. If the judgment result is that a signing is required, a signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, a specified signing node is generated according to the signing operation;
[0007] Update process: The configuration information of the generated signature node is persisted in the database. After the back-end signature process is completed, the front-end re-renders the page to display the new process after signature.
[0008] In a second aspect, the present invention provides a device for dynamically adding an approval node to a business process, comprising:
[0009] The configuration module is used to preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; obtain the signing authority of the specified node configured by the process designer, and then persist the configuration information of the node to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and corresponding signing node must be configured, and the configuration of the signing rule depends on the specified form field;
[0010] The node dynamic addition module is used to create a process running instance when the process is initiated. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, logical judgment is performed based on the signing rule and the value of the corresponding form field. If the judgment result is that signing is required, the signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, the specified signing node is generated according to the signing operation;
[0011] The update module is used to persist the configuration information of the generated signature node to the database, complete the back-end signature process, and re-render the page on the front end to display the new process after signature.
[0012] In a third aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the program.
[0013] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.
[0014] The technical solution provided in the embodiments of the present invention has at least the following technical effects:
[0015] By implementing three different signing methods: event signing, rule signing, and manual signing, during the process flow, the process engine can dynamically add approval nodes based on the event feature values selected when the process is drawn, the configured signing rules, or the node configuration information created by the processor through manual signing when the process is running. This meets the needs of the processor who needs other people to handle the approval together or needs to notify other people, resolves the contradiction between relatively rigid business processes and complex and changeable approval needs, and improves the company's process approval efficiency.
[0016] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.
[0018] Figure 1 This is a schematic diagram of the framework of the process engine according to an embodiment of the present invention;
[0019] Figure 2 is an overall flow chart of the method in Embodiment 1 of the present invention;
[0020] Figure 3 This is a schematic diagram of the process of signing an event in Embodiment 1 of the present invention;
[0021] Figure 4 This is a schematic diagram of the process of adding a rule in the first embodiment of the present invention;
[0022] Figure 5 This is a schematic diagram of the manual signing process in Embodiment 1 of the present invention;
[0023] Figure 6 It is a schematic diagram of the structure of the device in the second embodiment of the present invention. DETAILED DESCRIPTION
[0024] The embodiments of the present invention provide a method, device, equipment and medium for dynamically adding approval nodes to a business process, and implement a variety of flexible signing methods at the approval nodes to resolve the contradiction between relatively rigid business processes and complex and changeable approval requirements, thereby improving approval efficiency.
[0025] The technical solution in the embodiment of the present invention has the following general idea:
[0026] The process engine framework corresponding to the method of the embodiment of the present invention is as follows: Figure 1As shown, it is roughly divided into three parts: form designer, process designer and process running instance. The form designer is used to configure form fields, which are set according to business process requirements and associate the form with the business process. The process designer is used to provide a visual interface to draw processes and configure node data, and is usually operated by a process administrator. When a process is initiated, form information and process information are obtained to create a process running instance; during the process flow, the process engine can obtain the configuration information of each process approval node. The embodiment of the present invention solves the problem of insufficient flexibility in signing from three aspects, including event signing, rule signing, and manual signing. In this embodiment, the process administrator can configure any kind of signing authority for the specified approval node as needed.
[0027] Event signing: Before the process is initiated, it is configured inside the process engine and automatically signed when the event feature value matches.
[0028] Based on the relevant experience of the enterprise approval process, the developers preset some event signing operations and corresponding event characteristic values in the process engine, and predefine the relevant configuration information of the signing node based on the different types of preset events. Draw the process in the process designer interface and configure the node permissions. When configuring the node permissions, if you choose to sign the event, you need to select the characteristic value corresponding to the preset event. After the process is initiated, the process running instance information is created. When the process flows to the approval node, the process engine reads the configuration information of the approval node, and matches the characteristic value obtained from the approval node with the preset event characteristic value. If the match is successful, the event is automatically executed for signing.
[0029] Rule-based signing: Before the process is initiated, sign-based rules are configured when drawing the flowchart in the process designer. Sign-based signing is performed only when the process engine determines that the approval node meets the sign-based signing rules.
[0030] Based on business process requirements, configure form information in the form designer interface and associate the form with the process; based on business process requirements, draw the process and configure node data in the process designer interface, where signature rules are manually configured when configuring node permissions, and there is no limit on the number of signature rules; based on the configured form information, the process node can obtain relevant form fields, and the signature rule configuration depends on the form fields; after the process is initiated, the process running instance information will be created; when the process flows to the approval node, the process engine will read the node configuration information and read the signature rules from the configuration information; based on the signature rules, the process engine will determine whether the signature rules are met based on the form information and decide whether to sign or not.
[0031] Manual signature: After the process is initiated, the process engine executes according to the manual signature information of the user at the current approval node.
[0032] In addition to selecting the manual signature permission when drawing the flowchart and configuring the node information in the process designer interface, the previous steps are consistent with the processing of rule signatures before the process running instance reaches the approval node; based on the approval node with manual signature permission after the process is initiated, the user's manual signature will notify the process engine to perform the signature operation; the process engine creates a signature node based on the user's manual signature information and the predefined node configuration information. Embodiment 1
[0033] This embodiment provides a method for dynamically adding approval nodes to a business process, such as Figure 2 As shown, including:
[0034] Configuration process: Preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; obtain the signing authority of the specified node configured through the process designer, and then persist the node configuration information to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and corresponding signing node must be configured. The configuration of the signing rule depends on the specified form field.
[0035] Dynamic node addition process: When the process is initiated, a process running instance is created. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, a logical judgment is made based on the signing rule and the value of the corresponding form field. If the judgment result is that a signing is required, a signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, a specified signing node is generated according to the signing operation;
[0036] Update process: The configuration information of the generated signature node is persisted in the database. After the back-end signature process is completed, the front-end re-renders the page to display the new process after signature.
[0037] Specifically, the configuration process is also used to add components for selecting event characteristic values, rule signing components, and manual signing components to the approval node configuration authority setting interface on the front-end page of the process designer, so that the signing authority of the specified node can be configured through the process designer.
[0038] Preferably, during the dynamic addition of nodes, when the process flows to the approval node, the process engine performs logical judgment based on the signing rule, first performs a legality check, and excludes it. If the legality check fails, no signing will be performed. After the legality check passes, logical judgment is performed based on the signing rule and the value of the corresponding form field. The legality check is used to avoid executing incorrectly configured signing rules. For example, when checking the number of days of leave, when the process designer sets the signing rule, the form field corresponding to the number of days of leave should be obtained, but the process administrator selects other fields.
[0039] From the perspective of the signature types implemented by the process engine, there are event signatures, rule signatures, and manual signatures. The following is a detailed description of the implementation process of each signature type:
[0040] Event signing: configure event feature values at process nodes for signing. Event feature values correspond to built-in events in the process engine one by one, that is, event signing is configured inside the process engine. The implementation steps can be as follows: Figure 3 As shown:
[0041] Step A1: Developers preset some events in the process engine for performing signature operations based on the commonly used signature scenarios in the actual business process, and generate a corresponding event feature value for each preset event. The preset events are abstracted based on the business scenarios that appear frequently in the actual business process of the enterprise. The form designer is used to configure form fields, which are set according to the business process requirements.
[0042] Step A2: Draw a flowchart in the process designer and configure event feature values. The form is related to the process. On the front page of the process designer, add a component for selecting event feature values in the approval node configuration permission interface. The optional event feature values are obtained from the process designer server. When the process administrator uses the process designer to draw the process and configure node permission information, the configuration information of the node will be persisted in the database.
[0043] Step A3: Initiate a process and create a process running instance.
[0044] Step A4: During the process flow, the process engine can read the configuration information of each approval node, that is, the process engine can obtain the event characteristic value information of the approval node configured with the event characteristic value.
[0045] Step A5: Match the approval node feature value with the preset event feature predefined by the server, and decide whether to execute the signing operation according to the matching result. If the match is successful, execute the corresponding event signing operation.
[0046] Rule signing is a method of signing by configuring rules at process nodes. That is, rule signing is configured during process design. The implementation steps can be as follows Figure 4 As shown:
[0047] Step B1: Based on the business process, configure the form fields in the form designer;
[0048] Step B2: Draw a flowchart in the process designer and configure the signing rules for the approval nodes. The signing rules can be configured through the rule signing component in the process designer, and the rule signing component can obtain the corresponding form field information configured in the form designer. There is no limit on the number of signing rules, and the signing rules depend on the form fields for configuration.
[0049] Step B3: Initiate the process and create a process running instance.
[0050] Step B4, the process flows to the approval node, the process engine reads the node configuration information, obtains the signing rules, and makes logical judgments based on the signing rules. First, a legality check is performed. If the legality check fails, no signing will be performed. After the legality check passes, the process engine will proceed to the next step.
[0051] Step B5: The process engine performs a signing operation according to the relevant information of the signing rule. The configuration information of the signing node is predefined in the process engine.
[0052] Manual signature: During the process flow, the processor manually signs. The implementation steps can be as follows: Figure 5 As shown:
[0053] Step C1: Configure the form in the form designer based on the business process.
[0054] Step C2: Create a flowchart in the process designer and enable manual signing permissions.
[0055] Step C3: During the process flow, the approval node processor can manually sign in the interface to notify the process engine to sign.
[0056] Step C4: The process engine will first make a pre-judgment to verify whether the current node has the authority to add signatures. If so, the signing operation will be performed according to the node processor's operation.
[0057] After the signature operation is executed, the process engine persists the configuration information of the three types of signatures to the database. After the back-end signature process is completed, the front-end will re-render the page to display the new process. The above method can achieve flexible signatures, greatly improving the efficiency of enterprise approval.
[0058] Based on the same inventive concept, the present application also provides a device corresponding to the method in Example 1, see Example 2 for details. Embodiment 2
[0059] In this embodiment, a device for dynamically adding approval nodes to a business process is provided. Figure 6 As shown, including:
[0060] The configuration module is used to preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; obtain the signing authority of the specified node configured by the process designer, and then persist the configuration information of the node to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and corresponding signing node must be configured, and the configuration of the signing rule depends on the specified form field;
[0061] The node dynamic addition module is used to create a process running instance when the process is initiated. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, logical judgment is performed based on the signing rule and the value of the corresponding form field. If the judgment result is that signing is required, the signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, the specified signing node is generated according to the signing operation;
[0062] The update module is used to persist the configuration information of the generated signature node to the database, complete the back-end signature process, and re-render the page on the front end to display the new process after signature.
[0063] Preferably, the configuration module is also used to add components for selecting event characteristic values, rule signing components and manual signing components to the approval node configuration authority setting interface on the front-end page of the process designer, so that the signing authority of the specified node can be configured through the process designer.
[0064] Preferably, in the node dynamic adding module, when the process flows to the approval node, the process engine performs logical judgment based on the signing rules, first performing a legality check. If the legality check fails, no signing will be performed. After the legality check passes, logical judgment is performed based on the signing rules and the values of the corresponding form fields.
[0065] Since the device introduced in the second embodiment of the present invention is a device used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All devices used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.
[0066] Based on the same inventive concept, the present application provides an electronic device embodiment corresponding to the first embodiment, see the third embodiment for details. Embodiment 3
[0067] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, any implementation method in the first embodiment can be implemented.
[0068] Since the electronic device introduced in this embodiment is a device used to implement the method in the first embodiment of the present application, based on the method introduced in the first embodiment of the present application, a person skilled in the art can understand the specific implementation of the electronic device of the present embodiment and its various variations, so how the electronic device implements the method in the embodiment of the present application is not described in detail here. As long as a person skilled in the art implements the device used by the method in the embodiment of the present application, it belongs to the scope of protection of the present application.
[0069] Based on the same inventive concept, the present application provides a storage medium corresponding to the first embodiment, see the fourth embodiment for details. Embodiment 4
[0070] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any implementation method in the first embodiment can be implemented.
[0071] Since the computer-readable storage medium introduced in this embodiment is a computer-readable storage medium used to implement the method in the first embodiment of the present application, based on the method introduced in the first embodiment of the present application, a person skilled in the art can understand the specific implementation of the computer-readable storage medium of the present embodiment and its various variations, so how the computer-readable storage medium implements the method in the embodiment of the present application is not described in detail here. As long as a person skilled in the art implements the computer-readable storage medium used in the method in the embodiment of the present application, it belongs to the scope of protection of the present application.
[0072] The present invention realizes three different signing methods: event signing, rule signing and manual signing. During the process flow, the process engine can dynamically add approval nodes according to the event feature values selected when the process is drawn or the configured signing rules, or the node configuration information created by the processor through manual signing when the process is running, which meets the needs of the processor for other people to jointly handle or notify other people when approving, solves the contradiction between relatively rigid business processes and complex and changeable approval needs, and improves the process approval efficiency of the enterprise.
[0073] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0074] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0075] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0076] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0077] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.
Claims
1. A method for dynamically adding approval nodes to a business process, characterized in that: include: Configuration process: Preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; Obtain the signing authority of the specified node configured through the process designer, and then persist the node configuration information to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and the corresponding signing node must be configured. The configuration of the signing rule depends on the specified form field. Dynamic node addition process: When the process is initiated, a process running instance is created. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, a logical judgment is made based on the signing rule and the value of the corresponding form field. If the judgment result is that a signing is required, a signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, a specified signing node is generated according to the signing operation; Update process: The configuration information of the generated signature node is persisted in the database. After the back-end signature process is completed, the front-end re-renders the page to display the new process after signature.
2. The method according to claim 1, characterized in that: In the approval node configuration permission setting interface on the front-end page of the process designer, add components for selecting event characteristic values, rule signing components, and manual signing components, so that the signing permissions of specified nodes can be configured through the process designer.
3. The method according to claim 1, characterized in that: When the process flows to the approval node, the process engine performs logical judgment based on the signing rules. First, a legality check is performed. If the legality check fails, no signing will be performed. After the legality check passes, logical judgment is performed based on the signing rules and the values of the corresponding form fields.
4. A device for dynamically adding approval nodes to a business process, characterized in that: include: The configuration module is used to preset event signing operations and corresponding signing nodes in the process engine, and generate corresponding event feature values for each event signing operation; Obtain the signing authority of the specified node configured through the process designer, and then persist the node configuration information to the database. Each specified node can be configured with at most one of the following permissions: event signing, rule signing, and manual signing. When configuring rule signing, at least one signing rule and the corresponding signing node must be configured. The configuration of the signing rule depends on the specified form field. The node dynamic addition module is used to create a process running instance when the process is initiated. When the process flows to the approval node, the process engine obtains the configuration information of the approval node. When the event signing authority is configured, the event signing operation is automatically performed according to the obtained event feature value to generate a preset signing node; when the rule signing authority is configured, logical judgment is performed based on the signing rule and the value of the corresponding form field. If the judgment result is that signing is required, the signing node corresponding to the signing rule is generated; when the manual signing authority is configured, if the signing operation of the node processor is obtained, the specified signing node is generated according to the signing operation; The update module is used to persist the configuration information of the generated signature node to the database, complete the back-end signature process, and re-render the page on the front end to display the new process after signature.
5. The device according to claim 4, characterized in that: The configuration module is also used to add components for selecting event characteristic values, rule signing components, and manual signing components to the approval node configuration authority setting interface on the front-end page of the process designer, so that the signing authority of the specified node can be configured through the process designer.
6. The device according to claim 4, characterized in that: In the node dynamic addition module, when the process flows to the approval node, the process engine performs logical judgment based on the signing rules, first performing a legality check. If the legality check fails, no signing will be performed. After the legality check passes, logical judgment is performed based on the signing rules and the values of the corresponding form fields.
7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 3 is implemented.
8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 3 is implemented.
