CN114707961A - Method, apparatus, device, medium and program product for executing tasks to be approved based on approval flow configuration - Google Patents

Abstract

The present disclosure provides a method for executing a task to be approved based on an approval flow configuration, which can be applied to the technical field of the Internet of Things and the technical field of big data. The method for executing a task to be approved based on an approval flow configuration includes: 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 a preset approval flow matching rule; and based on the current approval flow of the current approval flow The requirement degree and the task requirement degree of the to-be-approved task match the upgrade approval flow corresponding to the current approval flow; and according to the approval execution status of the upgrade approval flow, a reversal operation is performed on the current approval flow to complete all the approval procedures. The task to be approved is executed. The present disclosure also provides an apparatus, device, storage medium and program product for executing a task to be approved based on an approval flow configuration.

Description

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

technical field

The present disclosure relates to the field of computer technologies, and in particular, to a method, apparatus, device, medium and program product for executing a task to be approved based on an approval flow configuration.

Background technique

With the rapid development and wide application of information technology, systematic electronic approval and circulation processes such as business approval, statement approval and document approval have basically been realized for various industries including finance, education, and manufacturing, thus replacing paper delivery. The traditional approval method of submission greatly improves the efficiency of business approval, ensures the transparency of the approval process, increases the accuracy of business approval processing, and can provide real-time review of approval nodes at any time, and the progress of the approval process can be intuitive. master. At present, the commonly used electronic approval circulation system generally provides operation pages that can be used by business personnel. The business personnel can select and fill in the information that needs to be approved through the operation page, and submit the system process for approval and circulation. In addition, further, in order to meet the continuous innovation of the business model 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 aspect of process configurability. Expand to achieve a high degree of reuse of the system and improve the stability of the modification and change process such as the addition and abandonment of approval nodes. However, although the electronic approval circulation system based on the existing process configurability (ie 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 limit its further development applications.

SUMMARY OF THE INVENTION

In view of the above problems, the present disclosure provides a method, apparatus, device, medium and program product for executing a task to be approved based on the configuration of an approval flow, which can improve the automatic approval speed of the task to be approved and optimize the execution process of the approval flow.

According to a first aspect of the present disclosure, a method for executing a task to be approved based on an approval flow configuration is provided, including: matching a task corresponding to the task to be approved according to a task type identifier of the task to be approved and a preset approval flow matching rule 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, matching the upgrade approval flow corresponding to the current approval flow; and according to the approval execution status of the upgrade approval flow, A turnaround operation is performed on the current approval flow to complete the execution of the to-be-approved task.

According to an embodiment of the present disclosure, before matching the current approval flow corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval flow matching rule, the method further includes: querying the to-be-approved task at the current moment ; Parse the task type identifier matching the task to be approved.

According to an embodiment of the present disclosure, in the matching the current approval flow corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval flow matching rule, the method includes: matching the current approval flow corresponding to the to-be-approved task according to the preset approval flow matching rule. The task type identifies a corresponding approval flow label; the current approval flow corresponding to the to-be-approved task is queried according to the approval flow label.

According to an embodiment of the present disclosure, before the current approval requirement degree based on the current approval flow and the task requirement degree of the to-be-approved task match the upgrade approval flow corresponding to the current approval flow, the method further includes: Before describing the current approval flow, the field analysis result of the task to be approved is parsed; the task requirement degree of the task to be approved is determined according to the field analysis result.

According to an embodiment of the present disclosure, in the matching 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, including: when the current approval flow is When the approval requirement degree is less than the task requirement degree, screen multiple process approval nodes of the current approval flow to generate the upgrade approval flow; when the current approval requirement degree is greater than the task requirement degree, execute the current approval flow Approval flow.

According to an embodiment of the present disclosure, when the current approval requirement degree is less than the task requirement degree, filtering multiple process approval nodes of the current approval flow to generate the upgrade approval flow includes: according to the The node authority information of multiple process approval nodes filters out at least one intermediate process approval node that matches the task requirement degree; and combines other process approval nodes after being screened out by the at least one intermediate process approval node to generate the upgrade approval flow.

According to an embodiment of the present disclosure, the executing the current approval flow includes: querying the current approval time of the approval node of the current process of the current approval flow; when the current approval time is greater than a first time threshold, reporting to the current approval flow The process approval node initiates a prompt operation; the current prompt time corresponding to the prompt operation of the current process approval node is queried; when the current prompt time is greater than a second time threshold, the first update approval flow corresponding to the current approval flow is matched.

According to an embodiment of the present disclosure, the matching of the first update approval flow corresponding to the current approval flow includes: querying a standby process approval node that is consistent with the node permission information of the current process approval node; combining the standby processes The approval node and multiple process approval nodes corresponding to the current approval flow after the current process approval node are filtered out to generate the first update approval flow; wherein, each process approval flow in the first update approval flow The approval time threshold corresponding to the node is less 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 less than the The prompt time threshold corresponding to each process approval node in the current approval flow.

According to an embodiment of the present disclosure, after matching 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, the method further includes: querying the Upgrading the current approval time of the current process approval node of the approval flow; when the current approval time is greater than the third time threshold, initiate a prompt operation to the current process approval node; query the current prompt corresponding to the prompt operation of the current process approval node time; when the current prompt time is greater than the fourth time threshold, match the second update approval flow corresponding to the upgrade approval flow.

According to an embodiment of the present disclosure, the matching of the second update approval flow corresponding to the upgrade approval flow includes: querying a standby process approval node that is consistent with the node permission information of the current process approval node; combining the standby processes The approval node and the multiple process approval nodes corresponding to the upgrade approval flow after the current process approval node are filtered out, to generate the second update approval flow; wherein, each process approval flow in the second update approval flow The approval time threshold corresponding to the node is less 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 less than the The prompt time threshold corresponding to each process approval node in the escalation approval flow.

According to an embodiment of the present disclosure, the performing a reversal operation on the current approval flow according to the approval execution state of the upgrade approval flow to complete the execution of the pending approval task includes: when the approval of the upgrade approval flow is approved When the execution state is the end state, the current approval flow is executed in a reversal manner; a reversal execution result corresponding to the approval execution result of the upgrade approval flow is generated.

According to an embodiment of the present disclosure, performing the current approval flow in the reversal includes: monitoring the reversal execution time of the current approval flow; when the reversal execution time exceeds a fifth time threshold, ending the current approval flow 's rotation.

A second aspect of the present disclosure provides an apparatus for executing tasks to be approved based on an approval flow configuration, including a current approval flow matching module, an upgraded approval flow matching module, and a current approval flow reversing module. The current approval flow matching module is used to match the current approval flow corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval flow matching rule; the upgraded approval flow matching module is used to match the current approval flow of the current approval flow based on the current approval flow The approval requirement degree and the task requirement degree of the to-be-approved task match the upgrade approval flow corresponding to the current approval flow; and the current approval flow rotation module is configured to, according to the approval execution status of the upgrade approval flow, perform the approval process for the current approval flow The flow performs a turnaround operation to complete the execution of the pending task.

A third aspect of the present disclosure provides an electronic device, comprising: 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 programs When the processor executes, one or more processors are caused to execute the above-mentioned method for executing the task to be approved based on the approval flow configuration.

A fourth aspect of the present disclosure also provides a computer-readable storage medium storing executable instructions thereon, and when the instructions are executed by the processor, the processor executes the above-mentioned method for executing a task to be approved based on an approval flow configuration.

A fifth aspect of the present disclosure also provides a computer program product, including a computer program, which, when executed by a processor, implements the above-mentioned method for executing a task to be approved based on an approval flow configuration.

The present disclosure provides a method, apparatus, device, medium and program product for executing a task to be approved based on an approval flow configuration. The method for executing a task to be approved based on an approval flow configuration includes: 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 a preset approval flow matching rule; based on the current approval flow of the current approval flow The approval requirement degree and the task requirement degree of the task to be approved match the upgrade approval flow corresponding to the current approval flow; and according to the approval execution status of the upgrade approval flow, a reversal operation is performed on the current approval flow to complete The task to be approved is executed. Therefore, compared with the conventional method in the prior art in which the approval flow configuration is fixed and cannot further realize approval optimization, the above-mentioned method for executing tasks to be approved based on the approval flow configuration according to the embodiment of the present disclosure can be further based on the current approval flow configured in the approval flow. By further self-identifying the tasks to be approved, an upgrade approval flow is generated, the approval process is significantly simplified by upgrading the approval flow, and the approval speed is further accelerated, and the execution of the original approval process is ensured by reversing the current approval flow, which can accelerate the approval process. Ensure the accuracy of approval as much as possible and reduce the approval error rate caused by accelerated approval, so as to optimize the execution of the task approval process based on the approval flow configuration.

Description of drawings

The foregoing and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

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

2 schematically shows a flowchart of a method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure;

3A schematically shows a flow chart of the current approval flow execution process in the method for executing tasks to be approved based on the approval flow configuration according to an embodiment of the present disclosure;

FIG. 3B schematically shows a scenario diagram of upgrading an approval flow execution process in a method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure;

FIG. 4 schematically shows a scenario diagram of an approval flow execution rotation process in the method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure;

FIG. 5 schematically shows a structural block diagram of an apparatus for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure; and

6 schematically shows a block diagram of an electronic device suitable for implementing a method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood, however, that these descriptions are exemplary only, and are not intended to limit the scope of the present disclosure. In the following detailed description, for convenience of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It will be apparent, however, that one or more embodiments may be practiced without these specific details. Also, in the following description, descriptions of well-known structures and techniques are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. The terms "comprising", "comprising" and the like as used herein indicate the presence of stated features, steps, operations and/or components, but do not preclude the presence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. It should be noted that terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly rigid manner.

Where expressions like "at least one of A, B, and C, etc.," are used, they should generally be interpreted in accordance with the meaning of the expression as commonly understood by those skilled in the art (eg, "has A, B, and C") At least one of the "systems" shall include, but not be limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc. ).

Although the existing electronic approval flow system can achieve a high degree of reuse of approval processes for different approval tasks through approval flow configuration, and maintain system stability in the process of modifying and changing the approval process nodes, the new approval flow is used in subsequent approvals. Basically, no changes can be made during the process. In other words, the configuration of one approval process will fix the approval flow of the approval information of this approval business, forming a fixed approval flow for the approval business. In other words, the approval information of the approval business submitted for this approval determines the approval flow configuration of the approval process, and it is difficult to make further adjustments to the approval process and process nodes during the execution of the approval flow. Therefore, for the scenario where the approval information of the submitted approval business should be an emergency approval business, but the wrong match is a common approval flow configuration and the approval process is executed, the approval process can only be resubmitted and the process approval of the duplicate node is performed, which seriously affects the process. The urgent approval efficiency of the approval business increases the complexity of the approval flow, which is not conducive to the modern office needs of simplified, fast and high-speed processes. In addition, if this kind of common approval flow configuration needs to be temporarily accelerated, the approvers of each process node can only be urged one by one, and an effective accelerated approval scheme cannot be realized.

In order to solve the technical problem in the prior art that the execution of the approval flow cannot be accelerated due to the fact that the configuration of the approval flow cannot be changed flexibly, the present disclosure provides an automated approval method that can significantly improve the tasks to be approved. A method, apparatus, device, medium and program product for executing tasks to be approved based on the approval flow configuration that optimizes the speed and execution process of the approval flow.

It should be noted that the above-mentioned method and apparatus for executing tasks to be approved based on the approval flow configuration in the embodiments of the present disclosure can be used in the technical field of the Internet of Things and the technical field of big data, and can also be used in the financial field and any fields other than the financial field. The application fields of the method and apparatus for executing tasks to be approved based on the approval flow configuration of the disclosed embodiments are not limited.

In the technical solutions of the present disclosure, the collection, storage, use, processing, transmission, provision, disclosure and application of data, including user personal information, etc., all comply with relevant laws and regulations, and necessary confidentiality measures have been taken. And it does not violate public order and good morals. Among them, the authorization or consent of the user is obtained before the user's personal information is obtained or collected.

An embodiment of the present disclosure provides a method for executing a task to be approved based on an approval flow configuration, including: matching a current approval flow corresponding to the task to be approved according to a task type identifier of the task to be approved and a preset approval flow matching rule; 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 upgrade approval flow corresponding to the current approval flow; The approval flow performs a reversal operation to complete the execution of the tasks to be approved.

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

As shown in FIG. 1 , an 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 a medium used to provide 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, among others.

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

The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 105 may be a server that provides various services, such as a background management server (just an example) that provides support for websites browsed by users using the terminal devices 101 , 102 , and 103 . The background management server can analyze and process the received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

It should be noted that, the method for executing a task to be approved based on the approval flow configuration provided by the embodiment of the present disclosure may generally be executed by the server 105 . Correspondingly, the apparatus for executing tasks to be approved based on the approval flow configuration provided by the embodiments of the present disclosure may generally be set in the server 105 . The method for executing tasks to be approved based on the approval flow configuration provided by the embodiments of the present disclosure may also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101 , 102 , 103 and/or the server 105 . Correspondingly, the apparatus for executing tasks to be approved based on the approval flow configuration provided by the embodiments of the present disclosure may also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101 , 102 , 103 and/or the server 105 . .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 1 are merely illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Based on the scenario described in FIG. 1 , the method for executing a task to be approved based on an approval flow configuration according to the disclosed embodiment will be described in detail below with reference to FIGS. 2 to 6 .

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

As shown in FIG. 2 , the method for executing a task to be approved based on an approval flow configuration in this embodiment includes operations S201 to S203.

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

In operation S202, matching an 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; and

In operation S203, a reversal operation is performed on the current approval flow according to the approval execution state of the upgrade approval flow, so as to complete the execution of the task to be approved.

A task to be approved may be a business task based on an electronic approval business document in the form of a report, and may contain business information to be approved. Wherein, the electronic approval business file may be an application file in xml format, which can be generated after being parsed or display pending approval information to be approved through the electronic approval system.

In the embodiment of the present disclosure, when each task to be approved is submitted to the corresponding task receiving module of the system for reception, the user who submitted the task to be approved can directly select or provide the corresponding task to be approved through the display page of the display device of the system. The approval identifier of the task, which can be used as the above task type identifier to identify the approval execution type such as task order type, transaction type or even post permission type at the current moment of the task to be approved. The preset approval flow matching rule is a matching rule of the correspondence 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 corresponding preset approval flow. The current approval flow at the current moment of the task to be approved identified by the task type.

Among them, each preset approval flow sets the corresponding approval process node and the approval flow logic of the process node during the approval process for the task to be approved, so that the task to be approved can be smoothly implemented according to the preset approval flow. process approval process without the need for other corresponding manual interventions. The current approval flow is the preset approval flow that matches the task to be approved at the current moment according to the preset approval flow matching rule. Therefore, the above task type identification can make it very convenient for the user to submit the task to be approved, and combined with the preset approval flow matching rules, the corresponding current approval flow can be quickly and effectively matched for the task to be approved at the current moment.

Further, each matching preset approval flow will correspond to a different approval requirement degree, and the approval requirement degree is a parameter that reflects the requirement information of the approval execution scenario of the preset approval flow, and can be a numerical value, which can be used to reflect the requirement. Corresponding approval requirement information such as the urgency of the preset approval flow during the execution process. The number of process nodes of the preset approval flow with different approval requirements and the corresponding approval execution logic of the process nodes are different. Generally, the higher the approval requirement, the less 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, so as to reflect the approval requirement information of the current approval flow.

In the embodiment of the present disclosure, corresponding to the current approval requirement degree of the current approval flow, a corresponding task requirement degree is also set for the to-be-approved task of the current approval flow. The task requirement degree is a parameter used to reflect 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. The two can perform corresponding matching operations, thereby establishing a The corresponding relationship between the requirement information and the approval scenario corresponding to the requirement information of the current approval flow. Among them, the higher the requirement degree of the task, the higher the requirement degree of the corresponding approval flow of the task to be approved, the less process node data corresponding to the approval flow, and the simpler the approval execution logic. It should be noted that, under normal circumstances, when a user submits a task to be approved to the system, it is usually difficult to understand the level of task requirements of the task to be approved, or the system restricts the submission page to display to the user the selection content. If too few, the task requirements of the tasks to be approved often do not match the current approval requirements of the current approval flow, which is easy to cause the accelerated approval process to be executed for ordinary approval tasks, while the urgent approval tasks that require accelerated approval In the ordinary approval process, which results in a waste of approval resources, and the fixed configuration of the existing approval flow is often unable to adapt to the approval process, which results in that the pending approval tasks that incorrectly match the approval flow can only be resubmitted for approval. , process approval for repeated nodes, which seriously affects the emergency approval efficiency of the approval business, increases the complexity of approval flow, and is not conducive to the modern office needs of simplified, fast, and high-speed processes.

Therefore, according to the corresponding relationship between the current approval requirement degree of the current approval flow and the task requirement degree of the to-be-approved task, the approval flow adjustment can be performed for the to-be-approved task whose current approval requirement degree and the task requirement degree cannot well match . In other words, on the basis of the approval flow configuration matching the current approval flow, the process node and the process approval execution logic of the approval flow of the pending task entering the approval execution operation process are further changed. The upgrade approval flow is an approval flow formed after changes are made based on the current approval flow. The approval flow can change some process nodes and process approval execution logic of the current approval flow. Generally, these changes can only simplify or simplify the current approval flow. Simplicity, such as removing some intermediate approval nodes and modifying the process logic involving circular approval to simple serial approval logic, etc. The upgrade approval flow can be regarded as an approval upgrade to the current approval flow. The upgrade approval flow has fewer process nodes, simpler process approval logic, and faster approval execution. Naturally, its corresponding upgrade approval requirement is relatively higher than the current approval requirement. higher degree. In other words, for tasks to be approved, the approval process is directly upgraded from the original complex current approval flow to an upgraded approval flow with a more simplified approval process. The approval of tasks to be approved is realized by upgrading the approval flow, and it is naturally possible to execute the approval process. During the approval process, the fixed approval flow configuration can be modified freely and flexibly, so as to speed up the approval speed and adapt to the business approval scenarios that require faster approval speed. Therefore, by upgrading the approval flow, the approval process can be further optimized, the approval process can be accelerated, the approval resources can be saved, the configuration of the approval flow can be changed, and it can better adapt to the increasingly demanding and diversified modern business approval needs.

In the embodiments of the present disclosure, on the basis of the current approval flow, in the process of matching the new upgraded approval flow for the task to be approved for accelerated approval, for the original current approval flow, the approval execution of the original task to be approved can continue to be maintained. , to ensure the normal approval operation of each node of the original current approval flow, and also to ensure that the tasks to be approved can be quickly approved by upgrading the approval flow. Alternatively, when there are many approval business processes, the original current approval flow can also suspend or suspend the approval execution of the current approval flow during the execution of the upgraded approval flow, so as to save the current approval resources of the system and ensure the orderly electronic approval system. Efficient approval and execution process. Therefore, when the task to be approved completes the approval process of the upgrade approval flow, the execution process status of the upgrade approval flow is queried and monitored to determine its approval execution status. That is, the approval execution status is the approval execution process status of the upgrade approval flow of the task to be approved.

When the approval execution status is the approval end, a corresponding response instruction can be generated according to the marked field of the approval execution status. In response to the response instruction, the original and current approval flow of the upgrade approval flow can be reversed, and the rotation can be understood as an upgrade After the approval flow finishes execution, the original approval flow is called back, and the approval process of the pending tasks in the current approval flow is continued. In this way, the approval execution of the current approval flow of the original to-be-approved task can be continued under the circumstance of 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, and prevent the accelerated execution of the upgrade approval flow from causing problems. In case of approval errors, the implementation review of the upgrade approval flow can be realized, and at the same time, it can also ensure that the tasks to be approved can be quickly approved through the upgrade approval flow.

Therefore, compared with the conventional method in the prior art in which the approval flow configuration is fixed and cannot further realize approval optimization, the above-mentioned method for executing tasks to be approved based on the approval flow configuration according to the embodiment of the present disclosure can be further based on the current approval flow configured in the approval flow. By further self-identifying the tasks to be approved, an upgrade approval flow is generated, the approval process is significantly simplified by upgrading the approval flow, and the approval speed is further accelerated, and the execution of the original approval process is ensured by reversing the current approval flow, which can accelerate the approval process. Ensure the accuracy of approval as much as possible and reduce the approval error rate caused by accelerated approval, so as to optimize the execution of the task approval process based on the approval flow configuration.

Fig. 3A schematically shows a flow chart of the current approval flow execution process in the method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure; Fig. 3B schematically shows an approval flow configuration based on an embodiment of the present disclosure. Figure 4 schematically shows a scene diagram of the approval flow execution rotation process in the method for executing tasks to be approved based on the approval flow configuration according to an embodiment of the present disclosure.

As shown in FIG. 2 to FIG. 4 , according to an embodiment of the present disclosure, before matching the current approval flow corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval flow matching rule in operation S201 , further include:

Query the task to be approved at the current moment;

Parse the task type identifier matching the to-be-approved task.

In the embodiment of the present disclosure, for the electronic approval system, the same user can submit multiple tasks to be approved through the submission page, but these multiple tasks to be approved are generally entered into the system in time-sharing. The single submit operation can confirm the pending tasks at the current moment, and then query the pending tasks at the current moment from all the pending tasks received by the system for the user to obtain the pending tasks. For details, see Operation S301. Wherein, the current time can be understood as the time corresponding to the user's order-taking and submitting operation this time.

After receiving the to-be-approved task, the electronic approval business file of the to-be-approved task is parsed, so that the task type identifier of the to-be-approved task and its corresponding to-be-approved information and other approval-related content can be determined.

Thereby, the task type identifier of the to-be-approved task can be determined simply and quickly, thereby helping to match and configure the current approval flow of the to-be-approved task through the task type identifier.

The task list approval and execution of the task to be approved is generally implemented by process nodes such as order starting and circulation approval. Specifically, the configuration transformation of process control will involve the configuration of node information parameters. The node information parameters include business type, transaction type, and the corresponding node parameters of job information. Specifically, parameters such as primary classification, major cause, minor cause, transaction type, institutions involved, number of positions in each institution, level and authority are extracted to the parameters. configuration data sheet. Provide parameter maintenance service for parameter configuration data table, and increase double-knocking review to ensure the correctness of parameter configuration. It abstracts actions such as statement, refund, revocation, voiding, saving, and transfer of task orders into different service units, and dynamically combines them into corresponding approval flow configuration services according to job authority parameters, and automatically matches tasks according to the organization and job level. Single-transfer approval flow.

As shown in FIG. 2 to FIG. 4 , according to an embodiment of the present disclosure, in operation S201 , the current approval flow corresponding to the task to be approved is matched according to the task type identifier of the task to be approved and the preset approval flow matching rule, including: :

According to the preset approval flow matching rule, match the approval flow label corresponding to the task type identifier:

The current approval flow corresponding to the to-be-approved task is queried according to the approval flow label.

After obtaining the corresponding task to be approved and its corresponding task type identifier, the approval flow label matching the task type identifier is determined by preset approval flow matching rules. The approval flow label is the matching label of the preset approval flow that matches the preset approval flow matching rule. Different approval flow labels are used to reflect different approval process types of the preset approval flow, and the approval process type is used to define the preset Approval-related types of the approval flow, such as multi-level approval types, peer approval types, etc., are related to the approval execution logic. Specifically, for the application scenario of multi-level approval type, such as the pending task proposed by the handling post of the second-level subsidiary, it needs to be approved by the supervisor and person in charge of the second-level subsidiary, and then approved by the superior of the second-level subsidiary. Approved by the handling posts, supervisors and persons-in-charge of the first-level sub-organizations, and finally approved by the handling posts, supervisors and persons-in-charge of the head office with multi-level authority approval. Serial approval is carried out at the authority level; for application scenarios of the same level approval type, such as the pending approval task proposed by the handling post of company A, it needs to be approved by the supervisor and person in charge of company A at the same time, and then approved by the same level of company A. Institution B and Institution C are subject to the same-level structure approval of their respective handling posts, supervisors, and persons-in-charge. Wherein, the corresponding other approval types may also include the above-mentioned approval types in the mixed mode of serial and parallel, which will not be repeated here. It should be noted that the above-mentioned institutions may be companies, units, enterprises, schools, etc., or may be an organization, department, etc. therein.

The preset approval flow matching rule may 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 to-be-approved task, a query operation can be performed in the data table and other files according to the mapping relationship to determine the corresponding preset approval flow as the current approval flow suitable for the to-be-approved task. Specifically, See operation S302. It can be seen that, compared with the existing traditional method of generating approval flow by flexibly combining process nodes according to tasks to be approved, this case can directly realize the matching of the current approval flow (that is, a string of process nodes, rather than a single process node), so as to be able to Call the approval flow faster and more accurately, define the approval execution logic corresponding to the approval type of the task to be approved, and avoid the problem of incorrect configuration of process nodes in the traditional way.

In this way, through the setting of the preset approval flow configuration rules, the current approval flow can be quickly and accurately configured, and the misconfiguration of the process nodes in the traditional method can be prevented.

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

Specifically, a start node is obtained first, and the start node is used to determine the business data to be approved. According to the flow direction and configuration habits of the general business approval flow, first obtain the start node of the necessary elements for the approval flow configuration. The start node is used to determine the business data to be approved. The permission attributes of the start node corresponding to different business approval flows can be different. That is, different service approval flow start nodes can receive some or all of the service approval requests initiated by users, and the start node is a node used to receive service approval requests initiated by users.

After that, one or more approval nodes are obtained, and the approval nodes are used to review the business data to be approved. After obtaining the start node of the business approval flow, the corresponding approval node needs to be selected according to the start node at this time. The approval node is used to review the business data to be approved of the above start node. According to different actual needs, there may be different The number of approval nodes, the specific number of approval nodes is not limited here.

Then, configure the approval node, where the type of the approval node is a hierarchical relationship node, a post relationship node or a user relationship node. After the approval node of the business approval flow is obtained above, the approval node type can be configured at this time, and the types of the approval node include three types: hierarchical relationship node, post relationship node and user relationship node. The hierarchical relationship node is used to indicate that the approval node will be parsed according to the hierarchical relationship of the enterprise organizational structure, the post relationship node indicates that the approval node will be analyzed according to the post relationship of the enterprise organizational structure, and the user relationship node indicates that the approval node will be analyzed according to specific users. . A hierarchical relationship node or a position relationship node can be regarded as a kind of variable user, which is a variable.

Further, an end node is acquired, and the end node is used to end the review of the business data to be approved. After all the obtained approval nodes are configured, that is, after the specific approval nodes are configured according to the actual needs of business review, the end node can be obtained after the last approval node, and the end node is used to end the pending approval. audit of business data.

After that, use the flow line to connect the start node, one or more approval nodes, and the end node in sequence to obtain the business approval flow. After the end node of the business approval flow is obtained above, all the nodes in all the necessary elements of the business approval flow are obtained. At this time, the flow line can be used to connect the start node, one or more approval nodes and the end node in sequence. , you can get the business approval flow. The so-called flow line is used to indicate that the business data of the business approval flow flows from one node to another node. The flow line is used to record the flow relationship between two nodes, from one node to another. When the business approval flow is designed, the node relationship information will be stored in the database table. Then, when the business approval flow is running, it will start from the start node to find the upstream and downstream relationships of the nodes, and connect the nodes through this relationship to build a business approval flow. Specifically, the data structure stored in the database table is: each node is a record, each flow line is also a record, the node record will record the approval authority configuration information, and the flow line will record the flow conditions and the start of the line connection Information such as the ID of the node and the target node. Subsequent to this information, the specific approval line can be parsed when the business approval flow is running.

Therefore, in the approval node configuration process of the business approval flow, various approval nodes can be configured, and when the approval nodes with variable properties are used to configure the business approval flow according to the docking of each approval node, multiple business approval flows can be configured at one time. . However, compared with the overall matching generation of the above approval flow, after the actual implementation, due to the limitations of the operation and maintenance management technology of the existing system, there will still be insufficient matching of approval nodes, thus affecting the corresponding approval configuration management efficiency.

As shown in FIGS. 2 to 4 , according to an embodiment of the present disclosure, 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 current approval flow corresponding to the Before upgrading the approval flow, also include:

Before executing the current approval flow, parse the field parsing result of the task to be approved;

Determine the task requirement degree of the task to be approved according to the field analysis result.

The tasks to be approved can be transferred in the electronic approval system based on the electronic approval business documents, in which, each task to be approved is defined by the user manually filling in the operation for this business approval when the order is submitted. Information to be approved, such as approval event information (such as leave, money, etc.), user identity information (such as name, level or authority, age, job number, etc.), approval explanation information (such as pregnancy, illness, customer business requirements, etc.) ), approval level information (such as normal, medium, urgent, special and other approval levels). For the above information to be approved, a fixed field information base can be established, that is, different information to be approved is defined by different fields, wherein the fields can be codes composed of numbers, letters or even Chinese characters, such as 100 for pregnancy, 200 for sick etc.

Further, different fields represent different approval information, and content such as corresponding approval events, approval descriptions, approval levels, and user identities are defined. In the embodiment of the present disclosure, the processing data form of the electronic approval system may be an electronic approval business file in xml format, wherein the xml format file is a data file in an extensible markup language similar to an html file, and is mainly applied to data or information transmission. Specifically, a document object is created, and the writing operation of the document object is performed to the system to form an xml format file. Wherein, the xml format file may include an xml version parser and encoding, and the corresponding API may be <Document.DocumenHelper.createrDocument>. Further, a character string corresponding to the field corresponding to the information to be approved in the above-mentioned xml file format is created, and the above-mentioned character string output is converted into an xml file. After that, load the existing xml file into the system memory to form an inverted tree structure, in which the root is the document object. Get the name of the root node of the root and get the number and name of the direct child nodes under the root node. The node attribute values of all root nodes and the contents of sub-nodes under all root nodes are parsed, so that the corresponding field contents of the information to be approved can be obtained by parsing, and these field contents can constitute the above-mentioned field parsing result. That is, after the parsing operation of the electronic approval service file corresponding to the task to be approved is completed, the pending approval information may be parsed to generate a field parsing result, see operation S303.

When the relationship between these field analysis results and different approval requirements is established in the field information database, it is possible to query the corresponding task requirements corresponding to the task to be approved in the field information database according to the field analysis results of the task to be approved. Spend. Among them, the field analysis result can also be determined by one of the above-mentioned pending approval information. For example, for the matter of pregnancy leave, the field information database can directly match the leave approval task that matches the event to the corresponding emergency approval flow. As for the approval requirement degree, the task approval requirement degree can also be matched only through the field analysis result for some special needs to be accelerated. For details, see operation S304.

In this way, the identification and confirmation of the task requirement degree of the current approval of the task to be approved can be realized, and the task requirement degree of the current approval can be confirmed only by simply identifying some specific fields in the pending approval information of the current task to be approved. Therefore, based on the configuration of the approval flow, through the enhanced identification of the approval information of the task to be approved, the fields that meet the corresponding approval requirements can be identified, and the task requirements of the to-be-approved task can be evaluated through these fields. Sure.

Therefore, on the basis of the configuration and execution of the approval flow, the embodiments of the present disclosure can further autonomously realize the identification of approval information of the task to be approved in the current approval flow, so that the task requirement degree of the task to be approved can be further identified. To judge whether the corresponding pending approval task needs to be upgraded to the approval flow, that is, on the basis of the execution or suspension of the original current approval flow, a new and simplified execution process of the upgraded approval flow is created, which can speed up the process from a system perspective. The approval speed of the pending tasks in the current approval flow.

As shown in FIG. 2 to FIG. 4 , according to an embodiment of the present disclosure, 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 current approval flow corresponding to the In the escalation approval flow, including:

When the current approval requirement degree is less than the task requirement degree, screening multiple process approval nodes of the current approval flow to generate the upgrade approval flow;

When the current approval requirement degree is greater than the task requirement degree, the current approval flow is executed.

In operation S305, when the current approval requirement degree of the task to be approved that matches the current approval flow is smaller than the task requirement degree of the to-be-approved task, it means that the urgency of the approval execution relative to the current approval flow is less than that required by the to-be-approved task The urgency of the approval execution, that is, the current approval flow has too many process nodes for approval and execution, and the process flow execution logic is too complicated, which is not conducive to meeting the urgent execution requirements of the tasks 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 flow, so it is necessary to consider screening multiple process approval nodes of the current approval flow. The main purpose of the screening process is to simplify the existing The process node of the current approval flow and the flow execution logic of the process flow form a new upgrade approval flow, which is used to match the pending approval task that needs to be executed urgently at the current moment. For details, refer to operations S311, S351 and S401. At this point, for the current approval flow of the original execution, you can abort or suspend the approval execution first.

On the contrary, when the current approval requirement degree of the task to be approved that matches the current approval flow is greater than the task requirement degree of the to-be-approved task, it means that the urgency of the approval execution relative to the current approval flow is greater than the approval execution required by the to-be-approved task. The urgency of the current approval flow, that is, there are not many process nodes for approval and execution in the current approval flow, and the process flow execution logic is not complicated, which meets the execution requirements of the tasks 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 flow, so there is no need to consider the screening and simplification of multiple process approval nodes of the current approval flow. The process node and the process flow execution logic may continue to flow and execute. For details, refer to operation S306. That is, the original and current approval flow can continue to execute the pending approval tasks.

Therefore, by creating the above-mentioned upgrade approval flow, the approval urgency of the current approval flow can only be increased but not lowered. Since the upgrade approval flow is generated on the basis of simplifying the process nodes and flow logic of the current approval flow, this can Accelerates the approval of tasks pending approval in the current approval flow without affecting the approval operation of the original approval flow. In this way, the free combination of process nodes configured in the existing approval flow results in a larger resource occupation and is easy to configure. In the case of errors, only the current approval flow with existing execution logic can be simplified to obtain an upgraded approval flow, which greatly saves resources, reduces the error rate of approval flow configuration, greatly speeds up approval, and ensures the accuracy of approval.

As shown in FIGS. 2-4 , according to an embodiment of the present disclosure, when the current approval requirement degree is less than the task requirement degree, multiple process approval nodes of the current approval flow are screened to generate the upgrade In the approval flow, including:

Filter out at least one intermediate process approval node matching the task requirement degree according to the node authority information of the plurality of process approval nodes;

The upgrade approval flow is generated by combining other process approval nodes screened out by the at least one intermediate process approval node.

For each process approval node in the current approval flow, the node authority information can be the approval authority content of the corresponding process approval node, which is used to reflect the approval position corresponding to the process approval node. The node authority information of the corresponding process approval node is low authority, the node authority information of the process approval node corresponding to the supervisor is medium authority, the node authority information of the process approval node corresponding to the person in charge is high authority, and the process approval node corresponding to the general person in charge The node authority information of the node is the highest authority, that is, the approval process of the same organization needs to go through the serial approval of the manager-supervisor-person-in-charge-general-in-charge in order to be considered approved. The intermediate approval process node is the approval node between the start approval process node and the termination approval process node defined in the current approval flow, such as the approval flow of the above-mentioned serial approval operator-supervisor-person in charge-general in charge, Supervisors and principals are considered intermediate approval process nodes.

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 task requirement degree of the to-be-approved task delete the corresponding number of intermediate process approval nodes in each institution corresponding to the current approval flow of the parallel approval type, or delete the corresponding number of intermediate process approval nodes corresponding to the current approval flow of the serial approval type delete. For example, delete at least one intermediate process node of "Director-Responsible Person" in "Attorney-Supervisor-Person-in-Charge-General Manager" of the current approval flow of Institution A, and correspondingly delete the "Manager-in-charge" of the current approval flow of Institution B. At least one intermediate process node of "Director-Responsible Person" in the "Manager-Supervisor-Responsible Person-General Manager" is deleted; All process nodes involved in the first-level sub-organization or some intermediate process nodes in the second-level sub-organization and the head office are deleted as intermediate process nodes, so as to simplify the screening of the current approval flow. The number of deleted intermediate process nodes may be specifically determined according to the degree of task requirement.

Further, based on the simplified screening operation of the current approval flow, other process approval nodes of the remaining current approval flow are executed according to the approval node execution order defined by the original process flow execution logic of the current approval flow. After the operation, other remaining process approval nodes perform combined configuration operations, so that a corresponding upgrade approval flow based on the simplified operation of the current approval flow can be generated. Wherein, the starting approval node of the upgrade approval flow may be an execution node of field parsing of the to-be-approved task involved in the current approval flow.

In this way, compared to the situation where the free combination of process nodes configured in the existing approval flow results in a large resource occupation and is prone to combination configuration errors, it is possible to simplify the current approval flow with the existing execution logic to obtain an upgraded approval flow, which greatly saves money. Resource occupation, reduce the error rate of approval flow configuration, greatly speed up the approval speed, and ensure the accuracy of approval.

As shown in FIGS. 2-4 , according to an embodiment of the present disclosure, the executing the current approval flow includes:

Query the current approval time of the current process approval node of the current approval flow;

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

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

When the current prompt time is greater than the second time threshold, the first update approval flow corresponding to the current approval flow is matched.

In operations S307-S310, in the process of executing the current approval flow, for each process approval node, it is necessary to push the approver corresponding to the approval position, and the node is pushed to the corresponding approver. The process approval node pushed by the current approver can be used as the current process approval node of the task to be approved.

For the approver of each approval position, the corresponding approval time can be calculated from the execution of the operation of pushing the approval node. The approval time is used as the total required approval time of the approver of the corresponding process approval node, such as 24 hours. Or wait for a longer time, you can set the matching according to the position permissions, etc., and there are no specific restrictions 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 time limit required by the approver set corresponding to each process approval node. The first time threshold is the maximum approval time limit required by the approver of the corresponding current process approval node.

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 limited approval time. At this time, prompt operations can be performed on the current process approval node, such as sending text messages, sending emails, computer startup pop-ups, and voice messages. That is, the prompt operation is a prompt operation for the approver to perform the approval.

Correspondingly, for the approver of each approval position, the corresponding prompt time can be calculated from the execution of the operation that initiates the prompt operation, and the prompt time is used as the total required prompt response time of the approver of the corresponding process approval node. , such as 24 hours or more, which can be matched and set according to the position permissions, etc., and no specific restrictions are imposed here. The current prompt time is the time elapsed 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 corresponding to 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.

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 the feedback of the prompt operation . At this time, a new approval flow may be generated according to the current process approval node of the current approval flow as the first update approval flow, so as to realize the replacement and update of the current process approval node of the current approval flow. Wherein, the first update approval flow is an alternative approval flow of the current approval flow, and the current process approval node and its subsequent nodes for which the current approval flow 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 prompt time threshold of other subsequent approval nodes in the first update approval flow are adaptively reduced and set, so that Ensure that the overall approval process of the tasks to be approved corresponding to the current approval flow is not delayed too long. At the same time, the execution of the original current approval flow is terminated, and the execution of the current approval flow is ended, and the subsequent approval tasks are only approved through the approval process defined by the first update approval flow.

Therefore, through the generation of the first update approval flow, the skipping of the current process approval node that cannot effectively perform the approval execution operation is completed. Further, by reducing the subsequent approval time threshold and prompt time threshold of the first update approval flow, it is possible It is ensured that the overall approval time of the task to be approved is almost the same as the approval execution time of the original current approval flow, thereby ensuring that the task to be approved can be successfully completed within the predetermined time range.

As shown in FIGS. 2-4 , according to an embodiment of the present disclosure, the first update approval flow corresponding to the matching current approval flow includes:

query the standby process approval node that is consistent with the node authority information of the current process approval node;

Combining the standby process approval node and multiple process approval nodes corresponding to the current approval flow after the current process approval node is filtered out, to generate the first update approval flow;

Wherein, 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 in the first update approval flow The prompt time threshold corresponding to each process approval node is smaller than the prompt time threshold corresponding to each process approval node in the current approval flow.

The standby process approval node is the standby node corresponding to the current process approval node. Specifically, the standby process approval node has the same approval post authority corresponding to the current approval process node, and the approver who performs the approval operation that conforms to the approval post authority may have If there are more than one, the approver corresponding to the standby process approval node is inconsistent with the approver corresponding to the current approval process node. Among them, the approvers corresponding to the authority of the same approval position are in accordance with the set standby sequence. If the current process approval node cannot continue to effectively approve the approval, the order of the approvers corresponding to the current process approval node is queried and replaced. Thereby, a new standby process approval node is formed.

A corresponding first update approval flow is generated by combining the above-mentioned standby process approval node and multiple process approval nodes of the remaining current approval flow after screening out the original current process approval node. At the same time, in the combining process, each process approval node in the multiple process approval nodes corresponding to the remaining current approval flow after the original current process approval node is filtered out reduces the approval time threshold and the prompt time threshold, so that the aforementioned current process approval time threshold is reduced. The approval time and prompt time delayed by the process approval node can be effectively compensated, so as to maintain the approval time of the overall approval process within a reasonable set range. That is, the approval time threshold corresponding to the standby process approval node in the first update approval flow is smaller than the first time threshold, and the corresponding prompt time threshold is smaller than the second time threshold. The scope is used to adjust the approval time and prompt time of each process approval node in the first update approval flow.

Therefore, through the generation of the first update 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, and further, the subsequent approval time threshold and prompt of the first update approval flow are completed. The reduction of the time threshold can ensure 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 the first update approval flow is generated, the approval execution of the original current approval flow is terminated, which can significantly reduce the occupation of system resources and ensure that the approval execution of the system is more stable and efficient.

As shown in FIGS. 2 to 4 , according to an embodiment of the present disclosure, 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 current approval flow corresponding to the After upgrading the approval flow, it also includes:

query the current approval time of the current process approval node of the upgrade approval flow;

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

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

When the current prompt time is greater than the fourth time threshold, the second update approval flow corresponding to the upgrade approval flow is matched.

Corresponding to the above execution operation of the current approval flow, in operations S312-S315, in the process of executing the upgrade approval flow, for each process approval node, it is necessary to push the approver of the corresponding approval position, and push the node to the corresponding approval flow. Approver. The process approval node pushed by the current approver can be used as the current process approval node of the task to be approved.

For the approver of each approval position, the corresponding approval time can be calculated from the execution of the operation of pushing the approval node. The approval time is used as the total required approval time of the approver of the corresponding process approval node, such as 24 hours. Or wait for a longer time, you can set the matching according to the position permissions, etc., and there are no specific restrictions 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 time limit required by the approver set corresponding to each process approval node. The first time threshold is the maximum approval time limit required by the approver of the corresponding current process approval node.

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, prompt operations can be performed on the current process approval node, such as sending text messages, sending emails, computer startup pop-ups, and voice messages. That is, the prompt operation is a prompt operation for the approver to perform the approval.

Correspondingly, for the approver of each approval position, the corresponding prompt time can be calculated from the execution of the operation that initiates the prompt operation, and the prompt time is used as the total required prompt response time of the approver of the corresponding process approval node. , such as 24 hours or more, which can be matched and set according to the position permissions, etc., and no specific restrictions are imposed here. The current prompt time is the time elapsed 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 corresponding to 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.

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 the feedback to the prompt operation . At this time, a new approval flow can be generated according to the current process approval node of the upgrade approval flow as the second update approval flow, so as to realize the replacement and update of the current process approval node of the upgrade approval flow. Wherein, the second update approval flow is an alternative approval flow for the upgrade approval flow, and the current process approval node and its subsequent nodes for which the upgrade approval flow 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 approval node of the current process, the approval time threshold and prompt time threshold of other subsequent approval nodes in the second update approval flow are adaptively reduced and set, so that Ensure that the overall approval process of the tasks to be approved corresponding to the upgrade approval flow is not delayed too long. At the same time, the execution of the original upgrade approval flow is terminated, the execution of the upgrade approval flow is ended, and the approval process of the pending approval task is subsequently approved only through the approval flow defined by the second update approval flow.

Therefore, through the generation of the second update approval flow, the skipping of the current process approval node that cannot effectively perform the approval execution operation is completed. It is ensured that the overall approval time of the task to be approved is almost the same as the approval execution time of the original upgrade approval flow, thus ensuring that the task to be approved can be successfully completed within the predetermined time range.

As shown in FIGS. 2-4 , according to an embodiment of the present disclosure, the second update approval flow corresponding to the matching upgrade approval flow includes:

query the standby process approval node that is consistent with the node authority information of the current process approval node;

Combining the standby process approval node and multiple process approval nodes corresponding to the upgrade approval flow after the current process approval node is filtered out, to generate the second update approval flow;

Wherein, 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 in the second update approval flow The prompt time threshold corresponding to each process approval node is smaller than the prompt time threshold corresponding to each process approval node in the upgrade approval flow.

The standby process approval node is the standby node corresponding to the current process approval node. Specifically, the standby process approval node has the same approval post authority corresponding to the current approval process node, wherein, the approver who performs the approval operation that conforms to the approval post authority may have If there are more than one, the approver corresponding to the standby process approval node is inconsistent with the approver corresponding to the current approval process node. Among them, the approvers corresponding to the authority of the same approval position are in accordance with the set standby sequence. If the current process approval node cannot continue to effectively approve the approval, the order of the approvers corresponding to the current process approval node is queried and replaced. Thereby, a new standby process approval node is formed.

A corresponding second update approval flow is generated by combining the above-mentioned standby process approval node and a plurality of process approval nodes for the upgrade approval flow after screening out the original current process approval node. At the same time, in the combining process, each process approval node in the multiple process approval nodes corresponding to the remaining upgrade approval flows after the original current process approval node is filtered out reduces the approval time threshold and the prompt time threshold, so that the aforementioned current process approval node is reduced. The approval time and prompt time delayed by the process approval node can be effectively compensated, so as to maintain the approval time of the overall approval process within a reasonable set range. That is, the approval time threshold corresponding to the standby process approval node in the second update approval flow is smaller than the third time threshold, and the corresponding prompt time threshold is smaller than the fourth time threshold. The scope is used to adjust the approval time and prompt time of each process approval node in the second update approval flow.

Therefore, through the generation of the second update approval flow, the skipping of the current process approval node that cannot effectively perform the approval execution operation during the execution of the upgrade approval flow is completed, and further, the subsequent approval time threshold and prompt of the second update approval flow are completed. The reduction of the time threshold can ensure 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 the second update approval flow is generated, the approval execution of the original upgrade approval flow is terminated, which can significantly reduce the occupation of system resources and ensure that the approval execution of the system is more stable and efficient.

It should be noted that those skilled in the art should understand that: for the execution of the current approval flow, during the approval execution process of forming the first update approval flow, if it is still encountered that the corresponding process approval node cannot perform the approval smoothly, you can On the basis of the first update approval flow, a new third update approval flow is further formed until the approval of the to-be-approved task is completed. During the approval execution process, if the corresponding process approval node still fails to approve the approval smoothly, a new fourth update approval flow can be further formed on the basis of the second update approval flow until the approval of the pending task is completed. Repeat. In other words, the application scenarios shown in FIG. 3A to FIG. 4 and the corresponding description and explanation content provided by the embodiments of the present disclosure can only be shown as the description of a specific embodiment, so that those skilled in the art can quickly and accurately grasp the present disclosure The technical solution of the present disclosure shall not be regarded as the limitation of the claimed protection scope of the present disclosure.

As shown in FIG. 2 to FIG. 4 , according to an embodiment of the present disclosure, in operation S203, according to the approval execution state of the upgrade approval flow, a reversal operation is performed on the current approval flow to complete the execution of the pending task. ,include:

When the approval execution state of the upgrade approval flow is the end state, revert to executing the current approval flow;

A rollover execution result corresponding to the approval execution result of the upgrade approval flow is generated.

In operations S352 and S402, for the execution of the upgrade approval flow, if the corresponding approval execution state is the end state, it means that the execution of the upgrade approval flow has been completed, and the preliminary approval of the pending approval task has been completed. At this time, a corresponding response command can be generated according to the tag field corresponding to the end state of the approval execution state, and in response to the response command, the original and current approval flow of the upgrade approval flow can be reversed, and the reversion can be understood as the upgrade approval flow End the execution, execute the callback for the original current approval flow in the suspended or suspended execution state, and continue to execute the approval process of the to-be-approved task in the original current approval flow.

Through the original current approval flow, the approval execution of the to-be-approved task is continued one by one according to the original process approval flow execution logic, thereby generating a reversal execution result corresponding to the approval execution result of the upgraded approval flow in the end state. Among them, the approval execution result is the approval result information of the task to be approved corresponding to the upgrade approval flow, and the approval result information includes the result event information such as pass, fail, intermediate termination of approval, intermediate termination of approval, etc. Approval comments left by the approvers of each node, etc. The reversal execution result is the approval result information of the to-be-approved task corresponding to the current approval flow. The approval result information includes the result event information of the current approval flow, such as pass, fail, intermediate termination of approval, and intermediate termination of approval, as well as event information including each Approval comment information left by the approver of the node, etc.

Therefore, by comparing the approval execution results and the reversal execution results of the two approval flows, the approval result information that does not exist in the approval execution results can be analyzed to extract the approvals of the approvers that are missing in the corresponding upgrade approval flow. Comments and approval result events, so as to make the final judgment on whether the approval execution result is further issued for execution, so as to speed up the approval process of the tasks to be approved, ensure the approval accuracy of the tasks to be approved, reduce the approval error rate, and improve the approval process. management efficiency.

In this way, the approval execution of the current approval flow of the original to-be-approved task can be continued under the circumstance of 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, and prevent the accelerated execution of the upgrade approval flow from causing problems. In case of approval errors, the implementation review of the upgrade approval flow can be realized, and at the same time, it can also ensure that the tasks to be approved can be quickly approved through the upgrade approval flow.

It should be noted that, in operation S316, after the execution of the second update approval flow corresponding to the upgrade approval flow is completed, the corresponding current approval flow corresponding to the original upgrade approval flow will also be executed in reverse. In other words, as long as the current approval flow is upgraded and simplified, the current approval flow needs to be reversed and executed after the simplified upgrade approval flow and its corresponding updated approval flow are approved.

As shown in FIG. 2 to FIG. 4 , according to an embodiment of the present disclosure, in the revolving execution of the current approval flow, the process includes:

monitoring the turnaround execution time of the current approval flow;

When the turnaround execution time exceeds a fifth time threshold, the turnaround of the current approval flow is ended.

In operations S403-S405, for the reversal execution of the current approval flow, the corresponding reversal execution time may be set. The reversal execution time is the overall actual execution time required for all unexecuted process approval nodes in the current approval flow to successfully complete all approval executions when the current approval flow is recalled. That is, if there are three unexecuted process approval nodes in the current approval flow for executing the approval of the pending task, then when these three process approval nodes have all completed the execution of the pending task, the actual execution consumption consumed by them is time.

The fifth time threshold is the maximum execution time limit that all unexecuted process approval nodes in the current approval process can provide when all approval executions are completed. Therefore, the fifth time threshold corresponding to the reversal execution time can be specifically based on the approval time and prompt time threshold of each process approval node as a reference, combined with the approval execution result of the completed upgrade approval flow corresponding to the current approval flow. Set the time threshold for delivery execution.

In order to ensure the smooth delivery of the completed approval execution result of the upgrade approval flow, the reversal execution time of the current approval flow of the reversal execution shall not exceed the fifth time threshold, so as to satisfy the continuous execution of the current approval flow to obtain the corresponding execution time. Rotation execution result. However, if the reversal execution time of the current approval flow of the reversal execution exceeds the fifth time threshold, the reversal execution of the current approval flow must be terminated in order to ensure the smooth delivery of the completed approval execution result of the upgrade approval flow. operation to obtain the corresponding pivot execution result that has been pivoted.

Therefore, with the help of the above-mentioned rotation execution time limit of the rotation execution of the current approval flow, it is possible to obtain as much as possible the same as the approval execution result of the pending approval task that has been accelerated through the upgrade approval flow without delaying the issuance and execution of the approval execution result. Upgrade the reversal execution result of the current approval flow corresponding to the approval flow, so as to realize the reversal and review of the approval information of the approval execution result of the accelerated approval, ensure the accuracy of the approval as much as possible, and reduce the approval error rate caused by the accelerated approval, so as to realize the approval process in the approval process. The execution of the task approval process is optimized based on the flow configuration.

Obviously, compared with the conventional method in the prior art in which the approval flow configuration is fixed and cannot further realize approval optimization, the above-mentioned method for executing tasks to be approved based on the approval flow configuration according to the embodiment of the present disclosure can be further based on the current approval flow configured in the approval flow. By further self-identifying the tasks to be approved, an upgrade approval flow is generated, the approval process is significantly simplified by upgrading the approval flow, and the approval speed is further accelerated, and the execution of the original approval process is ensured by reversing the current approval flow, which can accelerate the approval process. Ensure the accuracy of approval as much as possible and reduce the approval error rate caused by accelerated approval, so as to optimize the execution of the task approval process based on the approval flow configuration.

Wherein, the time mentioned in the embodiments of the present disclosure may be a time point or a time range, and a corresponding judgment may be made according to a specific scenario, which is not specifically limited.

Based on the above-mentioned method for executing a task to be approved based on an approval flow configuration, the present disclosure also provides an apparatus for executing a task to be approved based on an approval flow configuration. The device will be described in detail below with reference to FIG. 5 .

FIG. 5 schematically shows a structural block diagram of an apparatus for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure.

As shown in FIG. 5 , the apparatus 800 for executing tasks to be approved based on the approval flow configuration in this embodiment includes a current approval flow matching module 510 , an upgraded approval flow matching module 520 and a current approval flow reversing module 530 .

The current approval flow matching module 510 is configured to match the current approval flow corresponding to the to-be-approved task according to the task type identifier of the to-be-approved task and the preset approval flow matching rule. In an embodiment, the current approval flow matching module 510 may be configured to perform the operation S201 described above, which will not be repeated here.

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 repeated here.

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 upgraded 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 repeated here.

According to an embodiment of the present disclosure, any number of modules in the current approval flow matching module 510, the upgrade approval flow matching module 520, and the current approval flow rotation module 530 may be combined into one module for implementation, or any one of the modules may be disassembled into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments 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 implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA) , programmable logic array (PLA), system-on-chip, system-on-substrate, system-on-package, application-specific integrated circuit (ASIC), or hardware or firmware that can be implemented by any other reasonable means of integrating or packaging circuits , or in any one of the three implementation manners of software, hardware and firmware, or in an appropriate combination of any 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 implemented, at least in part, as computer program modules that, when executed, execute corresponding Function.

6 schematically shows a block diagram of an electronic device suitable for implementing a method for executing a task to be approved based on an approval flow configuration according to an embodiment of the present disclosure.

As shown in FIG. 6 , an electronic device 600 according to an embodiment of the present disclosure includes a processor 601 that can be loaded into a random access memory (RAM) 603 according to a program stored in a read only memory (ROM) 602 or from a storage part 608 program to perform various appropriate actions and processes. The processor 601 may include, for example, a general-purpose microprocessor (eg, a CPU), an instruction set processor and/or a related chipset, and/or a special-purpose microprocessor (eg, an application-specific integrated circuit (ASIC)), and the like. 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 the embodiments of the present disclosure.

In the RAM 603, various programs and data necessary 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 through a bus 604 . The processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the programs in the ROM 602 and/or the RAM 603 . Note 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 the embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 600 may also include an input/output (I/O) interface 605 which is also connected to the bus 604 . Electronic device 600 may also include one or more of the following components connected to I/O interface 605: input portion 606 including a keyboard, mouse, etc.; including components such as a cathode ray tube (CRT), liquid crystal display (LCD), etc., and An output section 607 of a speaker or the like; a storage section 608 including a hard disk or the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. 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 mounted on the drive 610 as needed so that a computer program read therefrom is installed into the storage section 608 as needed.

The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the device/apparatus/system described in the above embodiments; it may also exist alone without being assembled into the device/system. device/system. The above-mentioned computer-readable storage medium carries one or more programs, and when the above-mentioned one or more programs are executed, implement the method according to the embodiment of the present disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, 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 foregoing. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than ROM 602 and/or RAM 603 and/or ROM 602 and RAM 603 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flowchart. When the computer program product runs in the computer system, the program code is used to make the computer system implement the methods provided by the embodiments of the present disclosure.

When the computer program is executed by the processor 601, the above-described functions defined in the system/apparatus of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules.

In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal over a network medium, downloaded and installed through the communication section 609, and/or installed from a removable medium 611. The program code embodied by the computer program may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 609 and/or installed from the removable medium 611 . When the computer program is executed by the processor 601, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the above-described systems, apparatuses, apparatuses, modules, units, etc. can be implemented by computer program modules.

According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure may be written in any combination of one or more programming languages, and specifically, high-level procedures and/or object-oriented programming may be used. programming language, and/or assembly/machine language to implement these computational programs. Programming languages include, but are not limited to, languages such as Java, C++, python, "C" or similar programming languages. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the 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 kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations 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 diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is to be noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in various embodiments and/or claims of the present disclosure are possible, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments of the present disclosure and/or in the claims may be made without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of this disclosure.

Embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only, and are not intended to limit the scope of the present disclosure. Although the various embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. 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 (16)

1. A pending task execution method based on approval flow configuration comprises the following steps:

matching the current approval flow corresponding to the task to be approved according to the task type identification of the task to be approved and a preset approval flow matching rule;

matching an upgrading 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

and according to the approval execution state of the upgrading approval flow, executing rotation operation on the current approval flow so as to complete the execution of the task to be approved.

2. The method according to claim 1, wherein before the matching of the current approval flow corresponding to the pending task according to the task type identifier of the pending task and the preset approval flow matching rule, the method further comprises:

inquiring the task to be approved at the current moment;

and analyzing the task type identification matched with the task to be approved.

3. The method according to claim 1, wherein the matching, according to the task type identifier of the pending task and a preset approval flow matching rule, of the current approval flow corresponding to the pending task comprises:

matching an approval flow label corresponding to the task type identifier according to a preset approval flow matching rule;

and inquiring the current approval flow corresponding to the task to be approved according to the approval flow label.

4. The method of claim 1, wherein before the matching of the current approval requirement of the current approval flow and the task requirement of the pending task with the upgrade approval flow corresponding to the current approval flow, further comprises:

analyzing a field analysis result of the task to be approved before the current approval flow is executed;

and determining the task requirement degree of the task to be examined and approved according to the field analysis result.

5. The method according to claim 1, wherein the matching of the current approval flow corresponding to the current approval flow based on the current approval requirement of the current approval flow and the task requirement of the pending approval task comprises:

when the current approval requirement degree is smaller than the task requirement degree, screening a plurality of process approval nodes of the current approval flow to generate the upgrading approval flow;

and when the current approval requirement degree is greater than the task requirement degree, executing the current approval flow.

6. The method of claim 5, wherein, when the current approval requirement is smaller than the task requirement, the step of screening a plurality of process approval nodes of the current approval flow to generate the upgrade approval flow comprises:

screening out at least one intermediate process approval node matched with the task requirement degree according to the node permission information of the plurality of process approval nodes;

and combining the other process approval nodes after the at least one intermediate process approval node is screened out, and generating the upgrade approval flow.

7. The method of claim 5, wherein, in said performing the current approval flow, comprises:

inquiring the current approval time of the current process approval node of the current approval flow;

when the current approval time is larger than a first time threshold value, initiating a prompt operation to the current process approval node;

inquiring the current prompt time of the current process approval node corresponding to the prompt operation;

and when the current prompt time is larger than a second time threshold, matching a first updating approval flow corresponding to the current approval flow.

8. The method of claim 7, wherein in the first update approval flow corresponding to the matching of the current approval flow, comprises:

inquiring the standby process approval nodes consistent with the node authority information of the current process approval nodes;

combining the standby process approval nodes and a plurality of process approval nodes corresponding to the current approval flow after the current process approval nodes are screened out, and generating a first updating approval flow;

the approval time threshold corresponding to each process approval node in the first updating 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 updating approval flow is smaller than the prompt time threshold corresponding to each process approval node in the current approval flow.

9. The method of claim 1, wherein after matching the upgrade approval flow corresponding to the current approval flow based on the current approval requirement of the current approval flow and the task requirement of the pending approval task, further comprising:

inquiring the current approval time of the current process approval node of the upgrading approval flow;

when the current approval time is larger than a third time threshold, initiating a prompt operation to the current process approval node;

inquiring the current prompting time of the current process approval node corresponding to the prompting operation;

and when the current prompt time is greater than a fourth time threshold, matching a second updating approval flow corresponding to the upgrading approval flow.

10. The method of claim 9, wherein in the second update approval flow corresponding to the matching of the upgrade approval flow, comprising:

inquiring the standby process approval nodes consistent with the node authority information of the current process approval node;

combining the standby process approval nodes and screening a plurality of process approval nodes corresponding to the upgrading approval flow after the current process approval node, and generating a second updating approval flow;

the approval time threshold corresponding to each process approval node in the second updating approval flow is smaller than the approval time threshold corresponding to each process approval node in the upgrading approval flow, and the prompt time threshold corresponding to each process approval node in the second updating approval flow is smaller than the prompt time threshold corresponding to each process approval node in the upgrading approval flow.

11. The method of claim 1, wherein in the approval execution state according to the upgraded approval flow, performing a rotation operation on the current approval flow to complete the execution of the pending approval task comprises:

when the approval execution state of the upgrading approval flow is an end state, the current approval flow is executed in a rotary mode;

and generating a rotary execution result corresponding to the approval execution result of the upgrading approval flow.

12. The method of claim 1, wherein, in the slewing execution of the current approval flow, comprises:

monitoring the revolution execution time of the current approval flow;

and when the gyration execution time exceeds a fifth time threshold, ending the gyration of the current approval flow.

13. An approval flow configuration-based pending task execution device, comprising:

the current approval flow matching module is used for 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 a preset approval flow matching rule;

the upgrading approval flow matching module is used for matching the upgrading 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

and the current approval flow rotating module is used for executing rotating operation on the current approval flow according to the approval execution state of the upgrading approval flow so as to complete the execution of the task to be approved.

14. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-12.

15. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 12.

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

Images