Business data processing method and device based on workflow and server

Abstract

The invention provides a business data processing method and device based on workflow and a server, which can be used in the financial field. Obtaining target business data required for executing the target business; through interaction with a workflow system, creating and executing a target workflow corresponding to the target business, so as to process the target business data; if the target node of which the target node task execution fails exists in the target workflow, obtaining target node task execution information of the target node; determining a failure type of task execution failure of the target node; and under the condition that the failure frequency of the execution failure type of the target node task in the target workflow is determined to be greater than a preset frequency threshold value, interacting with a workflow system by utilizing target node task execution information, and adjusting a node responsible for the target node task and / or a task processing rule of the target node task. And continuing to process the target business data. Therefore, the efficiency and accuracy of node task scheduling execution are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a workflow-based business data processing method, device and server. Background Art

[0002] Although task scheduling systems are currently used in many scenarios, they are still difficult to manage due to their high reliance on complexity. When task scheduling fails, the entire workflow will be rescheduled, causing the node task scheduling system to have complexity and high error rate.

[0003] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0004] The present specification provides a workflow-based business data processing method, device and server, which avoids the problem of low task scheduling execution efficiency caused by multiple adjustments to the target workflow when the number of node failures of the execution failure type is small, and can improve the efficiency of node task scheduling execution. In addition, by interacting with the workflow system, the task processing rules of the nodes responsible for the target node tasks and / or the target node tasks can be accurately adjusted, thereby improving the accuracy of node task scheduling execution.

[0005] This specification provides a workflow-based business data processing method, which is applied to a node server of a task scheduling system, wherein the task scheduling system is associated with a workflow system, and the method includes:

[0006] Receive trigger execution instructions for target business;

[0007] In response to the trigger execution instruction, the target business data required for executing the target business is acquired; by interacting with the workflow system, a target workflow corresponding to the target business is created and executed to process the target business data; wherein the target workflow includes a plurality of node tasks;

[0008] According to the target workflow, monitoring the processing process of the target business data, if there is a node in the target workflow where the target node task execution fails, acquiring the execution information of the target node task;

[0009] Determine the failure type of the target node task execution failure according to the execution information of the target node task; and accumulate the number of failures of the execution failure type of the target node task in the target workflow;

[0010] Detecting whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold;

[0011] When it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining an adjusted target workflow;

[0012] Based on the adjusted target workflow, the target business data continues to be processed.

[0013] In one embodiment, the using the execution information of the target node task to interact with the workflow system and adjusting the node responsible for the target node task and / or the task processing rule of the target node task before adjusting the target workflow further includes:

[0014] Determine the failure reason leading to the failure of the execution of the target node task in the target workflow and the related reason type according to the execution information of the target node task; wherein the reason type includes temporary type or permanent type;

[0015] Generate a failure analysis report on the failure of executing the target node task in the target workflow according to the failure reason and the related reason type;

[0016] The failure analysis report is sent to the workflow system; wherein the workflow system determines whether to adjust the target workflow according to the failure analysis report.

[0017] In one embodiment, the method further comprises:

[0018] In the case of determining to adjust the target workflow, interacting with the workflow system to obtain the attribute information of the target business data and the task attributes of the target node task, and determining the node attributes of the associated node of the neighboring node task responsible for the target node task;

[0019] Determining a target adjustment strategy for the target workflow according to the attribute information of the target business data, the task attributes of the target node task, and the node attributes of the associated node;

[0020] According to the target adjustment strategy, the target workflow is adjusted by adjusting the node responsible for the target node task and / or the task processing rule of the target node task to obtain the adjusted target workflow;

[0021] The adjusted target workflow is fed back to the node server of the task scheduling system.

[0022] In one embodiment, when the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow, including:

[0023] Based on the adjusted target workflow, a restart start task is determined from neighboring node tasks of the target node task; and a plurality of consensus nodes are determined from nodes other than the target node that are responsible for node tasks in the target workflow;

[0024] Combining the multiple consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group to replace the target node;

[0025] The task processing record of the target workflow is queried to obtain task processing data for the restart start task; and the task processing data is sent to a node responsible for the restart start task to continue processing the target business data.

[0026] In one embodiment, after combining the plurality of consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group, the method further includes:

[0027] Generating notification information about using the target consensus node to replace the target node;

[0028] Sending the notification information to the target node;

[0029] Detecting whether a rejection instruction of the target node for the notification information is received within a preset tolerance time;

[0030] In the case where no rejection instruction is received from the target node for the notification information within the preset tolerance time, the target consensus node group is used to replace the target node.

[0031] In one embodiment, the continuing to process the target service data includes:

[0032] Acquire task processing data for the target node task;

[0033] Distributing the task processing data of the target node task to multiple consensus nodes of the target consensus node group;

[0034] Receive multiple intermediate task processing results fed back by the multiple consensus nodes;

[0035] According to the consensus rules, the plurality of intermediate task processing results are processed to obtain a target task processing result for the target node task;

[0036] The target business data continues to be processed according to the target task processing result and the adjusted target workflow.

[0037] In one embodiment, when the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: temporary, the target service data is continued to be processed based on the adjusted target workflow, including:

[0038] Based on the adjusted target workflow, a restart start task is determined from the neighboring node tasks of the target node task; and a temporary node is determined from the nodes other than the target node that are responsible for the node tasks in the target workflow to replace the target node; wherein the temporary node is set to be valid in the current target workflow;

[0039] Using the temporary node to complete the target processing task, and sending a request to the target node to determine whether to change the current target processing flow;

[0040] In the case where it is determined to change the current target processing flow, the target workflow is adjusted to obtain the adjusted target workflow to continue processing the target business data.

[0041] In one embodiment, when the failure reason is: the task processing rule of the target node task is abnormal, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow, including:

[0042] Based on the adjusted target workflow, determining key nodes in the target workflow;

[0043] Sending the updated task processing rules of the target node task to the key node; wherein the updated task processing rules are obtained by the workflow system adjusting the task processing rules of the target node task according to the target node task execution information;

[0044] When it is determined that a confirmation instruction for the updated task processing rule is received from the key node, the updated task processing rule is configured on the target node to replace the task processing rule of the target node task; and the target business data continues to be processed.

[0045] In one embodiment, the creating a target workflow corresponding to the target business by interacting with the workflow system includes:

[0046] Sending a creation request for the target workflow to the workflow system; wherein the creation request carries at least a service identifier of the target service indicated by the target service data;

[0047] Receive the configuration parameter set of the target workflow fed back by the workflow system; wherein the configuration parameter set of the target workflow at least includes the business execution process information of multiple node tasks in the target workflow, and the task processing rules; the configuration parameter set of the target workflow corresponds to the business identifier of the target business;

[0048] Determine the node responsible for processing the node task in the target workflow according to the business execution process information of the multiple node tasks in the target workflow; and determine the audit authority configuration information of the node;

[0049] The node tasks, the task processing rules, and the audit authority configuration information are configured on corresponding nodes to create the target workflow corresponding to the target business.

[0050] In one embodiment, the determining the audit authority configuration information of the node includes:

[0051] Using a preset authority configuration model, according to the business execution process information corresponding to the node task in the workflow system, the review priority and review content authority information of the node corresponding to the node task are determined; wherein the preset authority configuration model is constructed according to a preset machine learning algorithm;

[0052] The audit authority configuration information of the node corresponding to the node task is determined according to the audit priority and audit content authority information of the node corresponding to the node task.

[0053] In one embodiment, the target service data is data obtained by encryption processing using a preset encryption algorithm;

[0054] Accordingly, the step of acquiring target business data required for executing the target business includes:

[0055] Acquire target business data required for executing the target business, and first verification information corresponding to the target business data;

[0056] Decrypting the target service data to obtain decrypted target service data, and generating second verification information according to the decrypted target service data;

[0057] The first verification information and the second verification information are matched, and if the match is successful, it is determined that the target business data meets the requirements.

[0058] This specification provides a workflow-based business data processing device, including:

[0059] An instruction receiving module, used to receive a trigger execution instruction for a target business;

[0060] An instruction trigger module is used to obtain target business data required for executing the target business in response to the trigger execution instruction; create and execute a target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow includes multiple node tasks;

[0061] An execution information acquisition module, used to monitor the processing process of the target business data according to the target workflow, and if there is a node in the target workflow where the target node task fails to execute, acquire the execution information of the target node task;

[0062] A type determination module, used to determine the failure type of the target node task execution failure according to the execution information of the target node task; and accumulate the number of failures of the execution failure type of the target node task in the target workflow;

[0063] A number determination module is used to detect whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold;

[0064] A workflow adjustment module, for, when it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, to obtain an adjusted target workflow;

[0065] The business processing module is used to continue processing the target business data based on the adjusted target workflow. The specification also provides a server, including a processor and a memory for storing processor executable instructions, and the processor implements a workflow-based business data processing method when executing the instructions.

[0066] The present specification also provides a computer-readable storage medium on which computer instructions are stored, and when the instructions are executed, a workflow-based business data processing method is implemented.

[0067] The present specification also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, a workflow-based business data processing method is implemented.

[0068] A workflow-based business data processing method provided by the present specification is applied to a node server of a task scheduling system, wherein the task scheduling system is associated with a workflow system, and the method comprises: receiving a trigger execution instruction for a target business; in response to the trigger execution instruction, obtaining target business data required for executing the target business; creating and executing a target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow comprises a plurality of node tasks; according to the target workflow, monitoring the processing process of the target business data, and if there is a node in the target workflow where the target node task fails to execute, obtaining the execution information of the target node task; and according to the execution information of the target node task According to the present invention, the target node task of the embodiment of the present invention is a task that fails to execute a task of the target node, and the task of the target node task is executed by the target workflow. The task of the target node task is executed by the target workflow ... On the other hand, when adjusting the target workflow, the task information of the target node can be used to interact with the workflow system to accurately adjust the nodes responsible for the target node tasks and / or the task processing rules of the target node tasks, thereby improving the accuracy of node task scheduling execution. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0070] Figure 1It is a flowchart of a workflow-based business data processing method provided by an embodiment of this specification;

[0071] Figure 2 It is a workflow adjustment process diagram provided by an embodiment of this specification;

[0072] Figure 3 It is a schematic diagram of the structure of an electronic device provided by an embodiment of this specification;

[0073] Figure 4 This is a schematic diagram of the structure of a workflow-based business data processing device provided by an embodiment of this specification;

[0074] Figure 5 It is a workflow diagram of a monetary fund business provided by an embodiment of this specification. DETAILED DESCRIPTION

[0075] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0076] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0077] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0078] See also Figure 1 As shown, the embodiment of this specification provides a workflow-based business data processing method, wherein the method is specifically applied to the node server side of the task scheduling system, wherein the task scheduling system can be associated with the workflow system. When implemented specifically, the method may include the following contents:

[0079] S101: receiving a trigger execution instruction for a target service;

[0080] S102: In response to the trigger execution instruction, obtain target business data required for executing the target business; create and execute a target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow includes multiple node tasks;

[0081] S103: monitoring the processing process of the target business data according to the target workflow, and obtaining the execution information of the target node task if there is a node in the target workflow where the target node task execution fails;

[0082] S104: determining the failure type of the target node task execution failure according to the execution information of the target node task; and accumulating the number of failures of the execution failure type of the target node task in the target workflow;

[0083] S105: Detect whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold;

[0084] S106: When it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining an adjusted target workflow;

[0085] S107: Based on the adjusted target workflow, continue to process the target business data.

[0086] Among them, the workflow system can be used to determine the corresponding tasks and execution roles by decomposing the business to be processed, so that these tasks can be executed by the execution roles according to certain rules and processes. The workflow system can also monitor the execution process of the task to improve data processing efficiency, reduce production costs, and improve the production and operation management level and competitiveness of the enterprise. The workflow system can support business definition and automatic operation of workflows, and can be regarded as the driver and customizer of business processes. The workflow system has core functions such as process modeling and design, task allocation and scheduling, data collection and processing, data visualization and report statistics. Users can customize workflows that meet their needs through the workflow system to adapt to the ever-changing working methods.

[0087] The task scheduling system can be used to define the rules and attributes of tasks, and to arrange the execution order and logic of tasks to ensure efficient execution of tasks. The task scheduling system mainly focuses on the scheduling and management of tasks, including task definition and task scheduling. Task definition refers to determining the logic and rules of processes such as data calculation and data processing, including the frequency of task execution, the specific execution time of tasks, and the execution scripts and parameters of task execution. Task scheduling refers to determining the execution order of different tasks to ensure that each task can be carried out in an orderly manner. The task scheduling system improves the execution efficiency and effectiveness of tasks by optimizing the execution order and logical relationship of tasks.

[0088] The workflow system focuses more on the customization and management of business processes, while the task scheduling system focuses more on the optimization of task execution order and logical relationships. In practical applications, the two can complement each other and jointly improve the operational efficiency and effectiveness of the enterprise. For example, an enterprise can use a workflow system to define and manage business processes, and then use a task scheduling system to optimize and orchestrate tasks in the process to achieve more efficient task execution and process management.

[0089] In addition, workflow has significant advantages over task scheduling systems in terms of hierarchical permission control, conditional judgment, and high configurability. Specifically:

[0090] 1) Hierarchical permission control: The workflow system has permission management functions, which can perform detailed permission division on process templates, process instances, activity instances, etc. Among them, permissions can be subdivided into maintenance, read-only, invisible, etc. Through hierarchical permission control, it can be ensured that different users can only access and operate their authorized resources. This hierarchical permission control can effectively protect sensitive data and operations and improve the security of the system. The permission management in the task scheduling system is relatively simple, mainly focusing on the allocation and execution of tasks, and less involving the detailed permission division of resources such as process templates and instances.

[0091] 2) Conditional judgment: Conditional judgment in the workflow system is a crucial link. It can select different process branches according to different situations to achieve flexible process control. The workflow system can parse conditional expressions through expression engines and other technologies and perform corresponding processing based on the results of conditional judgment. This conditional judgment mechanism enables the workflow system to be flexibly configured and adjusted according to different business scenarios and needs. The task scheduling system mainly focuses on the triggering and execution of tasks, and rarely involves complex conditional judgment logic. Although the task scheduling system can also trigger task execution according to specific conditions, these conditions are usually simpler and mainly focus on the triggering timing of the task rather than the control of the process.

[0092] 3) High configurability: The workflow system is highly configurable and can be customized according to the specific business processes of the enterprise. Whether it is business process modeling and design, task allocation and collaborative processing, notification and reminder functions, or data visualization and real-time monitoring, the workflow system can be flexibly configured and adjusted according to the needs of the enterprise. This high degree of configurability enables the workflow system to adapt to the business needs of different enterprises and improve the flexibility and scalability of the system. The configurability of the task scheduling system is limited. For example, the trigger time and trigger conditions of the task can be configured, but usually its configuration capabilities are relatively limited, focusing mainly on the scheduling and execution of tasks rather than the management and control of the entire business process.

[0093] In summary, the workflow system has significant advantages over the task scheduling system in terms of hierarchical authority control, conditional judgment, and high configurability. Therefore, the combination of the two can better meet the business needs of the enterprise and improve the automation level and efficiency of business processes.

[0094] Among them, the target business can be any business to be processed, for example, the target business can be a resource transfer business, a resource transfer approval business, etc. The above-mentioned target business data can be the data required to execute the target business. For example, taking the target business as a resource transfer business as an example, the corresponding target business data can include data such as resource transfer time, resource transfer object, resource transfer quantity and resource transfer platform. Taking the target business as a resource transfer approval business as an example, the corresponding target business data can include payment approval documents, original vouchers, receipts, statements and other data.

[0095] Among them, the failure type of the above-mentioned target node task execution failure may vary according to the different business scenarios corresponding to the target business. For example, the failure type may include execution timeout type, audit failure type, temporary type, persistent type, etc. Different failure types can be selected according to the actual business scenario. The embodiments of this specification do not specifically mention this.

[0096] The execution information of the target task may include the start time of executing the target task, the data called by executing the target task, the specific execution process of the target task, the execution time of the target task and other information.

[0097] The number thresholds corresponding to different execution failure types may be different. For example, the number threshold set for a temporary type may be greater than the number threshold set for a permanent type.

[0098] In some embodiments, the failure type may include an execution timeout type, and accordingly, the task processing rule responsible for the target node task may be adjusted in the following manner, including:

[0099] Adjust the start time of executing the target node task.

[0100] In some embodiments, the failure type may include an audit failure type, and accordingly, the task processing rule responsible for the target node task may be adjusted in the following manner, including:

[0101] An audit node is determined from the nodes of the node tasks of the target workflow, and the task processing data of the target node task is sent to the audit node for audit processing.

[0102] In some embodiments, the failure type may include an execution timeout type, and accordingly, the task processing rule responsible for the target node task may be adjusted in the following manner, including:

[0103] Adjust the start time of executing the target node task.

[0104] In some embodiments, the failure type may include a node resource-limited type. Accordingly, the node responsible for the target node task may be adjusted in the following manner, including:

[0105] A target resource amount for processing the target node task is obtained, and according to the target resource amount, a configuration resource amount of a node for the target node task is adjusted.

[0106] Based on the above embodiments, when the task node relationship dependency is complex and the workflow processing resource consumption is large, on the one hand, by monitoring the processing process of the target business data, when the number of failures of the execution failure type of the target task node of the target workflow is greater than the preset number threshold, the target workflow that failed to execute can be adjusted, thereby avoiding the problem of low efficiency of task scheduling execution caused by the need to adjust the target workflow multiple times when the number of node failures of the execution failure type is small, and improving the efficiency of node task scheduling execution. On the other hand, when adjusting the target workflow, the task information of the target node can be used to interact with the workflow system to accurately adjust the node responsible for the target node task and / or the task processing rules of the target node task, thereby improving the accuracy of node task scheduling execution.

[0107] In some embodiments, the method may further include the following contents when the execution information of the target node task is used to interact with the workflow system and before adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task:

[0108] S1: Determine the failure reason leading to the failure of the execution of the target node task in the target workflow and the related reason type according to the execution information of the target node task; wherein the reason type includes temporary type or permanent type;

[0109] S2: generating a failure analysis report on the failure of executing the target node task in the target workflow according to the failure reason and the related reason type;

[0110] S3: Sending the failure analysis report to the workflow system; wherein the workflow system determines whether to adjust the target workflow according to the failure analysis report.

[0111] Among them, there may be multiple reasons for the failure of the target node task to execute. For example, the failure reasons may include the loss of connection with the target node responsible for the target node task, the execution timeout of the target node, the failure to obtain data for the target node task, etc. Accordingly, the type of reason related to the target node task can be determined based on the urgency of the target node task, the processing priority and other information. For example, when the urgency of the target node task is high, the type of reason related to the target node task can be determined as a persistent type. When the urgency of the target node task is low, the type of reason related to the target node task can be determined as a temporary type.

[0112] In some embodiments, the generating of the failure analysis report on the failure of the target node task execution in the target workflow according to the failure cause and the related cause type may also include the following contents:

[0113] A failure analysis report on the failure of executing the target node task in the target workflow is generated according to the failure cause and the related cause type by using a preset large language model.

[0114] Specifically, the server can call the large language model and input the failure reason, related reason type and preset prompt information (promot) into the large language model to utilize the analysis and collation capabilities of the large language model to generate a failure analysis report of the failure to execute the target node task in the target workflow.

[0115] Based on the above embodiment, a failure analysis report can be quickly and accurately generated according to the cause and type of the target node task execution failure, and then according to the failure analysis report, it is determined whether to adjust the target workflow.

[0116] In some embodiments, see Figure 2 As shown, the method also includes:

[0117] S1: in the case of determining to adjust the target workflow, interacting with the workflow system to obtain the attribute information of the target business data and the task attributes of the target node task, and determining the node attributes of the associated node of the neighboring node task responsible for the target node task;

[0118] S2: determining a target adjustment strategy for the target workflow according to the attribute information of the target business data, the task attributes of the target node task, and the node attributes of the associated node;

[0119] S3: According to the target adjustment strategy, the target workflow is adjusted by adjusting the node responsible for the target node task and / or the task processing rule of the target node task to obtain the adjusted target workflow;

[0120] S4: Feedback the adjusted target workflow to the node server of the task scheduling system.

[0121] Among them, the attribute information of the above-mentioned target business data may include security information of the target business data (i.e., whether the target business data is sensitive information that needs to be encrypted or desensitized, etc.), the task attributes of the above-mentioned target node task may include information such as the task type of the target node task, wherein the task type can be used to characterize the importance of the target node task, and the node attributes of the above-mentioned associated nodes may include information such as the node type of the node, wherein the node type can be used to characterize whether the node can be used to process node tasks with higher importance.

[0122] Based on the above embodiments, a target adjustment strategy can be determined in a targeted manner according to the attribute information of the target business, the task attributes of the target node task, and the node attributes of the node associated with the adjacent node task, thereby effectively adjusting the target workflow.

[0123] In some embodiments, when the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow. When the method is specifically implemented, the following contents may also be included:

[0124] S1: Based on the adjusted target workflow, determine a restart start task from neighboring node tasks of the target node task; and determine a plurality of consensus nodes from nodes other than the target node that are responsible for node tasks in the target workflow;

[0125] S2: Combining the multiple consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group to replace the target node;

[0126] S3: query the task processing record of the target workflow to obtain task processing data for the restart start task; and send the task processing data to the node responsible for the restart start task to continue processing the target business data.

[0127] Among them, the consensus nodes can be multiple nodes determined based on the matching degree between the task attributes of the target node task and the node attributes of each node of the node task in the target workflow. For example, the server can perform matching and screening processing on the nodes according to the task type of the target node task and the node type of the node to filter out the consensus nodes from the nodes of the node task in the target workflow.

[0128] Based on the above embodiment, when the failure cause is: the target node responsible for the target node task is lost, and the cause type is: persistent, multiple consensus nodes can be quickly and accurately determined to replace the target node to continue processing the target business data.

[0129] In some embodiments, after combining the plurality of consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group, the method may further include the following when implemented:

[0130] S1: Generate notification information about using the target consensus node to replace the target node;

[0131] S2: Send the notification information to the target node;

[0132] S3: Detecting whether a rejection instruction of the target node for the notification information is received within a preset tolerance time;

[0133] S4: When no rejection instruction is received from the target node for the notification information within the preset tolerance time, the target consensus node group is used to replace the target node.

[0134] The preset tolerance time may be determined according to the type of reason for the target node task execution failure. For example, the tolerance time for a temporary type may be greater than the tolerance time for a persistent type.

[0135] Based on the above embodiment, the tolerance time can be determined according to the type of reason for the target node task execution failure, and the target node can be effectively replaced.

[0136] In some embodiments, the method of continuing to process the target service data may further include the following when implemented:

[0137] S1: Acquire task processing data for the target node task;

[0138] S2: Distribute the task processing data of the target node task to multiple consensus nodes of the target consensus node group;

[0139] S3: receiving multiple intermediate task processing results fed back by the multiple consensus nodes;

[0140] S4: Processing the plurality of intermediate task processing results according to the consensus rule to obtain a target task processing result for the target node task;

[0141] S5: Continue to process the target business data according to the target task processing result and the adjusted target workflow.

[0142] In some embodiments, according to the consensus rule, the plurality of intermediate task processing results are processed to obtain a target task processing result for the target node task. When the method is specifically implemented, the following contents may also be included:

[0143] According to the consensus algorithm determined by the consensus rule, based on the multiple intermediate task processing results, a target task processing result for the target node task is determined.

[0144] Among them, the consensus algorithm may include proof of work (PoW), proof of stake (PoS), delegated proof of stake (DPoS) and other algorithms.

[0145] Based on the above embodiment, the target business data can be further accurately processed according to the intermediate task processing results fed back to multiple consensus nodes.

[0146] In some embodiments, when the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: temporary, the target business data is continued to be processed based on the adjusted target workflow. When the method is specifically implemented, the following contents may also be included:

[0147] S1: Based on the adjusted target workflow, determine a restart start task from neighboring node tasks of the target node task; and determine a temporary node from nodes other than the target node that are responsible for node tasks in the target workflow to replace the target node; wherein the temporary node is set to be valid in the current target workflow;

[0148] S2: using the temporary node to complete the target processing task, and sending a request to the target node to determine whether to change the current target processing flow;

[0149] S3: When it is determined to change the current target processing flow, the target workflow is adjusted to obtain the adjusted target workflow to continue processing the target business data.

[0150] The temporary node may be a node determined according to the matching degree between the task attribute of the target node task and the node attribute of each node of the node task in the target workflow.

[0151] Based on the above embodiments, when the cause of failure is that the target node responsible for the target node task is lost connection, and the cause type is: persistent type, the consensus mechanism can be used to utilize a target consensus node group including multiple consensus nodes to replace the target node to process the task. When the cause of failure is that the target node responsible for the target node task is lost connection, and the cause type is: temporary type, the selected temporary node can be used to replace the target node to process the task. The target workflow can be adjusted in a targeted and accurate manner to avoid waste of resources caused by invalid adjustments and poor adjustment accuracy, thereby improving the efficiency and accuracy of workflow adjustment.

[0152] In some embodiments, when the failure reason is: the task processing rule of the target node task is abnormal, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow. When the method is specifically implemented, the following contents may also be included:

[0153] S1: Based on the adjusted target workflow, determine the key nodes in the target workflow;

[0154] S2: sending the updated task processing rule of the target node task to the key node; wherein the updated task processing rule is obtained by the workflow system adjusting the task processing rule of the target node task according to the target node task execution information;

[0155] S3: When it is determined that a confirmation instruction for the updated task processing rule is received from the key node, the updated task processing rule is configured on the target node to replace the task processing rule of the target node task; and the target business data is continued to be processed.

[0156] The key node may be a node determined according to the matching degree between the task attribute of the target node task and the node attribute of each node of the node task in the target workflow.

[0157] Based on the above embodiment, when the failure reason is: the task processing rule of the target node task is abnormal, and the reason type is: persistent, the task processing rule is updated through the key node to continue to process the target business data effectively and accurately.

[0158] In some embodiments, the method of creating a target workflow corresponding to the target business by interacting with the workflow system may further include the following when the method is implemented:

[0159] S1: Sending a creation request for the target workflow to the workflow system; wherein the creation request carries at least a service identifier of the target service indicated by the target service data;

[0160] S2: receiving a configuration parameter set of the target workflow fed back by the workflow system; wherein the configuration parameter set of the target workflow at least includes business execution process information of multiple node tasks in the target workflow, and the task processing rule; the configuration parameter set of the target workflow corresponds to the business identifier of the target business;

[0161] S3: Determine the node responsible for processing the node task in the target workflow according to the business execution process information of the multiple node tasks in the target workflow; and determine the audit authority configuration information of the node;

[0162] S4: configuring the node tasks, the task processing rules, and the audit authority configuration information on corresponding nodes to create the target workflow corresponding to the target business.

[0163] Based on the above embodiment, the audit authority configuration information can be determined according to the creation request of the target workflow, the configuration parameter set and the business execution process information of the node task, and then the target workflow can be further accurately created.

[0164] In some embodiments, the method for determining the audit authority configuration information of the node may further include the following contents when implemented:

[0165] S1: using a preset authority configuration model, according to the business execution process information corresponding to the node task in the workflow system, determining the review priority and review content authority information of the node corresponding to the node task; wherein the preset authority configuration model is constructed according to a preset machine learning algorithm;

[0166] S2: Determine the audit authority configuration information of the node corresponding to the node task according to the audit priority and audit content authority information of the node corresponding to the node task.

[0167] In addition, the server can also provide a visual scheduling management interface, which can display information such as the execution status of the task and the usage of resources, helping users to understand the task scheduling process more intuitively.

[0168] In addition, the server can also receive adjustment instructions for task processing rules and / or configuration parameters entered by the user in the scheduling management interface, and adjust the target workflow in the workflow system according to the received adjustment instructions, so as to effectively solve the problem of inflexible scheduling conditions of traditional task scheduling platforms and improve scheduling efficiency and flexibility.

[0169] In some embodiments, the target service data is data obtained by encrypting the data using a preset encryption algorithm. Accordingly, the method for obtaining the target service data required for executing the target service may further include the following contents when the method is specifically implemented:

[0170] S1: Acquire target business data required to execute the target business, and first verification information corresponding to the target business data;

[0171] S2: decrypting the target service data to obtain decrypted target service data, and generating second verification information according to the decrypted target service data;

[0172] S3: Matching the first verification information and the second verification information, and if the matching is successful, determining that the target business data meets the requirements.

[0173] Among them, the first verification information can be information generated for the business data to be sent according to a preset signature algorithm (such as a hash function, etc.). For example, the data sender can generate a hash value for the business data to be sent through a hash function, and determine the generated hash value as the first verification information.

[0174] Based on the above embodiment, by matching the first verification information and the second verification information, it can be determined whether the target business data has been tampered with during the data transmission process. If the match is successful, it can be determined that the target business data has not been tampered with, that is, it can be determined that the target business data meets the requirements.

[0175] As can be seen from the above, a workflow-based business data processing method provided in an embodiment of the present specification is applied to a node server of a task scheduling system, wherein the task scheduling system is associated with a workflow system, and the method comprises: receiving a trigger execution instruction for a target business; in response to the trigger execution instruction, obtaining target business data required for executing the target business; creating and executing a target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow comprises a plurality of node tasks; according to the target workflow, monitoring the processing process of the target business data, and if there is a node in the target workflow where the target node task fails to execute, obtaining the execution information of the target node task; and according to the target node task, monitoring the processing process of the target business data; wherein the target node task fails to execute, obtaining the execution information of the target node task; and The target workflow is a process of determining the type of failure of the target node task execution by the execution information of the task; accumulating the number of failures of the execution failure type of the target node task in the target workflow; detecting whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold; in the case of determining that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining the adjusted target workflow; based on the adjusted target workflow, continuing to process the target business data. In this way, in the case of complex task node relationship dependence and large workflow processing resource consumption, on the one hand, by monitoring the processing process of the target business data, in the case of the number of failures of the execution failure type of the target task node of the target workflow is greater than the preset number threshold, adjusting the target workflow that failed to execute, avoiding the problem of low efficiency of task scheduling execution caused by multiple adjustments to the target workflow due to the small number of node failures of the execution failure type, and improving the efficiency of node task scheduling execution. On the other hand, when adjusting the target workflow, the task information of the target node can be used to interact with the workflow system to accurately adjust the nodes responsible for the target node tasks and / or the task processing rules of the target node tasks, thereby improving the accuracy of node task scheduling execution.

[0176] See also Figure 3 As shown, the embodiment of this specification also provides a specific electronic device, wherein the electronic device includes a network communication port 301, a processor 302 and a memory 303, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0177] The network communication port 301 may be used to receive a trigger execution instruction for a target service.

[0178] The processor 302 can be specifically used to respond to the trigger execution instruction to obtain the target business data required for executing the target business; create and execute the target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow includes multiple node tasks; according to the target workflow, monitor the processing process of the target business data, if there is a node in the target workflow where the target node task fails to execute, obtain the execution information of the target node task; according to the execution information of the target node task, determine the failure type of the target node task execution failure; and accumulate the target workflow. The method comprises the following steps: detecting the number of failures of the execution failure type of the target node task in the target workflow; detecting whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold; in the case of determining that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, utilizing the execution information of the target node task to interact with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining an adjusted target workflow; and continuing to process the target business data based on the adjusted target workflow.

[0179] The memory 303 may be specifically used to store corresponding instruction programs.

[0180] Based on the above method, the relevant structural performance of the electronic device can be effectively utilized, the data processing speed of the electronic device can be improved, and the workflow-based business data processing method can be efficiently implemented.

[0181] In this embodiment, the network communication port 301 can be a virtual port that is bound to different communication protocols so that different data can be sent or received. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. In addition, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM, CDMA, etc.; it can also be a Wifi chip; it can also be a Bluetooth chip.

[0182] In this embodiment, the processor 302 may be implemented in any appropriate manner. For example, the processor may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, etc. This specification does not limit this.

[0183] In this embodiment, the memory 303 may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function but no physical form is also called a memory, such as RAM, FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0184] The embodiment of the present specification also provides a computer-readable storage medium based on the above-mentioned workflow-based business data processing method, wherein the computer-readable storage medium stores computer program instructions, which, when executed, implement: receiving a trigger execution instruction for a target business; in response to the trigger execution instruction, obtaining target business data required for executing the target business; creating and executing a target workflow corresponding to the target business by interacting with a workflow system to process the target business data; wherein the target workflow includes a plurality of node tasks; according to the target workflow, monitoring the processing process of the target business data, and if there is a node in the target workflow where the target node task fails to execute, obtaining the execution information of the target node task; and according to the The method comprises the steps of: determining the failure type of the target node task execution failure based on the execution information of the target node task; and accumulating the number of failures of the execution failure type of the target node task in the target workflow; detecting whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold; in the case of determining that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task to interact with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining an adjusted target workflow; and continuing to process the target business data based on the adjusted target workflow.

[0185] In this embodiment, the storage medium includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD), or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0186] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other implementations and will not be described in detail here.

[0187] The embodiment of the present specification also provides a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, the following method steps are implemented: receiving a trigger execution instruction for a target business; in response to the trigger execution instruction, obtaining target business data required for executing the target business; creating and executing a target workflow corresponding to the target business by interacting with a workflow system to process the target business data; wherein the target workflow includes a plurality of node tasks; according to the target workflow, monitoring the processing process of the target business data, if there is a node in the target workflow where the target node task fails to execute, obtaining the execution information of the target node task; according to the execution information of the target node task, determining Determine the failure type of the target node task execution failure; and accumulate the number of failures of the target node task execution failure type in the target workflow; detect whether the number of failures of the target node task execution failure type in the target workflow is greater than a preset number threshold; when it is determined that the number of failures of the target node task execution failure type in the target workflow is greater than the preset number threshold, use the execution information of the target node task to interact with the workflow system, adjust the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtain an adjusted target workflow; based on the adjusted target workflow, continue to process the target business data.

[0188] See also Figure 4 At the software level, the embodiment of this specification also provides a workflow-based business data processing device, which may specifically include the following structural modules:

[0189] The instruction receiving module 401 is used to receive a trigger execution instruction for a target service;

[0190] The instruction trigger module 402 is used to obtain the target business data required for executing the target business in response to the trigger execution instruction; create and execute the target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow includes multiple node tasks;

[0191] An execution information acquisition module 403 is used to monitor the processing process of the target business data according to the target workflow, and if there is a node in the target workflow where the target node task fails to execute, acquire the execution information of the target node task;

[0192] The type determination module 404 is used to determine the failure type of the target node task execution failure according to the execution information of the target node task; and to accumulate the number of failures of the execution failure type of the target node task in the target workflow;

[0193] The number determination module 405 is used to detect whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold;

[0194] The workflow adjustment module 406 is used to, when it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, interact with the workflow system using the execution information of the target node task, and adjust the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task to obtain an adjusted target workflow;

[0195] The business processing module 407 is used to continue processing the target business data based on the adjusted target workflow.

[0196] In some embodiments, before the above-mentioned workflow adjustment module 406, during specific implementation, the failure cause leading to the failure of execution of the target node task in the target workflow and the related cause type are determined according to the execution information of the target node task; wherein the cause type includes temporary type or permanent type; according to the failure cause and the related cause type, a failure analysis report on the failure of execution of the target node task in the target workflow is generated; the failure analysis report is sent to the workflow system; wherein the workflow system determines whether to adjust the target workflow according to the failure analysis report.

[0197] In some embodiments, the method further comprises:

[0198] In the case of determining to adjust the target workflow, interacting with the workflow system to obtain the attribute information of the target business data and the task attributes of the target node task, and determining the node attributes of the associated node of the neighboring node task responsible for the target node task;

[0199] Determining a target adjustment strategy for the target workflow according to the attribute information of the target business data, the task attributes of the target node task, and the node attributes of the associated node;

[0200] According to the target adjustment strategy, the target workflow is adjusted by adjusting the node responsible for the target node task and / or the task processing rule of the target node task to obtain the adjusted target workflow;

[0201] The adjusted target workflow is fed back to the node server of the task scheduling system.

[0202] In some embodiments, when the failure reason is: the target node responsible for the target node task is lost, and the reason type is: persistent, the above-mentioned business processing module 407, when implemented, determines the restart start task from the neighboring node tasks of the target node task based on the adjusted target workflow; and determines multiple consensus nodes from the nodes other than the target node that are responsible for the node tasks in the target workflow; a node replacement module is used to combine the multiple consensus nodes and configure corresponding consensus rules to obtain a target consensus node group to replace the target node; query the task processing record of the target workflow to obtain the task processing data for the restart start task; and send the task processing data to the node responsible for the restart start task to continue processing the target business data.

[0203] In some embodiments, after the above-mentioned node replacement module, during specific implementation, a notification message about using the target consensus node to replace the target node is generated; the notification message is sent to the target node; it is detected whether a rejection instruction of the target node for the notification message is received within a preset tolerance time; if a rejection instruction of the target node for the notification message is not received within the preset tolerance time, the target consensus node group is used to replace the target node.

[0204] In some embodiments, the continuing to process the target business data is specifically implemented by obtaining task processing data for the target node task; distributing the task processing data for the target node task to multiple consensus nodes of the target consensus node group; receiving multiple intermediate task processing results fed back by the multiple consensus nodes; processing the multiple intermediate task processing results according to consensus rules to obtain a target task processing result for the target node task; and continuing to process the target business data according to the target task processing result and the adjusted target workflow.

[0205] In some embodiments, when the failure reason is: the target node responsible for the target node task is lost, and the reason type is: temporary, the above-mentioned business processing module 407, when implemented, determines the restart start task from the neighboring node tasks of the target node task based on the adjusted target workflow; and determines a temporary node from the nodes other than the target node that are responsible for the node tasks in the target workflow to replace the target node; wherein the temporary node is set to be valid in the current target workflow; uses the temporary node to complete the target processing task, and sends a request to the target node to determine whether to change the current target processing flow; when it is determined to change the current target processing flow, adjusts the target workflow to obtain the adjusted target workflow to continue processing the target business data.

[0206] In some embodiments, when the failure reason is: the task processing rule of the target node task is abnormal, and the reason type is: persistent, the above-mentioned business processing module 407, when implemented, determines the key nodes in the target workflow based on the adjusted target workflow; sends the updated task processing rules of the target node task to the key nodes; wherein the updated task processing rules are obtained by the workflow system adjusting the task processing rules of the target node task according to the target node task execution information; when it is determined that a confirmation instruction for the updated task processing rules is received from the key node, the updated task processing rules are configured at the target node to replace the task processing rules of the target node task; and the target business data continues to be processed.

[0207] In some embodiments, the target workflow corresponding to the target business is created by interacting with the workflow system. That is, the workflow creation module, when implemented specifically, sends a creation request for the target workflow to the workflow system; wherein the creation request carries at least the business identifier of the target business indicated by the target business data; receives the configuration parameter set of the target workflow fed back by the workflow system; wherein the configuration parameter set of the target workflow at least includes the business execution process information of multiple node tasks in the target workflow, and the task processing rules; the configuration parameter set of the target workflow corresponds to the business identifier of the target business; according to the business execution process information of multiple node tasks in the target workflow, the node responsible for processing the node task in the target workflow is determined; the authority determination module is used to determine the audit authority configuration information of the node; the node task, the task processing rule, and the audit authority configuration information are configured in the corresponding node to create the target workflow corresponding to the target business.

[0208] In some implementations, the above-mentioned permission determination module, when implemented specifically, utilizes a preset permission configuration model to determine the audit priority and audit content permission information of the node corresponding to the node task in the workflow system based on the business execution process information corresponding to the node task; wherein the preset permission configuration model is constructed based on a preset machine learning algorithm; and the audit permission configuration information of the node corresponding to the node task is determined based on the audit priority and audit content permission information of the node corresponding to the node task.

[0209] In some embodiments, the target business data is data obtained by encryption processing using a preset encryption algorithm; accordingly, the above-mentioned acquisition of the target business data required to execute the target business, that is, acquisition of target business data that meets the requirements, is specifically implemented by acquiring the target business data required to execute the target business, and first verification information corresponding to the target business data; decrypting the target business data to obtain the decrypted target business data, and generating second verification information based on the decrypted target business data; matching the first verification information and the second verification information, and if the match is successful, determining that the target business data meets the requirements.

[0210] As can be seen from the above, based on the workflow-based business data processing device provided by the embodiment of this specification, when the task node relationship dependency is complex and the workflow processing resource consumption is large, on the one hand, by monitoring the processing process of the target business data, when the number of failures of the execution failure type of the target task node of the target workflow is greater than the preset number threshold, the target workflow that failed to execute is adjusted, thereby avoiding the problem of low efficiency of task scheduling execution caused by the need to adjust the target workflow multiple times when the number of node failures of the execution failure type is small, and the efficiency of node task scheduling execution can be improved. On the other hand, when adjusting the target workflow, the task information of the target node can be used to interact with the workflow system to accurately adjust the node responsible for the target node task and / or the task processing rules of the target node task, thereby improving the accuracy of node task scheduling execution.

[0211] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described separately by functions divided into various modules. Of course, when implementing this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0212] In a specific scenario example, a workflow-based business data processing method provided in this specification can be applied to avoid the problem of low efficiency of task scheduling execution caused by multiple adjustments to the target workflow when the number of node failures of the execution failure type is small, and the efficiency of node task scheduling execution can be improved. In addition, by interacting with the workflow system, the task processing rules of the node responsible for the target node task and / or the target node task can be accurately adjusted, which can improve the accuracy of node task scheduling execution. The specific implementation process may include the following content.

[0213] Take the target business as resource transfer review business as an example. Figure 5 As shown, the business execution process information of the business can be as follows:

[0214] 1. Start: The whole process starts.

[0215] 2. Submit a payment application: This step may involve submitting a payment application and corresponding documents or original vouchers.

[0216] 3. Expenditure approval: Approve the payment application. During the approval process, the compliance of the documents and original vouchers will be checked.

[0217] Unqualified: If the document or original voucher does not meet the requirements, the process will return to the "Expenditure Approval" step for re-approval or correction.

[0218] Pass: If both the document and the original voucher meet the requirements, it will proceed to the next step.

[0219] 4. Judgment of large amount:

[0220] Within limit: If the payment amount is within the limit, the process will directly proceed to the "Payment" step.

[0221] Exceeding the limit: If the payment amount exceeds the limit, a "Signature / Stamp" step is required and further approval or authorization may be required.

[0222] 5. Payment: After passing all approvals and completing the necessary signatures / stamps, make the payment.

[0223] 6. Subsequent processing:

[0224] Receipt / Bank Slip: After payment, you should get a receipt or bank slip as proof of payment.

[0225] Register Cash: If the payment is made by cash, it is necessary to register the cash outflow.

[0226] Bank Journal: For payments made through a bank, they need to be recorded in the bank's journal.

[0227] Preparation of bank balance ledger: A bank balance ledger is prepared regularly to record the changes in bank deposits.

[0228] 7. Regular reconciliation: Regular reconciliation with the bank to ensure the accounts are accurate.

[0229] 8. End: The entire monetary funds business process ends here.

[0230] When the server receives the trigger execution instruction for the target business, it can obtain the target business data required to execute the target business, and receive the configuration parameter set of the target workflow fed back by the workflow system through interaction with the workflow system; wherein the configuration parameter set of the target workflow at least includes the business execution process information of multiple node tasks in the target workflow, and the task processing rules; the configuration parameter set of the target workflow corresponds to the business identifier of the target business. Then, according to the business execution process information of multiple node tasks in the target workflow, the node responsible for processing the node task in the target workflow is determined; and the audit authority configuration information of the node is determined; finally, the node task, the task processing rules, and the audit authority configuration information can be configured on the corresponding node to create the target workflow corresponding to the target business.

[0231] According to the target workflow, the processing process of the target business data is monitored, and if there is a node in the target workflow where the target node task execution fails, the execution information of the target node task is obtained.

[0232] According to the execution information of the target node task, the failure type of the target node task execution failure is determined; and the number of failures of the execution failure type of the target node task in the target workflow is accumulated. The failure type can be determined according to the failure cause and the cause type. The failure cause can include the target node responsible for the target node task being disconnected, and the cause type can include temporary type and persistent type, etc.

[0233] Detect whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold, and when it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, use the execution information of the target node task to interact with the workflow system, adjust the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtain the adjusted target workflow.

[0234] Based on the adjusted target workflow, the target business data continues to be processed.

[0235] In this way, by using the workflow system to trigger the task scheduling system, the entire process can be optimized in terms of hierarchical authority approval, complex conditional triggering of tasks, etc., so that the entire business process ensures resource security and process compliance through clear steps and approval mechanisms.

[0236] Although the present specification provides method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps, and does not represent a unique execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. The first, second, etc. words are used to represent the name, and do not represent any particular order.

[0237] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0238] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer-readable storage media including storage devices.

[0239] Through the description of the above embodiments, it can be known that those skilled in the art can clearly understand that the present specification can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present specification can essentially be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in each embodiment of the present specification or some parts of the embodiments.

[0240] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. This specification can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0241] Although the present specification is described through embodiments, those skilled in the art will appreciate that there are many modifications and changes to the present specification without departing from the spirit of the present specification, and it is intended that the appended claims include these modifications and changes without departing from the spirit of the present specification.

Claims

1. A workflow-based business data processing method, characterized in that: A node server applied to a task scheduling system, wherein the task scheduling system is associated with a workflow system, and the method comprises: Receive trigger execution instructions for target business; In response to the trigger execution instruction, the target business data required for executing the target business is acquired; by interacting with the workflow system, a target workflow corresponding to the target business is created and executed to process the target business data; wherein the target workflow includes a plurality of node tasks; According to the target workflow, monitoring the processing process of the target business data, if there is a node in the target workflow where the target node task execution fails, acquiring the execution information of the target node task; Determine the failure type of the target node task execution failure according to the execution information of the target node task; and accumulate the number of failures of the execution failure type of the target node task in the target workflow; Detecting whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold; When it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, and obtaining an adjusted target workflow; Based on the adjusted target workflow, the target business data continues to be processed.

2. The method according to claim 1, characterized in that The method of utilizing the execution information of the target node task to interact with the workflow system and adjusting the node responsible for the target node task and / or the task processing rule of the target node task to adjust the target workflow may further include: Determine the failure reason leading to the failure of the execution of the target node task in the target workflow and the related reason type according to the execution information of the target node task; wherein the reason type includes temporary type or permanent type; Generate a failure analysis report on the failure of executing the target node task in the target workflow according to the failure reason and the related reason type; The failure analysis report is sent to the workflow system; wherein the workflow system determines whether to adjust the target workflow according to the failure analysis report.

3. The method according to claim 2, characterized in that The method further comprises: In the case of determining to adjust the target workflow, interacting with the workflow system to obtain the attribute information of the target business data and the task attributes of the target node task, and determining the node attributes of the associated node of the neighboring node task responsible for the target node task; Determining a target adjustment strategy for the target workflow according to the attribute information of the target business data, the task attributes of the target node task, and the node attributes of the associated node; According to the target adjustment strategy, the target workflow is adjusted by adjusting the node responsible for the target node task and / or the task processing rule of the target node task to obtain the adjusted target workflow; The adjusted target workflow is fed back to the node server of the task scheduling system.

4. The method according to claim 2, characterized in that: When the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow, including: Based on the adjusted target workflow, a restart start task is determined from neighboring node tasks of the target node task; and a plurality of consensus nodes are determined from nodes other than the target node that are responsible for node tasks in the target workflow; Combining the multiple consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group to replace the target node; The task processing record of the target workflow is queried to obtain task processing data for the restart start task; and the task processing data is sent to a node responsible for the restart start task to continue processing the target business data.

5. The method according to claim 4, characterized in that After combining the plurality of consensus nodes and configuring corresponding consensus rules to obtain a target consensus node group, the method further includes: Generating notification information about using the target consensus node to replace the target node; Sending the notification information to the target node; Detecting whether a rejection instruction of the target node for the notification information is received within a preset tolerance time; In the case where no rejection instruction is received from the target node for the notification information within the preset tolerance time, the target consensus node group is used to replace the target node.

6. The method according to claim 4, characterized in that The continuing to process the target service data includes: Acquire task processing data for the target node task; Distributing the task processing data of the target node task to multiple consensus nodes of the target consensus node group; Receive multiple intermediate task processing results fed back by the multiple consensus nodes; According to the consensus rules, the plurality of intermediate task processing results are processed to obtain a target task processing result for the target node task; The target business data continues to be processed according to the target task processing result and the adjusted target workflow.

7. The method according to claim 2, characterized in that When the failure reason is: the target node responsible for the target node task is disconnected, and the reason type is: temporary, the target business data is continued to be processed based on the adjusted target workflow, including: Based on the adjusted target workflow, a restart start task is determined from the neighboring node tasks of the target node task; and a temporary node is determined from the nodes other than the target node that are responsible for the node tasks in the target workflow to replace the target node; wherein the temporary node is set to be valid in the current target workflow; Using the temporary node to complete the target processing task, and sending a request to the target node to determine whether to change the current target processing flow; In the case where it is determined to change the current target processing flow, the target workflow is adjusted to obtain the adjusted target workflow to continue processing the target business data.

8. The method according to claim 2, characterized in that: When the failure reason is: the task processing rule of the target node task is abnormal, and the reason type is: persistent, the target business data is continued to be processed based on the adjusted target workflow, including: Based on the adjusted target workflow, determining key nodes in the target workflow; Sending the updated task processing rules of the target node task to the key node; wherein the updated task processing rules are obtained by the workflow system adjusting the task processing rules of the target node task according to the target node task execution information; When it is determined that a confirmation instruction for the updated task processing rule is received from the key node, the updated task processing rule is configured on the target node to replace the task processing rule of the target node task; and the target business data continues to be processed.

9. The method according to claim 1, characterized in that: The step of creating a target workflow corresponding to the target business by interacting with the workflow system includes: Sending a creation request for the target workflow to the workflow system; wherein the creation request carries at least a service identifier of the target service indicated by the target service data; Receive the configuration parameter set of the target workflow fed back by the workflow system; wherein the configuration parameter set of the target workflow at least includes the business execution process information of multiple node tasks in the target workflow, and the task processing rules; the configuration parameter set of the target workflow corresponds to the business identifier of the target business; Determine the node responsible for processing the node task in the target workflow according to the business execution process information of the multiple node tasks in the target workflow; and determine the audit authority configuration information of the node; The node tasks, the task processing rules, and the audit authority configuration information are configured on corresponding nodes to create the target workflow corresponding to the target business.

10. The method according to claim 9, characterized in that The step of determining the audit authority configuration information of the node includes: Using a preset authority configuration model, according to the business execution process information corresponding to the node task in the workflow system, the review priority and review content authority information of the node corresponding to the node task are determined; wherein the preset authority configuration model is constructed according to a preset machine learning algorithm; The audit authority configuration information of the node corresponding to the node task is determined according to the audit priority and audit content authority information of the node corresponding to the node task.

11. The method according to claim 1, characterized in that: The target business data is data obtained by encryption processing using a preset encryption algorithm; Accordingly, the step of acquiring target business data required for executing the target business includes: Acquire target business data required for executing the target business, and first verification information corresponding to the target business data; Decrypting the target service data to obtain decrypted target service data, and generating second verification information according to the decrypted target service data; The first verification information and the second verification information are matched, and if the match is successful, it is determined that the target business data meets the requirements.

12. A workflow-based business data processing device, characterized in that: include: An instruction receiving module, used to receive a trigger execution instruction for a target business; An instruction trigger module is used to obtain target business data required for executing the target business in response to the trigger execution instruction; create and execute a target workflow corresponding to the target business by interacting with the workflow system to process the target business data; wherein the target workflow includes multiple node tasks; An execution information acquisition module, used to monitor the processing process of the target business data according to the target workflow, and if there is a node in the target workflow where the target node task fails to execute, acquire the execution information of the target node task; A type determination module, used to determine the failure type of the target node task execution failure according to the execution information of the target node task; and accumulate the number of failures of the execution failure type of the target node task in the target workflow; A number determination module is used to detect whether the number of failures of the execution failure type of the target node task in the target workflow is greater than a preset number threshold; A workflow adjustment module, for, when it is determined that the number of failures of the execution failure type of the target node task in the target workflow is greater than the preset number threshold, using the execution information of the target node task, interacting with the workflow system, adjusting the target workflow by adjusting the node responsible for the target node task and / or the task processing rule of the target node task, to obtain an adjusted target workflow; The business processing module is used to continue processing the target business data based on the adjusted target workflow.

13. A server, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 11 when executing the instructions.

14. A computer-readable storage medium, characterized in that: Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

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

Images