Data approval method and device, computer equipment, medium and product

Abstract

The embodiment of the invention discloses a data approval method and device, computer equipment, a medium and a product, which can be applied to various scenes such as cloud technology, artificial intelligence, intelligent traffic, auxiliary driving and the like, and the method comprises the following steps: obtaining a configuration operation on an approval form of a target service in an approval configuration interface of the target service, and generating a service approval form; the business approval form comprises a plurality of approval fields configured for the target business; obtaining a configuration operation on the approval process of the target business in the approval configuration interface, and generating a business approval process; the business approval process comprises a plurality of approval nodes for the target business; in the examination and approval configuration interface, selecting associated examination and approval fields for examination and approval nodes of the business examination and approval process based on the business examination and approval form; based on the business approval process, the business approval form and an approval field associated with an approval node of the business approval process, generating approval configuration data for performing approval processing on the target business; the development efficiency of examination and approval can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data approval method, apparatus, computer equipment, medium, and product. Background Technology

[0002] With the development of digitalization in the market economy, various enterprises may encounter approval needs for transactions such as transfers and purchases. During the approval process, documents are typically submitted to different approval bodies, resulting in lengthy processing times and low efficiency. To improve efficiency, developers have created approval workflows. However, these workflows are usually only applicable to specific business scenarios. Adding new workflows requires developers to rewrite the corresponding code, which is time-consuming and labor-intensive, further reducing development efficiency. Therefore, improving the development efficiency of approval processes has become a current research hotspot. Summary of the Invention

[0003] This application provides a data approval method, apparatus, computer equipment, medium, and product, which can improve the development efficiency of approval.

[0004] In a first aspect, embodiments of this application provide a data approval method; the method includes:

[0005] The system retrieves the configuration operations for the approval form of the target business in the approval configuration interface of the target business, and generates the business approval form for the target business; the business approval form contains multiple approval fields configured for the target business.

[0006] The configuration operation for the approval process of the target business is obtained in the approval configuration interface, and the business approval process of the target business is generated; the business approval process includes multiple approval nodes for the target business;

[0007] In the approval configuration interface, the business approval form is used to select the associated approval fields for the approval nodes of the business approval process; the target business is approved at an approval node based on the approval fields associated with that approval node.

[0008] Based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process, approval configuration data for approving the target business is generated.

[0009] Secondly, embodiments of this application provide a data approval device; the device includes:

[0010] The first generation unit is used to obtain the configuration operation of the approval form of the target business in the approval configuration interface of the target business, and generate the business approval form of the target business; the business approval form contains multiple approval fields configured for the target business;

[0011] The second generation unit is used to obtain the configuration operation of the approval process for the target business in the approval configuration interface, and generate the business approval process for the target business; the business approval process includes multiple approval nodes for the target business;

[0012] The association unit is used in the approval configuration interface to select associated approval fields for the approval nodes of the business approval process based on the business approval form; the target business is approved at an approval node based on the associated approval fields of that approval node;

[0013] The third generation unit is used to generate approval configuration data for approving the target business based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process.

[0014] Thirdly, embodiments of this application provide a computer device including a processor and a memory, wherein the memory is used to store a computer program, the computer program including program instructions, and the processor is configured to invoke the program instructions to execute some or all of the steps in the above method.

[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, are used to perform some or all of the steps in the above-described method.

[0016] Fifthly, embodiments of this application also provide a computer program product or computer program, which includes program instructions that, when executed by a processor, can implement some or all of the steps in the above-described method.

[0017] In this embodiment, configuration operations for the approval form of a target business can be obtained in the approval configuration interface of the target business, generating a business approval form for the target business. This business approval form contains multiple approval fields configured for the target business. Configuration operations for the approval process of the target business can also be obtained in the approval configuration interface, generating a business approval process for the target business. This business approval process contains multiple approval nodes for the target business. In the approval configuration interface, associated approval fields can be selected for the approval nodes of the business approval process based on the business approval form. The target business is approved at an approval node based on the associated approval fields. Furthermore, approval configuration data for approving the target business can be generated based on the business approval process, the business approval form, and the associated approval fields of the approval nodes of the business approval process. By implementing the above method, approval configuration data can be configured through the approval configuration interface, such as configuring form components in the approval form and approval nodes in the approval process online. This allows for online configuration of approval configuration data, enabling the data to be updated and overwritten at any time. This ensures flexibility in adjusting approval configuration data required for various approval business scenarios. In other words, a single system can be used to complete the configuration of various approval configuration data without new development operations, effectively improving development efficiency. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1a This is a schematic diagram of a data sharing system provided in an embodiment of this application;

[0020] Figure 1b This is a schematic diagram of a block composition structure provided in an embodiment of this application;

[0021] Figure 1c This is a flowchart illustrating the generation of a new block according to an embodiment of this application;

[0022] Figure 1d This is a schematic diagram of the architecture of an approval system provided in an embodiment of this application;

[0023] Figure 2 This is a flowchart illustrating a data approval method provided in an embodiment of this application;

[0024] Figure 3a This is a schematic diagram of an approval configuration interface provided in an embodiment of this application;

[0025] Figure 3b This is a schematic diagram of another approval configuration interface provided in an embodiment of this application;

[0026] Figure 3c This is a flowchart illustrating the combination of a business approval form and a business approval process, as provided in an embodiment of this application.

[0027] Figure 3d This is a flowchart illustrating an adjustment of a business approval form provided in an embodiment of this application;

[0028] Figure 3e This is a flowchart illustrating an adjustment to the business approval process provided in an embodiment of this application;

[0029] Figure 3f This is a schematic diagram of an approval process using approval configuration data, provided in an embodiment of this application.

[0030] Figure 4 This is a flowchart illustrating another data approval method provided in an embodiment of this application;

[0031] Figure 5a This is a schematic diagram of an approval contract management process provided in an embodiment of this application;

[0032] Figure 5b This is a schematic diagram of a process for configuring an approval contract for a conditional gateway node, provided in an embodiment of this application.

[0033] Figure 5c This is a schematic diagram of an approval process using an approval contract, provided in an embodiment of this application.

[0034] Figure 5d This is a flowchart illustrating another data approval method provided in the embodiments of this application;

[0035] Figure 6 This is a schematic diagram of the structure of a data approval device provided in an embodiment of this application;

[0036] Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0037] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0038] To better understand the solutions of the embodiments of this application, the relevant terms and concepts that may be involved in the embodiments of this application will be introduced below.

[0039] This application relates to blockchain networks. The following is a brief introduction to the relevant terms and concepts of blockchain networks:

[0040] Blockchain network 10 refers to a network used for data sharing between nodes. The blockchain network may include multiple nodes 101, among which consensus nodes may be included. Each node 101, in its normal operation, can receive input information and maintain the shared data (i.e., the blockchain) within the blockchain network based on the received input information.

[0041] In a blockchain network, different nodes can store the same blockchain, which consists of a series of blocks sequentially ordered by their creation time. A node here can refer to a node that maintains the complete blockchain within the network, such as a full node or consensus node mentioned above. Figure 1a The blocks shown are Block 1, Block M-1, etc., where M is a positive integer greater than 1. Once a new block is added to the blockchain, it will not be removed. A block records the data submitted by nodes in the blockchain network. To ensure information exchange within the blockchain network, each node can have a connection with another node, enabling peer-to-peer communication between any two nodes. This can be achieved through wired or wireless communication links. For example, when any node in the blockchain network receives input information, other nodes retrieve this input information according to the consensus algorithm and store it as part of the shared data, ensuring consistency of data stored on all nodes in the blockchain network.

[0042] Client 102 can access the blockchain network and communicate with nodes in the blockchain network. Specifically, the terminal where client 102 is located can be a smartphone, tablet, laptop, desktop computer, in-vehicle smart terminal, etc., and this embodiment of the application does not limit the scope.

[0043] It should be noted that, Figure 1a The number of nodes shown is merely illustrative. Any number of nodes can be deployed as needed. A node can refer to any form of computing device connected to the network, such as a server or terminal, which can all be added as a node.

[0044] Each node in the blockchain network has a corresponding node identifier, and each node can also store the node identifiers of other nodes in the blockchain network. This allows for the subsequent broadcasting of generated blocks to other nodes in the blockchain network based on their node identifiers. Each node can maintain a node identifier list as shown in the table below, storing the node name and node identifier in this list. The node identifier can be an Internet Protocol (IP) address or any other information that can be used to identify the node; the table only uses IP addresses as an example.

[0045] Table 1

[0046] Node Name Node identifier Node 1 117.114.151.174 Node 2 117.116.189.145 … … Node N 119.123.789.258

[0047] In this blockchain network, each node stores an identical copy of the blockchain. A blockchain consists of multiple blocks; see [link to blockchain documentation]. Figure 1b A blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores input information feature values, version number, timestamp, and difficulty value, while the block body stores the input information. The next block after the genesis block takes the genesis block as its parent block. The next block also includes a block header and a block body. The block header stores the input information feature values ​​of the current block (also known as the Merkle root hash), the block header feature values ​​of the parent block (also known as the prev_hash), version number, timestamp, and difficulty value), and so on. This ensures that the block data stored in each block is related to the block data stored in the parent block, guaranteeing the security of the input information in the blocks.

[0048] When generating the various blocks in the blockchain, see [link / reference]. Figure 1c When a node in the blockchain receives input information, it verifies the input information. After verification, it stores the input information in a memory pool and updates its hash tree used to record the input information. Then, it updates the timestamp to the time the input information was received and tries different random numbers multiple times to calculate the feature value, ensuring that the calculated feature value satisfies the following formula:

[0049] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x)) <TARGET

[0050] Wherein, SHA256 is the feature value algorithm used to calculate the feature value; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header feature value of the parent block of the current block; merkle_root is the feature value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value for a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the feature value threshold, which can be determined based on nbits.

[0051] Thus, when a random number satisfying the above formula is calculated, the information can be stored accordingly, generating a block header and a block body to obtain the current block. Subsequently, the node containing the blockchain sends the newly generated block to other nodes in its blockchain network based on the node identifiers of other nodes in the blockchain network. The other nodes verify the newly generated block and, after verification, add the newly generated block to their stored blockchain.

[0052] In this context, smart contracts can run on nodes of the blockchain network. A smart contract is an immutable, automatically executed computer program that runs on the blockchain. A smart contract is a code implementation that is executed when certain conditions are met. Developers can define contract logic using programming languages ​​and publish it on the blockchain (smart contract registration). According to the logic of the contract terms, execution is triggered by calling keys or other events to complete the contract logic. The blockchain also provides functions for upgrading and canceling smart contracts.

[0053] In one embodiment, the smart contract involved in this application embodiment may include a multi-signature contract. A multi-signature contract is a smart contract that requires multiple users to jointly sign in order to execute an operation. In general, a multi-signature contract is a type of contract that requires a specific number of parties to agree before a transaction can be executed. A common setting in multi-signature contracts is the m / n signature mode, meaning that m out of n signers must agree to complete a transaction. For example, the 2 / 3 multi-signature mode requires two out of three signers to agree before a transaction can be executed. Multi-signature contracts can effectively reduce the risk of asset theft because they require a certain number of signers to reach a consensus before funds can be used. Multi-signature contracts are suitable for scenarios where multiple people need to jointly manage funds, such as company vaults, partnership joint accounts, or any financial operations requiring collective decision-making. Compared to single-signature wallets, multi-signature contracts offer higher security because they require multiple private keys to complete a transaction, so even if one private key is leaked, funds will not be lost. In summary, multi-signature contracts are a blockchain tool that enhances security and trust by requiring the joint signatures of multiple participants to control funds and execute transactions, making them suitable for situations requiring joint management and decision-making by multiple parties.

[0054] Based on the above introduction to blockchain networks, this application proposes a data approval scheme and a corresponding approval system. Please refer to... Figure 1d This is a schematic diagram of the architecture of an approval system provided in an embodiment of this application. The approval system includes a backend management system and a rendering engine. The approval system can be built using the BPMN (Business Process Model and Notation) protocol. BPMN is a graphical representation method that can be used to model business processes and is suitable for automated approval processes. The backend management system may include a form design module for business approval forms, an approval process design module for business approval processes, a smart contract management module, and an object (user) management module. The rendering engine may include a form rendering engine for rendering business approval forms, an approval process rendering engine for rendering business approval processes, and access templates that can be connected to the rendering engine; for example, the rendering engine here can render the approval configuration interface, the form rendering engine can render the form interface used for configuring approval forms in the approval configuration interface, and the approval process rendering engine can render the process interface used for configuring approval processes in the approval configuration interface.

[0055] The object management module manages information about objects that can use the approval system, granting users access to the system. This object information may include the object's name, object ID, and Extra information. When an object needs to use the approval system to generate approval configuration data for processing, it can log in and perform relevant operations to generate the corresponding configuration data. The approval system supports entering object information to grant that object access. In one embodiment, the system supports multiple objects; therefore, user management can also import multiple available objects from the approval system using an Excel spreadsheet.

[0056] The form design module can manage the form component list, component editing panel, and form attribute panel. Objects can select form components from the form component list and configure them in the form editing panel and form attribute panel to generate the corresponding business approval form.

[0057] The approval process design module can manage the approval node list, process editing panel, and node attribute panel. Users can select approval nodes from the list and configure them in the process editing panel and node attribute panel to generate the corresponding business approval process. The approval nodes involved here can be nodes on the blockchain.

[0058] In the smart contract management module, objects can configure corresponding smart contracts for approval nodes in the business approval process, so that the approval process at that node can be implemented by calling the smart contract. Implementing approval processing through smart contracts effectively ensures the intelligence and efficiency of the approval process.

[0059] The aforementioned approval system provides an approval configuration interface, allowing users to configure approval forms, approval processes, and smart contracts. As mentioned earlier, the form component list, component editing panel, and form attribute panel involved in the form design module can be displayed on the approval configuration interface, enabling users to perform relevant operations on these elements to generate approval forms. Similarly, the approval node list, process editing panel, and node attribute panel involved in the approval process design module can also be displayed on the approval configuration interface, allowing users to perform relevant operations on these elements to generate approval processes.

[0060] In this embodiment of the application, the embodiment of the application is based on Figure 1d The approval system shown provides a data approval scheme. In its implementation, the scheme works as follows: It can acquire configuration operations for the approval form of the target business within the approval configuration interface to generate a business approval form for the target business. This business approval form can contain multiple approval fields configured for the target business. It can also acquire configuration operations for the approval process of the target business within the approval configuration interface to generate a business approval process for the target business. This business approval process can contain multiple approval nodes for the target business. Within the approval configuration interface, it can also select associated approval fields for the approval nodes of the business approval process based on the business approval form. The target business is approved at an approval node based on the associated approval fields of that node. Furthermore, based on the business approval process, the business approval form, and the associated approval fields of the approval nodes in the business approval process, approval configuration data for approving the target business can be generated.

[0061] Based on the above description of the data approval scheme, this application embodiment allows for the configuration of approval configuration data through the approval configuration interface. This includes online configuration of form components in the approval form and approval nodes in the approval process. This enables online configuration of approval configuration data, allowing for timely updates and overwriting of the data. This ensures flexibility in adjusting approval configuration data across various approval business scenarios, allowing for the configuration of various approval configuration data without requiring new development operations, effectively improving development efficiency. Furthermore, when adjusting relevant form information or approval processes in the approval configuration data, adjustments can be made directly online through the approval configuration interface and saved without overwriting existing approval configuration data. This ensures that adjustments to the process do not require compatibility with redundant business code and supports different versions of approval process data, thus enabling support for new versions of approval configuration data while maintaining the operation of older versions.

[0062] It should be noted that the executing entity of the aforementioned data approval scheme can be a computer device, which can be a terminal or a server. The terminal can display the approval configuration interface provided by the aforementioned approval system, and the server can refer to the backend service of the approval system. The terminal can be a smartphone, tablet, smart wearable device, smart voice interaction device, smart home appliance, laptop, vehicle terminal, etc., and this application does not impose any restrictions on this. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and intelligent platforms, but is not limited to these.

[0063] Based on the data approval scheme provided above, this application embodiment provides a data approval method that can be executed by a computer device. Please refer to... Figure 2 The data approval method includes, but is not limited to, the following steps:

[0064] S201, retrieve the configuration operation of the approval form for the target business in the approval configuration interface of the target business, and generate the business approval form for the target business; the business approval form contains multiple approval fields configured for the target business.

[0065] The target business can refer to the business that requires approval, such as a money transfer business, an NFT (Non-Fungible Token) exchange business, etc., without specific limitations.

[0066] In one implementation, this application embodiment can provide an approval system (or configuration system, approval platform, etc.), on which a target object can log in to configure approval configuration data. The target object can refer to the designer of the approval configuration data; the approval system can provide a relevant interface (such as an approval configuration interface) so that the target object can perform relevant operations on the interface, thereby generating approval configuration data for approving the target business.

[0067] In one embodiment, the approval configuration interface may include a form interface for configuring approval forms and a process interface for configuring approval processes. That is, configuring approval forms and approval processes are performed on different interfaces. When configuration of an approval form or approval process is required, the target object can switch between them to display the corresponding approval configuration interface on the approval system. Alternatively, the approval configuration interface may include a form area for configuring approval forms and a process area for configuring approval processes. That is, configuring approval forms and approval processes are performed on different areas of the same interface. Alternatively, the interface for configuring approval forms and approval processes may be displayed in other forms. This application embodiment uses different interfaces (i.e., the approval configuration interface includes a form interface and a process interface) as examples for related explanation.

[0068] The approval configuration interface (or form interface) may contain a list of form components, which may include multiple form components. For example, the form components in the form component list may include: input box components, personnel components, attachment components, etc., which will not be listed one by one.

[0069] In one implementation, the target object can select a form component from a list of form components, and the computer device can receive this selection and display the selected form component's editing panel in the approval configuration interface. This selection operation can be a move operation to the component editing panel or a click operation on the form component. Furthermore, the target object can perform related operations on the component editing panel to configure at least one field sub-component for the selected form component. Each field sub-component has a corresponding approval field, and each field sub-component is used to enter the field value associated with the approval field. After configuring these field sub-components, a business approval form can be generated based on at least one configured field sub-component. In summary, the configuration operations for the target business approval form can include: selecting a form component from a list of form components, and configuring field sub-components in the component editing panel.

[0070] In one embodiment, the configuration operation for the field sub-component mentioned above may refer to the configuration operation of the field attribute information of the field sub-component. Based on this, the specific implementation of configuring at least one field sub-component for the selected form component on the component editing panel can be as follows: obtain the selection operation for the field sub-component in the form component, display the form attribute panel of the selected field sub-component in the approval configuration interface, and configure the corresponding field attribute information for the selected field sub-component in the form attribute panel. This field attribute information can be used as prompt text provided to users when filling out approval forms in actual approval business scenarios, so that users can fill in relevant information based on the prompt text when filling out approval forms.

[0071] In one embodiment, as described above, the approval configuration interface may include a component list area displaying a list of form components, a component editing panel, and a form attribute panel. The target object can perform relevant operations on this approval configuration interface to generate the business approval form.

[0072] Specifically, the target object can select a form component from the list of form components displayed in the component list area. In response, the computer device can display the field sub-component of the selected form component on the component editing panel. This displayed field sub-component is associated with a corresponding approval field. The approval field associated with this field sub-component is a unique ID (identifier) ​​generated after the form component is displayed in the component editing area; this ID is a unique identifier bound to the approval process. Furthermore, the target object can configure field attribute information for each field sub-component. For example, the target object can select a field sub-component displayed in the component editing panel. In response, the computer device can display a configuration area on the node attribute panel for configuring the field attribute information of that field sub-component. The target object can input the field attribute information of the field sub-component in this configuration area; for example, the field attribute information could be: "Please enter the amount." The computer device can then respond to the input operation on the node attribute panel and obtain the information corresponding to the input operation, using this information as the field attribute information of the field sub-component.

[0073] In one embodiment, the form interface for the approval configuration interface can be found here. Figure 3a As shown, the component list area of ​​the form component list can be as follows: Figure 3aAs shown in the area marked 301, the component editing panel can be shown as shown in the area marked 302, and the node attribute panel can be shown as shown in the area marked 303. When the target object performs a move operation to move a form component in the component list area 301 to the component editing panel 302, or performs a click operation on a form component in the click area 301, the computer device can determine that a selection operation has been obtained on the form component in the form component list, and can display the field sub-components of the selected form component in the component editing panel 302. Each field sub-component is associated with and displayed with a corresponding approval field. For example, the box marked 304 in the component list area 301 represents a form component (i.e., an input box component). When the target object needs to include this form component in the business approval form, the target object can perform a selection operation on the input box component 304 to display the field sub-components of the input box component 304 in the component editing panel 302. For example, the area marked 305 displays a field sub-component, and the text marked 306 is the approval field associated with this field sub-component.

[0074] Furthermore, the target object can configure corresponding field attribute information for each field sub-component of the input box component 304. For example, the target object can click on a field sub-component in the component editing panel 302 to display the area for configuring the attributes of the field sub-component on the node attribute panel 303. For instance, when the target object selects field sub-component 305, the area for configuring the attributes of the field sub-component can be displayed on the node attribute panel 303, as shown by the box marked 307. Then, the target object can enter information (such as "Please enter the amount") in box 307, and the entered information is the field attribute information of the field sub-component.

[0075] S202, retrieve the configuration operation for the approval process of the target business in the approval configuration interface, and generate the business approval process of the target business; the business approval process includes multiple approval nodes for the target business.

[0076] The approval configuration interface (or process interface) can contain a list of approval nodes for configuring the approval process. The list of approval nodes contains multiple approval nodes. For example, the list of approval nodes includes approval object nodes and condition gateway nodes. The approval object node is configured with the approval object that will be approved for the target business. The condition gateway node is configured with node judgment conditions. These node judgment conditions can be used to determine the next approval node of the condition gateway node. In other words, the node judgment conditions can affect the direction of the approval process.

[0077] In one implementation, the target object can perform a selection operation on approval nodes in the approval node list, and the computer device can obtain the selection operation to obtain multiple selected approval nodes. These selected approval nodes are the nodes involved in constructing the approval process. Furthermore, the target object can perform a connection operation on the selected approval nodes, and the computer device can respond to this connection operation to construct the approval dependencies between the selected approval nodes. Finally, the computer device can generate a business approval process based on the selected approval nodes and the approval dependencies between them.

[0078] The business approval process can include a first approval node and a second approval node with an approval dependency relationship. The first approval node is the approval node that is depended upon, and the second approval node is the approval node that is dependent on it. The target business can only be approved at the second approval node after it has been approved at the first approval node that is depended upon.

[0079] In one embodiment, the approval configuration interface may include a node list area displaying a list of approval nodes, a process editing panel, and a node attribute panel. The target object can perform relevant operations on this approval configuration interface to generate a business approval process. The process editing panel can be used to display the approval nodes selected from the node list area, and the node attribute panel can be used to configure corresponding node attribute information for the approval nodes displayed on the process editing panel. As mentioned earlier, approval nodes may include approval object nodes and condition gateway nodes. The configured attribute information may differ for different types of nodes, thus allowing for the configuration of corresponding attribute information for different types of approval nodes. The attribute information for approval object nodes may include: object information of the approval object, which can be used to indicate the approval object, such as object name, object identifier, etc. The attribute information for corresponding condition gateway nodes may include: approval fields associated with the condition gateway node, node judgment conditions, etc.

[0080] Specifically, the target object can perform a selection operation on the approval nodes in the node list area, and the computer device can acquire the selection operation on the approval node list and display the process editing panel of the selected approval node in the approval configuration interface. The target object can perform a connection operation on each approval node displayed on the process editing panel, and the computer device can respond to the connection operation to build the approval dependencies between the various approval nodes. After completing these configurations, the corresponding business approval process can be generated. In one embodiment, the target object can also perform a selection operation on each approval node on the process editing panel, and the computer device can respond to the selection operation on the approval node to display an attribute configuration area on the node attribute panel for configuring attribute information for the approval node, so that the target object can configure the node attribute information in the attribute configuration area.

[0081] In one embodiment, the workflow interface for the approval configuration screen can be found here. Figure 3b As shown, the list of approval nodes can be as follows: Figure 3b As shown in the node list area marked 308, the process editing panel can be shown as the area marked 309, and the node attribute panel can be shown as the area marked 310. For example, the approval nodes displayed in the node list area 308 include the approval object node 311 and the condition gateway node 312. When the target object performs a move operation to move an approval node in the node list area 308 to the process editing panel 309, or performs a click operation to click an approval node in the node list area 308, the computer device can determine that a selection operation has been obtained for the approval node in the approval node list, and can display the selected approval node in the process editing panel 309. Then, the target object can perform a connection operation on the approval nodes displayed on the process editing panel 309 to build approval dependencies between the various approval nodes.

[0082] Furthermore, the target object can configure corresponding node attribute information for the approval node. For example, the target object can select the approval node in the process editing panel 309, and the computer device can respond to this selection operation by displaying the attribute configuration area for configuring the approval node's attributes on the node attribute panel 310. For instance, the area marked 313 is the attribute configuration area for configuring the attribute information of the approval node, and the target object can input the attribute information of the approval node in the attribute configuration area 313.

[0083] S203, In the approval configuration interface, select the associated approval fields for the approval nodes of the business approval process based on the business approval form.

[0084] In this process, the target business is approved at an approval node based on the approval fields associated with that node. It's understandable that in the business approval process, the approval node needs to know the data to be processed; therefore, here we can also select the associated approval fields for the approval node of the business approval process based on the business approval form.

[0085] In one implementation, as described above, the approval configuration interface may include a node attribute panel for the approval nodes on the workflow interface. This node attribute panel can be used to configure the node attribute information of the approval nodes. This node attribute information may include the approval fields that the approval node needs to be associated with; that is, the target object can select the associated approval fields for the approval node on this node attribute panel.

[0086] For example, in a resource quantity approval scenario, the approval node can include an approval object node and a condition gateway node. The approval task in this scenario might be: approving the transfer of a first resource quantity (e.g., 50,000 yuan) from company A to company B; where the node's judgment condition is that if the transferred resource quantity exceeds a second resource quantity (e.g., 30,000 yuan), it needs to be submitted to the manager for approval. In this case, the approval field associated with the approval object node can be the field related to the transferred resource quantity, indicating that the approval object corresponding to this node needs to approve the transferred resource quantity (e.g., 50,000 yuan). The approval field associated with the condition gateway node can be the field related to the resource quantity involved in the node's judgment condition (e.g., 30,000 yuan).

[0087] In one implementation, when the approval node is a condition gateway node, in addition to configuring the approval fields associated with that condition gateway node, the node judgment condition corresponding to that condition gateway node can also be configured. This node judgment condition can be used to determine the next approval node after the condition gateway node for the target business, thus determining the direction of the approval process. For example, in a resource quantity approval scenario, the node judgment condition could be: transferring resources greater than the target resource quantity requires CEO approval; transferring resources less than the target resource quantity only requires department manager approval. That is, if it is determined that the transferred resource quantity is greater than the target resource quantity, the next approval node of the condition gateway node is the approval node for the CEO; and if it is determined that the transferred resource quantity is less than the target resource quantity, the next approval node of the condition gateway node is the approval node for the department manager.

[0088] In one implementation, the decision condition type for a node can be determined based on the field type of the approval field. The field type can be numeric or boolean (indicating "yes" or "no"). The decision condition type can include types for comparison relationships (such as greater than, equal to, less than), and types for true / false relationships. When the field type is numeric, the decision condition type is for comparison relationships; when the field type is boolean, the decision condition type is for true / false relationships.

[0089] As mentioned above, the embodiments of this application can combine approval forms with approval processes. For example, in business scenarios, the approval process can often use the data in the approval form as a condition to influence the direction of the approval process. As described above, if the amount of resources transferred in the approval form is greater than the target amount of resources, the process needs to proceed with the approval by the president. If the amount of resources transferred in the approval form is less than the target amount of resources, the process needs to proceed with the approval by the department manager.

[0090] For example, a detailed implementation of combining approval forms with approval processes can be found in [reference needed]. Figure 3c As shown, this mainly involves combining the two using a conditional gateway node. It's important to note that the business approval form generated on the approval configuration interface has a corresponding JSON file. This JSON file can refer to the file containing the source code of the business approval form. In the specific implementation, the computer device can parse the JSON file corresponding to the business approval form to obtain the corresponding approval fields. The target object can configure the associated approval fields and node judgment conditions for the conditional gateway node on the approval configuration interface. After the computer device obtains these configurations, it can modify the JSON file corresponding to the business approval form to associate the approval fields with the corresponding conditional gateway node, and update the node identifier of the conditional gateway node in the reference array of the form component corresponding to the approval field.

[0091] Computer devices can also determine the type of judgment condition for a node based on the field type of the approval field. For example, when the field type is numeric, the judgment condition type is for comparison relationships, and when the field type is boolean, the judgment condition type is for true / false relationships.

[0092] After completing these configurations, the XML file corresponding to the approval configuration data can be further modified based on these configurations. Corresponding condition tags can be added to the condition gateway nodes in this XML file. These condition tags indicate the existence of corresponding node judgment conditions in the condition gateway node, thereby influencing the direction of the approval process. It should be noted that the approval configuration interface in this embodiment can be built using the BPMN protocol, and the BPMN protocol uses XML files for data storage. Therefore, the file containing the approval source code corresponding to the approval configuration data can be an XML file.

[0093] In summary, the embodiments of this application can configure form components in the approval form and approval nodes in the approval process online, thereby achieving online configuration of approval configuration data.

[0094] It should be noted that when a deletion operation is detected on a form component within a business approval form, a target prompt message can be output. This prompt message can be used to indicate the approval node associated with that form component. As mentioned earlier, the approval field of a sub-component within a form component can be associated with an approval field. When the form component is deleted, the associated approval field is also deleted. Furthermore, the computer device can delete the approval node associated with the approval field based on this prompt message, thereby severing the association between the approval node and the approval field. After completing the above operations, the XML file can be updated, meaning the information about the corresponding approval node in the XML file can be deleted.

[0095] S204 generates approval configuration data for approving the target business based on the business approval process, business approval form, and the approval fields associated with the approval nodes of the business approval process.

[0096] The approval configuration data can be the approval source code used to process the target business. The approval source code is used to run on the approval device to perform the approval process for the target business.

[0097] In one implementation, in the approval configuration interface, the target object can perform adjustment operations on the business approval process or business approval form for the target business. The computer device can respond to the adjustment operation and obtain the adjustment operation on the business approval process or business approval form for the target business. After obtaining the adjustment operation, the computer device can adjust the content of the business approval process or business approval form based on the adjustment operation to synchronously update the approval configuration data and generate updated configuration data for the approval configuration data.

[0098] In one embodiment, regarding adjustments to business approval forms, see [link to relevant documentation]. Figure 3dAs shown, the target object can perform a move operation on the form components in the form component list on the approval configuration interface to move the selected form component to the component editing panel. When the computer device detects the existence of a form component on the component editing panel, it can generate a data instance for that form component. This data instance contains the metadata of the form component, which can refer to data used to represent the attributes of the form component. As mentioned earlier, the business approval form of the target business is generated based on the form components on the component editing panel, and the various field sub-components of the form components can be configured on the form property panel. That is, the data instance of the form component is generated based on the target object's operations on the form property panel.

[0099] When a business approval form needs adjustment, the target object can perform relevant operations on the form properties panel to modify the information contained in the data instance of the form component. After the computer device detects the modification operation on the data instance in the form properties panel, the root container corresponding to the component's editing panel can monitor the changes in the information within the data instance. If a change is detected, it can notify the child containers corresponding to the field child components to update. The child containers can compare their existing information with the information passed from the root container to determine if the information has changed. If it has, it can be updated; otherwise, it will not be updated.

[0100] In one embodiment, regarding adjustments to the business approval process, see [link to relevant documentation]. Figure 3e As shown, this section primarily describes the adjustment of approval nodes in the approval process. Specifically, the approval configuration interface can monitor the selection of approval nodes in the approval node list in real time, and the node attribute panel can also monitor the selection of approval nodes on the process editing panel in real time, so as to adjust the approval nodes based on the monitoring. The implementation process may include the following steps:

[0101] S11, the approval configuration interface monitors the selection event of approval nodes in the approval node list in real time.

[0102] S12, the approval configuration interface detects the selection of an approval node in the approval node list.

[0103] Once the approval configuration interface detects the selection of an approval node in the approval node list, the selected approval node can be displayed on the process editing panel.

[0104] S13, the node attribute panel monitors the selection of approval nodes on the process editing panel in real time.

[0105] S14. When the node attribute panel detects the selection operation of the approval node on the process editing panel, the node attribute panel for configuring the approval node is expanded on the approval configuration interface, and the area of ​​configurable node attribute information is expanded according to the node type of the approval node.

[0106] It's important to understand that the node attribute panel on the approval configuration interface can initially be hidden. This means that before any node attribute information for the approval node is configured, the node attribute panel may not be displayed on the approval configuration interface. However, once the node attribute panel detects a selection of the approval node on the workflow editing panel, and node attribute information needs to be configured, the node attribute panel can be expanded on the approval configuration interface, or its hidden state can be changed to a visible state.

[0107] As mentioned earlier, considering that the configured node attribute information may differ for different approval nodes (such as approval object nodes and condition gateway nodes), the configurable node attribute information area can be expanded in the node attribute panel based on different node types, and the corresponding approval node configuration information can be configured in that area.

[0108] S15, After the node attribute information is configured, the node attribute panel will send the configured node attribute information to the JSON file.

[0109] S16, Modify the node attribute information of the corresponding approval node in the JSON file.

[0110] After configuration, the computer device can modify the node attribute information of the corresponding approval node in the JSON file corresponding to the approval configuration data based on the node attribute information configured in the node attribute panel, so as to obtain the updated JSON file.

[0111] S17, the approval configuration interface re-renders the approval node based on the node attribute information in the adjusted JSON file.

[0112] S18, the target object triggers a save operation on the JSON file to save the adjusted JSON file.

[0113] S19 converts the JSON file to an XML file.

[0114] Since the BPMN protocol uses XML files for data storage, computer devices can also convert JSON files into XML files and store the XML files.

[0115] In summary, the embodiments of this application enable online configuration of approval configuration data on the approval configuration interface, and allow online modification of approval forms or approval processes. This achieves the effect of updating and overwriting approval configuration data at any time, ensuring flexibility in adjusting approval configuration data required for various approval business scenarios. It guarantees that a single system can be used to configure various approval configuration data without new development operations, effectively improving development efficiency. Furthermore, the generated approval configuration data can be considered a version for approval processing. When an upgrade version needs to be generated, the data can be directly updated on the approval configuration interface to obtain the new version of approval configuration data. In the case of version updates, only the relevant information needs to be adjusted on the approval configuration interface; no new code needs to be rewritten, effectively reducing development difficulty and improving development efficiency. Additionally, when generating a new version using the approval configuration interface, the old version can also be run.

[0116] In one implementation, the approval configuration data obtained above can be approval source code used to process the target business. This approval source code can be run on the approval device to execute the approval process for the target business. That is, in actual approval business scenarios, business personnel with approval needs can utilize the approval source code running on the approval device to implement the approval process.

[0117] For example, the implementation process can be as follows: Figure 3f As shown, business personnel can log in to the approval device and select the corresponding approval configuration data. After selecting the corresponding approval configuration data, the approval device can also display the required approval form corresponding to the approval configuration data. Business personnel can fill in the corresponding form information on the approval form. After completing the filling operation, they can trigger the submission operation, and the computer device can respond to the submission operation to process the approval according to the approval process in the approval configuration data.

[0118] In this embodiment, approval configuration data can be configured through the approval configuration interface. This includes configuring form components in the approval form and approval nodes in the approval process online. This allows for online configuration of approval configuration data, enabling timely updates and overwriting of the data. This ensures flexibility in adjusting approval configuration data across various approval business scenarios, allowing a single system to handle all configurations without requiring new development, thus significantly improving development efficiency. Furthermore, when adjusting related form information or approval processes within the approval configuration data, adjustments can be made directly online through the approval configuration interface. This data can be saved without overwriting existing approval configuration data, ensuring that adjustments do not require redundant business code and supporting different versions of approval process data. This allows for support for new versions of approval configuration data while maintaining the operation of older versions.

[0119] Based on the above embodiments, this application provides another data approval method. This data approval method can be executed by a computer device. Please refer to [link to relevant documentation]. Figure 4 The data approval method includes, but is not limited to, the following steps:

[0120] S401, retrieve the configuration operation of the approval form for the target business in the approval configuration interface of the target business, and generate the business approval form for the target business; the business approval form contains multiple approval fields configured for the target business.

[0121] S402, retrieve the configuration operation for the approval process of the target business in the approval configuration interface, and generate the business approval process of the target business; the business approval process includes multiple approval nodes for the target business.

[0122] S403, in the approval configuration interface, select the associated approval fields for the approval nodes of the business approval process based on the business approval form.

[0123] The specific implementation methods of steps S401-S403 can be found in the specific implementation methods of steps S201-S203 above, and will not be repeated here.

[0124] S404, in the approval configuration interface, configure the corresponding approval contract for the approval node of the business approval process; the target business is approved at an approval node based on the approval contract configured for that approval node.

[0125] In one implementation, this application embodiment can also incorporate smart contracts to implement the approval process, thereby improving the reliability and security of the approval process. The smart contract described here can be referred to as an approval contract.

[0126] In one implementation, the target object can configure the corresponding approval contract for the approval node of the business approval process in the approval configuration interface; and the computer device can respond to the corresponding configuration operation to associate the approval node with the corresponding approval contract.

[0127] As mentioned above, the approval node may include the approval object node and the condition gateway node. In this embodiment, a corresponding approval contract can be configured for the condition gateway node, that is, the approval contract can be associated in the condition gateway node so that the approval contract can realize business scenarios that do not require approval (such as transfer, exchange of NFT, etc.).

[0128] In one embodiment, as described above, the node attribute information of the condition gateway node can be configured on the node attribute panel of the approval configuration interface, and the node attribute information may include the approval fields associated with the condition gateway node and the node judgment conditions; in addition, for the condition gateway node, its corresponding node attribute information may also include relevant information of the approval contract, that is, the target object can configure the approval contract for the condition gateway node on the node attribute panel.

[0129] For example, see Figure 3b As shown, the target object can configure the corresponding approval contract for the condition gateway node in the area marked with 314. In one embodiment, the following is combined with Figure 5a as well as Figure 5b The configuration of approval contracts is described. Target objects can pre-enter approval contracts related to data approval in the approval system, and the number of such contracts can be one or more. When it is necessary to configure approval contracts for approval nodes later, they can be selected from the pre-set approval contracts. That is, the approval system manages approval contracts.

[0130] See Figure 5a As shown, the approval contract management process can be as follows: the target object can enter the contract address of the approval contract in the approval system, and the computer device can obtain the contract address and verify its legality. When the legality verification is successful, the target object can configure the attribute information of the approval contract. When the computer device detects the configuration operation, it can respond to the configuration operation and associate the configured attribute information with the approval contract. After the configuration is completed, the computer device can save and publish the approval contract.

[0131] See Figure 5b The diagram illustrates the process of configuring an approval contract for a conditional gateway node, which may include the following steps:

[0132] S21, The computer device detects the selection operation of the conditional gateway node.

[0133] When the target object needs to configure the corresponding approval contract for the condition gateway node, the target object can select the condition gateway node displayed on the process editing panel so that the computer device can respond to the selection operation and proceed with the subsequent process.

[0134] S22 displays the contract options for approving contracts on the node properties panel.

[0135] After the computer device responds to the above selection operation, the contract options for approving contracts can be displayed on the node properties panel. The contract options here indicate that there are pre-entered approval contracts.

[0136] S23, The computer device detected a selection operation for the approval contract.

[0137] S24, Computer equipment updates the node attribute information of the gateway node.

[0138] The target object can perform a selection operation on the contract options of the approval contract, and the computer device can respond to the selection operation on the approval contract by updating the node attribute information corresponding to the condition gateway node, that is, associating the condition gateway node with its approval contract.

[0139] S25, The computer device detects a configuration operation for the attribute information of the approved contract.

[0140] S26, Update the node attribute information of the gateway node for computer equipment update conditions.

[0141] The target object can configure the attribute information of the selected approval contract on the node attribute panel. The computer device can respond to the configuration operation of the attribute information of the approval contract and update the node attribute information corresponding to the condition gateway node, that is, update the attribute information of the approval contract associated with the condition gateway node.

[0142] For example, if the target object is a multi-signature contract with an approval contract of type n / m configured for the conditional gateway node, there may be numeric input boxes for n and m in the node attribute panel. The target object can then enter the values ​​of n and m in these numeric input boxes. Here, m represents the number of objects in the approval target node, and n represents the number of signatures received by the conditional gateway node for the approved signature data.

[0143] As mentioned earlier, the approval nodes in a business approval process can include condition gateway nodes. Condition gateway nodes can be configured with node judgment conditions and approval contracts. Therefore, the process of approving a target business at a condition gateway node can be described as follows:

[0144] The condition gateway node can obtain the signature dataset generated by the approval nodes preceding it. This signature dataset can contain at least one signature, which is generated by the approval object of an approval node preceding the condition gateway node approving the target business. Specifically, the approval node generates signature data as follows: after approving the target business, the approval node generates a corresponding approval result. Upon obtaining this approval result, the approval node can then sign it using its private key to obtain the corresponding signature data. Specifically, the approval node can perform a hash operation on the approval result to obtain a hash result, which can be referred to as the first hash result. Then, the approval node can use its private key to sign the first hash result to obtain the signature data.

[0145] After obtaining the signature dataset, the condition gateway node can invoke the approval contract to verify the signature data in the dataset. Based on the verification results and node judgment conditions, it determines the next approval node for the target business after the condition gateway node. The verification results can include the validity verification result of each signature in the signature dataset, indicating whether that signature is valid or invalid.

[0146] In one embodiment, the verification process can be implemented as follows: First, the signature data can be designed using the public key corresponding to the private key to obtain a designing result; then, the approval result can be hashed to obtain a second hash result. This second hash result is the result of hashing the approval result, and the hash calculation used here is the same as the hash algorithm used during the signing process. Then, a consistency check can be performed on the designing result and the second hash result to obtain a corresponding valid verification result. If the designing result and the second hash result pass the consistency check, the valid verification result indicates that the signature data is valid; if the designing result and the second hash result fail the consistency check, the valid verification result indicates that the signature data is invalid.

[0147] In one embodiment, the aforementioned approval contract is an n / m multi-signature contract, where m represents the number of approval object nodes approving the target business, and n represents the number of signatures received by the condition gateway node for approved signature data. For example, assuming m = 3 and n = 2, this indicates that the target business needs to be assigned to 3 approval object nodes to process the target business using the approval objects of these nodes, obtaining the corresponding signature data. This signature data needs to be sent to the condition gateway node connected to the approval object node. It is understood that when the target business is assigned to an approval object node for approval processing, the approval object node can also refuse to process the approval, meaning that the approval object node does not send signature data to the condition gateway node, and the number of signature data received by the condition gateway node can be less than or equal to 3.

[0148] Therefore, when the condition gateway node receives at least two signature data, it can be determined that the approval process for the target business is successful, and the next approval node can proceed. When the condition gateway node receives less than two signature data, it can be determined that the approval process for the target business is unsuccessful, and the approval process for the target business ends, indicating that the approval of the target business has failed.

[0149] Based on this, the specific implementation of determining the next approval node for the target business after the condition gateway node, based on the verification process results and node judgment conditions, can be as follows: First, the number of valid signatures in the signature dataset can be counted. If the number of signatures is greater than or equal to a preset threshold, it indicates that the approval process for the target business at the approval object node is successful. Then, based on the node judgment conditions, the next approval node for the target business after the condition gateway node can be determined for further approval processing. If the number of signatures is less than the threshold, the approval process for the target business can be terminated, and the approval of the target business can be determined to have failed.

[0150] In one possible implementation, to ensure timely approval processing and avoid excessive waiting time for the condition gateway node to obtain signature data from the approval target node, a pre-set waiting period for the condition gateway node to receive signature data can be configured. Signature data obtained after this waiting period can be considered invalid. That is, if not enough valid signature data is obtained within this waiting period, the approval of the target business can be deemed a failure. Based on this, the specific implementation of counting the number of valid signatures in the signature dataset can also be combined with the waiting period. Specifically, the number of valid signatures in the signature dataset can be counted within the waiting period.

[0151] For example, see Figure 5c As shown, the process of approval processing using an approval contract is illustrated. Here, the approval contract is a 2 / 3 multi-signature contract. Specifically, the computer device assigns the target task to approval object node 1, approval object node 2, and approval object node 3. The approval objects of these three approval object nodes approve the target business respectively. After obtaining the corresponding approval result, each approval object node can use its private key to sign the approval result to obtain the corresponding signature data.

[0152] After each approval object node receives its signature data, it can send it to the condition gateway node. The condition gateway node can then invoke the approval contract to verify the signature data in the signature dataset. Based on the verification result and node judgment conditions, it determines the next approval node for the target business after the condition gateway node. Specifically, the condition gateway node can count the number of signatures received. If the number of signatures is greater than or equal to 2, it indicates that the approval process for the target business at the approval object node was successful, and the next approval node for the target business after the condition gateway node can be determined based on the node judgment conditions. If the number of signatures is less than 2, the approval process for the target business can be terminated, and the approval of the target business can be determined as a failure.

[0153] In one implementation, as mentioned above, when configuring approval configuration data, corresponding approval contracts can be pre-associated with approval nodes in the approval process. To avoid approval execution failure at a certain stage due to unreasonable attribute settings of the approval contract or approval node, a process and execution can be performed before formally submitting the approval configuration data. That is, a pre-execution stage can be set up to allow the designer of the approval configuration data (i.e., the aforementioned target object) to check the approval configuration data, so as to ensure that the approval configuration data can be successfully used to complete the approval process in the actual target business scenario.

[0154] In summary, the embodiments of this application can integrate smart contracts (such as the multi-signature contract mentioned above) into the approval process to serve as conditions for process flow and achieve approval processing. The use of smart contracts can endow traditional approval workflows with Web3 capabilities, making approval processing more transparent and trustworthy. Web3 refers to the next-generation internet built on blockchain technology, aiming to achieve a decentralized, user-controlled data, and enhanced privacy-preserving network environment. Here, the capabilities of Web3 can be reflected in providing users with a freer, fairer, and more secure network environment.

[0155] In summary, the embodiments of this application can combine low-code forms, process design, and the application of the BPMN protocol to build a general approval process. By combining form design, approval process design, and blockchain, a general approval flow solution that is applicable to blockchain, cross-platform, configurable, versioned, and suitable for various business scenarios can be designed.

[0156] S405 generates approval configuration data based on the business approval process, business approval form, approval fields associated with the approval nodes of the business approval process, and approval contracts configured for the approval nodes of the business approval process.

[0157] The specific implementation of this step can be found in the relevant description in step S204 above, and will not be repeated here.

[0158] To better understand the data approval method proposed in this application, the following is combined with Figure 5d The process will be further explained.

[0159] The configuration of approval configuration data mainly involves setting up business approval forms and business approval processes. When a target entity wants to configure approval configuration data, it can log in to the approval system to configure the business approval forms and processes, thereby generating the corresponding approval configuration data. After the approval configuration data is configured, the target entity can publish and enable it so that relevant business personnel can use it to implement actual approval processes.

[0160] The configuration of the business approval form involves a process that includes: the target object selecting a form component on the form interface of the approval configuration screen and dragging the selected form component to the component editing panel. The component editing panel displays one or more field sub-components contained in the form component. The target object can adjust the display position of each field sub-component on the component editing panel, and can also add or delete field sub-components. At this time, the field sub-components displayed on the component editing panel are associated with the corresponding approval fields. Furthermore, the target object can configure the field attribute information of each field sub-component on the form interface. Specifically, the target object can select a field sub-component displayed on the component editing panel to configure the field attribute information of that field sub-component in the node attribute panel of the form interface.

[0161] In configuring the business approval process, the involved processes may include: the target object selecting an approval node (such as an approval object node or a condition gateway node) on the process interface of the approval configuration interface, and performing a move operation on the selected approval node to drag and drop it onto the process editing panel. The selected approval node can be displayed on the process editing panel, where the target object can perform connection operations on different approval nodes to establish approval dependencies between them. The target object can also configure corresponding node attribute information for each approval node. Specifically, the target object can select an approval node displayed on the process editing panel to configure the node attribute information of that approval node on the process attribute panel of the process interface.

[0162] In the management of approval contracts, the target object can enter the contract address of the approval contract in the approval system and configure the attribute information of the approval contract. When the computer device detects the configuration operation, it can save and publish the approval contract.

[0163] In this application embodiment, a corresponding smart contract can be configured for the approval node on the approval configuration interface to combine the approval flow with the smart contract running on the blockchain. This allows the relevant approval process to be completed by calling the smart contract deployed on the approval node, thereby achieving an intelligent approval process and effectively improving the security, authenticity, credibility, and reliability of the approval process.

[0164] The methods of the embodiments of this application have been described in detail above. In order to facilitate better implementation of the above solutions of the embodiments of this application, the apparatus of the embodiments of this application is provided below.

[0165] Figure 6 The illustration shows a schematic diagram of a data approval device provided in an exemplary embodiment of this application; the data approval device can be used as a computer program (including program code) running on the aforementioned computer device, for example, the data approval device can be an application program in the computer device; the data approval device can be used to execute Figure 2 and Figure 4 Some or all of the steps in the method embodiments shown. Please refer to [link / reference]. Figure 6 The data approval device includes the following units:

[0166] The first generation unit 601 is used to obtain the configuration operation of the approval form of the target business in the approval configuration interface of the target business, and generate the business approval form of the target business; the business approval form contains multiple approval fields configured for the target business.

[0167] The second generation unit 602 is used to obtain the configuration operation of the approval process for the target business in the approval configuration interface and generate the business approval process for the target business; the business approval process includes multiple approval nodes for the target business.

[0168] The association unit 603 is used to select associated approval fields for the approval nodes of the business approval process based on the business approval form in the approval configuration interface; the target business is approved at an approval node based on the associated approval fields of that approval node;

[0169] The third generation unit 604 is used to generate approval configuration data for approving the target business based on the business approval process, business approval form and the approval fields associated with the approval nodes of the business approval process.

[0170] In one implementation, the third generating unit 604 is specifically used for:

[0171] In the approval configuration interface, configure the corresponding approval contract for the approval node of the business approval process; the target business is approved at an approval node based on the approval contract configured for that approval node;

[0172] Based on the business approval process, business approval form, approval fields associated with the approval nodes of the business approval process, and approval contracts configured for the approval nodes of the business approval process, approval configuration data is generated.

[0173] In one implementation, the approval configuration interface includes a list of form components, which contains multiple form components; the first generation unit 601 is specifically used for:

[0174] Get the selection operation of form components in the list of form components, and display the component editing panel of the selected form component in the approval configuration interface;

[0175] In the component editing panel, configure at least one field sub-component for the selected form component; each field sub-component has an approval field, and the field value associated with the approval field is entered in any field sub-component;

[0176] Generate a business approval form based on at least one configured field sub-component;

[0177] The configuration operations for the approval form of the target business include the selection of form components in the form component list and the configuration operations of field sub-components in the component editing panel.

[0178] In one implementation, the approval configuration interface includes a list of approval nodes for configuring the approval process, and the list contains multiple approval nodes; the second generation unit 602 is specifically used for:

[0179] Get the selection operation of the approval node in the approval node list, and get the selected multiple approval nodes;

[0180] Establish approval dependencies between multiple selected approval nodes;

[0181] A business approval process is generated based on the selected multiple approval nodes and the approval dependencies between the selected multiple approval nodes.

[0182] In one implementation, the business approval process includes a first approval node and a second approval node with an approval dependency relationship, where the first approval node is the approved node that is depended upon, and the second approval node is the approved node that is dependent upon.

[0183] In this process, the target business can only be approved at the second approval node after it has been approved at the first approval node it is dependent on.

[0184] In one implementation, the approval node of the business approval process includes a condition gateway node, which is configured with node judgment conditions and an approval contract. The process of approving the target business at the condition gateway node includes:

[0185] Retrieve the signature dataset generated in the approval node before the condition gateway node; the signature dataset contains at least one signature, which is generated by the approval object of the approval node before the condition gateway node after the target business is approved;

[0186] The approval contract is invoked to verify the signature data in the signature dataset, and based on the verification results and node judgment conditions, the next approval node after the condition gateway node for the target business is determined.

[0187] In one implementation, the result of the verification process includes the validity verification result of each signature in the signature dataset, whereby the validity verification result of any signature indicates whether that signature is valid or invalid. Based on the result of the verification process and the node judgment conditions, the next approval node after the condition gateway node for the target service is determined, including:

[0188] Count the number of valid signatures in the signature dataset;

[0189] If the number of signatures is greater than or equal to the preset threshold, the next approval node for the target business after the condition gateway node is determined based on the node judgment conditions.

[0190] If the number of signatures is less than the threshold, the approval process for the target business will end, and the approval for the target business will be deemed a failure.

[0191] In one implementation, the approval configuration data is approval source code used to process the target business, and the approval source code is used to run on the approval device to perform the approval processing of the target business; the third generation unit 604 is further used for:

[0192] In the approval configuration interface, you can obtain the adjustment operations for the business approval process or business approval form of the target business;

[0193] Based on the adjustments made to the business approval process or business approval form by the adjustment operation, the approval configuration data is updated synchronously to generate updated configuration data for the approval configuration data.

[0194] It is understood that the division of units in this embodiment is illustrative and merely a logical functional division; in actual implementation, there may be other division methods. The functional units in this embodiment can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units can be implemented in hardware or as software functional units.

[0195] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 7 As shown, the computer device includes at least one processor 701 and a memory 702. Optionally, the computer device may also include a network interface 703. The processor 701, memory 702, and network interface 703 can exchange data. The network interface 703, controlled by the processor 701, is used to send and receive messages. The memory 702 stores a computer program, which includes program instructions. The processor 701 executes the program instructions stored in the memory 702. The processor 701 is configured to invoke the program instructions to execute the aforementioned method.

[0196] The memory 702 may include volatile memory, such as random-access memory (RAM); the memory 702 may also include non-volatile memory, such as flash memory, solid-state drive (SSD); the memory 702 may also include a combination of two or more of the above types of memory.

[0197] The processor 701 may be a central processing unit (CPU). In one embodiment, the processor 701 may also be a graphics processing unit (GPU). The processor 701 may also be a combination of a CPU and a GPU.

[0198] In one possible implementation, memory 702 is used to store program instructions, which processor 701 can invoke to perform the following steps:

[0199] The system retrieves the configuration operations for the approval form of the target business in the approval configuration interface of the target business, and generates the business approval form for the target business; the business approval form contains multiple approval fields configured for the target business.

[0200] The configuration operation for the approval process of the target business is obtained in the approval configuration interface, and the business approval process of the target business is generated; the business approval process includes multiple approval nodes for the target business;

[0201] In the approval configuration interface, the business approval form is used to select the associated approval fields for the approval nodes of the business approval process; the target business is approved at an approval node based on the approval fields associated with that approval node.

[0202] Based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process, approval configuration data for approving the target business is generated.

[0203] In one implementation, processor 701 is specifically used for:

[0204] In the approval configuration interface, configure the corresponding approval contract for the approval node of the business approval process; the target business is approved at an approval node based on the approval contract configured for that approval node;

[0205] Based on the business approval process, business approval form, approval fields associated with the approval nodes of the business approval process, and approval contracts configured for the approval nodes of the business approval process, approval configuration data is generated.

[0206] In one implementation, the approval configuration interface includes a list of form components, which contains multiple form components; processor 701 is specifically used for:

[0207] Get the selection operation of form components in the list of form components, and display the component editing panel of the selected form component in the approval configuration interface;

[0208] In the component editing panel, configure at least one field sub-component for the selected form component; each field sub-component has an approval field, and the field value associated with the approval field is entered in any field sub-component;

[0209] Generate a business approval form based on at least one configured field sub-component;

[0210] The configuration operations for the approval form of the target business include the selection of form components in the form component list and the configuration operations of field sub-components in the component editing panel.

[0211] In one implementation, the approval configuration interface includes a list of approval nodes for configuring the approval process, and the list contains multiple approval nodes; processor 701 is specifically used for:

[0212] Get the selection operation of the approval node in the approval node list, and get the selected multiple approval nodes;

[0213] Establish approval dependencies between multiple selected approval nodes;

[0214] A business approval process is generated based on the selected multiple approval nodes and the approval dependencies between the selected multiple approval nodes.

[0215] In one implementation, the business approval process includes a first approval node and a second approval node with an approval dependency relationship, where the first approval node is the approved node that is depended upon, and the second approval node is the approved node that is dependent upon.

[0216] In this process, the target business can only be approved at the second approval node after it has been approved at the first approval node it is dependent on.

[0217] In one implementation, the approval node of the business approval process includes a condition gateway node, which is configured with node judgment conditions and an approval contract. The process of approving the target business at the condition gateway node includes:

[0218] Retrieve the signature dataset generated in the approval node before the condition gateway node; the signature dataset contains at least one signature, which is generated by the approval object of the approval node before the condition gateway node after the target business is approved;

[0219] The approval contract is invoked to verify the signature data in the signature dataset, and based on the verification results and node judgment conditions, the next approval node after the condition gateway node for the target business is determined.

[0220] In one implementation, the result of the verification process includes the validity verification result of each signature in the signature dataset, whereby the validity verification result of any signature indicates whether that signature is valid or invalid. Based on the result of the verification process and the node judgment conditions, the next approval node after the condition gateway node for the target service is determined, including:

[0221] Count the number of valid signatures in the signature dataset;

[0222] If the number of signatures is greater than or equal to the preset threshold, the next approval node for the target business after the condition gateway node is determined based on the node judgment conditions.

[0223] If the number of signatures is less than the threshold, the approval process for the target business will end, and the approval for the target business will be deemed a failure.

[0224] In one implementation, the approval configuration data is approval source code used to process the target business, and the approval source code is used to run on the approval device to perform the approval processing of the target business; the processor 701 is also used for:

[0225] In the approval configuration interface, you can obtain the adjustment operations for the business approval process or business approval form of the target business;

[0226] Based on the adjustments made to the business approval process or business approval form by the adjustment operation, the approval configuration data is updated synchronously to generate updated configuration data for the approval configuration data.

[0227] In specific implementations, the devices, processors, memory, etc. described above can execute the implementation methods described in the above method embodiments, or they can execute the implementation methods described in the embodiments of this application, which will not be repeated here.

[0228] This application also provides a computer-readable storage medium storing a computer program. The computer program includes program instructions, which, when executed by a processor, enable the processor to perform some or all of the steps described in the above method embodiments. Optionally, the computer storage medium can be volatile or non-volatile. The computer-readable storage medium may primarily include a program storage area and a data storage area. The program storage area may store an operating system, at least one application program required for a given function, etc.; the data storage area may store data created based on the use of blockchain nodes, etc.

[0229] This application also provides a computer program product, which includes program instructions that, when executed by a processor, can implement some or all of the steps in the data approval method described above. Optionally, the program instructions may be stored in a computer-readable storage medium, and a computer device, such as a processor of a computer device, reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the computer device to perform the data approval method provided above.

[0230] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0231] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more program instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The program instructions can be stored in a computer-readable storage medium or transmitted through a computer-readable storage medium.

[0232] Program instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line, DSL) or wireless (e.g., infrared, wireless, microwave, etc.) means. Computer-readable storage media can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives, SSDs), etc.

[0233] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data approval method, characterized in that, The method includes: The system retrieves the configuration operations for the approval form of the target business in the approval configuration interface of the target business, and generates the business approval form for the target business; the business approval form contains multiple approval fields configured for the target business. The configuration operation for the approval process of the target business is obtained in the approval configuration interface, and the business approval process of the target business is generated; the business approval process includes multiple approval nodes for the target business; In the approval configuration interface, the business approval form is used to select the associated approval fields for the approval nodes of the business approval process; the target business is approved at an approval node based on the approval fields associated with that approval node. Based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process, approval configuration data for approving the target business is generated.

2. The method according to claim 1, characterized in that, The approval configuration data for approving the target business is generated based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process, including: In the approval configuration interface, a corresponding approval contract is configured for the approval node of the business approval process; the target business is approved at an approval node based on the approval contract configured for that approval node. The approval configuration data is generated based on the business approval process, the business approval form, the approval fields associated with the approval nodes of the business approval process, and the approval contracts configured for the approval nodes of the business approval process.

3. The method according to claim 1, characterized in that, The approval configuration interface includes a list of form components, which includes multiple form components; the step of obtaining the configuration operation of the approval form for the target business in the approval configuration interface of the target business, and generating the business approval form for the target business, includes: Get the selection operation of the form component in the form component list, and display the component editing panel of the selected form component in the approval configuration interface; Configure at least one field sub-component for the selected form component in the component editing panel; each field sub-component has an approval field, and the field value associated with the approval field is entered in any field sub-component; The business approval form is generated based on the at least one field sub-component configured; The configuration operation for the approval form of the target business includes the selection operation of form components in the form component list, and the configuration operation of field sub-components in the component editing panel.

4. The method according to claim 1, characterized in that, The approval configuration interface includes a list of approval nodes for configuring the approval process, and the list of approval nodes contains multiple approval nodes; the step of obtaining the configuration operation for the approval process of the target business in the approval configuration interface and generating the business approval process of the target business includes: Obtain the selection operation for the approval nodes in the list of approval nodes, and obtain multiple selected approval nodes; Establish the approval dependencies between the selected multiple approval nodes; The business approval process is generated based on the selected multiple approval nodes and the approval dependencies between the selected multiple approval nodes.

5. The method according to claim 4, characterized in that, The business approval process includes a first approval node and a second approval node with an approval dependency relationship. The first approval node is the approval node that is depended upon, and the second approval node is the approval node that depends on it. The target business can only be approved at the second approval node after it has been approved at the first approval node it is dependent on.

6. The method according to claim 1, characterized in that, The approval node of the business approval process includes a condition gateway node, and the condition gateway node is configured with node judgment conditions and approval contract. The process of approving the target service at the condition gateway node includes: Obtain the signature dataset generated in the approval node before the condition gateway node; the signature dataset contains at least one signature data, which is generated by the approval object of the approval node before the condition gateway node after the target business is approved; The approval contract is invoked to verify the signature data in the signature dataset, and based on the verification result and the node judgment conditions, the next approval node for the target business after the condition gateway node is determined.

7. The method according to claim 6, characterized in that, The result of the verification process includes the validity verification result of each signature in the signature dataset, and the validity verification result of any signature is used to indicate whether the signature is valid or invalid. The process of determining the next approval node for the target service after the condition gateway node based on the verification process result and the node judgment conditions includes: Count the number of valid signatures in the signature dataset; If the number of signatures is greater than or equal to a preset threshold, then based on the node judgment condition, the next approval node for the target service after the condition gateway node is determined; If the number of signatures is less than the threshold, the approval process for the target business ends, and the approval of the target business is determined to have failed.

8. The method according to claim 1, characterized in that, The approval configuration data is approval source code used to approve the target business. This approval source code is used to run on the approval device to perform the approval process for the target business. The method further includes: In the approval configuration interface, you can obtain the adjustment operation for the business approval process or the business approval form of the target business; Based on the adjustments made to the business approval process or the business approval form by the adjustment operation, the approval configuration data is synchronously updated to generate updated configuration data for the approval configuration data.

9. A data approval device, characterized in that, The device includes: The first generation unit is used to obtain the configuration operation of the approval form of the target business in the approval configuration interface of the target business, and generate the business approval form of the target business; the business approval form contains multiple approval fields configured for the target business; The second generation unit is used to obtain the configuration operation of the approval process for the target business in the approval configuration interface, and generate the business approval process for the target business; the business approval process includes multiple approval nodes for the target business; The association unit is used in the approval configuration interface to select associated approval fields for the approval nodes of the business approval process based on the business approval form; the target business is approved at an approval node based on the associated approval fields of that approval node; The third generation unit is used to generate approval configuration data for approving the target business based on the business approval process, the business approval form, and the approval fields associated with the approval nodes of the business approval process.

10. A computer device, characterized in that, The system includes a processor and a memory, wherein the memory is used to store a computer program, the computer program including program instructions, and the processor is configured to invoke the program instructions to perform the method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program instructions that, when executed, implement the method as described in any one of claims 1-8.

12. A computer program product or computer program, the computer program product or computer program comprising program instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

Images