Examination and approval processing method and device, equipment, medium and product

By obtaining the list of rule expressions and callback functions in financial transactions and dynamically matching the target approval flow, the problem of inaccurate approval process in complex transaction scenarios is solved, and more efficient approval processing and risk prevention are achieved.

CN120672293APending Publication Date: 2025-09-19INDUSTRIAL AND COMMERCIAL BANK OF CHINA +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510872007.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-06-26
Publication Date
2025-09-19

AI Technical Summary

Technical Problem

Existing technologies are unable to accurately match corresponding approval processes in complex financial transaction scenarios, resulting in inaccurate approval processing.

Method used

By obtaining the rule expression list and callback function of the business type to be approved, the target approval flow is dynamically matched, and approval is performed according to the approval flow corresponding to the rule expression that successfully matches the business element value.

Benefits of technology

It improves the accuracy of approval processing, ensures that the corresponding approval flow is selected for approval according to different business types, and enhances the ability to prevent transaction risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120672293A_ABST
    Figure CN120672293A_ABST
Patent Text Reader

Abstract

The invention provides an approval processing method and device, equipment, a medium and a product, and relates to the field of financial science and technology or other related fields. The method comprises the steps of obtaining a rule expression list and a callback function corresponding to a to-be-approved business type in response to an approval instruction; the approval instruction comprises a serial number of a to-be-approved business type; each rule expression in the rule expression list corresponds to one approval flow; calling a callback function, and obtaining the value of each business element under the approval instruction; and adding the values of the business elements to the business elements corresponding to the rule expressions, taking the approval flow corresponding to the successfully matched rule expressions as a target approval flow corresponding to the approval instruction, and performing approval according to the target approval flow. According to the scheme, the accuracy of approval processing is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of financial technology or other related fields, and in particular to an approval processing method, device, equipment, medium and product. Background Art

[0002] The number of transaction scenarios involving dynamic matching of approval flows in the application system has increased, and different approval processes need to be matched according to different transaction scenarios to facilitate efficient prevention of transaction risks.

[0003] Currently, some solutions set up several corresponding approval processes based on different transaction scenario rules. However, due to the complexity of transaction scenarios in the financial system, the current solutions are unable to match the corresponding accurate approval processes for complex business scenarios. Summary of the Invention

[0004] This application provides an approval processing method, device, equipment, medium and product to improve the accuracy of approval processing.

[0005] In the first aspect, the present application provides an approval processing method, including: in response to an approval instruction, obtaining a list of rule expressions and a callback function corresponding to the business type to be approved; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; calling the callback function to obtain the value of each business element under the approval instruction; adding the value of the business element to each business element corresponding to each rule expression, and using the approval flow corresponding to the successfully matched rule expression as the target approval flow corresponding to the approval instruction, and approving according to the target approval flow.

[0006] In the second aspect, the present application provides an approval processing device, including: an acquisition module, used to respond to an approval instruction, obtain a list of rule expressions and a callback function corresponding to the business type to be approved; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; a calling module, used to call the callback function to obtain the value of each business element under the approval instruction; a processing module, used to add the value of the business element to each business element corresponding to each rule expression, and use the approval flow corresponding to the successfully matched rule expression as the target approval flow corresponding to the approval instruction, and perform approval according to the target approval flow.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor;

[0008] The memory stores computer-executable instructions;

[0009] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0010] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementation methods of the first aspect.

[0011] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0012] The approval processing method, apparatus, device, medium and product provided by the present application, in response to an approval instruction, obtains a list of rule expressions and a callback function corresponding to the business type to be approved contained in the approval instruction; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; the callback function is called to obtain the value of each business element under the approval instruction; the value of the business element is added to each business element corresponding to each rule expression, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow corresponding to the approval instruction, and approval is performed according to the target approval flow. The solution of the present application matches each rule expression in the rule list according to the business element value of the business type to be approved returned by the callback function, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow of the corresponding business to be approved, so that the corresponding approval flow can be accurately selected for the business class to be approved for approval, thereby improving the accuracy of the approval processing of the business. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0014] Figure 1 A flowchart illustrating an approval process is shown as an example;

[0015] Figure 2 A flowchart illustrating an approval process is shown as an example;

[0016] Figure 3 A flowchart illustrating an approval process is shown as an example;

[0017] Figure 4 The following is a schematic diagram showing the structure of an approval processing device;

[0018] Figure 5 Schematic diagram of the structure of an electronic device is shown in FIG.

[0019] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0020] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0021] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0022] In addition, this application involves conducting big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and using artificial intelligence technology to make automated decisions, and making technical solutions that have a significant impact on personal rights and interests based on the results of automated decisions. The application provides users with corresponding operation entrances for them to choose to agree or reject the results of automated decisions; if the user chooses to reject, the expert decision-making process will be entered.

[0023] It should be noted that the approval processing methods, devices, equipment, media and products provided in this application can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The application fields of the regional economic health risk assessment methods, devices, equipment, media and products provided in this application are not limited.

[0024] The number of transaction scenarios involving dynamic matching of approval flows in the application system has increased, and different approval processes need to be matched according to different transaction scenarios to facilitate efficient prevention of transaction risks.

[0025] Currently, some solutions set up several corresponding approval processes based on different transaction scenario rules. However, due to the complexity of transaction scenarios in the financial system, the current solutions are unable to match the corresponding accurate approval processes for complex business scenarios.

[0026] The approval processing method, device, equipment, medium and product provided by the present application are intended to solve the above technical problems of the prior art. The approval processing method, device, equipment, medium and product provided by the present application, in response to the approval instruction, obtains the rule expression list and callback function corresponding to the business type to be approved contained in the approval instruction; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; the callback function is called to obtain the value of each business element under the approval instruction; the value of the business element is added to each business element corresponding to each rule expression, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow corresponding to the approval instruction, and approval is performed according to the target approval flow. The scheme of the present application matches each rule expression in the rule list according to the business element value of the business type to be approved returned by the callback function, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow of the corresponding business to be approved, so that the corresponding approval flow can be accurately selected for the business class to be approved for approval, thereby improving the accuracy of the approval processing of the business.

[0027] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0028] Example 1

[0029] Figure 1 The following is a flowchart illustrating an approval process method:

[0030] Step 101: In response to an approval instruction, a list of rule expressions corresponding to the business type to be approved and a callback function are obtained; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow;

[0031] Step 102: Call the callback function to obtain the value of each business element under the approval instruction;

[0032] Step 103: Add the value of the business element to each business element corresponding to each rule expression, use the approval flow corresponding to the successfully matched rule expression as the target approval flow corresponding to the approval instruction, and perform approval according to the target approval flow.

[0033] Specifically, business types include business scenario types, transaction types, and financial product types; for example, financial products include income-based financial products and pension-based financial products. Each business type corresponds to a specific business rule, such as a transaction amount greater than or less than 100,000 yuan, and a transaction risk level of one, two, or three. Each business rule corresponds to a rule expression, and a business type includes rule expressions under multiple business rules. Each rule expression corresponds to an approval flow. In actual applications, when it is necessary to approve multiple business rules or one business rule under a certain business type, the list of rule expressions corresponding to the business type to be approved and the callback function corresponding to the business type are obtained in response to the approval instruction. The rule expression list and callback function of each business type are directly preset according to each business rule. The approval instruction includes the number corresponding to the business type to be approved, and the rule list and callback function corresponding to the business type to be approved can be obtained according to the number. The callback function retrieved is called, and the callback function is used to retrieve the values ​​of each business element in the approval instruction. The retrieved values ​​of each business element are added to the business elements corresponding to each rule expression. The approval flow corresponding to the successfully matched rule expression is used as the target approval flow for the business type in the approval instruction. Subsequently, approval is performed according to the target approval flow. In this example, based on the obtained business element values ​​corresponding to the business type to be approved, the business element values ​​are entered into the preset rule expression, and the matched approval flow is used as the target approval flow. This allows dynamic matching of the corresponding approval flow for business rules under different business types, improving the accuracy of business approvals.

[0034] Optional, Figure 2 A flowchart of an approval processing method is exemplified; the method further includes:

[0035] Step 201: Generate a rule expression list for each service type in response to a configuration rule instruction; the configuration rule instruction includes a service element name corresponding to each service type and a preset value corresponding to each service element name;

[0036] Step 202: According to the rule expression list of each business type and based on the approval flow list of each business type, configure the approval flow corresponding to each rule expression in the rule expression list.

[0037] Specifically, before approving the actual business, it is necessary to configure the rule expression list corresponding to each business type; in response to the rule configuration instruction, generate the rule expression list for each business type; wherein, the configuration rule instruction includes the business element name corresponding to each business type and the preset value corresponding to each business element name; illustratively, the business element includes element value, operator, element type, etc. In addition, the configuration rule instruction also includes the business type name, business rule name, etc.; the business type information contained in the configuration rule instruction is stored in the log table and log file for subsequent search. The business element name, operator, element value, element type and other fields are processed into expressions and stored, such as amount>100000&&(folder_id=='111'||folder_id=='222'||folder_id=='333'); amount represents the quantity, and folder_id represents the folder name. Each business rule pair is processed into a corresponding expression, generating a list of rule expressions corresponding to the business type. Based on the rule expression list for each business type and the approval flow list for each business type, a corresponding approval flow can be configured for each rule expression in the rule expression list corresponding to each business type. In this example, by generating a rule expression list in response to rule configuration instructions, and then configuring a corresponding workflow for each rule expression based on the rule expression list and the approval flow list, the accuracy of subsequent business approvals is improved.

[0038] Optionally, in response to the configuration rule instruction, a list of rule expressions for each service type is generated, including:

[0039] Customize various combinations of business elements of each business type based on the business element names and values ​​corresponding to each business element name;

[0040] Generate a regular expression corresponding to each combination relationship of each business type based on the multiple combination relationships between the business elements of each business type;

[0041] Generate a list of rule expressions for each service type based on the rule expressions corresponding to each combination relationship of each service type.

[0042] Specifically, in response to a rule configuration instruction, based on the information about each business element in the rule configuration instruction, including the business element names corresponding to each business type and the actual values ​​corresponding to each business element name, you can customize rules and various combinations of relationships between business elements. Based on these combinations of relationships between business elements in each business type, a rule expression corresponding to each combination of relationships is generated. For example, a rule expression is generated for the combination of a business element with an amount greater than 100,000 and a risk level of three; a rule expression is generated for the combination of a business element with an amount less than 100,000 and a risk level of two. Each rule expression corresponds to an approval flow. In addition, various other business elements and combinations between business elements are included, which are not listed here. Based on the rule expression corresponding to each combination of relationships for each business type, a rule expression list for that business type is generated. In this example, by defining each business element and the combinations between them, multiple rule expressions corresponding to business rules are generated. This ensures that, during the actual approval process, the rule expression list corresponding to each business type covers the business rules corresponding to the business type to be approved, allowing the correct approval flow to be selected for approval, thereby improving the accuracy of the approval process.

[0043] Optional, Figure 3 A flowchart of an approval processing method is exemplified; the method further includes:

[0044] Step 301: Acquire approval flow management data for each business type; the approval flow management data includes approval flow name, approval flow type, node name, and node approval role;

[0045] Step 302: Generate a list of approval flow configuration files for each business type based on the approval flow management data for each business type;

[0046] Step 303: Based on the approval flow configuration file list of each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the approval flow configuration file list of each business type.

[0047] Specifically, the approval flow management data of the business type is obtained; wherein, the approval flow management data includes the name of the approval flow, the approval flow type, the node name, and the node approval role, etc. Exemplarily, the approval flow management data can be stored in the log table and the log file. Based on the approval flow management data of each business type, a list of approval flow configuration files for each business type is generated; exemplarily, for the approval flow management data corresponding to a rule expression, an XML format configuration file is generated based on the approval flow management data such as the workflow name, workflow type, node name, and node approval role. Based on the list of approval flow configuration files for each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the list of approval flow configuration files for each business type. In this example, by generating the corresponding configuration file based on the obtained approval flow management data, and then calling the approval flow engine to generate the approval flow corresponding to each approval flow configuration file in the list of approval flow configuration files, the accuracy of the generated approval flow is improved.

[0048] Optionally, based on the approval flow management data of each business type, generate a list of approval flow configuration files for each business type, including:

[0049] Customize multiple combinations of approval flow management data for each business type based on the approval flow management data for each business type;

[0050] Generate a workflow configuration file corresponding to each combination relationship between the approval flow management data of each business type based on the multiple combination relationships between the approval flow management data of each business type;

[0051] According to the workflow configuration files corresponding to each combination relationship between the approval flow management data of each business type, a list of approval flow configuration files of each business type is generated.

[0052] Specifically, based on the acquired approval flow management data for each business type, the approval flow management data corresponding to each business type and the various combination relationships between the approval flow management data are customized. Exemplarily, the approval nodes are defined as three or five, and the approvers are defined as group leaders, supervisors, and managers. Based on the various combination relationships between the approval flow management data for different business types, a workflow configuration file corresponding to each combination relationship between the approval flow management data for each business type is generated. Afterwards, based on the workflow configuration file corresponding to each combination relationship between the approval flow management data for each business type, a list of approval flow configuration files for each business type is generated. In this example, by defining the approval flow management data for each business type and the combination relationship between the approval flow management data, an approval flow configuration file corresponding to each combination is generated, and based on the approval flow configuration files corresponding to the various combinations, a list of approval flow configuration files is generated, thereby improving the accuracy of generating the list of approval flow configuration files.

[0053] Optionally, the approval flow includes a main flow and sub-flows. Based on the approval flow configuration file list for each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the approval flow configuration file list for each business type, including:

[0054] If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the main process, it is determined whether the approval flow configuration file of the main process needs to be associated with the approval flow configuration file of the sub-process. If association is required, the approval flow engine is called to generate the approval flow corresponding to the main process approval flow configuration file and the associated approval flow configuration file of the sub-process;

[0055] If no association is required, the approval flow engine is called to generate the approval flow corresponding to the approval flow configuration file of the main process.

[0056] Specifically, the approval flow includes a main process and a sub-process; among which, the sub-process is a risk control process. According to the business rules of the business to be approved, it can be determined whether the risk control sub-process is enabled. When the approval flow profile in the approval flow profile list of the business type is the approval flow profile of the main process, it is further determined whether the approval flow profile of the main process needs to be associated with the approval flow profile of the sub-process. If association is required, the approval flow engine is called to generate the approval flow corresponding to the main process approval flow profile and the associated sub-process approval flow profile. If association is not required, the approval flow engine is directly called to generate the approval flow corresponding to the main process approval flow profile. In this example, by further determining whether the approval flow is the approval flow profile of the main process, it is determined whether the approval flow profile of the sub-process needs to be associated. If association is required, the approval flow corresponding to the main process and the sub-process approval flow profile is generated. If not, the approval flow corresponding to the approval flow profile of the main process is generated, thereby improving the accuracy of approval flow generation.

[0057] Optionally, the method further includes:

[0058] If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the sub-process, the approval flow engine will be stopped from being called.

[0059] Specifically, if the approval flow configuration file in the business type's approval flow configuration file is a sub-process approval flow configuration file, the approval flow engine will not be called to generate the sub-process approval flow. For example, when the approval flow configuration file is a sub-process, the sub-process approval flow will not be generated. Instead, the sub-process approval flow configuration file can be associated with the corresponding main process's approval flow configuration file list, and the approval flow engine will be called to generate the corresponding approval flow, thereby improving the accuracy and efficiency of approval flow generation.

[0060] Optionally, the method further includes:

[0061] Visualize the rule expression list, approval flow list, and approval process.

[0062] Specifically, the rule expression list, approval flow list, and complete approval process generated above are visualized. This makes it easier for operations and maintenance personnel to search for the approval process, rule expression list, and approval flow list, improving the accuracy of the approval process.

[0063] Optionally, the method further includes:

[0064] If the approval instruction includes a risk flag, the risk control approval flow sub-process is enabled.

[0065] Specifically, when an approval instruction (i.e., the type of business to be approved) includes a risk indicator, the risk control approval flow sub-process needs to be activated. For example, when a business requiring approval includes a risk indicator, a risk control sub-process needs to be added, such as adding a risk control department approval process and the corresponding approver. In this example, when an approval instruction carries a risk indicator, the risk control approval flow sub-process is activated, further improving the accuracy of the approval process.

[0066] In the approval processing method provided by this embodiment, in response to an approval instruction, a list of rule expressions and a callback function corresponding to the business type to be approved contained in the approval instruction are obtained; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; the callback function is called to obtain the value of each business element under the approval instruction; the value of the business element is added to each business element corresponding to each rule expression, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow corresponding to the approval instruction, and approval is performed according to the target approval flow. The solution of the present application matches each rule expression in the rule list according to the business element value of the business type to be approved returned by the callback function, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow of the corresponding business to be approved, so that the corresponding approval flow can be accurately selected for the business class to be approved for approval, thereby improving the accuracy of the approval processing of the business.

[0067] Example 2

[0068] Figure 4 The following is a schematic diagram showing the structure of an approval processing device; it includes:

[0069] An acquisition module 21 is configured to obtain a list of rule expressions and a callback function corresponding to the business type to be approved in response to an approval instruction; the approval instruction includes the number of the business type to be approved; and each rule expression in the rule expression list corresponds to an approval flow;

[0070] The calling module 22 is used to call the callback function to obtain the value of each business element under the approval instruction;

[0071] The processing module 23 is used to add the value of the business element to each business element corresponding to each rule expression, use the approval flow corresponding to the successfully matched rule expression as the target approval flow corresponding to the approval instruction, and perform approval according to the target approval flow.

[0072] Specifically, business types include business scenario types, transaction types, and financial product types; for example, financial products include income-based financial products and pension-based financial products. Each business type corresponds to a specific business rule, such as a transaction amount greater than or less than 100,000 yuan, and a transaction risk level of one, two, or three. Each business rule corresponds to a rule expression, and a business type includes rule expressions under multiple business rules. Each rule expression corresponds to an approval flow. In actual applications, when it is necessary to approve multiple business rules or one business rule under a certain business type, the list of rule expressions corresponding to the business type to be approved and the callback function corresponding to the business type are obtained in response to the approval instruction. The rule expression list and callback function of each business type are directly preset according to each business rule. The approval instruction includes the number corresponding to the business type to be approved, and the rule list and callback function corresponding to the business type to be approved can be obtained according to the number. The callback function retrieved is called, and the callback function is used to retrieve the values ​​of each business element in the approval instruction. The retrieved values ​​of each business element are added to the business elements corresponding to each rule expression. The approval flow corresponding to the successfully matched rule expression is used as the target approval flow for the business type in the approval instruction. Subsequently, approval is performed according to the target approval flow. In this example, based on the obtained business element values ​​corresponding to the business type to be approved, the business element values ​​are entered into the preset rule expression, and the matched approval flow is used as the target approval flow. This allows dynamic matching of the corresponding approval flow for business rules under different business types, improving the accuracy of business approvals.

[0073] Optionally, the device further includes: a generating module 24, the generating module 24 is configured to:

[0074] In response to the configuration rule instruction, a rule expression list for each business type is generated; the configuration rule instruction includes a business element name corresponding to each business type and a preset value corresponding to each business element name;

[0075] According to the rule expression list of each business type and the approval flow list of each business type, configure the approval flow corresponding to each rule expression in the rule expression list.

[0076] Specifically, before approving the actual business, it is necessary to configure the rule expression list corresponding to each business type; in response to the rule configuration instruction, generate the rule expression list for each business type; wherein, the configuration rule instruction includes the business element name corresponding to each business type and the preset value corresponding to each business element name; illustratively, the business element includes element value, operator, element type, etc. In addition, the configuration rule instruction also includes the business type name, business rule name, etc.; the business type information contained in the configuration rule instruction is stored in the log table and log file for subsequent search. The business element name, operator, element value, element type and other fields are processed into expressions and stored, such as amount>100000&&(folder_id=='111'||folder_id=='222'||folder_id=='333'); amount represents the quantity, and folder_id represents the folder name. Each business rule pair is processed into a corresponding expression, generating a list of rule expressions corresponding to the business type. Based on the rule expression list for each business type and the approval flow list for each business type, a corresponding approval flow can be configured for each rule expression in the rule expression list corresponding to each business type. In this example, by generating a rule expression list in response to rule configuration instructions, and then configuring a corresponding workflow for each rule expression based on the rule expression list and the approval flow list, the accuracy of subsequent business approvals is improved.

[0077] Optionally, the generating module 24 is used to:

[0078] Customize various combinations of business elements of each business type based on the business element names and values ​​corresponding to each business element name;

[0079] Generate a regular expression corresponding to each combination relationship of each business type based on the multiple combination relationships between the business elements of each business type;

[0080] Generate a list of rule expressions for each service type based on the rule expressions corresponding to each combination relationship of each service type.

[0081] Specifically, in response to a rule configuration instruction, based on the information about each business element in the rule configuration instruction, including the business element names corresponding to each business type and the actual values ​​corresponding to each business element name, you can customize rules and various combinations of relationships between business elements. Based on these combinations of relationships between business elements in each business type, a rule expression corresponding to each combination of relationships is generated. For example, a rule expression is generated for the combination of a business element with an amount greater than 100,000 and a risk level of three; a rule expression is generated for the combination of a business element with an amount less than 100,000 and a risk level of two. Each rule expression corresponds to an approval flow. In addition, various other business elements and combinations between business elements are included, which are not listed here. Based on the rule expression corresponding to each combination of relationships for each business type, a rule expression list for that business type is generated. In this example, by defining each business element and the combinations between them, multiple rule expressions corresponding to business rules are generated. This ensures that, during the actual approval process, the rule expression list corresponding to each business type covers the business rules corresponding to the business type to be approved, allowing the correct approval flow to be selected for approval, thereby improving the accuracy of the approval process.

[0082] Optionally, the device further includes a configuration module 25, which is configured to:

[0083] Obtain approval flow management data for each business type; approval flow management data includes approval flow name, approval flow type, node name, and node approval role;

[0084] Generate a list of approval flow configuration files for each business type based on the approval flow management data for each business type;

[0085] According to the approval flow configuration file list of each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the approval flow configuration file list of each business type.

[0086] Specifically, the approval flow management data of the business type is obtained; wherein, the approval flow management data includes the name of the approval flow, the approval flow type, the node name, and the node approval role, etc. Exemplarily, the approval flow management data can be stored in the log table and the log file. Based on the approval flow management data of each business type, a list of approval flow configuration files for each business type is generated; exemplarily, for the approval flow management data corresponding to a rule expression, an XML format configuration file is generated based on the approval flow management data such as the workflow name, workflow type, node name, and node approval role. Based on the list of approval flow configuration files for each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the list of approval flow configuration files for each business type. In this example, by generating the corresponding configuration file based on the obtained approval flow management data, and then calling the approval flow engine to generate the approval flow corresponding to each approval flow configuration file in the list of approval flow configuration files, the accuracy of the generated approval flow is improved.

[0087] Optionally, the configuration module 25 is used to:

[0088] Customize multiple combinations of approval flow management data for each business type based on the approval flow management data for each business type;

[0089] Generate a workflow configuration file corresponding to each combination relationship between the approval flow management data of each business type based on the multiple combination relationships between the approval flow management data of each business type;

[0090] According to the workflow configuration files corresponding to each combination relationship between the approval flow management data of each business type, a list of approval flow configuration files of each business type is generated.

[0091] Specifically, based on the acquired approval flow management data for each business type, the approval flow management data corresponding to each business type and the various combination relationships between the approval flow management data are customized. Exemplarily, the approval nodes are defined as three or five, and the approvers are defined as group leaders, supervisors, and managers. Based on the various combination relationships between the approval flow management data for different business types, a workflow configuration file corresponding to each combination relationship between the approval flow management data for each business type is generated. Afterwards, based on the workflow configuration file corresponding to each combination relationship between the approval flow management data for each business type, a list of approval flow configuration files for each business type is generated. In this example, by defining the approval flow management data for each business type and the combination relationship between the approval flow management data, an approval flow configuration file corresponding to each combination is generated, and based on the approval flow configuration files corresponding to the various combinations, a list of approval flow configuration files is generated, thereby improving the accuracy of generating the list of approval flow configuration files.

[0092] Optionally, the approval process includes a main process and a sub-process; the configuration module 25 is used to:

[0093] If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the main process, it is determined whether the approval flow configuration file of the main process needs to be associated with the approval flow configuration file of the sub-process. If association is required, the approval flow engine is called to generate the approval flow corresponding to the main process approval flow configuration file and the associated approval flow configuration file of the sub-process;

[0094] If no association is required, the approval flow engine is called to generate the approval flow corresponding to the approval flow configuration file of the main process.

[0095] Specifically, the approval flow includes a main process and a sub-process; among which, the sub-process is a risk control process. According to the business rules of the business to be approved, it can be determined whether the risk control sub-process is enabled. When the approval flow profile in the approval flow profile list of the business type is the approval flow profile of the main process, it is further determined whether the approval flow profile of the main process needs to be associated with the approval flow profile of the sub-process. If association is required, the approval flow engine is called to generate the approval flow corresponding to the main process approval flow profile and the associated sub-process approval flow profile. If association is not required, the approval flow engine is directly called to generate the approval flow corresponding to the main process approval flow profile. In this example, by further determining whether the approval flow is the approval flow profile of the main process, it is determined whether the approval flow profile of the sub-process needs to be associated. If association is required, the approval flow corresponding to the main process and the sub-process approval flow profile is generated. If not, the approval flow corresponding to the approval flow profile of the main process is generated, thereby improving the accuracy of approval flow generation.

[0096] Optionally, the device further includes a deactivation module 26, which is configured to:

[0097] If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the sub-process, the approval flow engine will be stopped from being called.

[0098] Specifically, if the approval flow configuration file in the business type's approval flow configuration file is a sub-process approval flow configuration file, the approval flow engine will not be called to generate the sub-process approval flow. For example, when the approval flow configuration file is a sub-process, the sub-process approval flow will not be generated. Instead, the sub-process approval flow configuration file can be associated with the corresponding main process's approval flow configuration file list, and the approval flow engine will be called to generate the corresponding approval flow, thereby improving the accuracy and efficiency of approval flow generation.

[0099] Optionally, the device further includes a visualization module 27, which is configured to:

[0100] Visualize the rule expression list, approval flow list, and approval process.

[0101] Specifically, the rule expression list, approval flow list, and complete approval process generated above are visualized. This makes it easier for operations and maintenance personnel to search for the approval process, rule expression list, and approval flow list, improving the accuracy of the approval process.

[0102] Optionally, the device further includes an activation module 28, which is configured to:

[0103] If the approval instruction includes a risk flag, the risk control approval flow sub-process is enabled.

[0104] Specifically, when an approval instruction (i.e., the type of business to be approved) includes a risk indicator, the risk control approval flow sub-process needs to be activated. For example, when a business requiring approval includes a risk indicator, a risk control sub-process needs to be added, such as adding a risk control department approval process and the corresponding approver. In this example, when an approval instruction carries a risk indicator, the risk control approval flow sub-process is activated, further improving the accuracy of the approval process.

[0105] The approval processing device provided in this embodiment responds to an approval instruction, obtains a list of rule expressions and a callback function corresponding to the business type to be approved contained in the approval instruction; the approval instruction includes the number of the business type to be approved; each rule expression in the rule expression list corresponds to an approval flow; the callback function is called to obtain the value of each business element under the approval instruction; the value of the business element is added to each business element corresponding to each rule expression, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow corresponding to the approval instruction, and approval is performed according to the target approval flow. The solution of the present application matches each rule expression in the rule list according to the business element value of the business type to be approved returned by the callback function, and the approval flow corresponding to the successfully matched rule expression is used as the target approval flow of the corresponding business to be approved, so that the corresponding approval flow can be accurately selected for the business class to be approved for approval, thereby improving the accuracy of the approval processing of the business.

[0106] Example 3

[0107] Figure 5 exemplarily shows a structural diagram of an electronic device, the device comprising:

[0108] The device includes a processor 291 and memory 292; a communication interface 293, and a bus 294. The processor 291, memory 292, and communication interface 293 can communicate with each other via bus 294. Communication interface 293 can be used for information transmission. Processor 291 can invoke logic instructions in memory 292 to execute the above-described method.

[0109] In addition, the logic instructions in the memory 292 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

[0110] Memory 292, as a computer-readable storage medium, can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present application. Processor 291 executes the software programs, instructions, and modules stored in memory 292 to execute functional applications and data processing, thereby implementing the methods in the above-mentioned method examples.

[0111] Memory 292 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data generated based on the use of the terminal device. Memory 292 may also include high-speed random access memory and non-volatile memory.

[0112] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method in any embodiment.

[0113] An embodiment of the present application further provides a computer program product, including a computer program, which is used to implement the method in any embodiment when executed by a processor.

[0114] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0115] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0116] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0117] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0118] If an integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0119] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk, or optical disk, etc., various media that can store program code.

[0120] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined in any way. To keep the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0121] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0122] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. An approval processing method, characterized in that: include: In response to an approval instruction, a list of rule expressions corresponding to the business type to be approved and a callback function are obtained; the approval instruction includes the number of the business type to be approved; each rule expression in the list of rule expressions corresponds to an approval flow; Calling the callback function to obtain the value of each business element under the approval instruction; The value of the business element is added to each business element corresponding to each rule expression, the approval flow corresponding to the successfully matched rule expression is used as the target approval flow corresponding to the approval instruction, and approval is performed according to the target approval flow.

2. The method according to claim 1, characterized in that The method further comprises: In response to the configuration rule instruction, a rule expression list for each business type is generated; the configuration rule instruction includes a business element name corresponding to each business type and a preset value corresponding to each business element name; According to the rule expression list of each business type and based on the approval flow list of each business type, the approval flow corresponding to each rule expression in the rule expression list is configured.

3. The method according to claim 2, characterized in that The generating of a list of rule expressions for each service type in response to the configuration rule instruction includes: Customize multiple combination relationships between the business elements of each business type according to the business element names corresponding to the business types and the values ​​corresponding to the business element names; Generate a regular expression corresponding to each combination relationship of each business type according to the multiple combination relationships between the business elements of each business type; A list of regular expressions for each service type is generated according to the regular expressions corresponding to each combination relationship of each service type.

4. The method according to claim 1, wherein The method further comprises: Acquire approval flow management data for each business type; the approval flow management data includes approval flow name, approval flow type, node name, and node approval role; Generate a list of approval flow configuration files for each business type based on the approval flow management data for each business type; According to the approval flow configuration file list of each business type, the approval flow engine is called to generate the approval flow corresponding to each approval flow configuration file in the approval flow configuration file list of each business type.

5. The method according to claim 4, characterized in that The generation of a list of approval flow configuration files for each business type based on the approval flow management data for each business type includes: Customize multiple combination relationships between the approval flow management data of each business type based on the approval flow management data of each business type; generating a workflow configuration file corresponding to each combination relationship between the approval flow management data of each business type according to the multiple combination relationships between the approval flow management data of each business type; A list of approval flow configuration files for each business type is generated according to the workflow configuration files corresponding to each combination relationship between the approval flow management data for each business type.

6. The method according to claim 4, characterized in that The approval flow includes a main flow and a sub-flow; the approval flow engine is called according to the approval flow configuration file list of each business type to generate the approval flow corresponding to each approval flow configuration file in the approval flow configuration file list of each business type, including: If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the main process, determine whether the approval flow configuration file of the process needs to be associated with the approval flow configuration file of the sub-process; if so, call the approval flow engine to generate the approval flow corresponding to the main process approval flow configuration file and the associated sub-process approval flow configuration file; If no association is required, the approval flow engine is called to generate the approval flow corresponding to the main process approval flow configuration file.

7. The method according to claim 6, characterized in that The method further comprises: If the approval flow configuration file in the approval flow configuration file list of each business type is the approval flow configuration file of the sub-process, the approval flow engine is stopped from being called.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The rule expression list, the approval flow list and the approval process are visually displayed.

9. The method according to any one of claims 1 to 7, characterized in that The method further comprises: If the approval instruction includes a risk flag, the risk control approval flow sub-process is activated.

10. An approval processing device, characterized in that: include: An acquisition module, configured to acquire, in response to an approval instruction, a list of rule expressions corresponding to the business type to be approved and a callback function; the approval instruction includes a serial number of the business type to be approved; and each rule expression in the list of rule expressions corresponds to an approval flow; A calling module, configured to call the callback function and obtain the value of each business element under the approval instruction; The processing module is used to add the value of the business element to each business element corresponding to each rule expression, use the approval flow corresponding to the successfully matched rule expression as the target approval flow corresponding to the approval instruction, and perform approval according to the target approval flow.

11. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 9 when executed by a processor.

13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 9 when being executed by a processor.