Configuration method, device, equipment and product of workflow approval system
By backward verification of the current task in the workflow approval system, testing and configuring the approval personnel for subsequent tasks, the problem of inefficient approval efficiency caused by the lack of approval personnel is solved, ensuring process integrity and efficiency.
Patent Information
- Application Number
- CN202411727296.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-28
- Publication Date
- 2025-03-14
AI Technical Summary
In the enterprise's workflow approval system, the lack of approval personnel will lead to the failure to find the next node approver during the approval process, thereby blocking the flow of the process and affecting the approval efficiency.
By backward verification of the current task of the target workflow, check whether the corresponding approval personnel are configured for subsequent tasks. When it is detected that the subsequent task has not been configured with the approval personnel, create a configuration task and mark it as a waiting state, add an approval personnel and mark the configuration task as a completion state until all subsequent tasks have been configured with the approval personnel.
Ensure that the entire approval process will not be interrupted or vulnerable due to the lack of approval links, improves approval efficiency, and facilitates tracking and auditing the configuration and implementation of the approval process.
Smart Images
Figure CN119624371A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a configuration method, device, equipment and product for a workflow approval system. Background Art
[0002] In many large enterprises, the organizational structure is often complicated. Therefore, in the enterprise-related workflow, the approvers corresponding to the approval nodes are mostly configured by roles for the sake of versatility and flexibility. In the actual workflow, the node approvers will be queried based on the configured roles and the organizations corresponding to the process. In the enterprise system, if an organization does not configure the user corresponding to the relevant role, it will lead to the situation that the approver of the next node cannot be found during the approval process.
[0003] The most widely used workflow engine at present, if the approver is not passed in during the approval process, the process flow will be blocked and the approval efficiency will be affected.
[0004] Therefore, how to improve approval efficiency without blocking the approval process is an issue that needs to be urgently addressed. Summary of the invention
[0005] The main purpose of this application is to provide a configuration method, device, equipment and product for a workflow approval system, aiming to solve the technical problem of low approval efficiency caused by the lack of approval personnel.
[0006] To achieve the above purpose, the present application proposes a configuration method of a workflow approval system, the method comprising:
[0007] Perform a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks;
[0008] When it is detected that the corresponding approval personnel are not configured for the subsequent task, a corresponding configuration task is created, and the status of the configuration task is marked as a waiting state;
[0009] Adding the corresponding approval personnel to the configuration task, and marking the configuration task with the corresponding approval personnel added as completed;
[0010] Return to the step of performing backward verification on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approvers.
[0011] In one embodiment, the step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person includes:
[0012] Perform a backward check on the current task of the target workflow, and when the subsequent task is a serial or parallel branch, check whether all tasks of the serial and parallel branches are configured with corresponding approval personnel;
[0013] When the subsequent task is a conditional branch, the object to be detected is determined according to the judgment condition corresponding to the conditional branch, and whether the subsequent task is configured with a corresponding approval personnel is detected based on the object to be detected.
[0014] In one embodiment, the step of determining the object to be detected according to the judgment condition corresponding to the conditional branch includes:
[0015] When the judgment condition corresponding to the conditional branch cannot determine the direction of the subsequent branch, the previous task of the judgment condition is determined as the object to be detected;
[0016] When the judgment condition corresponding to the conditional branch is confirmed, the confirmed branch is regarded as a serial or parallel branch, and the object to be detected is determined based on all tasks of the serial and parallel branches.
[0017] In one embodiment, the step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person further includes:
[0018] Performing a backward check on the current task of the target workflow, and updating the configuration task when the conditional branch of the subsequent task changes;
[0019] The object to be detected is determined according to the updated configuration task, and whether the subsequent task is configured with a corresponding approval personnel is detected based on the object to be detected.
[0020] In one embodiment, the subsequent task includes a decision node, and the step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person also includes:
[0021] Performing a backward check on the current task of the target workflow, and when the subsequent task is the decision node, marking the configuration task state of the decision node as a waiting state;
[0022] When the decision process is finished, the next node of the decision node is determined to be the object to be detected, and whether the subsequent task is configured with a corresponding approval person is detected based on the object to be detected.
[0023] In one embodiment, when it is detected that the corresponding approval personnel are not configured for the subsequent task, the step of creating a corresponding configuration task and marking the status of the configuration task as a waiting status includes:
[0024] When it is detected that the subsequent task is not configured with the corresponding approval personnel, the subsequent task that is not configured with the corresponding approval personnel is marked to obtain a node to be configured;
[0025] A virtual node is inserted between the next node of the node to be configured and the node to be configured, and the state of the configuration task is marked as a waiting state. The virtual node is used to configure the corresponding approval personnel.
[0026] In addition, to achieve the above purpose, the present application also proposes a configuration device for a workflow approval system, the configuration device for the workflow approval system comprising:
[0027] The task verification module is used to perform backward verification on the current task of the target workflow to detect whether the subsequent tasks are configured with corresponding approval personnel;
[0028] A task creation module, used for creating a corresponding configuration task and marking the status of the configuration task as a waiting state when detecting that the corresponding approval personnel are not configured for the subsequent task;
[0029] A task marking module, used for adding the corresponding approval personnel to the configuration task, and marking the configuration task with the corresponding approval personnel added as completed;
[0030] The repeat verification module is used to return to the step of performing backward verification on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel.
[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes a configuration device for a workflow approval system, the device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the configuration method for the workflow approval system as described above.
[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the configuration method of the workflow approval system as described above are implemented.
[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the configuration method of the workflow approval system as described above are implemented.
[0034] One or more technical solutions proposed in this application have at least the following technical effects:
[0035] Perform a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks; when it is detected that the corresponding approval personnel are not configured for the subsequent tasks, create a corresponding configuration task and mark the status of the configuration task as waiting; add the corresponding approval personnel to the configuration task, and mark the configuration task with the corresponding approval personnel added as completed; return to the step of performing a backward check on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel. By performing a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks, it is possible to promptly discover whether the approval personnel configuration is missing in the subsequent tasks, ensuring that the entire approval process will not be interrupted or have loopholes due to the lack of approval links. By recording the status of the configuration task (such as waiting status, completed status, etc.), it is possible to easily track and audit the configuration and execution of the entire approval process. Through automated verification and supplementary processes, it is possible to ensure that the configuration of the approver and the process approval are carried out simultaneously, thereby improving the approval efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0038] Figure 1 This is a flow chart of the first embodiment of the configuration method of the application workflow approval system;
[0039] Figure 2 A schematic diagram of the configuration task flow of an embodiment of the present application;
[0040] Figure 3 This is a flow chart of the second embodiment of the configuration method of the application workflow approval system;
[0041] Figure 4 A schematic diagram of branches in which subsequent tasks are serial or parallel in the embodiment of the present application;
[0042] Figure 5 A schematic diagram of a subsequent task as a judgment condition in an embodiment of the present application;
[0043] Figure 6 Another schematic diagram of a subsequent task as a judgment condition in an embodiment of the present application;
[0044] Figure 7A schematic diagram of a change in a judgment condition in an embodiment of the present application;
[0045] Figure 8 A schematic diagram of a subsequent task being a decision node in an embodiment of the present application;
[0046] Fig. 9 This is a flowchart of a third embodiment of the configuration method of the application workflow approval system;
[0047] Fig.10 This is a schematic diagram of the module structure of the configuration device of the workflow approval system of the embodiment of the present application;
[0048] Fig.11 This is a schematic diagram of the device structure of the hardware operating environment involved in the configuration method of the workflow approval system in the embodiment of the present application.
[0049] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0052] In many large enterprises, the organizational structure is often complicated. Therefore, in the enterprise-related workflows, the approvers corresponding to the approval nodes are mostly configured through roles for the sake of versatility and flexibility. In the actual workflow, the approvers of the node will be queried according to the configured roles and the organizations corresponding to the processes. In the enterprise system, if an organization does not configure the users corresponding to the relevant roles, it will lead to the situation that the approver of the next node cannot be found during the approval process. The most widely used workflow engine at present often leads to approval errors if the approver is not passed in during the approval, blocking the flow of the process and affecting the user experience. In addition, the administrator can only know which specific task has no approver configured when the approver reports an error when approving the task, and cannot configure the approver in advance, which seriously affects the approval efficiency.
[0053] The present application provides a solution, which performs a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks; when it is detected that the corresponding approval personnel are not configured for the subsequent tasks, a corresponding configuration task is created, and the status of the configuration task is marked as a waiting state; a corresponding approval personnel is added to the configuration task, and the configuration task with the corresponding approval personnel added is marked as a completed state; and the step of performing a backward check on the current task of the target workflow is returned until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel. By performing a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks, it is possible to timely discover whether the approval personnel configuration is missing in the subsequent tasks, and ensure that the entire approval process will not be interrupted or cause loopholes due to the lack of approval links. By recording the status of the configuration task (such as waiting state, completed state, etc.), the configuration and execution of the entire approval process can be easily tracked and audited. Through automated verification and supplementary processes, it can be ensured that the configuration of the approver and the process approval are carried out simultaneously, thereby improving the approval efficiency.
[0054] Based on this, the present application embodiment provides a configuration method of a workflow approval system, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the configuration method of the application workflow approval system.
[0055] In this embodiment, the configuration method of the workflow approval system includes steps S10 to S40:
[0056] Step S10, performing a backward check on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person.
[0057] It should be noted that the target workflow can be the entire workflow task set that is currently being configured for approval. The workflow can contain multiple task nodes, and each node may require different approvers to approve. The current task can be a specific task node in the target workflow that is being operated and verified. Backward verification can be understood as checking the subsequent task nodes of the current task node to ensure that all subsequent tasks have been configured with corresponding approvers. The subsequent task can be the task node after the current task node. The subsequent task can be the next task that is directly connected, or it can be a task in multiple branch nodes.
[0058] Step S20: When it is detected that the subsequent task has not been configured with a corresponding approval person, a corresponding configuration task is created, and the status of the configuration task is marked as a waiting status.
[0059] It should be noted that the corresponding approver can be the approver that matches the task node, which can be understood as the specific person responsible for reviewing and approving the task. When it is detected that there is a lack of approvers in the subsequent task, the system can automatically generate a task for configuring the approvers required for the subsequent task. The waiting state can be a task state, indicating that the configuration task has not been completed and is still waiting for the configuration of the approver.
[0060] Step S30, adding a corresponding approval person to the configuration task, and marking the configuration task with the corresponding approval person added as completed.
[0061] It should be noted that the completed status can be another task status, indicating that the configuration task has been completed and the approver has been successfully added to the subsequent tasks. The completed status indicates that the configuration is complete and you can proceed to the verification or configuration of the next task.
[0062] Step S40, returning to the step of performing backward verification on the current task of the target workflow, until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel.
[0063] It should be noted that after the configuration task is completed, the system automatically returns to the initial verification step and continues to check the subsequent tasks of the current task until it is confirmed that all subsequent tasks have been configured with approvers.
[0064] For example, Figure 2 As shown in the figure, after the system detects that the approver is missing, it sends the task of configuring the approver, and you can configure the corresponding approver for the task. Configuring the approver and process approval are parallel and can be performed at the same time. If the task corresponding to the configuration task has been created and is in the waiting state, the subsequent task will be assigned to the designated approver, and the task will be turned into the open state (completed state), and then the configuration task will be closed. If the corresponding task has not been created, the configuration task will be closed directly after the approver is configured.
[0065] In this embodiment, by performing a backward check on the current task of the target workflow and detecting whether the corresponding approver is configured for the subsequent task, it is possible to timely discover whether the approver configuration is missing in the subsequent task, ensuring that the entire approval process will not be interrupted or have loopholes due to the lack of approval links. By recording the status of the configuration task (such as waiting status, completion status, etc.), the configuration and execution of the entire approval process can be easily tracked and audited. Through automated verification and supplementary processes, it can be ensured that the configuration of the approver and the process approval are carried out simultaneously, thereby improving the approval efficiency.
[0066] Reference Figure 3 , Figure 3 This is a flow chart of the second embodiment of the configuration method of the application workflow approval system. Figure 1The first embodiment shown is a second embodiment of the configuration method of the workflow approval system of the present application.
[0067] In the second embodiment, the step S10 includes:
[0068] Step S101, perform a backward check on the current task of the target workflow, and when the subsequent task is a serial or parallel branch, check whether all tasks of the serial and parallel branches are configured with corresponding approval personnel.
[0069] For example, Figure 4 As shown, when the subsequent task is a serial or parallel branch (no need to judge or select the branch), all parallel branch tasks will be checked. It should be noted that the serial branch can represent the task nodes that the subsequent tasks are executed in sequence. The parallel branch represents multiple task nodes that can be performed simultaneously in the subsequent task. Each task in the parallel branch can be executed at the same time, and each task node needs to be configured with an approver separately.
[0070] Step S102, when the subsequent task is a conditional branch, determine the object to be detected according to the judgment condition corresponding to the conditional branch, and detect whether the subsequent task is configured with a corresponding approval personnel based on the object to be detected.
[0071] It should be noted that the step of determining the object to be detected according to the judgment condition corresponding to the conditional branch includes: when the judgment condition corresponding to the conditional branch cannot determine the direction of the subsequent branch, determining the previous task of the judgment condition as the object to be detected; when the judgment condition corresponding to the conditional branch is confirmed, the confirmed branch is regarded as a serial or parallel branch, and the object to be detected is determined based on all the tasks of the serial and parallel branches. Exemplarily, the conditional branch can be understood as that the workflow will continue to execute along different paths according to different conditions, and these conditions determine which tasks will be executed. The judgment condition can be understood as selecting different subsequent tasks according to different condition values, and the result of the judgment condition determines how the workflow will continue and which task nodes will become the object to be detected. The object to be detected can be understood as a specific task node determined according to the judgment condition in the case of a conditional branch.
[0072] For example, Figure 5 As shown in , if the judgment condition in the current process cannot determine the direction of the subsequent branch, only the task before the judgment branch node (task C) will be checked. Figure 6 As shown, if the judgment condition in the current process satisfies a certain branch, the subsequent tasks will continue to be checked along the branch that meets the condition. That is, if the judgment branch determines that the next task node is task D2, task D2 will be regarded as the current task of the target workflow and continue to be checked backward.
[0073] In this embodiment, by automatically identifying and verifying serial, parallel and conditional branches, corresponding processing can be performed according to the actual branch type (such as serial, parallel or conditional branches), ensuring that the approval configuration of each branch node meets the process requirements and improving the flexibility and adaptability of the process. By determining the object to be detected according to the judgment conditions of the conditional branch, the subsequent tasks to be detected can be dynamically adjusted to adapt to different process directions under different conditional branches, thereby enhancing the intelligence and dynamic response capabilities of the system.
[0074] In one embodiment, the step S10 further includes: performing a backward check on the current task of the target workflow, and updating the configuration task when the conditional branch of the subsequent task changes; determining the object to be detected based on the updated configuration task, and detecting whether the subsequent task is configured with the corresponding approval personnel based on the object to be detected.
[0075] It should be noted that when the judgment condition of the conditional branch changes, the path of the workflow is also adjusted accordingly. Furthermore, the system will update the configuration task to configure the approver for the new path node. For example, Figure 6 and Figure 7 As shown, Figure 6 This is a flowchart of the process when the conditional branch of the subsequent task has not changed. Figure 7 This is a flow diagram for processing when the conditional branches of subsequent tasks have not changed. It can be understood that if the branch judgment condition expression in the current process has changed, resulting in a change in the subsequent judgment branch, the system will dynamically modify the approver configuration task.
[0076] In this embodiment, when a conditional branch changes, the system can automatically adjust the object to be detected and perform approval configuration verification on the newly added or changed task nodes to avoid missing the approval personnel configuration of any task node and ensure the approval integrity of the entire process.
[0077] In one embodiment, the step S10 also includes: performing a backward check on the current task of the target workflow, and when the subsequent task is a decision node, marking the configuration task status of the decision node as a waiting state; when the decision process ends, determining that the next node of the decision node is an object to be detected, and detecting whether the subsequent task is configured with a corresponding approval personnel based on the object to be detected.
[0078] It should be noted that a decision node can be a type of node in a workflow, which is used to select a process branch based on specific conditions or decisions. The decision node will select different subsequent paths based on the decision results, affecting the approval process direction of subsequent tasks. For example, Figure 8 As shown, when the subsequent task is verified to the decision node (the subsequent branch is determined by the approver), the system will only verify to the decision node.
[0079] In this implementation, by setting a waiting state for the decision node, different decision paths can be flexibly responded to. When the decision process is completed and a specific subsequent path is selected, the system will configure the approval personnel according to the actual path, effectively avoiding incorrect configuration when the process is pending, thereby improving the accuracy and adaptability of the approval configuration.
[0080] Reference Fig. 9 , Fig. 9 This is a flow chart of the third embodiment of the configuration method of the application workflow approval system. Figure 3 The second embodiment shown is a third embodiment of the configuration method of the workflow approval system of the present application.
[0081] In the third embodiment, the step S20 includes:
[0082] Step S201: when it is detected that a subsequent task has not been assigned a corresponding approval person, the subsequent task that has not been assigned a corresponding approval person is marked to obtain a node to be configured.
[0083] It should be noted that the nodes to be configured may be subsequent task nodes that have not yet been configured with approval personnel and require further configuration, and the marking may facilitate subsequent system identification and processing of the task.
[0084] Step S202: insert a virtual node between the next node of the node to be configured and the node to be configured, and mark the state of the configuration task as a waiting state.
[0085] It should be noted that the virtual node is used to configure the corresponding approval personnel, and a temporary task node can be inserted between the node to be configured and its next node for the configuration of the approval personnel. Fig.10 As shown in the figure, when there is no approver for the next node task, the approver can be configured by creating a virtual node, and the current node task can be approved normally without blocking the process.
[0086] In this embodiment, when a subsequent task is detected that has no approval personnel configured, by marking the node to be configured and inserting a virtual node, the system can effectively ensure that all task nodes have corresponding approval personnel configured to avoid omissions and process faults. By inserting a virtual node, the system can dynamically add approval personnel. The virtual node is used as a temporary configuration task to quickly configure the approval personnel without affecting the overall process, reducing the time for manual operation and reconfiguration, and improving the efficiency of the overall process.
[0087] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the configuration method of the workflow approval system of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0088] This application also provides a configuration device for a workflow approval system, please refer to Fig.10 , the configuration device of the workflow approval system includes:
[0089] The task verification module 10 is used to perform a backward verification on the current task of the target workflow to detect whether the subsequent tasks are configured with corresponding approval personnel;
[0090] The task creation module 20 is used to create a corresponding configuration task and mark the status of the configuration task as a waiting state when it is detected that the corresponding approval personnel are not configured for the subsequent task;
[0091] The task marking module 30 is used to add the corresponding approval personnel to the configuration task, and mark the configuration task with the corresponding approval personnel added as completed;
[0092] The repeat verification module 40 is used to return to the step of performing backward verification on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding reviewers.
[0093] The configuration device of the workflow approval system provided by the present application adopts the configuration method of the workflow approval system in the above embodiment, which can solve the technical problem of low approval efficiency caused by the lack of approval personnel. Compared with the prior art, the beneficial effects of the configuration device of the workflow approval system provided by the present application are the same as the beneficial effects of the configuration method of the workflow approval system provided by the above embodiment, and other technical features in the configuration device of the workflow approval system are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0094] The present application provides a configuration device for a workflow approval system, the configuration device for the workflow approval system comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the configuration method for the workflow approval system in the above-mentioned embodiment 1.
[0095] Reference below Fig.11, which shows a schematic diagram of the structure of a configuration device suitable for implementing a workflow approval system in an embodiment of the present application. The configuration device of the workflow approval system in an embodiment of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.11 The configuration device of the workflow approval system shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0096] like Fig.11 As shown, the configuration device of the workflow approval system may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. Various programs and data required for the operation of the configuration device of the workflow approval system are also stored in the RAM 1004. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the configuration device of the workflow approval system to communicate with other devices wirelessly or by wire to exchange data. Although Fig.11 The configuration device of the workflow approval system with various systems is shown, but it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.
[0097] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0098] The configuration device of the workflow approval system provided by the present application adopts the configuration method of the workflow approval system in the above embodiment, which can solve the technical problem of low approval efficiency caused by the lack of approval personnel. Compared with the prior art, the beneficial effects of the configuration device of the workflow approval system provided by the present application are the same as the beneficial effects of the configuration method of the workflow approval system provided by the above embodiment, and other technical features in the configuration device of the workflow approval system are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0099] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0100] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0101] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the configuration method of the workflow approval system in the above-mentioned embodiment.
[0102] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0103] The computer-readable storage medium may be included in the configuration device of the workflow approval system; or may exist independently without being assembled into the configuration device of the workflow approval system.
[0104] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the configuration device of the workflow approval system, the configuration device of the workflow approval system: performs a backward check on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval personnel; when it is detected that the subsequent task is not configured with the corresponding approval personnel, creates a corresponding configuration task and marks the status of the configuration task as a waiting state; adds the corresponding approval personnel to the configuration task, and marks the configuration task of adding the corresponding approval personnel as a completed state; returns to the step of performing a backward check on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel.
[0105] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0106] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0107] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0108] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the configuration method of the above-mentioned workflow approval system, and can solve the technical problem of low approval efficiency caused by the lack of approval personnel. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the configuration method of the workflow approval system provided by the above-mentioned embodiment, and will not be repeated here.
[0109] The present application also provides a computer program product, including a computer program, which implements the steps of the configuration method of the workflow approval system as described above when the computer program is executed by a processor.
[0110] The computer program product provided by this application can solve the technical problem of low approval efficiency caused by the lack of approval personnel. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the configuration method of the workflow approval system provided by the above embodiment, which will not be repeated here.
[0111] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A configuration method for a workflow approval system, characterized in that: The method includes: Perform a backward check on the current task of the target workflow to detect whether the corresponding approval personnel are configured for the subsequent tasks; When it is detected that the corresponding approval personnel are not configured for the subsequent task, a corresponding configuration task is created, and the status of the configuration task is marked as a waiting state; Adding the corresponding approval personnel to the configuration task, and marking the configuration task with the corresponding approval personnel added as completed; Return to the step of performing backward verification on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approvers.
2. The method according to claim 1, characterized in that The step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person includes: Perform a backward check on the current task of the target workflow, and when the subsequent task is a serial or parallel branch, check whether all tasks of the serial and parallel branches are configured with corresponding approval personnel; When the subsequent task is a conditional branch, the object to be detected is determined according to the judgment condition corresponding to the conditional branch, and whether the subsequent task is configured with a corresponding approval personnel is detected based on the object to be detected.
3. The method according to claim 2, characterized in that The step of determining the object to be detected according to the judgment condition corresponding to the conditional branch includes: When the judgment condition corresponding to the conditional branch cannot determine the direction of the subsequent branch, the previous task of the judgment condition is determined as the object to be detected; When the judgment condition corresponding to the conditional branch is confirmed, the confirmed branch is regarded as a serial or parallel branch, and the object to be detected is determined based on all tasks of the serial and parallel branches.
4. The method according to claim 2, characterized in that The step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person also includes: Performing a backward check on the current task of the target workflow, and updating the configuration task when the conditional branch of the subsequent task changes; The object to be detected is determined according to the updated configuration task, and whether the subsequent task is configured with a corresponding approval personnel is detected based on the object to be detected.
5. The method according to claim 2, characterized in that The subsequent task includes a decision node, and the step of performing backward verification on the current task of the target workflow to detect whether the subsequent task is configured with a corresponding approval person also includes: Performing a backward check on the current task of the target workflow, and when the subsequent task is the decision node, marking the configuration task state of the decision node as a waiting state; When the decision process is finished, the next node of the decision node is determined to be the object to be detected, and whether the subsequent task is configured with a corresponding approval person is detected based on the object to be detected.
6. The method according to any one of claims 1 to 5, characterized in that The step of creating a corresponding configuration task and marking the status of the configuration task as a waiting status when detecting that the corresponding approval personnel are not configured for the subsequent task includes: When it is detected that the subsequent task is not configured with the corresponding approval personnel, the subsequent task that is not configured with the corresponding approval personnel is marked to obtain a node to be configured; A virtual node is inserted between the next node of the node to be configured and the node to be configured, and the state of the configuration task is marked as a waiting state. The virtual node is used to configure the corresponding approval personnel.
7. A configuration device for a workflow approval system, characterized in that: The device comprises: The task verification module is used to perform backward verification on the current task of the target workflow to detect whether the subsequent tasks are configured with corresponding approval personnel; A task creation module, used for creating a corresponding configuration task and marking the status of the configuration task as a waiting state when detecting that the corresponding approval personnel are not configured for the subsequent task; A task marking module, used for adding the corresponding approval personnel to the configuration task, and marking the configuration task with the corresponding approval personnel added as completed; The repeat verification module is used to return to the step of performing backward verification on the current task of the target workflow until it is detected that all subsequent tasks of the target workflow are configured with corresponding approval personnel.
8. A configuration device for a workflow approval system, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the configuration method of the workflow approval system according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the configuration method of the workflow approval system according to any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the method for configuring the workflow approval system according to any one of claims 1 to 6 are implemented.