Method, apparatus, device, medium, and program product for executing a to-be-approved task based on approval flow configuration

Abstract

The present disclosure provides a method for executing a to-be-approved task based on approval flow configuration, which can be applied to the fields of Internet of Things technology and big data technology. The method for executing a to-be-approved task based on approval flow configuration includes: matching a current approval flow corresponding to the to-be-approved task according to a task type identifier of the to-be-approved task and a preset approval flow matching rule; matching an upgraded approval flow corresponding to the current approval flow based on a current approval requirement degree of the current approval flow and a task requirement degree of the to-be-approved task; and performing a rollback operation on the current approval flow according to an approval execution status of the upgraded approval flow to complete the execution of the to-be-approved task. The present disclosure also provides an apparatus, a device, a storage medium, and a program product for executing a to-be-approved task based on approval flow configuration.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, device, equipment, medium and program product for executing a task to be approved based on approval flow configuration. Background Art

[0002] With the rapid development and widespread application of information technology, the systematic electronic approval process of business approval, report approval and document approval has been basically realized in various industries such as finance, education, and manufacturing, thus replacing the traditional approval method of paper delivery and submission, greatly improving the efficiency of business approval, ensuring the transparency of the approval process, and increasing the accuracy of business approval. It can also provide real-time approval nodes for anytime review, and can intuitively grasp the progress of the approval process. At present, the commonly used electronic approval circulation system generally provides business personnel with an available operation page, and the business personnel select and fill in the information that needs to be approved through the operation page, and submit the system process for approval circulation. In addition, in order to meet the continuous innovation of business model progress and the frequently adjusted business approval scenarios, while reducing the development cost of the approval system and improving the development efficiency, the existing electronic approval circulation system has begun to move towards the configurable process to achieve a high degree of system reuse and improve the stability of the modification and change process of the addition and abandonment of approval nodes. However, although the electronic approval circulation system based on the existing process configurability (i.e. approval flow configuration) can improve the efficiency of electronic approval to a considerable extent, in many application scenarios, it still has many approval restrictions, which limits its further development and application. Summary of the invention

[0003] In view of the above problems, the present disclosure provides a method, device, equipment, medium and program product for executing tasks to be approved based on approval flow configuration, which can improve the automated approval speed of tasks to be approved and optimize the approval flow execution process.

[0004] According to a first aspect of the present disclosure, a method for executing a pending approval task based on an approval flow configuration is provided, comprising: matching a current approval flow corresponding to the pending approval task according to a task type identifier of the pending approval task and a preset approval flow matching rule; matching an upgraded approval flow corresponding to the current approval flow based on a current approval requirement of the current approval flow and a task requirement of the pending approval task; and performing a reversal operation on the current approval flow according to the approval execution status of the upgraded approval flow to complete the execution of the pending approval task.

[0005] According to an embodiment of the present disclosure, before matching the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule, it further includes: querying the to-be-approved task at the current moment; parsing the task type identifier matching the to-be-approved task.

[0006] According to an embodiment of the present disclosure, in the process of matching the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule, it includes: matching the approval process label corresponding to the task type identifier according to the preset approval process matching rule; querying the current approval process corresponding to the to-be-approved task according to the approval process label.

[0007] According to an embodiment of the present disclosure, before matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it further includes: parsing the field parsing result of the to-be-approved task before executing the current approval process; determining the task requirement degree of the to-be-approved task according to the field parsing result.

[0008] According to an embodiment of the present disclosure, in the process of matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it includes: when the current approval requirement degree is less than the task requirement degree, screening multiple process approval nodes of the current approval process to generate the upgraded approval process; when the current approval requirement degree is greater than the task requirement degree, executing the current approval process.

[0009] According to an embodiment of the present disclosure, in the process of screening multiple process approval nodes of the current approval process to generate the upgraded approval process when the current approval requirement degree is less than the task requirement degree, it includes: screening at least one intermediate process approval node matching the task requirement degree according to the node permission information of the multiple process approval nodes; combining the other process approval nodes after screening the at least one intermediate process approval node to generate the upgraded approval process.

[0010] According to an embodiment of the present disclosure, in the process of executing the current approval process, it includes: querying the current approval time of the current process approval node of the current approval process; when the current approval time is greater than the first time threshold, initiating a prompt operation to the current process approval node; querying the current prompt time of the current process approval node corresponding to the prompt operation; when the current prompt time is greater than the second time threshold, matching the first updated approval process corresponding to the current approval process.

[0011] According to an embodiment of the present disclosure, in the first updated approval process that matches the current approval process, it includes: querying a backup process approval node whose node permission information is consistent with that of the current process approval node; combining the backup process approval node and multiple process approval nodes corresponding to the current approval process after screening out the current process approval node to generate the first updated approval process; wherein, the approval time threshold corresponding to each process approval node in the first updated approval process is less than the approval time threshold corresponding to each process approval node in the current approval process, and the prompt time threshold corresponding to each process approval node in the first updated approval process is less than the prompt time threshold corresponding to each process approval node in the current approval process.

[0012] According to an embodiment of the present disclosure, after matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it further includes: querying the current approval time of the current process approval node of the upgraded approval process; when the current approval time is greater than the third time threshold, initiating a prompt operation to the current process approval node; querying the current prompt time of the current process approval node corresponding to the prompt operation; when the current prompt time is greater than the fourth time threshold, matching the second updated approval process corresponding to the upgraded approval process.

[0013] According to an embodiment of the present disclosure, in the second updated approval process that matches the upgraded approval process, it includes: querying a backup process approval node whose node permission information is consistent with that of the current process approval node; combining the backup process approval node and multiple process approval nodes corresponding to the upgraded approval process after screening out the current process approval node to generate the second updated approval process; wherein, the approval time threshold corresponding to each process approval node in the second updated approval process is less than the approval time threshold corresponding to each process approval node in the upgraded approval process, and the prompt time threshold corresponding to each process approval node in the second updated approval process is less than the prompt time threshold corresponding to each process approval node in the upgraded approval process.

[0014] According to an embodiment of the present disclosure, in the process of performing a rollback operation on the current approval process according to the approval execution status of the upgraded approval process to complete the execution of the to-be-approved task, it includes: when the approval execution status of the upgraded approval process is the end status, rolling back and executing the current approval process; generating a rollback execution result corresponding to the approval execution result of the upgraded approval process.

[0015] According to an embodiment of the present disclosure, in the process of rolling back and executing the current approval process, it includes: monitoring the rollback execution time of the current approval process; when the rollback execution time exceeds the fifth time threshold, ending the rollback of the current approval process.

[0016] The second aspect of the present disclosure provides an apparatus for executing a task to be approved based on approval flow configuration, including a current approval flow matching module, an upgraded approval flow matching module, and a current approval flow reversal module. The current approval flow matching module is configured to match the current approval flow corresponding to the task to be approved according to the task type identifier of the task to be approved and a preset approval flow matching rule; the upgraded approval flow matching module is configured to match the upgraded approval flow corresponding to the current approval flow based on the current approval requirement degree of the current approval flow and the task requirement degree of the task to be approved; and the current approval flow reversal module is configured to perform a reversal operation on the current approval flow according to the approval execution status of the upgraded approval flow, so as to complete the execution of the task to be approved.

[0017] The third aspect of the present disclosure provides an electronic device, including: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the above-mentioned method for executing a task to be approved based on approval flow configuration.

[0018] The fourth aspect of the present disclosure further provides a computer-readable storage medium, on which executable instructions are stored, and when the instructions are executed by a processor, the processor is caused to execute the above-mentioned method for executing a task to be approved based on approval flow configuration.

[0019] The fifth aspect of the present disclosure further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the above-mentioned method for executing a task to be approved based on approval flow configuration is implemented.

[0020] The present disclosure provides a method, apparatus, device, medium, and program product for executing a to-be-approved task based on approval flow configuration. Among them, the method for executing a to-be-approved task based on approval flow configuration includes: matching a current approval flow corresponding to the to-be-approved task according to a task type identifier of the to-be-approved task and a preset approval flow matching rule; matching an upgraded approval flow corresponding to the current approval flow based on a current approval requirement degree of the current approval flow and a task requirement degree of the to-be-approved task; and performing a rollback operation on the current approval flow according to an approval execution status of the upgraded approval flow to complete the execution of the to-be-approved task. Therefore, compared with the traditional method in the prior art where the approval flow configuration is fixed and further approval optimization cannot be achieved, the above method for executing a to-be-approved task based on approval flow configuration in the embodiments of the present disclosure can, on the basis of the current approval flow of the approval flow configuration, further generate an upgraded approval flow by self-identifying the to-be-approved task, significantly simplify the approval process through the upgraded approval flow, further speed up the approval speed, and ensure the execution of the original approval process by rolling back the current approval flow. It can ensure the accuracy of the approval as much as possible on the basis of accelerating the approval, reduce the approval error rate caused by accelerating the approval, and thus achieve the execution optimization of the task approval process on the basis of the approval flow configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Through the following description of the embodiments of the present disclosure with reference to the drawings, the above content and other objects, features, and advantages of the present disclosure will become clearer. In the drawings:

[0022] Figure 1 Schematically shows an application scenario diagram of a method, apparatus, device, medium, and program product for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure;

[0023] Figure 2 Schematically shows a flowchart of a method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure;

[0024] Figure 3A Schematically shows a flowchart of the execution process of the current approval flow in the method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure;

[0025] Figure 3B Schematically shows a scenario diagram of the execution process of the upgraded approval flow in the method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure;

[0026] Figure 4 Schematically shows a scenario diagram of the rollback process of the approval flow execution in the method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure;

[0027] Figure 5Schematically shows a structural block diagram of an apparatus for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure; and

[0028] Figure 6 Schematically shows a block diagram of an electronic device suitable for implementing a method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure. Detailed implementation manners

[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the following detailed description, for the sake of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is obvious that one or more embodiments can also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present disclosure.

[0030] The terms used herein are merely for describing specific embodiments and are not intended to limit the present disclosure. The terms "including", "comprising", etc. used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

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

[0032] In cases where expressions similar to "at least one of A, B, and C, etc." are used, generally, it should be interpreted according to the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include, but not be limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).

[0033] Although the existing electronic approval and circulation system can achieve a high degree of reuse of approval processes for different approval tasks through approval process configuration and maintain system stability during the modification process of approval process nodes, the newly formed approval process can basically not be changed during the subsequent approval process. In other words, the approval information of this approval business is fixed through the configuration of one approval process, forming a fixed approval process for this approval business. In other words, the approval information of this approval business submitted this time determines the approval process configuration of this approval process. During the execution of the approval process, it will be difficult to further adjust the approval process and process nodes. Therefore, for the approval information of an approval business that has been submitted and should be an urgent approval business, but is mis-matched to the ordinary approval process configuration and the approval process is executed, only the approval can be submitted again and the process approval of repeated nodes can be carried out, which seriously affects the urgent approval efficiency of this approval business, increases the complexity of approval circulation, and is not conducive to the modern office requirements of process simplicity, speed, and high speed. In addition, for such an ordinary approval process configuration, if it is temporarily necessary to speed up the processing, only the approvers of each process node can be urged one by one, and an effective accelerated approval plan cannot be realized.

[0034] To solve the technical problem in the prior art that the execution of the approval process cannot be accelerated due to the fixed approval process configuration and cannot well meet the diverse modern office requirements, the present disclosure provides a method, device, equipment, medium, and program product for executing a to-be-approved task based on approval process configuration, which can significantly improve the automated approval speed of to-be-approved tasks and optimize the approval process execution process.

[0035] It should be noted that the above-mentioned method and device for executing a to-be-approved task based on approval process configuration in the embodiments of the present disclosure can be used in the fields of Internet of Things technology and big data technology, and can also be used in the financial field and any field outside the financial field. The application fields of the method and device for executing a to-be-approved task based on approval process configuration in the embodiments of the present disclosure are not limited.

[0036] In the technical solution of the present disclosure, the processing of data such as user personal information, including collection, storage, use, processing, transmission, provision, disclosure, and application, all comply with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and public order and good customs are not violated. Among them, before obtaining or collecting user personal information, the authorization or consent of the user is obtained.

[0037] Embodiments of the present disclosure provide a method for executing a to-be-approved task based on approval flow configuration, including: matching a current approval flow corresponding to the to-be-approved task according to a task type identifier of the to-be-approved task and a preset approval flow matching rule; matching an upgraded approval flow corresponding to the current approval flow based on a current approval requirement degree of the current approval flow and a task requirement degree of the to-be-approved task; and performing a rollback operation on the current approval flow according to an approval execution status of the upgraded approval flow to complete the execution of the to-be-approved task.

[0038] Figure 1 Schematically shows an application scenario diagram of a method, apparatus, device, medium, and program product for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure.

[0039] As Figure 1 shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0040] Users can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0041] The terminal devices 101, 102, 103 may be various electronic devices with a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop portable computers, and desktop computers, etc.

[0042] The server 105 may be a server providing various services, such as a background management server that supports websites browsed by users using the terminal devices 101, 102, 103 (only as an example). The background management server may analyze and process data such as received user requests, and feedback the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0043] It should be noted that the method for executing a to-be-approved task based on approval flow configuration provided in the embodiments of the present disclosure can generally be executed by the server 105. Correspondingly, the device for executing a to-be-approved task based on approval flow configuration provided in the embodiments of the present disclosure can generally be set in the server 105. The method for executing a to-be-approved task based on approval flow configuration provided in the embodiments of the present disclosure can also be executed by a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and / or the server 105. Correspondingly, the device for executing a to-be-approved task based on approval flow configuration provided in the embodiments of the present disclosure can also be set in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and / or the server 105.

[0044] It should be understood that Figure 1 the numbers of terminal devices, networks, and servers in

[0045] are merely illustrative. According to the implementation requirements, there can be any number of terminal devices, networks, and servers. Figure 1 The following will be based on Figures 2 to 6 the described scenario, and will describe in detail the method for executing a to-be-approved task based on approval flow configuration of the disclosed embodiments through

[0046] Figure 2 FIG. schematically shows a flowchart of the method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure.

[0047] As Figure 2 shown, the method for executing a to-be-approved task based on approval flow configuration of this embodiment includes operations S201 to S203.

[0048] In operation S201, according to the task type identifier of the to-be-approved task and the preset approval flow matching rule, match the current approval flow corresponding to the to-be-approved task;

[0049] In operation S202, based on the current approval requirement degree of the current approval flow and the task requirement degree of the to-be-approved task, match the upgraded approval flow corresponding to the current approval flow; and

[0050] In operation S203, according to the approval execution status of the upgraded approval flow, perform a rollback operation on the current approval flow to complete the execution of the to-be-approved task.

[0051] The to-be-approved task can be a business task of an electronic approval service file in the form of a report, and can contain the business information to be approved. Among them, the electronic approval service file can be an application file in the xml format, and can generate or display through an electronic approval system the to-be-approved information to be executed after being parsed.

[0052] In an embodiment of the present disclosure, when each task to be approved is received by the corresponding task receiving module of the system, the user who submits the task to be approved can directly select or provide an approval identifier of the corresponding task to be approved through the display page of the display device of the system. This approval identifier can be used as the above-mentioned task type identifier to identify the approval execution type of the task to be approved at the current moment, such as the task order type, transaction type, or even the position permission type. The preset approval flow matching rule is a matching rule for the corresponding relationship between the task type identifier and the corresponding preset approval flow, and is used to match the preset approval flow corresponding to the task type identifier through the task type identifier as the current approval flow of the task to be approved corresponding to the task type identifier at the current moment.

[0053] Among them, each preset approval flow sets the corresponding approval process nodes and the approval transfer logic of these process nodes during the approval process of the corresponding task to be approved, so that when the task to be approved executes the approval according to the preset approval flow, the corresponding process approval process can be smoothly realized without other corresponding manual intervention. The current approval flow is the preset approval flow matched according to the above-mentioned preset approval flow matching rule and corresponding to the task to be approved at the current moment. Therefore, through the above-mentioned task type identifier, the user can very conveniently submit the task to be approved, and combined with the preset approval flow matching rule, the corresponding current approval flow can be quickly and effectively matched for the task to be approved at the current moment.

[0054] Furthermore, each matched preset approval flow corresponds to a different approval requirement degree. The approval requirement degree is a parameter reflecting the requirement information of the approval execution scenario of the preset approval flow, and can specifically be a numerical value, which can be used to reflect the corresponding approval requirement information such as the urgency during the execution of the preset approval flow. The number of process nodes and the approval execution logic of the process nodes of the preset approval flows with different approval requirement degrees are correspondingly different. Generally, the higher the approval requirement degree, the fewer the process node data corresponding to the preset approval flow, and the simpler the approval execution logic. Correspondingly, the current approval requirement degree is the approval requirement information parameter of the corresponding current approval flow to reflect the approval requirement information of the current approval flow.

[0055] In an embodiment of the present disclosure, corresponding to the current approval requirement degree of the above-mentioned current approval process, a corresponding task requirement degree is also set for the to-be-approved task of the current approval process. The task requirement degree is a parameter for reflecting the requirement information of the approval execution scenario of the to-be-approved task. Specifically, it can be the same setting rule as the approval requirement degree, and the two can perform corresponding matching operations, so as to establish a corresponding relationship between the requirement information of the to-be-approved task and the requirement information of the approval scenario corresponding to the current approval process. Among them, the higher the task requirement degree, the higher the corresponding approval process requirement degree of the to-be-approved task, the fewer the process node data of the corresponding approval process, and the simpler the approval execution logic. It should be noted that usually, when a user submits a to-be-approved task to the system, it is often difficult to well understand the high or low requirement of the task requirement degree of the to-be-approved task submitted by oneself, or the system has too few selection contents displayed to the user on the submission page due to its own limitations, which often leads to the mismatch between the task requirement degree of the to-be-approved task and the current approval requirement degree of the current approval process. This easily causes ordinary approval tasks to often execute the accelerated approval process, while the urgent approval tasks that need to be accelerated are instead in the ordinary approval process, resulting in a waste of approval resources. Moreover, the fixed configuration of the existing approval process often cannot adaptively adjust the approval process, which causes the to-be-approved tasks with mis-matched approval processes to only be resubmitted for approval, and the process approval of repeated nodes is carried out, seriously affecting the urgent approval efficiency of the approval business, increasing the complexity of approval transfer, and being not conducive to the modern office requirements of process simplicity, rapidity, and high speed.

[0056] Therefore, according to the correspondence between the current approval requirement degree of the above-mentioned current approval process and the task requirement degree of the task to be approved, the approval process of the task to be approved whose current approval requirement degree and task requirement degree cannot be well matched can be adjusted. In other words, on the basis of matching the approval process configuration of the current approval process, the process nodes and process approval execution logic of the approval process for the task to be approved entering the approval execution operation process are further changed. Among them, the upgraded approval process is the approval process formed after changing based on the current approval process. This approval process can change some process nodes and process approval execution logic of the current approval process. These changes generally can only simplify or streamline the current approval process. For example, some intermediate approval nodes are deleted, and the process logic involving loop approval is modified into a simple serial approval logic, etc. The upgraded approval process can be regarded as an approval upgrade of the current approval process. This upgraded approval process has fewer process nodes, simpler process approval logic, and faster approval execution speed. Naturally, the corresponding upgraded approval requirement degree is higher than the current approval requirement degree. In other words, for the task to be approved, its approval process is directly upgraded from the original complex current approval process to the upgraded approval process with a more simplified approval process. By implementing the approval of the task to be approved through the upgraded approval process, it is naturally possible to freely and flexibly modify the fixed approval process configuration during the approval execution process, thereby accelerating the approval speed and adapting to the business approval scenarios that require faster approval speed. Therefore, through the upgraded approval process, the further optimization of the approval process can be achieved, the approval process can be accelerated, approval resources can be saved, the change of the approval process configuration is realized, and it can better meet the increasingly high requirements of diverse modern business approvals.

[0057] In the embodiments of the present disclosure, during the process of matching the new upgraded approval process to execute accelerated approval for the task to be approved on the basis of the current approval process, for the original current approval process, the approval execution of the original task to be approved can continue to be maintained to ensure the normal approval operations of each node of the original current approval process, and at the same time, it can also ensure that the task to be approved can be quickly approved through the upgraded approval process. Or, in the case of a large number of approval business processes, the original current approval process can also abort or suspend the approval execution of the current approval process during the execution of the upgraded approval process to save the occupancy of the current approval resources of the system and ensure the orderly and efficient approval execution process of the electronic approval system. Therefore, during the approval process of the task to be approved for the upgraded approval process, the execution process status of the upgraded approval process is queried and monitored to determine its approval execution status. That is, this approval execution status is the approval execution process status of the upgraded approval process for the task to be approved, which can be "approval in progress", "approval ended", etc., and can be specifically marked by corresponding codes or fields.

[0058] When the approval execution status is the end of approval, a corresponding response instruction can be generated according to the tag field of the approval execution status. In response to the response instruction, the original current approval flow of the upgraded approval flow can be reversed. Reversal can be understood as the end of the execution of the upgraded approval flow, the callback of the original approval flow, and the approval process of the pending approval task of the original current approval flow. In this way, the approval execution of the current approval flow of the original pending approval task can be continued while saving the current approval resource occupation of the system, so as to ensure the normal approval operation of each node of the original current approval flow, prevent the occurrence of approval errors caused by the accelerated execution of the upgraded approval flow, realize the execution review of the upgraded approval flow, and at the same time ensure that the pending approval task can be quickly approved through the upgraded approval flow.

[0059] Therefore, compared with the traditional method in the prior art where the approval flow configuration is fixed and further approval optimization cannot be achieved, the above-mentioned method for executing pending approval tasks based on approval flow configuration in the embodiment of the present disclosure can further generate an upgraded approval flow by further self-identifying the pending approval business tasks on the basis of the current approval flow of the approval flow configuration. The upgraded approval flow can significantly simplify the approval process and further speed up the approval speed. Moreover, by reversing the current approval flow, the execution of the original approval process can be ensured. On the basis of speeding up the approval, the accuracy of the approval can be guaranteed as much as possible, and the approval error rate caused by speeding up the approval can be reduced, thereby realizing the execution optimization of the task approval process based on the approval flow configuration.

[0060] Figure 3A A flowchart schematically shows a current approval flow execution process in a method for executing tasks to be approved based on approval flow configuration according to an embodiment of the present disclosure; Figure 3B A scene diagram schematically shows the process of executing the upgrading approval flow in the method for executing tasks to be approved based on the approval flow configuration according to an embodiment of the present disclosure; Figure 4 The scene diagram of the approval flow execution reversal process in the method for executing tasks to be approved based on approval flow configuration according to an embodiment of the present disclosure is schematically shown.

[0061] like Figures 2 - 4 As shown, according to an embodiment of the present disclosure, before matching the current approval flow corresponding to the task to be approved according to the task type identifier of the task to be approved and the preset approval flow matching rule in operation S201, it also includes:

[0062] Query the pending approval tasks at the current moment;

[0063] The task type identifier that matches the task to be approved is parsed.

[0064] In the embodiments of the present disclosure, for an electronic approval system, the same user can submit multiple tasks to be approved through a submission page. However, these multiple tasks to be approved are generally input into the system at different times. Therefore, in response to the user's operation of submitting a task start form, the task to be approved at the current moment can be confirmed, and then the task to be approved corresponding to the current moment can be queried from all the tasks to be approved received by the system from this user to obtain the task to be approved. Specifically, reference can be made to operation S301. Herein, the current moment can be understood as the moment corresponding to the operation of submitting the task start form by the user this time.

[0065] After receiving the task to be approved, perform a parsing operation on the electronic approval business document of the task to be approved, so as to be able to determine the task type identifier of the task to be approved and its corresponding information to be approved and other approval-related contents.

[0066] Thereby, it can be realized to simply and quickly determine the task type identifier of the task to be approved, which helps to match and configure the current approval process of the task to be approved through the task type identifier.

[0067] The execution of the task order approval of the task to be approved is generally mainly composed of process nodes such as task start and transfer approval. Specifically, the process control configuration transformation will involve the configuration of node information parameters. The node information parameters include the corresponding node parameters of the business type, transaction type, and position information. Specifically, parameters such as the first-level classification, major reason, minor reason, transaction type, involved institutions, the number of positions in each institution, level, and permissions are extracted into a parameter configuration data table. Provide parameter configuration data table parameter maintenance services, and at the same time add double-key verification to ensure the correctness of the parameter configuration. Abstract actions such as the closing, returning, canceling, invalidating, saving, and transferring to a higher-level institution of the task order into different service units, dynamically combine them into corresponding approval process configuration services according to the position permission parameters, and automatically match the task order transfer approval process according to the institution and position levels.

[0068] As Figures 2 - 4 shown, according to the embodiments of the present disclosure, in the operation S201 of matching the current approval process corresponding to the task to be approved according to the task type identifier of the task to be approved and the preset approval process matching rule, it includes:

[0069] According to the preset approval process matching rule, match the approval process label corresponding to the task type identifier:

[0070] Query the current approval process corresponding to the task to be approved according to the approval process label.

[0071] After obtaining the corresponding task to be approved and its corresponding task type identifier, the approval flow label that matches the task type identifier is determined through a preset approval flow matching rule. The approval flow label is the matching label of a preset approval flow adapted to the preset approval flow matching rule. Different approval flow labels are used to reflect different approval process types of the preset approval flow. The approval process type is used to define the approval-related types of the preset approval flow, such as multi-level approval types, peer-to-peer approval types, and other content related to the approval execution logic. Specifically, for the application scenario of the multi-level approval type, such as the task to be approved proposed by the user in the handling position of the secondary sub-organization, it needs to be approved by the supervisor and person in charge of the secondary sub-organization, and then by the handling position, supervisor, and person in charge of the primary sub-organization, which is the superior of the secondary sub-organization, and finally by the handling position, supervisor, and person in charge of the head office. In other words, according to different institutional authority levels, the approval rights levels of different positions in the same institution are serially approved; for the application scenario of the peer-to-peer approval type, such as the task to be approved proposed by the user in the handling position of Company A, it needs to be approved by the supervisor and person in charge of Company A at the same time, and then by the handling position, supervisor, and person in charge of Institution B and Institution C, which are at the same level as Company A. In other words, according to the peer-to-peer authority level, the approval rights levels of different positions in the same institution are institutionally approved in parallel. Among them, the corresponding other approval types can also include the approval types in the above serial and parallel hybrid modes, which will not be elaborated here. It should be noted that the above institutions can be companies, units, enterprises, schools, etc., or a certain organization or department among them.

[0072] The preset approval flow matching rule can be constructed in the form of a data table based on the mapping relationship between the task type identifier - approval flow label - preset approval flow. Therefore, after obtaining the approval flow label of the task to be approved, the corresponding preset approval flow can be determined as the current approval flow adapted to the task to be approved by performing a query operation in a data table or other files according to this mapping relationship. For details, see operation S302. It can be seen that compared with the traditional method of generating an approval flow by flexibly combining process nodes according to the task to be approved, in this case, the matching of the current approval flow (that is, the process node string, rather than a single process node) can be directly achieved, so that the approval flow can be retrieved faster and more accurately, and the approval execution logic corresponding to the approval type of the task to be approved can be defined, avoiding the problem of incorrect configuration of process nodes in the traditional method.

[0073] Therefore, by setting the preset approval flow configuration rule, the rapid and accurate configuration of the current approval flow can be realized, preventing the situation of incorrect configuration of process nodes in the traditional method.

[0074] In another embodiment of the present disclosure, the approval process configuration method may also configure business approval data based on the start node of the process approval, and then further perform matching acquisition node by node, and finally form a business approval process.

[0075] Specifically, first obtain the start node, which is used to determine the business data to be approved. According to the flow direction and configuration habits of general business approval processes, first obtain the start node that is a necessary element for approval process configuration. This start node is used to determine the business data to be approved. The permission attributes of the start nodes corresponding to different business approval processes may be different, that is, the start nodes of different business approval processes can receive some or all of the business approval requests initiated by users. The start node is the node used to receive the business approval requests initiated by users.

[0076] After that, obtain one or more approval nodes, which are used to review the business data to be approved. After obtaining the start node of the business approval process, at this time, it is necessary to select the corresponding approval node according to this start node. This approval node is used to review the business data to be approved at the above-mentioned start node. According to different actual needs, there may be different numbers of approval nodes, and the specific number of approval nodes is not limited here.

[0077] Then, configure the approval nodes, where the types of approval nodes are hierarchical relationship nodes, position relationship nodes, or user relationship nodes. After obtaining the approval nodes of the business approval process as described above, at this time, the types of the approval nodes can be configured. Assume that the types of approval nodes include these three types: hierarchical relationship nodes, position relationship nodes, and user relationship nodes. The hierarchical relationship node is used to indicate that this approval node will be parsed according to the hierarchical relationship of the enterprise organizational structure. The position relationship node indicates that this approval node will be parsed according to the position relationship of the enterprise organizational structure. The user relationship node indicates that this approval node will be parsed according to specific users. The hierarchical relationship node or the position relationship node can be regarded as a kind of variable user, which is a variable.

[0078] Further, obtain the end node, which is used to end the review of the business data to be approved. After configuring all the obtained approval nodes, that is, after configuring all the specific approval nodes according to the actual needs of business review, the end node can be obtained after the last approval node. This end node is used to end the review of this business data to be approved.

[0079] After that, use transfer lines to connect the start node, one or more approval nodes, and the end node in sequence to obtain the business approval process. After obtaining the end node of the business approval process as described above, all the nodes in all the necessary elements of the business approval process have been obtained. At this time, transfer lines can be used to connect the start node, one or more approval nodes, and the end node in sequence to obtain the business approval process. The so-called transfer lines are used to indicate the flow of business data in the business approval process from one node to another. Transfer lines are used to record the flow relationship between two nodes, recording the flow from one node to another. When designing the business approval process, the node relationship information will be stored in a database table, and then when the business approval process runs, starting from the start node, the upstream and downstream relationships of the nodes are searched, and the nodes are connected through this relationship to form a business approval process. Specifically, the data structure stored in the database table is as follows: each node is a record, and each transfer line is also a record. The approval permission configuration information will be recorded on the node record, and the transfer conditions, the IDs of the start node and the target node connected by the line, etc. will be recorded on the transfer line. Subsequently, through this information, the specific approval route can be parsed when the business approval process runs.

[0080] Therefore, the process of configuring the approval nodes of the business approval process can configure various approval nodes. According to each approval node, when docking to implement the configuration of the business approval process using approval nodes with variable element properties, multiple business approval processes can be configured at one time. However, compared with the overall matching generation of the above-mentioned approval process, after actual implementation, due to the limitations of the operation and maintenance management technology of the existing system, there will still be a situation where the matching of approval nodes is not accurate enough, thus affecting the corresponding approval configuration management efficiency.

[0081] As Figures 2 - 4 shown, according to an embodiment of the present disclosure, before matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task in operation S202, it further includes:

[0082] Before executing the current approval process, parse the field parsing result of the to-be-approved task;

[0083] Determine the task requirement degree of the to-be-approved task according to the field parsing result.

[0084] Pending approval tasks can perform business transmission operations in the electronic approval system in the form of electronic approval business documents. Among them, the pending approval information for each pending approval task is defined at the time of form submission through operations such as manual filling by the user for this business approval, such as approval event information (such as leave application, payment request, etc.), user identity information (such as name, level or permission, age, employee number, etc.), approval description information (such as approval reasons like pregnancy, illness, customer business requirements, etc.), and approval level information (such as general, medium, urgent, special, etc. approval levels). A fixed field information library can be established for the above-mentioned pending approval information, that is, different pending approval information is defined through different fields. Among them, the fields can be codes composed of numbers, letters, or even Chinese characters. For example, 100 represents pregnancy, 200 represents illness, etc.

[0085] Furthermore, different fields represent different approval information, defining corresponding approval events, approval descriptions, approval levels, and user identities, etc. In the embodiments of the present disclosure, the processing data form of the electronic approval system can be an electronic approval business document in xml format. Among them, the xml format file is a data file of an extensible markup language similar to an html file, mainly used for data or information transmission. Specifically, a document object is created, and a write operation of the document object is executed on the system to form an xml format file. Among them, the xml format file can include an xml version parser and encoding, and the corresponding API can be <Document.DocumenHelper.createrDocument>. Furthermore, a string corresponding to the fields of the pending approval information that conforms to the above xml file format is created, and the above string is output and converted into an xml file. Then, the existing xml file is loaded into the system memory to form an inverted tree structure, where the root is the document object. The name of the root node of the root is obtained, and the number and name of the direct child nodes under the root node are obtained. The node attribute values of all root nodes and the content of the child nodes under all root nodes are parsed, so that the field content of the corresponding pending approval information can be parsed. These field contents can constitute the above-mentioned field parsing result. That is, after completing the parsing operation of the electronic approval business document corresponding to the above pending approval task, the pending approval information can be parsed to generate a field parsing result. See operation S303.

[0086] When establishing the relationship between these field parsing results and different approval requirement degrees in the field information database, it is possible to query the corresponding task requirement degree of the to-be-approved task in the field information database according to the field parsing result of the to-be-approved task. Among them, the field parsing result can also be determined by one of the above to-be-approved information. For example, for the matter of pregnancy leave, the field information database can directly match the high approval requirement degree of the emergency approval process for the leave approval task that meets this event. Similarly, for some special cases that require accelerated processing, the task approval requirement degree can also be matched only through the field parsing result. For details, refer to operation S304.

[0087] In this way, it is possible to identify and confirm the task requirement degree of the current approval of the to-be-approved task. By simply identifying some specific fields in the to-be-approved information of the current to-be-approved task, the specific parameter size of the task requirement degree of the current approval can be confirmed. Thus, based on the approval process configuration, through the enhanced identification of the approval information of the to-be-approved task, the fields that meet the corresponding approval requirement degree can be identified, and the task requirement degree of the to-be-approved task can be determined through these fields.

[0088] Therefore, based on the execution of the approval process configuration, the embodiments of the present disclosure can further autonomously identify the approval information of the to-be-approved task of the current approval process, thereby further identifying the task requirement degree of the to-be-approved task. Based on this task requirement degree, it can be determined whether the corresponding to-be-approved task needs to perform an approval process upgrade operation, that is, on the basis of the execution or suspension of the original current approval process, a new and more simplified execution process of the upgraded approval process is further created, so as to accelerate the approval speed of the to-be-approved task of the current approval process from the system perspective.

[0089] As Figures 2 - 4 shown, according to the embodiments of the present disclosure, in the operation S202 of matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it includes:

[0090] When the current approval requirement degree is less than the task requirement degree, screen multiple process approval nodes of the current approval process to generate the upgraded approval process;

[0091] When the current approval requirement degree is greater than the task requirement degree, execute the current approval process.

[0092] In operation S305, when the current approval requirement degree of the current approval process corresponding to the task to be approved is less than the task requirement degree of the task to be approved, it indicates that the urgency of the approval execution for the current approval process is less than the urgency of the approval execution required for the task to be approved. That is, there are too many process nodes in the approval execution of the current approval process, and the process flow execution logic is too complex, which is not conducive to meeting the urgent execution requirements of the task to be approved. In other words, the task requirement degree of the task to be approved does not match the current approval requirement degree of the current approval process. This requires considering screening multiple process approval nodes of the current approval process. The main purpose of the screening process is to simplify the process nodes and process flow execution logic of the existing current approval process to form a new upgraded approval process for matching the task to be approved that needs to be executed urgently at the current moment. For details, see operations S311, S351, and S401. At this time, for the originally executed current approval process, the approval execution can be aborted or paused first.

[0093] On the contrary, when the current approval requirement degree of the current approval process corresponding to the task to be approved is greater than the task requirement degree of the task to be approved, it indicates that the urgency of the approval execution for the current approval process is greater than the urgency of the approval execution required for the task to be approved. That is, the number of process nodes in the approval execution of the current approval process is not many, and the process flow execution logic is not complex either, which meets the execution requirements of the task to be approved. In other words, the task requirement degree of the task to be approved matches the current approval requirement degree of the current approval process. In this case, there is no need to consider screening and simplifying multiple process approval nodes of the current approval process. Just continue to execute according to the process nodes and process flow execution logic of the current approval process. For details, see operation S306. That is, the original current approval process can continue to execute the task to be approved.

[0094] Therefore, through the creation of the above-mentioned upgraded approval process, it is possible to only increase and not decrease the approval urgency of the current approval process. Since the upgraded approval process is generated on the basis of simplifying the process nodes and flow logic of the current approval process, it is possible to accelerate the approval of the tasks to be approved in the current approval process, and it can also not affect the approval operations of the original current approval process. In this way, compared with the situation where the free combination of process nodes in the existing approval process configuration leads to large resource occupancy and is prone to combination configuration errors, it is possible to simplify the existing current approval process with an existing execution logic to obtain an upgraded approval process, thereby greatly saving resource occupancy, reducing the error rate of approval process configuration, greatly accelerating the approval speed, and ensuring the accuracy of approval.

[0095] As Figures 2 - 4 shown, according to an embodiment of the present disclosure, when the current approval requirement degree is less than the task requirement degree, screening multiple process approval nodes of the current approval process to generate the upgraded approval process includes:

[0096] Screen at least one intermediate process approval node that matches the task requirement degree according to the node permission information of the multiple process approval nodes;

[0097] Combine the other process approval nodes after screening the at least one intermediate process approval node to generate the upgraded approval flow.

[0098] For each process approval node in the current approval flow, the node permission information can be the approval permission content of the corresponding process approval node, which is used to reflect the approval position corresponding to this process approval node. For example, in the same organization, the node permission information of the process approval node corresponding to the operator is low permission, the node permission information of the process approval node corresponding to the supervisor is medium permission, the node permission information of the process approval node corresponding to the person in charge is high permission, and the node permission information of the process approval node corresponding to the general person in charge is the highest permission. That is, for the approval process of the same organization, it needs to go through the serial approval of operator - supervisor - person in charge - general person in charge in sequence before it is considered approved. The intermediate approval process node is the approval node between the starting approval process node and the ending approval process node defined in the current approval flow. For example, in the approval flow of operator - supervisor - person in charge - general person in charge in the above serial approval, the supervisor and the person in charge are regarded as intermediate approval process nodes.

[0099] When the current approval requirement degree is less than the task requirement degree, the current approval requirement degree of the current approval flow does not match the task requirement degree of the to - be - approved task. Therefore, according to the size of the task requirement degree of the to - be - approved task, delete the corresponding number of intermediate process approval nodes in each organization corresponding to the current approval flow of the parallel approval type, or delete the corresponding number of intermediate process approval nodes in the current approval flow of the serial approval type. For example, delete at least one of the intermediate process nodes of "supervisor - person in charge" in the current approval flow of "operator - supervisor - person in charge - general person in charge" of Organization A, and at the same time, correspondingly delete at least one of the intermediate process nodes of "supervisor - person in charge" in the current approval flow of "operator - supervisor - person in charge - general person in charge" of Organization B; or, delete all the process nodes involving the first - level subsidiary in the serial approval flow of second - level subsidiary - first - level subsidiary - head office, or some of the intermediate process nodes in the second - level subsidiary and the head office together with the first - level subsidiary as intermediate process nodes, so as to realize the screening and simplification of the current approval flow. Among them, the number of deleted intermediate process nodes can be determined specifically according to the size of the task requirement degree.

[0100] Further, based on the simplified screening operation of the current approval process, the remaining other process approval nodes of the current approval process are combined and configured according to the execution order of the approval nodes defined by the original process flow execution logic of the current approval process, so as to generate an upgraded approval process based on the simplified operation of the current approval process. Among them, the starting approval node of the upgraded approval process can be the execution node for field parsing of the to-be-approved task involved in the current approval process.

[0101] In this way, compared with the situation where the free combination of process nodes in the existing approval process configuration leads to large resource occupation and easy combination configuration errors, an upgraded approval process can be obtained by simply simplifying the current approval process with existing execution logic, thereby greatly saving resource occupation, reducing the error rate of approval process configuration, greatly accelerating the approval speed, and ensuring the accuracy of approval.

[0102] As Figures 2 - 4 shown, according to the embodiments of the present disclosure, in the execution of the current approval process, it includes:

[0103] Query the current approval time of the current process approval node of the current approval process;

[0104] When the current approval time is greater than the first time threshold, initiate a prompt operation to the current process approval node;

[0105] Query the current prompt time of the current process approval node corresponding to the prompt operation;

[0106] When the current prompt time is greater than the second time threshold, match the first updated approval process corresponding to the current approval process.

[0107] In operations S307 - S310, during the execution of the current approval process, for each process approval node, it is necessary to push the approval person of the corresponding approval position, and push the node to the corresponding approval person. The process approval node corresponding to the current approval person's push can be used as the current process approval node of the to-be-approved task.

[0108] For the approval person of each approval position, the corresponding approval time can be calculated since the operation of pushing the approval node is executed, and this approval time is used as the total required approval time of the approval person for the corresponding process approval node. For example, 24 hours or longer, etc., and specifically, it can be matched and set according to the position authority, etc., and no specific limitation is made here. The current approval time is the time elapsed for the real-time approval of the to-be-approved task at the current process approval node. The approval time threshold is the maximum approval limit time required by the approval person set for each process approval node. The first time threshold is the maximum approval limit time required by the approval person for the corresponding current process approval node.

[0109] When the current approval time of the approver of the current process approval node exceeds the first time threshold, it means that the approver has not completed the approval operation of the current process approval node within the specified approval time limit. At this time, a prompt operation can be performed on the current process approval node based on this, such as sending text messages, emails, pop-up windows when the computer is turned on, and voice messages. That is, the prompt operation is a reminder operation to the approver to perform the approval.

[0110] Accordingly, for each approver in each approval position, the corresponding prompt time can be calculated from the execution of the operation that initiates the prompt operation. The prompt time is used as the total prompt response time required for the approver of the corresponding process approval node, such as 24 hours or longer, etc. It can be specifically matched and set according to the position authority, etc., and no specific restrictions are made here. The current prompt time is the time that has passed after the real-time prompt operation of the current process approval node for the task to be approved. The prompt time threshold is the maximum prompt feedback limit time required by the approver set for each process approval node. The second time threshold is the maximum prompt feedback limit time required by the approver of the corresponding current process approval node.

[0111] When the current prompt time of the approver of the current process approval node exceeds the second time threshold, it means that the approver has not completed the approval operation of the current process approval node within the specified limit prompt time as feedback for the prompt operation. At this time, a new approval flow can be generated as the first update approval flow according to the current process approval node of the current approval flow to achieve the replacement and update of the current process approval node of the current approval flow. Among them, the first update approval flow is a replacement approval flow for the current approval flow, and the current process approval node and its subsequent nodes that cannot continue to perform approval within the specified time are uniformly replaced. In addition, in order to make up for the first time threshold and the second time threshold delayed by the current process approval node, the approval time threshold and the prompt time threshold of other subsequent approval nodes in the first update approval flow are adaptively reduced, so as to ensure that the overall approval process of the pending approval task corresponding to the current approval flow is not delayed too long. At the same time, the original current approval flow is terminated, the execution of the current approval flow is ended, and the pending approval task is subsequently approved only through the approval process defined by the first update approval flow.

[0112] Therefore, by generating the first updated approval flow, the current process approval nodes that cannot effectively perform approval execution operations are skipped. Furthermore, by reducing the subsequent approval time threshold and prompt time threshold of the first updated approval flow, it can ensure that the overall approval time of the pending approval task is almost the same as the approval execution time of the original current approval flow, thereby ensuring that the pending approval task can be successfully completed within the predetermined time range.

[0113] likeFigures 2 - 4 As shown, according to an embodiment of the present disclosure, in the first update approval flow corresponding to the matching current approval flow, it includes:

[0114] Querying a standby process approval node having the same node authority information as the current process approval node;

[0115] Combining the standby process approval node and a plurality of process approval nodes corresponding to the current approval flow after the current process approval node is screened out, to generate the first update approval flow;

[0116] Among them, the approval time threshold corresponding to each process approval node in the first update approval flow is smaller than the approval time threshold corresponding to each process approval node in the current approval flow, and the prompt time threshold corresponding to each process approval node in the first update approval flow is smaller than the prompt time threshold corresponding to each process approval node in the current approval flow.

[0117] The standby process approval node is a standby node corresponding to the current process approval node. Specifically, the standby process approval node and the current approval process node have the same approval position authority. There may be multiple approvers who can perform the approval operation that meets the approval position authority. The approver corresponding to the standby process approval node is inconsistent with the approver corresponding to the current approval process node. In the case that the current process approval node cannot continue to approve effectively, the approver corresponding to the current process approval node is queried and replaced in sequence according to the set standby order, thereby forming a new standby process approval node.

[0118] The above-mentioned backup process approval node and the multiple process approval nodes of the remaining current approval flow after the original current process approval node is filtered out are combined to generate the corresponding first updated approval flow. At the same time, during the combination process, the approval time threshold and the prompt time threshold of each process approval node corresponding to the multiple process approval nodes of the remaining current approval flow after the original current process approval node is filtered out are reduced, so that the approval time and prompt time delayed by the above-mentioned current process approval node can be effectively compensated, thereby maintaining the approval time of the overall approval process within a reasonable set range. That is, the approval time threshold corresponding to the backup process approval node in the first updated approval flow is less than the first time threshold, and the corresponding prompt time threshold is less than the second time threshold. Specifically, the approval time and prompt time of each process approval node in the first updated approval flow can be adjusted according to the corresponding overall time range.

[0119] Therefore, by generating the first updated approval flow, the skipping of the current process approval node that cannot effectively perform the approval execution operation during the execution of the current approval flow is completed. Further, by reducing the subsequent approval time threshold and the prompt time threshold of the first updated approval flow, it can be ensured that the overall approval time of the task to be approved is almost the same as the approval execution time range of the original current approval flow, thus ensuring that the task to be approved can be successfully completed within the predetermined time range. Finally, when generating the first updated approval flow, terminating the approval execution of the original current approval flow can significantly reduce the system resource occupancy and ensure that the approval execution of the system is more stable and efficient.

[0120] As Figures 2 - 4 shown, according to the embodiments of the present disclosure, after matching the upgraded approval flow corresponding to the current approval flow based on the current approval requirement degree of the current approval flow and the task requirement degree of the task to be approved in operation S202, it further includes:

[0121] Query the current approval time of the current process approval node of the upgraded approval flow;

[0122] When the current approval time is greater than the third time threshold, initiate a prompt operation to the current process approval node;

[0123] Query the current prompt time of the current process approval node corresponding to the prompt operation;

[0124] When the current prompt time is greater than the fourth time threshold, match the second updated approval flow corresponding to the upgraded approval flow.

[0125] Corresponding to the above execution operation of the current approval flow, in operations S312 - S315, during the execution of the upgraded approval flow, for each process approval node, it is necessary to push the corresponding approval person of the approval position, and push the node to the corresponding approval person. The process approval node pushed by the corresponding current approval person can be used as the current process approval node of the task to be approved.

[0126] For the approval person of each approval position, the corresponding approval time can be calculated since the operation of pushing the approval node is executed, and this approval time is used as the total required approval time of the approval person of the corresponding process approval node, such as 24 hours or longer, etc. Specifically, it can be matched and set according to the position authority, etc., and no specific limitation is made here. The current approval time is the time elapsed for the real-time approval of the task to be approved at the current process approval node. The approval time threshold is the maximum approval limit time required by the approval person set for each process approval node. The first time threshold is the maximum approval limit time required by the approval person of the corresponding current process approval node.

[0127] When the current approval time of the approver of the current process approval node exceeds the third time threshold, it means that the approver has not completed the approval operation of the current process approval node within the specified limited approval time. At this time, a prompt operation can be performed on the current process approval node based on this, such as sending a text message, sending an email, a pop-up window when the computer is turned on, and a voice message. That is, the prompt operation is a reminder operation to the approver to perform the approval.

[0128] Accordingly, for each approver in each approval position, the corresponding prompt time can be calculated from the execution of the operation that initiates the prompt operation. The prompt time is used as the total prompt response time required for the approver of the corresponding process approval node, such as 24 hours or longer, etc. It can be specifically matched and set according to the position authority, etc., and no specific restrictions are made here. The current prompt time is the time that has passed after the real-time prompt operation of the current process approval node for the task to be approved. The prompt time threshold is the maximum prompt feedback limit time required by the approver set for each process approval node. The second time threshold is the maximum prompt feedback limit time required by the approver of the corresponding current process approval node.

[0129] When the current prompt time of the approver of the current process approval node exceeds the fourth time threshold, it means that the approver has not completed the approval operation of the current process approval node within the specified limit prompt time as feedback for the prompt operation. At this time, a new approval flow can be generated as the second update approval flow according to the current process approval node of the upgrade approval flow to achieve the replacement and update of the current process approval node of the upgrade approval flow. Among them, the second update approval flow is a replacement approval flow for the upgrade approval flow, and the current process approval node and its subsequent nodes that cannot continue to perform approval within the specified time are uniformly replaced. In addition, in order to make up for the first time threshold and the second time threshold delayed by the current process approval node, the approval time threshold and the prompt time threshold of other subsequent approval nodes in the second update approval flow are adaptively reduced, so as to ensure that the overall approval process of the pending approval task of the entire corresponding upgrade approval flow is not delayed too long. At the same time, the original upgrade approval flow is terminated, the execution of the upgrade approval flow is ended, and the pending approval task is subsequently approved only through the approval process defined by the second update approval flow.

[0130] Therefore, by generating the second updated approval flow, the current process approval node that cannot effectively perform the approval execution operation is skipped. Furthermore, by reducing the subsequent approval time threshold and prompt time threshold of the second updated approval flow, it can ensure that the overall approval time of the pending approval task is almost the same as the approval execution time of the original upgraded approval flow, thereby ensuring that the pending approval task can be successfully completed within the predetermined time range.

[0131] like Figures 2 - 4As shown, according to an embodiment of the present disclosure, in the second update approval flow corresponding to the matching upgrade approval flow, it includes:

[0132] Querying a standby process approval node having the same node authority information as the current process approval node;

[0133] Combining the standby process approval node and a plurality of process approval nodes corresponding to the upgrade approval flow after the current process approval node is excluding, to generate the second update approval flow;

[0134] Among them, the approval time threshold corresponding to each process approval node in the second update approval flow is smaller than the approval time threshold corresponding to each process approval node in the upgrade approval flow, and the prompt time threshold corresponding to each process approval node in the second update approval flow is smaller than the prompt time threshold corresponding to each process approval node in the upgrade approval flow.

[0135] The standby process approval node is a standby node corresponding to the current process approval node. Specifically, the standby process approval node and the current approval process node have the same approval position authority. There may be multiple approvers who can perform the approval operation that meets the approval position authority. The approver corresponding to the standby process approval node is inconsistent with the approver corresponding to the current approval process node. In the case that the current process approval node cannot continue to approve effectively, the approver corresponding to the current process approval node is queried and replaced in sequence according to the set standby order, thereby forming a new standby process approval node.

[0136] The above-mentioned backup process approval node and the remaining multiple process approval nodes of the upgrade approval flow after the original current process approval node is filtered out are combined to generate the corresponding second update approval flow. At the same time, during the combination process, the approval time threshold and prompt time threshold of each process approval node corresponding to the remaining multiple process approval nodes of the upgrade approval flow after the original current process approval node is filtered out are reduced, so that the approval time and prompt time delayed by the above-mentioned current process approval node can be effectively compensated, thereby maintaining the approval time of the overall approval process within a reasonable set range. That is, the approval time threshold corresponding to the backup process approval node in the second update approval flow is less than the third time threshold, and the corresponding prompt time threshold is less than the fourth time threshold. Specifically, the approval time and prompt time of each process approval node in the second update approval flow can be adjusted according to the corresponding overall time range.

[0137] Therefore, through the generation of the second updated approval flow, the current process approval node that cannot effectively perform the approval execution operation during the execution of the upgrade approval flow is skipped. Further, by reducing the subsequent approval time threshold and the prompt time threshold of the second updated approval flow, it can be ensured that the overall approval time of the task to be approved is almost the same as the approval execution time range of the original upgrade approval flow, thus ensuring that the task to be approved can be successfully completed within the predetermined time range. Finally, when generating the second updated approval flow, terminating the approval execution of the original upgrade approval flow can significantly reduce the system resource occupancy and ensure that the approval execution of the system is more stable and efficient.

[0138] It should be noted that those skilled in the art should understand that: for the execution of the current approval flow, if corresponding process approval nodes still cannot be smoothly approved during the approval execution process of forming the first updated approval flow, a new third updated approval flow can be further formed on the basis of the first updated approval flow until the approval of the task to be approved is completed, which will not be elaborated here; correspondingly, for the execution of the upgrade approval flow, if corresponding process approval nodes still cannot be smoothly approved during the approval execution process of forming the second updated approval flow, a new fourth updated approval flow can be further formed on the basis of the second updated approval flow until the approval of the task to be approved is completed, which will not be elaborated here. In other words, the Figures 3A - 4 application scenario cases and their corresponding explanatory content shown can only be used as illustrations of specific embodiments to enable those skilled in the art to quickly and accurately master the technical solutions of the present disclosure, and cannot be used as a limitation of the scope of protection claimed by the present disclosure.

[0139] As Figures 2 - 4 shown, according to the embodiments of the present disclosure, in the operation S203 of performing a rollback operation on the current approval flow according to the approval execution status of the upgrade approval flow to complete the execution of the task to be approved, it includes:

[0140] When the approval execution status of the upgrade approval flow is the end status, rollback and execute the current approval flow;

[0141] Generate a rollback execution result corresponding to the approval execution result of the upgrade approval flow.

[0142] In operations S352 and S402, for the execution of the upgrade approval process, if the corresponding approval execution status is the end status, it indicates that the execution of the upgrade approval process has been completed, and the pending approval task has completed the preliminary approval. At this time, a corresponding response instruction can be generated according to the marking field corresponding to the end status of the approval execution status. In response to this response instruction, the original current approval process of the upgrade approval process can be reversed. Reversal can be understood as the end of the execution of the upgrade approval process, and the original current approval process in the suspended or paused execution state is called back to continue the approval process of the pending approval task of the original current approval process.

[0143] Through the original current approval process, continue to perform the approval execution of the pending approval task for each process approval node according to the original process approval transfer execution logic, so as to generate a reversal execution result corresponding to the approval execution result of the upgrade approval process in the end state. Among them, the approval execution result is the approval result information corresponding to the pending approval task of the upgrade approval process. The approval result information includes result event information such as passing, not passing, intermediate termination of approval, intermediate suspension of approval, etc. corresponding to the upgrade approval process, and includes approval opinion information left by the approvers of each node, etc. The reversal execution result is the approval result information corresponding to the pending approval task of the current approval process. The approval result information includes result event information such as passing, not passing, intermediate termination of approval, intermediate suspension of approval, etc. corresponding to the current approval process, and includes approval opinion information left by the approvers of each node, etc.

[0144] Therefore, by comparing the approval execution results and reversal execution results of the two approval processes, the approval result information that does not exist in the approval execution results can be analyzed to extract the approval opinions and approval result events of the approvers missing in the corresponding upgrade approval process, so as to make a final judgment on whether the approval execution result is further issued for execution, so as to ensure the approval accuracy of the pending approval task, reduce the approval error rate, and improve the approval management efficiency while accelerating the approval process of the pending approval task.

[0145] In this way, the approval execution of the current approval process of the original pending approval task can be continued while saving the occupation of the current approval resources of the system, so as to ensure the normal approval operations of each node of the original current approval process, prevent the occurrence of approval errors caused by the accelerated execution of the upgrade approval process, realize the execution review of the upgrade approval process, and at the same time ensure that the pending approval task can be quickly approved through the upgrade approval process.

[0146] It should be noted that in operation S316, after the execution of the second update approval process corresponding to the upgrade approval process ends, the corresponding rollback execution of the original upgrade approval process for the current approval process will also be executed accordingly. In other words, as long as the approval process is upgraded and simplified for the current approval process, after the simplified upgrade approval process and its corresponding update approval process are completed for approval, the rollback execution of the current approval process needs to be performed.

[0147] As Figures 2 - 4 shown, according to an embodiment of the present disclosure, in the rollback execution of the current approval process, it includes:

[0148] Monitoring the rollback execution time of the current approval process;

[0149] When the rollback execution time exceeds the fifth time threshold, end the rollback of the current approval process.

[0150] In operations S403 - S405, for the rollback execution of the current approval process, the corresponding rollback execution time can be set. The rollback execution time is the overall actual execution time required for all unexecuted process approval nodes in the current approval process to successfully complete all approval executions when the current approval process is called back. That is, if there are three unexecuted process approval nodes in the current approval process for executing the approval of the to-be-approved task, then the actual execution time consumed after these three process approval nodes complete the execution of the to-be-approved task.

[0151] The fifth time threshold is the maximum execution limit time that all unexecuted process approval nodes in the current approval process can provide when completing all approval executions. Therefore, the fifth time threshold corresponding to the rollback execution time can be specifically set with reference to the approval time of each process approval node and the threshold of the prompt time, combined with the time threshold for the issuance and execution of the approval execution result of the completed upgrade approval process corresponding to the current approval process.

[0152] To ensure the smooth issuance of the approval execution result of the completed upgrade approval process, the rollback execution time of the current approval process for rollback execution shall not exceed the fifth time threshold to meet the continued execution of the current approval process to obtain the corresponding rollback execution result. However, if the rollback execution time of the current approval process for rollback execution exceeds the fifth time threshold, then to ensure the smooth issuance of the approval execution result of the completed upgrade approval process, it is necessary to terminate the rollback execution operation of the current approval process and obtain the corresponding rollback execution result of the rollback execution.

[0153] Therefore, by means of the rollback execution time limit of the rollback execution of the above-mentioned current approval process, it is possible to obtain the rollback execution result of the current approval process corresponding to the upgrade approval process as much as possible under the condition of ensuring that the approval execution result of the to-be-approved task that has been accelerated through the upgrade approval process is not delayed, so as to realize the rollback review of the approval information of the approval execution result of the accelerated approval, ensure the accuracy of the approval as much as possible, reduce the approval error rate caused by accelerating the approval, and thus realize the execution optimization of the task approval process on the basis of the approval process configuration.

[0154] Obviously, compared with the traditional method in the prior art where the approval process configuration is fixed and further approval optimization cannot be achieved, the above-mentioned method for executing a to-be-approved task based on approval process configuration according to an embodiment of the present disclosure can, on the basis of the current approval process of the approval process configuration, further generate an upgrade approval process by self-identifying the to-be-approved business task, significantly simplify the approval process through the upgrade approval process, further speed up the approval speed, and moreover, ensure the execution of the original approval process by rolling back the current approval process, and can, on the basis of accelerating the approval, ensure the accuracy of the approval as much as possible, reduce the approval error rate caused by accelerating the approval, and thus realize the execution optimization of the task approval process on the basis of the approval process configuration.

[0155] Among them, the time mentioned in the embodiments of the present disclosure can be a time point or a time range, and corresponding judgments can be made according to specific scenarios, and there is no specific limitation.

[0156] Based on the above-mentioned method for executing a to-be-approved task based on approval process configuration, the present disclosure also provides a device for executing a to-be-approved task based on approval process configuration. The following will be combined with Figure 5 Describe this device in detail.

[0157] Figure 5 The structural block diagram of a device for executing a to-be-approved task based on approval process configuration according to an embodiment of the present disclosure is schematically shown.

[0158] As Figure 5 shown, the device 800 for executing a to-be-approved task based on approval process configuration in this embodiment includes a current approval process matching module 510, an upgrade approval process matching module 520, and a current approval process rollback module 530.

[0159] The current approval process matching module 510 is configured to match the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and a preset approval process matching rule. In one embodiment, the current approval process matching module 510 can be used to execute the operation S201 described above, which will not be elaborated here.

[0160] The upgrade approval flow matching module 520 is configured to match the upgrade approval flow corresponding to the current approval flow based on the current approval requirement degree of the current approval flow and the task requirement degree of the to-be-approved task. In one embodiment, the upgrade approval flow matching module 520 may be configured to perform the operation S202 described above, which will not be elaborated herein.

[0161] The current approval flow reversal module 530 is configured to perform a reversal operation on the current approval flow according to the approval execution status of the upgrade approval flow, so as to complete the execution of the to-be-approved task. In one embodiment, the current approval flow reversal module 530 may be configured to perform the operation S203 described above, which will not be elaborated herein.

[0162] According to an embodiment of the present disclosure, any multiple modules among the current approval flow matching module 510, the upgrade approval flow matching module 520, and the current approval flow reversal module 530 may be combined and implemented in one module, or any one of the modules may be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules may be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the current approval flow matching module 510, the upgrade approval flow matching module 520, and the current approval flow reversal module 530 may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on chip, a system on substrate, a system on package, an application specific integrated circuit (ASIC), or any other reasonable manner that can integrate or package circuits, etc., implemented by hardware or firmware, or implemented in any one of the three implementation manners of software, hardware, and firmware, or in any appropriate combination of several of them. Alternatively, at least one of the current approval flow matching module 510, the upgrade approval flow matching module 520, and the current approval flow reversal module 530 may be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0163] Figure 6 A block diagram of an electronic device suitable for implementing a method for executing a to-be-approved task based on approval flow configuration according to an embodiment of the present disclosure is schematically shown.

[0164] As Figure 6As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general microprocessor (such as a CPU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (such as an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include on-board memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0165] In the RAM 603, various programs and data required for the operation of the electronic device 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flow according to an embodiment of the present disclosure by executing the programs in the ROM 602 and / or the RAM 603. It should be noted that the program may also be stored in one or more memories other than the ROM 602 and the RAM 603. The processor 601 may also perform various operations of the method flow according to an embodiment of the present disclosure by executing the programs stored in the one or more memories.

[0166] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, and the input / output (I / O) interface 605 is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read from it can be installed into the storage section 608 as needed.

[0167] The present disclosure also provides a computer-readable storage medium, which may be included in the device / device / system described in the above embodiments; or may exist separately without being assembled into the device / device / system. The above computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to an embodiment of the present disclosure is implemented.

[0168] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the above-described ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603.

[0169] An embodiment of the present disclosure further includes a computer program product, which includes a computer program that contains program code for executing the method shown in the flowchart. When the computer program product runs in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0170] When the computer program is executed by the processor 601, it executes the above functions defined in the system / apparatus of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0171] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices and magnetic storage devices. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and be downloaded and installed through the communication part 609, and / or be installed from the removable medium 611. The program code included in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0172] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or be installed from the removable medium 611. When the computer program is executed by the processor 601, it executes the above functions defined in the system of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, devices, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0173] According to embodiments of the present disclosure, program code for executing the computer programs provided by the embodiments of the present disclosure may be written in any combination of one or more programming languages. Specifically, these computing programs may be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. The programming languages include, but are not limited to, such as Java, C++, Python, the "C" language, or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., by connecting through the Internet using an Internet service provider).

[0174] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

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

[0176] The embodiments of the present disclosure have been described above. However, these embodiments are merely for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments have been described separately above, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and these substitutions and modifications should all fall within the scope of the present disclosure.

Claims

1. A method for executing a task to be approved based on approval process configuration, wherein, Including: Matching the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule; Based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, matching the upgraded approval process corresponding to the current approval process; And According to the approval execution status of the upgraded approval process, performing a rollback operation on the current approval process to complete the execution of the to-be-approved task; Wherein, in the matching of the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it includes: when the current approval requirement degree is less than the task requirement degree, screening multiple process approval nodes of the current approval process to generate the upgraded approval process; when the current approval requirement degree is greater than the task requirement degree, executing the current approval process; Wherein, in the screening of multiple process approval nodes of the current approval process to generate the upgraded approval process when the current approval requirement degree is less than the task requirement degree, it includes: screening out at least one intermediate process approval node that matches the task requirement degree according to the node permission information of the multiple process approval nodes; combining the other process approval nodes after screening out the at least one intermediate process approval node to generate the upgraded approval process.

2. The method according to claim 1, wherein, Before matching the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule, it further includes: Querying the to-be-approved task at the current moment; Parsing the task type identifier that matches the to-be-approved task.

3. The method according to claim 1, wherein, In the matching of the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule, it includes: Matching the approval process label corresponding to the task type identifier according to the preset approval process matching rule; Querying the current approval process corresponding to the to-be-approved task according to the approval process label.

4. The method according to claim 1, wherein, Before matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it further includes: Before executing the current approval process, parsing the field parsing result of the to-be-approved task; Determining the task requirement degree of the to-be-approved task according to the field parsing result.

5. The method according to claim 1, wherein, In the execution of the current approval process, it includes: Querying the current approval time of the current process approval node of the current approval process; When the current approval time is greater than the first time threshold, initiating a prompt operation to the current process approval node; Querying the current prompt time corresponding to the prompt operation of the current process approval node; When the current prompt time is greater than the second time threshold, matching the first updated approval process corresponding to the current approval process.

6. The method according to claim 5, wherein, In the matching of the first updated approval process corresponding to the current approval process, it includes: Query for standby process approval nodes whose node permission information is the same as that of the current process approval node of the current process; combine the standby process approval nodes and the multiple process approval nodes corresponding to the current approval process after screening out the current process approval node to generate the first updated approval process; Among them, the approval time threshold corresponding to each process approval node in the first updated approval process is less than the approval time threshold corresponding to each process approval node in the current approval process, and the reminder time threshold corresponding to each process approval node in the first updated approval process is less than the reminder time threshold corresponding to each process approval node in the current approval process.

7. The method according to claim 1, wherein, After matching the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task, it further includes: Query the current approval time of the current process approval node of the upgraded approval process; When the current approval time is greater than the third time threshold, initiate a reminder operation to the current process approval node; Query the current reminder time of the current process approval node corresponding to the reminder operation; When the current reminder time is greater than the fourth time threshold, match the second updated approval process corresponding to the upgraded approval process.

8. The method according to claim 7, wherein In the matching of the second updated approval process corresponding to the upgraded approval process, it includes: Query for standby process approval nodes whose node permission information is the same as that of the current process approval node; Combine the standby process approval nodes and the multiple process approval nodes corresponding to the upgraded approval process after screening out the current process approval node to generate the second updated approval process; Among them, the approval time threshold corresponding to each process approval node in the second updated approval process is less than the approval time threshold corresponding to each process approval node in the upgraded approval process, and the reminder time threshold corresponding to each process approval node in the second updated approval process is less than the reminder time threshold corresponding to each process approval node in the upgraded approval process.

9. The method according to claim 1, wherein In the process of performing a rollback operation on the current approval process according to the approval execution status of the upgraded approval process to complete the execution of the to-be-approved task, it includes: When the approval execution status of the upgraded approval process is the end status, roll back and execute the current approval process; Generate a rollback execution result corresponding to the approval execution result of the upgraded approval process.

10. The method according to claim 1, wherein, In the rollback execution of the current approval process, it includes: Monitor the rollback execution time of the current approval process; When the rollback execution time exceeds the fifth time threshold, end the rollback of the current approval process.

11. An apparatus for executing a to-be-approved task based on approval process configuration, wherein, It includes: A current approval process matching module, used to match the current approval process corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval process matching rule; An upgraded approval process matching module, used to match the upgraded approval process corresponding to the current approval process based on the current approval requirement degree of the current approval process and the task requirement degree of the to-be-approved task; And A current approval process rollback module, used to perform a rollback operation on the current approval process according to the approval execution status of the upgraded approval process to complete the execution of the to-be-approved task; Among them, in the matching of the current approval requirement degree based on the current approval process and the task requirement degree of the to-be-approved task to the upgraded approval process corresponding to the current approval process, it includes: when the current approval requirement degree is less than the task requirement degree, screening multiple process approval nodes of the current approval process to generate the upgraded approval process; when the current approval requirement degree is greater than the task requirement degree, executing the current approval process. Among them, in the screening of multiple process approval nodes of the current approval process to generate the upgraded approval process when the current approval requirement degree is less than the task requirement degree, it includes: screening out at least one intermediate process approval node that matches the task requirement degree according to the node permission information of the multiple process approval nodes; combining the other process approval nodes after screening out the at least one intermediate process approval node to generate the upgraded approval process.

12. An electronic device, comprising: One or more processors; A storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 10.

13. A computer-readable storage medium having executable instructions stored thereon, which when executed by a processor cause the processor to execute the method according to any one of claims 1 to 10.

14. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 10.

Images