Method and system for realizing summary approval
By creating approval task summary rules and building summary approval rules, the problems of low approval efficiency and information asymmetry in traditional task approval methods are solved, batch approval and unified approval of tasks are realized, and approval efficiency and accuracy are improved.
Patent Information
- Application Number
- CN202510078758.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-17
- Publication Date
- 2025-04-25
AI Technical Summary
When the traditional task approval method expands the scale of the enterprise and increases business complexity, frequent approval notices will interrupt the leader's work rhythm, resulting in low approval efficiency, and information asymmetry may lead to confusion in the approval process.
By creating approval task summary rules, using the preset processing model to extract and analyze historical approval information, construct summary approval rules, and add new fields to the task table to indicate whether the approved task is a summary approval push task. According to these rules and fields, the tasks to be approved are summarized and pushed to achieve batch approval.
It improves the efficiency and accuracy of approval, realizes regular and unified approval of tasks, reduces interruptions in leadership work, and avoids confusion in the approval process caused by information asymmetry.
Smart Images
Figure CN119887119A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer application technology, and in particular to a method and system for implementing aggregated approval. Background Art
[0002] Task approval, as a key link in an enterprise's internal control and decision-making mechanism, is an indispensable part of enterprise management.
[0003] Traditional task approval methods generally use instant notifications. Whenever a new approval task arrives, the task approval system will immediately send a pending task notification to the relevant leaders. However, with the increase in enterprise scale and the increase in the complexity of enterprise business, for some tasks that do not require urgent approval, frequent approval notifications will interrupt the work rhythm of leaders, resulting in poor timeliness of task approval and low approval efficiency. At the same time, it may also cause confusion in the approval process due to information asymmetry, which will also have an adverse impact on the efficiency of task approval and make approval efficiency low. Summary of the invention
[0004] The present application provides a method and system for implementing aggregate approval, which is used to solve the technical problem of low efficiency of existing approval methods.
[0005] This application adopts the following technical solutions:
[0006] On the one hand, the present application provides a method for implementing summary approval, the method comprising: creating an approval task summary rule based on a preset summary rule table, the summary rule table including at least a process classification ID; performing data extraction and analysis on historical approval information using a preset processing model, and constructing a summary approval rule based on the results of the data extraction and analysis; adding a new field to the task table, the new field being used to indicate whether the task to be approved is a summary approval push task; when there is a new task to be approved, querying the approval task summary rule based on the process classification ID corresponding to the task to be approved, and assigning a value of yes to the new field in the task table based on the query result; querying the summary approval rule based on the approver ID and / or process classification ID corresponding to the task to be approved, and summarizing and pushing the task to be approved based on the queried rule content.
[0007] In a possible implementation of the present application, the approval task summary rule also includes a user ID, a user name, an approval type, a sending method and an update time; wherein the user ID is used to indicate the system user ID that is allowed to use the approval task summary rule; the user name is used to indicate the system user name that is allowed to use the approval task summary rule; the approval type is used to indicate the type of approval corresponding to the task to be approved, including at least one of work report approval, supplementary approval and leave application approval, and the approval type corresponds one-to-one to the process classification ID; the sending method is used to indicate the sending time of the task to be pushed; the update time is used to indicate the creation time and / or the last modification time of the approval task summary rule.
[0008] In a possible implementation of the present application, the historical approval information includes at least an approver and / or approver ID, a process classification ID, a task reception time, and a task processing time; the use of a preset processing model to perform data extraction and analysis on the historical approval information includes: fixing the approver and / or approver ID and the process classification ID in the historical approval information; using the preset processing model to analyze the task reception time and the task processing time to confirm the probability distribution of the task processing time for the same approver and / or approver ID under the same process classification ID; constructing the aggregate approval rule based on the probability distribution, and the aggregate approval rule includes at least the push time.
[0009] In a possible implementation of the present application, after constructing the aggregate approval rule according to the probability distribution, the method further includes: traversing all approvers and / or approver IDs and all process classification IDs to obtain an aggregate approval rule library.
[0010] In a possible implementation of the present application, after obtaining the aggregate approval rule library, the method further includes: using the preset processing model to recognize the input voice for creating the aggregate approval rule to determine the approver and / or approver ID and the approval type; determining the corresponding process classification ID according to the approval type, and querying the aggregate approval rule library through the approver and / or approver ID and the process classification ID; generating and enabling the aggregate approval rule according to the query result.
[0011] In a possible implementation of the present application, the pending approval tasks are summarized and pushed according to the queried rule content, including: if the approver ID and / or process classification ID is queried in the summarized approval rules, the status field corresponding to the pending approval task is modified to pending push; and the pending approval tasks to be pushed are summarized and pushed according to the scheduled tasks.
[0012] In a possible implementation of the present application, the pending approval tasks to be pushed are summarized and pushed according to the scheduled tasks, including: polling the summary approval rules according to the scheduled tasks; if the corresponding push time in the summary approval rules is earlier than the current time, triggering the task push and pushing the pending approval tasks out immediately; if the corresponding push time in the summary approval rules is later than the current time, then when the push time is reached, the pending approval tasks in the task table whose status field is to be pushed are summarized and pushed.
[0013] In a possible implementation of the present application, the tasks to be approved are summarized and pushed according to the queried rule content, and also include: if the approver ID and / or process classification ID are not found in the summarized approval rules, the tasks to be approved are pushed out immediately and the value of the new field in the task table is updated to no.
[0014] In one possible implementation of the present application, the method also includes: setting a front-end display page; displaying the summarized and pushed pending approval tasks on the front-end display page, wherein the display method is a parent-child structure display, wherein the parent data in the parent-child structure is displayed as a summary approval, and the child data is displayed as each pending approval task; in response to the approver clicking on the approval and / or one-click approval operation, each pending approval task is approved separately and / or in batches.
[0015] On the other hand, the present application also provides a system for implementing summary approval, the system comprising: a rule creation module, which creates approval task summary rules based on a preset summary rule table, wherein the summary rule table includes at least a process classification ID; the rule creation module, which uses a preset processing model to perform data extraction and analysis on historical approval information, and constructs summary approval rules based on the results of the data extraction and analysis; a task table modification module, which adds a new field to the task table, wherein the new field is used to indicate whether the task to be approved is a summary approval push task; a rule query module, which queries the approval task summary rules based on the process classification ID corresponding to the task to be approved when there is a new task to be approved, and assigns the new field in the task table to be "yes" based on the query result; a task push module, which queries the summary approval rules based on the approver ID and / or process classification ID corresponding to the task to be approved, and summarizes and pushes the task to be approved based on the queried rule content.
[0016] The present application provides a method and system for implementing a consolidated approval process, which has the following beneficial effects:
[0017] By creating an approval task summary rule, the pending approval tasks that meet the requirements of the rule are used as summary push tasks, which can realize the summary push of pending approval tasks and provide the possibility for the summary approval of tasks; the push time of each approver under each process classification ID during the summary approval is determined by constructing a summary approval rule, and the pending approval tasks are summarized and pushed through the scheduled task polling summary approval rule, so that the approver can summarize and approve the pending approval tasks, realizing the batch approval of pending approval tasks and improving the approval efficiency of pending approval tasks. In this process, the task table was also modified, and a new field was added to the task table. The new field is used to determine whether the pending approval task is a summary approval push task. Through the fields in the task table, it can be further determined whether the pending approval is a summary approval or a separate approval when the pending approval task is pushed, providing technical support for the summary approval of pending approval tasks. In short, the implementation method of summary approval in this application can improve the efficiency and accuracy of approval, realize the scheduled approval and unified approval of tasks, and also help promote the development of enterprise management in a more efficient direction. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to more clearly illustrate the technical solutions in this application or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0019] Figure 1 A flow chart of a method for implementing the aggregate approval provided for this application;
[0020] Figure 2 A system architecture diagram for implementing a summary approval provided for this application. DETAILED DESCRIPTION
[0021] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in this application will be described clearly and completely below in conjunction with the drawings in this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.
[0022] The method in this application is described in detail below with reference to the accompanying drawings.
[0023] Figure 1 A flowchart of a method for implementing a summary approval provided for this application, such as Figure 1 As shown, the summary approval implementation method in this application includes at least the following execution steps:
[0024] Step 101: Create approval task summary rules based on the preset summary rule table.
[0025] In the summary approval implementation method in this application, the summary rules are first modeled and the table structure of the summary rules is constructed. The creation of the summary rules depends on the summary rule table.
[0026] The sample data involved in the aggregation rules are shown in Table 1 below, where each row represents an aggregation rule.
[0027]
[0028] Table 1
[0029] In Table 1 above, the contents of the main fields are explained as follows:
[0030] User ID: stores the system user ID that can use the current aggregation rule. For example, U001 represents the unique ID of person Zhang San.
[0031] User Name: Stores the name of the user who can use the current aggregation rule.
[0032] Approval Type: Indicates the type of approval for creating the current rule. For example, "Work Report Approval". This value can be customized by the creator.
[0033] Process classification ID: Process classification corresponds to approval type, and different approval types correspond to different process classification IDs. For example, the process classification ID corresponding to "Work Order" is "WF001", and the task generated for "Zhang San" by the process of the work order will match the summary rule of the row with the primary key ID "R001".
[0034] Sending method: indicates the time when the tasks to be approved are pushed. For example, "17:00 every day" means that at 17:00 every day, the system will count the tasks that need to be summarized and approved. If the number is greater than 0, the approval task will be pushed.
[0035] Task title: The tasks pushed by the summary approval will be displayed in the task center in a parent-child structure. After clicking the parent title outside, the task data (child) pushed by the summary approval rules will pop up. The parent title supports custom settings. For example, getting the context variable ('process initiator') will get the corresponding process initiator of each task and display it on the parent title. The parent title displays by default: approval type plus task title.
[0036] Creation time / last modification time: the creation time of the corresponding aggregation rule and the time of the last updated data. These time data are used to record historical modification records.
[0037] Step 102: Use the preset processing model to perform data extraction and analysis on the historical approval information, and construct summary approval rules based on the results of the data extraction and analysis.
[0038] In a possible implementation of the present application, there is an approval record table in the system that records task-related information, which records historical approval information related to the task, such as the approver and / or approver ID, process classification ID, task receiving time, and task processing time. The historical approval information in the system is extracted and analyzed using the data processing capabilities of the preset processing model. Specifically, the approver and / or approver ID and process classification ID are fixed, and the task processing time and task receiving time are analyzed using the preset processing model to confirm the probability distribution of approval time under the same approver and / or approver ID and the same process classification ID, thereby constructing a suitable aggregate approval rule, where the aggregate approval rule at least includes the push time.
[0039] For example, Zhang San will review the tasks under WF001 every day, so the corresponding summary rule can be set to be sent at 17:00 every afternoon; if he reviews every Friday, the corresponding summary method can be set to 17:00 every Friday afternoon, and so on. By using the preset processing model to process data accurately, quickly and extract features, and by analyzing historical approval information, the default summary approval rules for a certain approver under a certain process classification ID can be obtained.
[0040] Finally, all approvers and all process classification IDs are traversed to obtain the summary approval rule library.
[0041] Furthermore, when the leader needs to create a summary approval rule, he can create a task through voice, and use the voice recognition capability of the preset processing model to recognize the valid information in the received voice. For example, if the voice message is "Create a summary approval rule under the expense report for me", the corresponding approval type can be obtained as the expense report, and the user is the current login user. Then, the corresponding rule is found in the summary approval rule library. The approval type corresponds to the process classification ID, and the user corresponds to the approver and / or the approver ID, and the default summary approval rule is generated. When the voice message is "Create an approval rule for Zhang San", the rule data with the approver Zhang San is found in the summary approval rule, and the default summary approval rule generated by the preset processing model is displayed for the current login user. The leader can continue to interact with the preset processing model through voice. For example, "Only display the summary approval rule under the work application" or "Modify the default summary approval rule corresponding to the work application to send at 15:00 in the afternoon". After adjusting the data, the leader can choose to enable all or part of the currently displayed summary approval rules. After the summary approval rule is enabled, the corresponding data will be checked in the subsequent approval process. It should be noted that only one summary approval rule can be set for the same approver and the same process classification ID.
[0042] Step 103: Add a new field in the task table to indicate whether the task to be approved is a summary approval push task.
[0043] The operation of the approval process relies on the underlying support of the process engine. When the approval process runs to a new node, the pending approval tasks are pushed by monitoring the work item creation event. The pending approval tasks are stored in the task table of the task center, which records the task-related fields, such as the task owner, receipt time and other information.
[0044] In a possible implementation of the present application, in order to support aggregate approval, a new field is added to the task table, and the new field is used to indicate whether the task to be approved is a aggregate approval push task, that is, whether it can be aggregated for approval.
[0045] The sample data and main fields involved in the above task table are shown in Table 2 below:
[0046]
[0047] Table 2
[0048] The contents of each field in Table 2 above are explained as follows:
[0049] Task owner ID / task owner name: basic information of the approver. The task owner ID represents the unique identifier of the approver.
[0050] Task classification ID: The task classification ID corresponds to the process classification ID one by one. When the process classification ID is saved, a task classification data will be generated. The task classification ID of the corresponding data is the same as the process classification ID.
[0051] Status: indicates the current status of the pending approval task. The supported statuses are: created, paused, running, canceled, terminated, completed, deleted, and pending.
[0052] Summary approval push task: indicates whether summary approval push is required.
[0053] Step 104: When there is a new task to be approved, the approval task summary rule is queried according to the process classification ID corresponding to the task to be approved, and the new field in the task table is assigned a value of yes according to the query result.
[0054] In a possible implementation of the present application, when there is a new task to be approved and the approval process runs to the approval node, a task will be generated for the approver and / or approver ID, and the task will be pushed to the task center. According to the approver and / or approver ID and the process classification ID, the approval task summary rule created in the system will be queried. If the corresponding approval task summary rule is found, the pushed task to be approved needs to modify the corresponding status field to be pushed, and set the whether to summarize the approval push task field to yes; if the corresponding approval task summary rule is not found according to the approver and / or approver ID and the process classification ID, the task to be approved will be pushed out immediately / immediately, and the whether to summarize the approval push task field in the task table will be set to no.
[0055] Step 105: query and summarize approval rules according to the approver ID and / or process classification ID corresponding to the pending approval tasks, and summarize and push the pending approval tasks according to the queried rule content.
[0056] In one possible implementation of the present application, if a corresponding approval task summary rule is found based on the approver and / or approver ID and process classification ID, the summary approval rule is continued to be queried based on the approver ID and / or process classification ID corresponding to the task to be approved. If the approver ID and / or process classification ID are found in the summary approval rule, the tasks to be approved will be summarized and pushed according to the scheduled task.
[0057] Specifically, add a scheduled task in the background. The scheduled task polls every five minutes. First, query the summary approval rules. If the current time has exceeded the sending time set in the summary approval rules, query the tasks to be pushed in the task table according to the process classification ID and approver ID set in the corresponding summary approval rules, and according to the status of pending push, trigger the task push, and push the pending approval tasks out immediately. After the task push is triggered, the corresponding status is changed to running. If the current time does not exceed the sending time set in the summary approval rules, when the push time is reached, the pending approval tasks in the task table with the status field of pending push will be pushed together so that the approver can conduct summary approval and improve approval efficiency.
[0058] In a possible implementation of the present application, the method also includes: setting a front-end display page, and displaying the tasks for summary approval on the front-end display page according to the parent-child structure. The parent data is displayed in the process center, and the corresponding category is the preset "summary approval", and the corresponding title is the task title set in the summary approval rule. Click on the parent, and the data displayed in the child is the corresponding tasks generated under the summary approval rule. The approver can select each task to view and approve, or batch approve, to provide support for the implementation of summary approval. That is, the parent data in the aforementioned parent-child structure is displayed as summary approval, and the child data is displayed as each task to be approved. When the approver clicks on approval and / or one-click approval, each task to be approved is approved separately and / or batch approved to achieve summary approval.
[0059] Based on the same inventive concept, the present application also provides a system for implementing the aggregated approval, the architecture of which is as follows: Figure 2 shown.
[0060] Figure 2 A system architecture diagram for implementing a summary approval process provided for this application. Figure 2As shown, the summary approval implementation system 200 in the present application specifically includes: a rule creation module 201, which creates an approval task summary rule based on a preset summary rule table, wherein the summary rule table includes at least a process classification ID; the rule creation module 201, which uses a preset processing model to perform data extraction and analysis on historical approval information, and constructs a summary approval rule based on the results of the data extraction and analysis; a task table modification module 202, which adds a new field to the task table, wherein the new field is used to indicate whether the task to be approved is a summary approval push task; a rule query module 203, which queries the approval task summary rule according to the process classification ID corresponding to the task to be approved when there is a new task to be approved, and assigns a value of yes to the new field in the task table according to the query result; a task push module 204, which queries the summary approval rule according to the approver ID and / or process classification ID corresponding to the task to be approved, and pushes the task to be approved in a summary manner according to the queried rule content.
[0061] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0062] The system and method provided in the present application correspond one to one, and therefore the system also has similar beneficial technical effects as its corresponding method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the system will not be repeated here.
[0063] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media that include computer-usable program code.
[0064] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0065] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims
1. A method for implementing summary approval, characterized in that: The method comprises: Creating an approval task summary rule according to a preset summary rule table, wherein the summary rule table at least includes a process classification ID; Use the preset processing model to extract and analyze historical approval information, and build summary approval rules based on the results of data extraction and analysis; Add a new field in the task table, which is used to indicate whether the task to be approved is a summary approval push task; When there is a new task to be approved, the approval task summary rule is queried according to the process classification ID corresponding to the task to be approved, and the new field in the task table is assigned a value of yes according to the query result; The summary approval rules are queried according to the approver ID and / or process classification ID corresponding to the pending approval tasks, and the pending approval tasks are summarized and pushed according to the queried rule content.
2. A method for implementing collective approval according to claim 1, characterized in that: The approval task summary rules also include user ID, user name, approval type, sending method and update time; Among them, the user ID is used to indicate the system user ID that is allowed to use the approval task summary rule; the user name is used to indicate the system user name that is allowed to use the approval task summary rule; the approval type is used to indicate the approval type corresponding to the task to be approved, including at least one of the following: work report approval, supplementary approval and leave application approval, and the approval type corresponds one-to-one to the process classification ID; the sending method is used to indicate the sending time of the task to be pushed; the update time is used to indicate the creation time and / or the last modification time of the approval task summary rule.
3. A method for implementing collective approval according to claim 1, characterized in that: The historical approval information at least includes the approver and / or approver ID, process classification ID, task receiving time and task processing time; The data extraction and analysis of historical approval information using a preset processing model includes: Fix the approver and / or approver ID and process classification ID in the historical approval information; Analyze the task receiving time and the task processing time using the preset processing model to confirm the probability distribution of the task processing time for the same approver and / or approver ID under the same process classification ID; The aggregate approval rule is constructed according to the probability distribution, and the aggregate approval rule at least includes the push time.
4. A method for implementing collective approval according to claim 3, characterized in that: After constructing the summary approval rule according to the probability distribution, the method further includes: Traverse all approvers and / or approver IDs and all process classification IDs to obtain a summary approval rule library.
5. A method for implementing collective approval according to claim 4, characterized in that: After obtaining the summary approval rule base, the method further includes: Using the preset processing model to recognize the input speech for creating the summary approval rule to determine the approver and / or the approver ID and the approval type; Determine the corresponding process classification ID according to the approval type, and query the summary approval rule library through the approver and / or approver ID and the process classification ID; Generate and enable aggregate approval rules based on query results.
6. A method for implementing collective approval according to claim 1, characterized in that: According to the queried rule content, the pending approval tasks are summarized and pushed, including: If the approver ID and / or process classification ID is found in the summary approval rule, the status field corresponding to the pending approval task is modified to pending push; The tasks to be approved are summarized and pushed according to the scheduled tasks.
7. A method for implementing collective approval according to claim 6, characterized in that: According to the scheduled tasks, the tasks to be pushed are summarized and pushed, including: Polling the summary approval rules according to the scheduled task; If the corresponding push time in the summary approval rule is earlier than the current time, the task push is triggered and the pending approval task is pushed out immediately; If the push time corresponding to the summary approval rule is later than the current time, when the push time is reached, the pending approval tasks with the status field "to be pushed" in the task table are pushed in a summary manner.
8. A method for implementing collective approval according to claim 1, characterized in that: According to the queried rule content, the pending approval tasks are summarized and pushed, and also include: If the approver ID and / or process classification ID is not found in the summary approval rule, the task to be approved is pushed out immediately, and the value of the new field in the task table is updated to "no".
9. A method for implementing collective approval according to claim 1, characterized in that: The method further comprises: Set the front-end display page; Displaying the tasks to be approved that are pushed in summary on the front-end display page, the display method is a parent-child structure display, the parent-level data in the parent-child structure is displayed as summary approval, and the child-level data is displayed as each task to be approved; In response to the approver clicking the approval button and / or one-click approval operation, the tasks to be approved are approved individually and / or in batches.
10. A system for implementing summary approval, characterized in that: The system comprises: A rule creation module, which creates an approval task summary rule according to a preset summary rule table, wherein the summary rule table at least includes a process classification ID; The rule creation module uses a preset processing model to perform data extraction and analysis on historical approval information, and constructs summary approval rules based on the results of the data extraction and analysis; A task table modification module adds a new field to the task table, wherein the new field is used to indicate whether the task to be approved is a summary approval push task; A rule query module, when there is a new task to be approved, queries the approval task summary rule according to the process classification ID corresponding to the task to be approved, and assigns a value of yes to the new field in the task table according to the query result; The task pushing module queries the summary approval rule according to the approver ID and / or process classification ID corresponding to the pending approval task, and pushes the pending approval task in a summary manner according to the query rule content.