Approval data configuration method and approval method and device of transaction information

Abstract

The application provides an approval data configuration method, a transaction information approval method and device, electronic equipment, a storage medium and a program product. It can be applied to the field of big data technology. The method comprises the following steps: obtaining approval data; the approval data comprises at least a plurality of first nodes; the first node represents the processing link information in the approval process; obtaining transaction data; the transaction data comprises a plurality of transaction attributes; creating a process instance based on the approval data and the transaction data; the process instance is configured with an associated node, and the associated node represents the corresponding relationship between the transaction attributes and the corresponding nodes in the approval process; wherein, the process instance is used to respond to an approval request, and based on the transaction information indicated in the approval request, the corresponding associated node is triggered to obtain a target approval process, so as to flow to the target approval process.

Description

Technical Field

[0001] This application relates to the field of big data technology, specifically to approval process configuration technology, and more specifically to an approval data configuration method, a transaction information approval method, device, electronic device, storage medium, and program product. Background Technology

[0002] In financial transaction approval systems, different types of transactions require different approval processes. However, when faced with diverse transaction scenarios, it is difficult to flexibly determine and trigger the appropriate approval process based on the specific attributes of the transaction, which affects approval efficiency. Summary of the Invention

[0003] In view of the above problems, embodiments of this application provide an approval data configuration method, a transaction information approval method, an apparatus, an electronic device, a storage medium, and a program product.

[0004] According to a first aspect of this application, an approval data configuration method is provided, characterized by comprising: acquiring approval data; the approval data includes at least a plurality of first nodes; the first nodes represent processing stage information in the approval process; acquiring transaction data; the transaction data includes a plurality of transaction attributes; creating a process instance based on the approval data and the transaction data; the process instance is configured with associated nodes, the associated nodes representing the correspondence between transaction attributes and corresponding nodes in the approval process; wherein, the process instance is used to respond to an approval request, and triggers the corresponding associated nodes based on the transaction information indicated in the approval request to obtain a target approval process, so as to transfer to the target approval process.

[0005] According to an embodiment of this application, creating a process instance based on approval data and transaction data includes: determining the node processing order and node processing information of multiple first nodes based on the approval data; arranging the multiple first nodes according to the node processing order to obtain an approval chain; determining the correspondence between multiple transaction attributes and multiple first nodes; generating a process instance based on the approval chain, and configuring associated nodes in the process instance according to the correspondence.

[0006] According to an embodiment of this application, the approval data further includes multiple second nodes; the second nodes represent abnormal approval process information; the method further includes: determining whether the transaction category information in the transaction data meets preset conditions to obtain a judgment result; the preset conditions represent the range of transaction categories for which abnormal approval needs to be enabled; if the judgment result represents that the preset conditions are met, then multiple second nodes and their node processing order are extracted, and multiple second nodes are added to the approval chain.

[0007] According to embodiments of this application, determining the correspondence between multiple transaction attributes and multiple first nodes includes: obtaining transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information from transaction data; generating multiple matching conditions based on at least one of the transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information; the matching conditions characterize the combination of transaction attributes used to determine the approval process; configuring a corresponding process identifier for each matching condition; the process identifier is used to point to the approval chain in the process instance; and establishing the correspondence between multiple matching conditions and corresponding process identifiers.

[0008] According to a second aspect of this application, a method for approving transaction information is provided, comprising: obtaining a process instance; the process instance being created based on the aforementioned approval data configuration method; deploying the process instance to a process engine; the process engine being used to generate an executable approval process based on the process instance; responding to an approval request and extracting target transaction attributes from the transaction information indicated in the approval request; matching the target transaction attributes based on the associated nodes configured in the process instance to obtain a matching result, and determining the target approval process based on the matching result; creating an execution instance corresponding to the target approval process based on the process engine; the execution instance being used to generate approval tasks sequentially according to the node order in the target approval process; and assigning the approval tasks to the processing personnel of the corresponding nodes to complete the approval workflow.

[0009] According to an embodiment of this application, assigning an approval task to a corresponding node's processing personnel includes: obtaining a preset processing personnel for the node corresponding to the approval task; recursively searching for the final processing personnel based on the preset processing personnel's sub-authorization records; the sub-authorization records represent configuration information where the approval personnel transfer approval authority to other personnel; the recursive search extracts authorized persons level by level along the sub-authorization chain until there are no valid sub-authorization records for the authorized persons; and assigning the approval task to the final processing personnel.

[0010] According to an embodiment of this application, determining the target approval process based on the matching result includes: determining whether the matching result indicates that an approval process needs to be executed; if the matching result indicates that no approval is required, then marking the transaction status corresponding to the approval request as completed; if the matching result indicates that approval is required, then extracting the process identifier associated with the matching result, and determining the target approval process based on the process identifier.

[0011] According to a third aspect of this application, an approval data configuration device is provided, comprising: a configuration acquisition module for acquiring approval data; the approval data includes at least a plurality of first nodes; the first nodes represent processing stage information in the approval process; a transaction acquisition module for acquiring transaction data; the transaction data includes a plurality of transaction attributes; and an instance creation module for creating a process instance based on the approval data and the transaction data; the process instance is configured with associated nodes, the associated nodes representing the correspondence between transaction attributes and corresponding nodes in the approval process; wherein the process instance is used to respond to an approval request, trigger the corresponding associated nodes based on the transaction information indicated in the approval request to obtain a target approval process, so as to transfer to the target approval process.

[0012] According to a fourth aspect of this application, a transaction information approval device is provided, comprising: an instance acquisition module for acquiring a process instance; the process instance is created based on the aforementioned approval data configuration method; an instance deployment module for deploying the process instance to a process engine; the process engine for generating an executable approval process based on the process instance; an attribute extraction module for responding to an approval request and extracting target transaction attributes from the transaction information indicated in the approval request; a process matching module for matching the target transaction attributes based on the associated nodes configured in the process instance to determine the target approval process; an instance creation module for creating an execution instance corresponding to the target approval process based on the process engine; the execution instance is used to generate approval tasks sequentially according to the node order in the target approval process; and a task allocation module for allocating approval tasks to the processing personnel of the corresponding nodes to complete the approval workflow.

[0013] According to a fifth aspect of this application, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] According to a sixth aspect of this application, a computer-readable storage medium is also provided, on which a computer program or instructions are stored, wherein the computer program or instructions, when executed by a processor, implement the steps of the above-described method.

[0015] According to a seventh aspect of this application, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method. Attached Figure Description

[0016] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1This illustration schematically depicts application scenarios of the approval data configuration method, transaction information approval method, apparatus, electronic device, storage medium, and program product according to embodiments of this application.

[0018] Figure 2 This illustration schematically shows one of the flowcharts of an approval data configuration method according to an embodiment of this application;

[0019] Figure 3 A second flowchart illustrating an approval data configuration method according to an embodiment of this application is shown schematically.

[0020] Figure 4 A flowchart illustrating a method for approving transaction information according to an embodiment of this application is shown schematically.

[0021] Figure 5 This schematic diagram illustrates the structural block diagram of an approval data configuration device according to an embodiment of this application;

[0022] Figure 6 This schematic diagram illustrates a structural block diagram of a transaction information approval device according to an embodiment of this application;

[0023] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing an approval data configuration method and a transaction information approval method according to an embodiment of this application. Detailed Implementation

[0024] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0026] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0027] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0028] Figure 1 The illustrations depict application scenarios of the approval data configuration method, transaction information approval method, apparatus, electronic device, storage medium, and program product according to embodiments of this application. Figure 1 As shown, application scenario 100 according to an embodiment of this application may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables. For example, personnel configuring approval processes, operating procedures, or approving personnel in financial institutions can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to configure approval processes, submit approval requests, query approval status, or perform approval operations.

[0029] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be electronic devices such as smartphones, wearable devices, personal computers, tablets, and workstations. The terminal devices can install and run client applications for approval management, which may include, but are not limited to, approval process configuration platform clients, transaction approval system clients, business management platform clients, process monitoring system clients, etc. (these are just examples). Furthermore, this application embodiment does not limit the form of the application, and may include, but is not limited to, applications, mini-programs, etc., installed on the terminal devices, or even web pages.

[0030] Server 105 can be a server that provides approval data configuration and transaction approval services, such as a back-end management server that provides approval process management support for financial institution business systems (for example only). Server 105 can acquire approval data and transaction data, wherein the approval data includes at least multiple first nodes, the first nodes representing processing stage information in the approval process, and the transaction data includes multiple transaction attributes. A process instance is created based on the approval data and the transaction data. The process instance is configured with associated nodes, the associated nodes representing the correspondence between the transaction attributes and corresponding nodes in the approval process. When an approval request is received, the process instance can respond to the approval request, trigger the corresponding associated nodes based on the transaction information indicated in the approval request to obtain the target approval process, and feed back the approval result (e.g., approval status, process node information, approval opinion, flow path, etc.) to the terminal device. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services such as cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and other basic cloud computing services. The server can be the backend server of a financial institution's approval management platform, used to provide backend services to the clients of the approval management application.

[0031] It should be noted that the approval data configuration method and transaction information approval method provided in the embodiments of this application can generally be executed by server 105 and / or terminal devices 101-103. Accordingly, the approval data configuration device and transaction information approval device provided in the embodiments of this application can generally be set in server 105 and / or terminal devices 101-103. In some embodiments, server 105 may be a server with an approval process engine deployed, which directly executes process instance creation and approval flow locally; in other embodiments, server 105 may be an independent approval management server, which receives approval requests from the business system and executes process matching and approval flow.

[0032] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0033] Figure 2 A flowchart illustrating one of the approval data configuration methods according to an embodiment of this application is shown. Figure 2 As shown, the approval data configuration method according to the embodiments of this application may include steps S210 to S230.

[0034] Step S210: Obtain approval data; the approval data includes at least multiple first nodes; the first node represents the processing information in the approval process.

[0035] Step S220: Obtain transaction data; the transaction data includes multiple transaction attributes.

[0036] Step S230: Create a process instance based on approval data and transaction data; the process instance is configured with associated nodes, which represent the correspondence between transaction attributes and corresponding nodes in the approval process; the process instance is used to respond to approval requests, and trigger the corresponding associated nodes based on the transaction information indicated in the approval request to obtain the target approval process, so as to flow to the target approval process.

[0037] In step S210, approval data refers to the basic configuration information used to construct the approval process, which can be understood as a set of node definitions and processing requirements required to form the approval process.

[0038] Optionally, the approval data may include multiple first nodes, each representing a processing step in the approval process. The processing step information refers to the processing content and personnel involved in the processing of a single approval node; it can be understood as descriptive information about who should handle each approval step and in what order.

[0039] Optionally, the approval data may also include configuration content such as node name, node order, node handler, and flow relationship between nodes.

[0040] In one implementation, the process administrator can input approval data in the configuration interface, and the system receives and stores the configuration information, which includes fields such as business role, operating user, affiliated organization, approval node name, node processing order, and node corresponding approver.

[0041] In another implementation, approval data can be imported from an existing process configuration template. The system reads the predefined node information and processing order in the template and then loads it.

[0042] In another implementation, approval data can be obtained by calling external system interfaces, and organizational structure and approval personnel configuration information maintained in other business systems can be synchronized to this system.

[0043] Optionally, the first node can correspond to different processing stages in the financial transaction approval process, such as the initial business review node, the compliance review node, etc., and each node can be configured with one or more candidate processing personnel.

[0044] Optionally, the approval data can be acquired in one go or acquired in batches and then integrated.

[0045] In step S220, transaction data refers to the business information generated when a business transaction occurs, which can be understood as various business parameters used to describe the characteristics of the transaction.

[0046] Optionally, transaction data includes multiple transaction attributes. Transaction attributes refer to the business characteristics inherent in the transaction itself, which can be understood as business parameters that can distinguish different transaction categories and approval requirements.

[0047] For example, transaction attributes may include, but are not limited to, transaction type, counterparty information, transaction direction, business classification information, and transaction limit information. Specifically, the transaction type may be a financial transaction business category such as spot foreign exchange, forward foreign exchange, precious metals trading, or options trading; the counterparty information may include the counterparty's classification attributes, such as domestic institutions, overseas institutions, banking institutions, or non-banking institutions; the transaction direction may be buy, sell, or other preset directions; and the transaction limit information may be the amount or range corresponding to the transaction application.

[0048] Optionally, transaction data may also include supplementary information such as the transaction initiator, the time of the transaction initiation, and the institution to which the transaction belongs.

[0049] In one feasible implementation, when a business user submits a transaction application through the transaction system, the system can automatically extract the transaction data corresponding to the transaction. The system reads various transaction attributes such as transaction type, counterparty, and transaction amount from the transaction application form and stores the attribute information in a structured manner.

[0050] In another feasible implementation, transaction data can be obtained from an external trading platform. The system receives transaction information transmitted by other business systems through interface calls, and extracts the various transaction attributes contained in the data packets returned by the interface after parsing them.

[0051] Optionally, transaction data can be acquired in real time when the transaction is initiated, or in batches after the transaction is submitted. The specific acquisition method can be determined based on the actual deployment of the business system.

[0052] Optionally, the number and type of transaction attributes can be configured according to actual business needs. The required transaction attributes may vary in different business scenarios, and the system can support extended configuration of transaction attributes.

[0053] In step S230, after obtaining the approval data and transaction data, the two types of data need to be associated to create a process instance. A process instance refers to an executable approval process configuration generated based on the approval data and transaction data. It can be understood as a process configuration object formed by associating approval nodes with transaction attributes, which is used to quickly match and start the corresponding approval process when actual business occurs.

[0054] Optionally, the process instance is configured with associated nodes. Associated nodes refer to the mapping relationship between transaction attributes and approval nodes established in the process instance. They can be understood as a configuration that describes which transaction attributes should enter which approval nodes, and is used to determine which approval path should be taken when an approval request occurs.

[0055] For example, associated nodes can record the corresponding relationships such as the sequence of approval nodes for a specific transaction type, the combination of approval nodes for different transaction amount ranges, and the approval nodes that a specific counterparty category needs to go through.

[0056] Optionally, a process instance may also include configuration content such as process name, process identifier, node name, node order, node handler information, and flow relationship between nodes.

[0057] Optionally, the target approval process refers to the approval process that should be executed for the transaction, which is matched based on specific transaction information.

[0058] In one feasible implementation, the system can associate the first node in the approval data with the transaction attributes in the transaction data. The system assigns a corresponding approval node sequence to each group of transaction attributes and stores these correspondences as associated node configurations, ultimately generating a process instance containing associated nodes. When a business user submits an approval request, the system extracts transaction information from the approval request and performs a matching search in the associated nodes of the process instance based on the transaction attributes in the transaction information to determine the target approval process corresponding to the transaction.

[0059] In another feasible implementation, process instances can be created through a process configuration tool interface. The administrator selects the approval nodes and transaction attributes to be associated on the interface. The system establishes the corresponding relationship based on the administrator's selection and saves it as associated nodes to form a complete process instance. After the process instance is deployed, when an approval request is received, the system extracts the transaction information such as transaction type and transaction amount contained in the approval request, traverses the associated nodes configured in the process instance, and finds the approval node sequence that matches the transaction information as the target approval process.

[0060] Optionally, a process instance can contain multiple associated node configurations to support business requirements for different approval paths corresponding to different combinations of transaction attributes.

[0061] Optionally, the process instance can be modified and updated after it is created. When approval data or transaction data changes, the configuration of related nodes in the process instance can be adjusted.

[0062] Optionally, the approval request can be a transaction approval application initiated by the business personnel, or it can be an approval process start request automatically triggered by the system based on the transaction submission.

[0063] Optionally, transferring to the target approval process means that the system guides the transaction to its corresponding approval node sequence for processing, thus initiating the actual approval process.

[0064] By adopting the technical solution of this application, approval data containing multiple first nodes and transaction data containing multiple transaction attributes are obtained, and a process instance is created based on the approval data and the transaction data. Since the process instance is configured with associated nodes, the associated nodes represent the correspondence between the transaction attributes and the corresponding nodes in the approval process. This allows the process instance to trigger the corresponding associated nodes to obtain the target approval process based on the transaction information indicated in the approval request when responding to an approval request. This enables flexible determination and triggering of the approval process to be executed based on the specific attributes of the transaction, solving the problem of difficulty in flexibly determining and triggering the approval process to be executed based on the specific attributes of the transaction, and improving approval efficiency.

[0065] Figure 3 A flowchart illustrating a method for configuring approval data according to an embodiment of this application is shown in the illustration. Figure 3 As shown in the embodiment of this application, step S230 may further include the following steps.

[0066] Step S310: Determine the node processing order and node processing information of multiple first nodes based on the approval data.

[0067] Step S320: Arrange the multiple first nodes according to their node processing order to obtain the approval chain.

[0068] Step S330: Determine the correspondence between multiple transaction attributes and multiple first nodes.

[0069] Step S340: Generate a process instance based on the approval chain, and configure associated nodes in the process instance according to the corresponding relationship.

[0070] In step S310, the node processing order refers to the sequential order of multiple first nodes in the approval process, which can be understood as the arrangement rules for the order in which each approval node should be executed. Node processing information refers to the approval data of the personnel corresponding to each first node, which can be understood as the configuration content used to determine which personnel should handle the approval node.

[0071] Optionally, the node processing order can be determined by assigning a sequence number to each first node, for example, setting the business initial review node as the first position, the compliance review node as the second position, and the risk control final review node as the third position.

[0072] Optionally, the node processing information may include configuration content such as the approver corresponding to the node, the organization to which the approver belongs, and the business role of the approver.

[0073] In one implementation, the node processing order field corresponding to each first node can be extracted from the approval data. After reading the field, the system sorts the first nodes according to their numerical values ​​to form an ascending order. At the same time, the system extracts the approval personnel field and the affiliated organization field corresponding to the node recorded in the approval data and saves these fields as node processing information.

[0074] In another implementation, the administrator can adjust the order of multiple first nodes by dragging and dropping in the configuration interface. The system automatically generates the node processing order based on the node positions adjusted by the administrator. The administrator configures the corresponding list of approvers on each node, and the system records the list of approvers as node processing information.

[0075] Optionally, when the same approval node corresponds to multiple candidates, the node processing information may include allocation rules, which are used to determine which person should handle the node task during actual approval.

[0076] Optionally, the allocation rule can be one of the following: uniquely determined by the affiliated organization, determined by a set of business roles, or directly designated by a list of personnel.

[0077] In step S320, the approval chain refers to the set of all approval nodes arranged in the order of processing from the beginning to the end of the process. It can be understood as a complete approval path formed by connecting multiple first nodes in a determined order.

[0078] Optionally, the approval chain may include a process start node, multiple first nodes, and a process end node, wherein the multiple first nodes are arranged sequentially according to the node processing order.

[0079] In one implementation, the system can add a process start node before the first first node and a process end node after the last first node according to the node processing order, thereby forming an approval chain containing a complete node sequence; the system saves the connection relationship between each node in the approval chain as flow relationship data.

[0080] In another implementation, the system can display the approval chain in the form of a flowchart, where each first node is represented as a node graphic, and the nodes are connected by connecting lines according to the processing order of the nodes, forming a visual approval chain structure. Administrators can view the complete structure of the approval chain on the graphical interface to confirm whether the node order and the connection relationship between nodes meet the business requirements.

[0081] Optionally, after the approval chain is formed, a structural verification can be performed. The structural verification is used to check whether there are any abnormalities in the approval chain, such as missing nodes, incorrect order, or broken connections.

[0082] Optionally, when the approval chain contains only one first node, that first node is the only approval processing step; when the approval chain contains multiple first nodes, each first node is executed sequentially.

[0083] In step S330, the correspondence refers to the mapping relationship established between multiple transaction attributes and multiple first nodes. It can be understood as a configuration rule used to indicate which combination of transaction attributes should be processed by which approval nodes.

[0084] Optionally, the correspondence can be a one-to-one relationship, where one combination of transaction attributes corresponds to one specific first node; or it can be a one-to-many relationship, where one combination of transaction attributes corresponds to multiple first nodes.

[0085] Optionally, the correspondence can be determined based on at least one of the following transaction attributes: transaction type, counterparty information, transaction direction, business classification information, or transaction amount information.

[0086] In one implementation, the administrator can select one or more transaction attributes as judgment conditions in the configuration interface, and specify the first node to be entered for each set of judgment conditions. The system establishes and saves the correspondence between transaction attributes and the first node according to the administrator's configuration. For example, the administrator configures the corresponding business preliminary review node and compliance review node when the transaction type is spot foreign exchange and the transaction amount is less than 1 million. The system saves the configuration as a correspondence record.

[0087] In another implementation, the system can import corresponding relationship configurations from an existing business rule base. The business rule base pre-stores mapping rules between different combinations of transaction attributes and approval nodes. After reading the mapping rules in the rule base, the system parses the transaction attribute conditions and corresponding first node information contained therein, and loads the parsing results as corresponding relationships.

[0088] Optionally, the correspondence can contain multiple levels, and the correspondence at different levels has different priorities. When multiple correspondences are satisfied at the same time, the system determines the correspondence to be used according to the priority.

[0089] In step S340, after the approval chain is generated and the corresponding relationship is determined, the approval chain and the corresponding relationship need to be combined to generate a process instance.

[0090] Optionally, when generating a process instance, a unique process identifier can be assigned to the process instance at the same time. The process identifier is used to identify the process instance during subsequent invocation and deployment.

[0091] In one implementation, the first nodes, node order, and flow relationships between nodes in the approval chain can be used as the basic structure of the process instance. Then, the system reads the determined correspondence, converts the transaction attribute conditions recorded in the correspondence and the corresponding first node information into associated node configurations, and embeds the associated node configurations into the process instance. The system generates a unique process identifier for the process instance and saves the process instance as structured data.

[0092] In another implementation, the system can use a process definition language to describe the structure of the process instance, representing each first node in the approval chain as a task node in the process definition language, and representing the flow relationship between nodes as a connection relationship in the process definition language; the system converts the correspondence into conditional expressions in the process definition language, and configures the conditional expressions in the decision nodes or gateway nodes of the process instance, so that the process instance can determine which first nodes should be entered according to the conditional expressions when it runs; the system saves the content described in the process definition language as a process definition file.

[0093] Optionally, after a process instance is generated, it can be saved as an editable instance. Administrators can modify and adjust the process instance, and after modification, save it again and update the process instance content corresponding to the process identifier.

[0094] By adopting the technical solution of this application, the node processing order and node processing information of multiple first nodes are determined based on approval data, and the multiple first nodes are arranged according to the node processing order to obtain an approval chain. After determining the correspondence between multiple transaction attributes and multiple first nodes, a process instance is generated based on the approval chain, and associated nodes are configured in the process instance according to the correspondence. This enables the process instance to simultaneously contain a complete sequence of approval nodes and the mapping relationship between transaction attributes and approval nodes, thereby effectively integrating the node structure of the approval process with business rules and improving the accuracy of process configuration.

[0095] According to the embodiments of this application, the approval data also includes multiple second nodes; the second nodes represent information on abnormal approval processes, and the above-mentioned approval data configuration method may further include the following steps.

[0096] The system determines whether the transaction category information in the transaction data meets the preset conditions and obtains the judgment result; the preset conditions represent the scope of transaction categories that need to be approved by exceptions; if the judgment result represents that the preset conditions are met, multiple second nodes and their node processing order are extracted, and multiple second nodes are added to the approval chain.

[0097] In this embodiment, the second node refers to the node approval data used to process specific risk control approvals. This can be understood as an additional approval processing step that needs to be added when a transaction meets specific conditions. Abnormal approval process information refers to additional approval requirements that differ from the regular approval process. This can be understood as approval processing content added for high-risk or special categories of transactions.

[0098] Optionally, the second node may include configuration content such as node name, node order, and node handler.

[0099] Optionally, the second node can maintain the same data structure as the first node. The difference lies in whether the approval process corresponding to the second node is activated, depending on the judgment result of the transaction category information.

[0100] It should be noted that transaction category information refers to the business category to which the transaction belongs, which can be understood as a classification field used to distinguish different types of financial transaction business. For example, transaction category information may include financial transaction business categories such as spot foreign exchange, forward foreign exchange, swap foreign exchange, precious metals trading, and options trading.

[0101] Optionally, the preset conditions can be activation rules for one or more trading categories. For example, the preset conditions could be enabling the second node when the trading category is forward foreign exchange or options trading; or the preset conditions could be enabling the second node when the trading category falls within the scope of derivatives trading.

[0102] When determining whether the transaction category information in the transaction data meets the preset conditions, the system extracts the transaction category field from the transaction data and compares the extracted transaction category with the range of transaction categories defined in the preset conditions. When the transaction category falls within the range defined in the preset conditions, the judgment result is that the preset conditions are met; when the transaction category does not fall within the range defined in the preset conditions, the judgment result is that the preset conditions are not met.

[0103] In one implementation, during the approval data configuration phase, the administrator can configure an identifier for each transaction category to indicate whether a second node is enabled. The system then determines whether to add the second node to the approval chain based on this identifier. When the administrator configures an identifier for a transaction category to be enabled, the system extracts the corresponding second node information from the approval data when processing the approval process for that transaction category, and reads the configuration content such as the node name, node processing order, and node handler of the second node.

[0104] Optionally, extracting multiple second nodes and their processing order means that the system reads all the second node configurations corresponding to the transaction category from the approval data and obtains the processing order of these second nodes in the approval process.

[0105] When adding multiple second nodes to an approval chain, the system needs to determine the insertion position of each second node within the chain. Optionally, the second node can be inserted at the end of the first node sequence, forming an approval chain structure with the main process node preceding the second node. Alternatively, the second node can also be inserted in the middle of the first node sequence; the specific insertion position can be determined based on the node processing order field.

[0106] In one implementation, the system can directly append the second node to the end of the existing first node sequence and readjust the overall sequence number of each node in the approval chain so that the approval chain contains a complete sequence of first and second nodes.

[0107] Optionally, when the judgment result does not meet the preset conditions, the system does not extract the second node, and the approval chain only contains multiple first nodes and does not contain the second node.

[0108] Optionally, a trading category may correspond to one or more second nodes, and the second nodes corresponding to different trading categories may be the same or different.

[0109] By adopting the technical solution of this application, by judging whether the transaction category information in the transaction data meets the preset conditions, and extracting multiple second nodes and their node processing order when the preset conditions are met, and adding them to the approval chain, the approval chain can dynamically include or exclude second nodes according to different transaction categories, thereby realizing the need for flexible configuration of the approval process for different transaction categories and improving the flexibility of the approval process configuration.

[0110] According to the embodiments of this application, step S330 may further include the following steps.

[0111] Obtain transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information from transaction data; generate multiple matching conditions based on at least one of the transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information; the matching conditions represent the combination of transaction attributes used to determine the approval process.

[0112] Configure a corresponding process identifier for each matching condition; the process identifier is used to point to the approval chain in the process instance; establish the correspondence between multiple matching conditions and their corresponding process identifiers.

[0113] In this embodiment, when obtaining transaction type, counterparty information, transaction direction, transaction business classification information and transaction amount information from transaction data, the system extracts the above five types of transaction attribute fields from the transaction data.

[0114] It should be noted that transaction business classification information refers to the classification field used to identify the business category or product catalog to which a transaction belongs. This can be understood as a classification identifier used to distinguish the approval requirements corresponding to different business lines or business units. For example, transaction business classification information may include the business catalog level to which the transaction belongs, product category code, or internal management catalog number, etc.

[0115] Optionally, the matching condition can be a single transaction attribute condition, such as a matching condition generated solely based on the transaction type. Optionally, the matching condition can also be a combination of multiple transaction attributes, such as a matching condition generated simultaneously based on transaction type and transaction amount information.

[0116] In one implementation, the administrator can select the transaction attributes to be used as the basis for judgment in the configuration interface, and the system generates corresponding matching conditions based on the transaction attributes selected by the administrator.

[0117] Optionally, the generated matching conditions may have different coverage ranges, and different matching conditions may correspond to different ranges of transaction attribute values. When configuring a corresponding process identifier for each matching condition, the process identifier refers to an identifier used to uniquely identify a process instance, which can be understood as a reference number pointing to a specific approval chain.

[0118] Optionally, the process identifier can be a unique code automatically generated by the system, or a process name or process number defined by the administrator.

[0119] In one implementation, the system can automatically assign a unique process identifier to each generated process instance. When the administrator configures a process for matching conditions, the system displays all available process identifiers for the administrator to select. The administrator selects one of the process identifiers to associate with the current matching conditions, and the system records the association between the matching conditions and the selected process identifier.

[0120] Optionally, a process identifier can be referenced by multiple matching conditions, and different matching conditions can point to the approval chain within the same process instance. When establishing the correspondence between multiple matching conditions and their corresponding process identifiers, the system saves each matching condition and its configured process identifier as a set of associated data.

[0121] Optionally, the mapping relationship can be stored in a key-value pair format, where the matching condition is the key and the process identifier is the value. Optionally, the mapping relationship can also be stored in an association table format, where the association table records the identifier of the matching condition and the corresponding process identifier.

[0122] In one implementation, the system can assign a unique relationship identifier to each set of corresponding relationships and store the content of the matching conditions, the corresponding process identifier, and the relationship identifier together in the corresponding relationship configuration table. When it is necessary to find the corresponding approval process based on the transaction attributes later, the system traverses each record in the corresponding relationship configuration table, compares the transaction attributes with the matching conditions, and extracts the process identifier from the record that meets the conditions.

[0123] Optionally, the correspondence may also include a priority field, which is used to determine which matching condition's corresponding process identifier should be used when multiple matching conditions are met simultaneously. Optionally, the correspondence can be modified and deleted after it is established. Administrators can adjust the binding relationship between matching conditions and process identifiers, and the system updates the correspondence approval data based on the adjustment results.

[0124] By adopting the technical solution of this application, multiple transaction attributes are obtained from transaction data and multiple matching conditions are generated based on at least one transaction attribute. A corresponding process identifier is configured for each matching condition, and a correspondence between the matching condition and the process identifier is established. This enables the system to accurately match the corresponding approval process according to different combinations of transaction attributes, thereby realizing the need for approval process matching based on multi-dimensional transaction attributes and improving the accuracy of approval process matching.

[0125] Figure 4 A flowchart illustrating a transaction information approval method according to an embodiment of this application is shown. Figure 4 As shown, the transaction information approval method according to the embodiments of this application may include steps S410 to S460.

[0126] Step S410: Obtain a process instance; the process instance is created based on the above-described approval data configuration method.

[0127] Step S420: Deploy the process instance to the process engine; the process engine is used to generate an executable approval process based on the process instance.

[0128] Step S430: In response to the approval request, extract the target transaction attributes from the transaction information indicated in the approval request.

[0129] Step S440: Match the target transaction attributes based on the associated nodes configured in the process instance to obtain the matching results, and determine the target approval process based on the matching results.

[0130] Step S450: Create an execution instance corresponding to the target approval process based on the process engine; the execution instance is used to generate approval tasks sequentially according to the node order in the target approval process.

[0131] Step S460: Assign the approval task to the corresponding node's processing personnel to complete the approval workflow.

[0132] In step S420, when deploying a process instance to the process engine, the system converts the process instance into a process definition format that the process engine can recognize, and submits the converted process definition to the process engine for deployment.

[0133] In one implementation, the system can convert the approval chain, node information, and flow relationship in the process instance into a process definition file, and then call the deployment interface of the process engine to upload the process definition file to the process engine. After receiving the process definition file, the process engine parses and verifies it. If the verification is successful, the process definition is registered in the process definition library of the process engine and a deployment success identifier is returned.

[0134] Optionally, the process engine can perform validity checks on the process definition during deployment, including checking whether the node connection relationships are complete and whether the handler configuration is valid.

[0135] In step S430, the approval request can be an approval application initiated proactively by business personnel in the transaction system, or it can be an approval request automatically generated by the transaction system after the transaction is submitted.

[0136] Upon receiving an approval request, the system parses the request and extracts transaction information. Target transaction attributes refer to the key attributes extracted from the transaction information used to match the approval process; these can be understood as the criteria for determining which approval process the transaction should follow.

[0137] In one implementation, the system can parse the transaction information field in the approval request and extract the target transaction attributes from the transaction information according to preset attribute extraction rules; for example, the system reads the values ​​of the transaction type field and the transaction amount field from the transaction information and saves these values ​​as target transaction attributes.

[0138] Optionally, the number and type of target transaction attributes extracted can be determined based on the matching conditions required by the associated nodes configured in the process instance.

[0139] In step S440, when matching the target transaction attributes based on the associated nodes configured in the process instance, the system reads the associated node data configured in the process instance, extracts each matching condition from the associated nodes, and compares the target transaction attributes with each matching condition.

[0140] The target approval process refers to the approval process that should be executed for the transaction based on the matching results. It can be understood as a sequence of approval nodes corresponding to the attributes of the target transaction.

[0141] In one implementation, the system can traverse all the matching conditions configured in the associated nodes, determine whether the target transaction attributes meet the requirements of the matching condition for each matching condition, and when a matching condition that meets the conditions is found, the system extracts the process identifier corresponding to the matching condition, determines the corresponding approval chain based on the process identifier, and uses the approval chain as the target approval process.

[0142] Optionally, when multiple matching conditions are met simultaneously, the system can select the target approval process to be used based on the priority of the matching conditions.

[0143] In step S450, the execution instance refers to the executable process object created by the process engine based on the target approval process, which can be understood as an approval process running instance bound to a specific transaction application.

[0144] When creating an execution instance corresponding to the target approval process based on the process engine, the system sends a process start request to the process engine. The process start request contains the process identifier of the target approval process and the business data of this transaction application. After receiving the process start request, the process engine retrieves the corresponding process definition from the process definition library according to the process identifier, creates a new execution instance based on the process definition, and associates the business data with the execution instance.

[0145] Optionally, after an execution instance is created, a unique instance identifier can be assigned, which is used to track and manage the execution instance during subsequent process flows.

[0146] After the execution instance is created, the workflow engine generates approval tasks sequentially according to the node order in the target approval workflow. An approval task refers to a pending work item generated during the execution instance's workflow; it can be understood as a specific approval matter that requires processing by the approver.

[0147] In one implementation, after creating an execution instance, the process engine automatically generates the approval task corresponding to the first approval node. The system records the node name, task identifier, and task status corresponding to the approval task. After the first approval task is completed, the process engine generates the approval task corresponding to the next approval node according to the node order, and so on until all the approval tasks of all nodes are generated and processed.

[0148] In step S460, when assigning an approval task to the corresponding node's processing personnel, the system obtains the processing personnel configuration of the node corresponding to the current approval task and determines the processing personnel who should receive the approval task.

[0149] The completion of the approval process refers to the process by which approval tasks are passed and processed sequentially among the personnel at each approval node. It can be understood as the complete execution process of the approval process from the start node to the end node.

[0150] In one implementation, the system can read the information of the processing personnel from the node configuration corresponding to the approval task, and push the approval task to the processing personnel's to-do list; the processing personnel can view the approval task in the to-do list, perform the approval operation on the approval task and submit the approval result; after receiving the approval result, the system updates the status of the approval task, triggers the process engine to flow to the next approval node, generates a new approval task at the next approval node and assigns it to the corresponding processing personnel.

[0151] By adopting the technical solution of this application, a process instance created based on the approval data configuration method is obtained and deployed to the process engine. When responding to an approval request, the target transaction attributes are extracted and matched based on the associated nodes to determine the target approval process. Then, an execution instance is created based on the process engine and the approval task is assigned to the corresponding personnel at the corresponding node. This enables the system to automatically match and start the corresponding approval process when a transaction occurs and drive the approval task to complete the flow between various nodes, thereby realizing the automated execution of the approval process and improving the efficiency of approval processing.

[0152] According to an embodiment of this application, step S460 may further include the following steps.

[0153] Obtain the preset handler for the node corresponding to the approval task; recursively search for the final handler based on the sub-authorization record of the preset handler; the sub-authorization record represents the configuration information of the approver transferring the approval authority to other personnel; the recursive search extracts the authorized persons level by level along the sub-authorization chain until there is no valid sub-authorization record for the authorized person; assign the approval task to the final handler.

[0154] In this embodiment, the preset handler refers to the initial personnel who should handle the approval task as determined by the node configuration. It can be understood as the handler corresponding to the approval node without considering sub-authorization.

[0155] A sub-authorization record refers to the configuration information where an approver transfers approval authority to another person. It can be understood as approval data that records the relationship between the original approver and the proxy approver. Optionally, the sub-authorization record may include fields such as the authorizer, the authorized person, the effective start time, the effective end time, and the activation status.

[0156] Recursive search refers to the process of searching down the hierarchy along the sub-delegation relationship. It can be understood as starting from the authorizer, searching for the authorized person in turn, and then searching for the authorized person's authorized person, until the person who has not been further sub-delegated is found.

[0157] When recursively searching for sub-authorization records based on a preset processor, the system queries for valid sub-authorization records of the preset processor. If a record exists, the authorized person is extracted. The system then uses the authorized person as a query condition to continue querying for their sub-authorization records, repeating the above query process until no valid sub-authorization record exists for the current authorized person. The authorized person is then identified as the final processor.

[0158] The final handler refers to the person who should actually receive the approval task, determined through recursive search. This can be understood as the authorized person at the end of the delegation chain or a pre-defined handler without any delegation authority. When assigning an approval task to the final handler, the system pushes the task to the final handler's to-do list.

[0159] By adopting the technical solution of this application, the final processor is obtained by recursively searching based on the sub-authorization records of the preset processor and the approval task is assigned to the final processor. This enables the system to automatically search for the actual person who should handle the task when there is a sub-authorization relationship between the approvers. This achieves dynamic adjustment of the recipient of the approval task and improves the continuity of the approval process.

[0160] According to an embodiment of this application, step S440 may further include the following steps.

[0161] Determine whether the matching result indicates that an approval process is required. If the matching result indicates that no approval is required, mark the transaction status corresponding to the approval request as completed. If the matching result indicates that approval is required, extract the associated process identifier from the matching result and determine the target approval process based on the process identifier.

[0162] In this embodiment, when determining whether the matching result indicates that an approval process needs to be executed, the system analyzes the matching result obtained based on the matching of associated nodes to determine whether the transaction needs to enter the approval process.

[0163] Optionally, the matching result may include an approval identifier field, which is used to identify whether approval is required; the system reads the value of the approval identifier field and determines whether the approval process needs to be executed based on the value.

[0164] Optionally, the system can also determine whether approval is required based on whether the matching result contains a valid process identifier; when the matching result does not contain a process identifier or the process identifier is empty, it is determined that no approval is required; when the matching result contains a valid process identifier, it is determined that approval is required.

[0165] If the matching result indicates that no approval is required, the system will mark the transaction status corresponding to the approval request as "completed". The completed status means that the transaction has completed all necessary processing, which can be understood as the final state where the transaction can be completed directly without approval.

[0166] By adopting the technical solution of this application, the system can determine whether the matching result indicates that an approval process is required. When no approval is required, the transaction status is directly marked as completed. When approval is required, the process identifier is extracted and the target approval process is determined. This enables the system to distinguish between transactions that require approval and those that do not, thereby achieving rapid processing of transactions that do not require approval and improving the efficiency of transaction processing.

[0167] Based on the above-described approval data configuration method, embodiments of this application also provide an approval data configuration device. The following will be combined with... Figure 5 The device is described in detail.

[0168] Figure 5 A schematic block diagram of an approval data configuration device according to an embodiment of this application is shown.

[0169] The approval data configuration 500 may include a configuration acquisition module 510, a transaction acquisition module 520, and an instance creation module 530. The configuration acquisition module 510 acquires approval data; the approval data includes at least multiple first nodes; each first node represents a processing stage in the approval process. The transaction acquisition module 520 acquires transaction data; the transaction data includes multiple transaction attributes. The instance creation module 530 creates a process instance based on the approval data and transaction data; the process instance is configured with associated nodes, which represent the correspondence between transaction attributes and corresponding nodes in the approval process. The process instance responds to approval requests, triggering the corresponding associated nodes based on the transaction information indicated in the approval request to obtain the target approval process, thus facilitating the flow to the target approval process.

[0170] According to an embodiment of this application, the instance creation module 530 is further configured to determine the node processing order and node processing information of multiple first nodes based on the approval data; arrange the multiple first nodes according to the node processing order of the multiple first nodes to obtain an approval chain; determine the correspondence between multiple transaction attributes and multiple first nodes; generate a process instance based on the approval chain, and configure associated nodes in the process instance according to the correspondence.

[0171] According to the embodiments of this application, the instance creation module 530 is further used to determine whether the transaction category information in the transaction data meets the preset conditions to obtain the judgment result; the preset conditions represent the range of transaction categories that need to be approved by exception; if the judgment result represents that the preset conditions are met, then multiple second nodes and their node processing order are extracted, and multiple second nodes are added to the approval chain.

[0172] According to an embodiment of this application, the instance creation module 530 is further configured to obtain transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information from transaction data; generate multiple matching conditions based on at least one of the transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information; the matching conditions represent the combination of transaction attributes used to determine the approval process; configure a corresponding process identifier for each matching condition; the process identifier is used to point to the approval chain in the process instance; and establish a correspondence between multiple matching conditions and corresponding process identifiers.

[0173] Based on the above-described transaction information approval method, embodiments of this application also provide a transaction information approval device. The following will be combined with... Figure 6 The device is described in detail.

[0174] Figure 6 A schematic block diagram of a transaction information approval device according to an embodiment of this application is shown.

[0175] The transaction information approval device 600 may include an instance acquisition module 610, an instance deployment module 620, an attribute extraction module 630, a process matching module 640, an instance creation module 650, and a task allocation module 660.

[0176] The instance acquisition module 610 is used to acquire process instances; the instance deployment module 620 is used to deploy process instances to the process engine; the process engine is used to generate executable approval processes based on process instances; the attribute extraction module 630 is used to respond to approval requests and extract target transaction attributes from the transaction information indicated in the approval request; the process matching module 640 is used to match target transaction attributes based on the associated nodes configured in the process instance to obtain matching results, and determine the target approval process based on the matching results; the instance creation module 650 is used to create execution instances corresponding to the target approval process based on the process engine; the execution instances are used to generate approval tasks sequentially according to the node order in the target approval process; and the task allocation module 660 is used to allocate approval tasks to the corresponding personnel at the nodes to complete the approval workflow.

[0177] According to an embodiment of this application, the task allocation module 660 is further configured to obtain the preset handler of the node corresponding to the approval task; recursively search for the final handler based on the sub-authorization record of the preset handler; the sub-authorization record represents the configuration information of the approver transferring the approval authority to other personnel; the recursive search extracts the authorized person level by level along the sub-authorization chain until there is no valid sub-authorization record for the authorized person; and allocate the approval task to the final handler.

[0178] According to an embodiment of this application, the process matching module 640 is further configured to determine whether the matching result indicates that an approval process needs to be executed; if the matching result indicates that no approval is required, the transaction status corresponding to the approval request is marked as completed; if the matching result indicates that approval is required, the process identifier associated with the matching result is extracted, and the target approval process is determined based on the process identifier.

[0179] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing an approval data configuration method and a transaction information approval method according to an embodiment of this application.

[0180] like Figure 7 As shown, an electronic device 700 according to an embodiment of this application includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory 702 or a program loaded from a storage portion 708 into a random access memory 703. The processor 701 may include, for example, a general-purpose microprocessor, an instruction set processor and / or an associated chipset and / or a dedicated microprocessor. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for executing different steps of the method flow according to an embodiment of this application.

[0181] Random access memory 703 stores various programs and data required for the operation of electronic device 700. Processor 701, read-only memory 702, and random access memory 703 are interconnected via bus 704. Processor 701 executes various steps of the method flow according to embodiments of this application by executing programs in read-only memory 702 and / or random access memory 703. It should be noted that the programs may also be stored in one or more memories other than read-only memory 702 and random access memory 703. Processor 701 may also execute various steps of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0182] According to embodiments of this application, the electronic device 700 may further include an input / output interface 705, which is also connected to a bus 704. The electronic device 700 may also include one or more of the following components connected to the input / output interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube, liquid crystal display, etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card, such as a local area network card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0183] Embodiments of this application also provide a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0184] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof. In embodiments of this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include the read-only memory 702, and / or random access memory 703, and / or one or more memories other than read-only memory 702 and random access memory 703 described above.

[0185] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this application.

[0186] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 709, and / or installed from a removable medium 711. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0187] In embodiments of this application, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by processor 701, it performs the functions defined in the system of embodiments of this application. According to embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0188] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0189] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0190] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for configuring approval data, characterized in that, include: Obtain approval data; the approval data includes at least multiple first nodes; The first node represents information about the processing steps in the approval process; Obtain transaction data; the transaction data includes multiple transaction attributes; Create a process instance based on the approval data and the transaction data; The process instance is configured with associated nodes, which represent the correspondence between the transaction attributes and the corresponding nodes in the approval process; The process instance is used to respond to an approval request, trigger the corresponding associated node based on the transaction information indicated in the approval request to obtain the target approval process, so as to transfer to the target approval process.

2. The approval data configuration method according to claim 1, characterized in that, The process instance created based on the approval data and the transaction data includes: Based on the approval data, the node processing order and node processing information of the plurality of first nodes are determined; An approval chain is obtained by arranging the multiple first nodes according to their node processing order. Determine the correspondence between the multiple transaction attributes and the multiple first nodes; A process instance is generated based on the approval chain, and associated nodes are configured in the process instance according to the correspondence.

3. The approval data configuration method according to claim 2, wherein the approval data further includes multiple second nodes; The second node represents information about abnormal approval processes; The approval data configuration method also includes: The judgment result is obtained by determining whether the transaction category information in the transaction data meets preset conditions; the preset conditions represent the range of transaction categories for which abnormal approval needs to be enabled. If the judgment result indicates that the preset conditions are met, then the plurality of second nodes and their node processing order are extracted, and the plurality of second nodes are added to the approval chain.

4. The approval data configuration method according to claim 2, wherein determining the correspondence between the plurality of transaction attributes and the plurality of first nodes includes: Obtain the transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information from the transaction data; Multiple matching conditions are generated based on at least one of the transaction type, counterparty information, transaction direction, transaction business classification information, and transaction amount information. The matching criteria represent the combination of transaction attributes used to determine the approval process; Configure a corresponding process identifier for each of the matching conditions; The process identifier is used to point to the approval chain in the process instance; Establish the correspondence between the multiple matching conditions and their corresponding process identifiers.

5. A method for approving transaction information, characterized in that, include: Obtain a process instance; The process instance is created based on the approval data configuration method as described in any one of claims 1-4; Deploy the process instance to the process engine; The process engine is used to generate executable approval processes based on process instances; In response to an approval request, extract the target transaction attributes from the transaction information indicated in the approval request; The target transaction attributes are matched based on the associated nodes configured in the process instance to obtain a matching result, and the target approval process is determined based on the matching result. Create an execution instance corresponding to the target approval process based on the process engine; The execution instance is used to generate approval tasks sequentially according to the node order in the target approval process; The approval tasks are assigned to the corresponding personnel at the appropriate nodes to complete the approval process.

6. The method for approving transaction information according to claim 5, characterized in that, The personnel who assign the approval tasks to the corresponding nodes include: Obtain the preset handler for the node corresponding to the approval task; The final processor is obtained by recursively searching through the sub-authorization records of the preset processor; the sub-authorization records represent the configuration information of the approver transferring approval authority to other personnel; the recursive search extracts the authorized persons level by level along the sub-authorization chain until there are no valid sub-authorization records for the authorized persons. The approval task is assigned to the final processor.

7. The method for approving transaction information according to claim 5, characterized in that, The step of determining the target approval process based on the matching results includes: Determine whether the matching result indicates that an approval process needs to be executed; If the matching result indicates that no approval is required, then the transaction status corresponding to the approval request is marked as completed. If the matching result indicates that approval is required, the process identifier associated with the matching result is extracted, and the target approval process is determined based on the process identifier.

8. An approval data configuration device, characterized in that, include: Configure the acquisition module to obtain approval data; The approval data includes at least multiple first nodes; The first node represents information about the processing steps in the approval process; The transaction acquisition module is used to acquire transaction data; the transaction data includes multiple transaction attributes. The instance creation module is used to create process instances based on the approval data and the transaction data; The process instance is configured with associated nodes, which represent the correspondence between the transaction attributes and the corresponding nodes in the approval process; The process instance is used to respond to an approval request, trigger the corresponding associated node based on the transaction information indicated in the approval request to obtain the target approval process, so as to transfer to the target approval process.

9. A transaction information approval device, characterized in that, include: The instance acquisition module is used to obtain process instances; The process instance is created based on the approval data configuration method as described in any one of claims 1-4; The instance deployment module is used to deploy the process instance to the process engine; The process engine is used to generate executable approval processes based on process instances; The attribute extraction module is used to extract the target transaction attributes from the transaction information indicated in the approval request in response to the approval request. The process matching module is used to match the target transaction attributes based on the associated nodes configured in the process instance in order to determine the target approval process; The instance creation module is used to create an execution instance corresponding to the target approval process based on the process engine; the execution instance is used to generate approval tasks sequentially according to the node order in the target approval process. The task allocation module is used to assign the approval tasks to the corresponding personnel at the corresponding nodes to complete the approval process.

10. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

11. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

12. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images