Task approval method and device, computer equipment and storage medium

Abstract

The invention belongs to the technical field of data processing, and relates to a task approval method which comprises the following steps: judging whether a processing request triggered by a user and corresponding to a preset approval operation service is received or not; if yes, obtaining examination and approval configuration information from the processing request, and extracting corresponding examination and approval parameters from the examination and approval configuration information based on the parameter type; transmitting the examination and approval parameters to an examination and approval component; verifying the examination and approval parameters based on a verification strategy; if the examination and approval parameters pass the verification, creating an examination and approval task based on the examination and approval parameters; and sending the approval task to an approver, so that the approver performs approval processing on the approval task. The invention further provides a task approval device, computer equipment and a storage medium. In addition, the approval task can be stored in the block chain. The method can be applied to task examination and approval processing scenes in the financial field and the medical field, and can achieve the efficient and intelligent generation and examination and approval processing of the examination and approval task based on the use of the examination and approval component.

Description

Technical Field

[0001] The present application relates to the field of data processing technology and can be applied to fields such as financial technology and digital medicine, and in particular to task approval methods, devices, computer equipment and storage media. Background Art

[0002] Against the backdrop of accelerating digital transformation, approval processes for various businesses are becoming increasingly complex and frequent, placing higher demands on the efficiency and flexibility of approval systems. However, existing approval systems have exposed numerous issues in practical applications, making it difficult to meet the demand for efficient and flexible approval.

[0003] Specifically, the existing approval system requires a lot of customization and docking work. When initiating an audit task, a lot of development work is often required. When financial institutions launch new financial products or adjust business rules, the approval system needs to update its functions and optimize its processes accordingly. Take a bank's newly launched online credit loan product for small and micro enterprises as an example. Since this product differs from traditional loan products in terms of loan amount, term, interest rate, repayment method, etc., its approval process also needs to be redesigned. At this time, technical personnel need to devote a lot of energy to code writing, system testing and other work to ensure that the new audit task can be smoothly initiated and executed in the approval system. This undoubtedly prolongs the time it takes to launch new businesses and reduces the market response speed of financial institutions.

[0004] The direct consequence of this highly customized and complex development requirement is inefficient approval processes. Under the traditional approval model, a loan application may require review by multiple stages and departments, each requiring manual intervention and system interaction, resulting in a lengthy approval cycle. For example, the approval process for large-scale corporate project loans can take weeks or even months from application submission to final approval. During this time, issues such as poor system integration and cumbersome processes can hinder the approval process, severely impacting the company's cash flow and business development, and reducing customer satisfaction.

[0005] Therefore, there is an urgent need to provide a new type of approval system to reduce customization and docking work, reduce the initiation cost of audit tasks, and improve approval efficiency, so as to better meet the processing needs of efficient and flexible approval. Summary of the Invention

[0006] The purpose of the embodiments of the present application is to provide a task approval method, apparatus, computer equipment and storage medium to solve the technical problem of low approval efficiency in existing approval systems.

[0007] In a first aspect, a task approval method is provided, comprising:

[0008] Determine whether a processing request corresponding to a preset approval operation service triggered by a user is received; wherein the processing request carries approval configuration information;

[0009] If yes, obtaining the approval configuration information from the processing request, and extracting corresponding approval parameters from the approval configuration information based on a preset parameter type;

[0010] Passing the approval parameters to a preset approval component;

[0011] Verifying the approval parameters based on a preset verification strategy;

[0012] If the approval parameters pass the verification, then based on the approval component, a corresponding approval task is created using the approval parameters;

[0013] The approval task is sent to the relevant approval personnel so that the approval task can be approved by the approval personnel.

[0014] In a second aspect, a task approval device is provided, comprising:

[0015] A first determination module is configured to determine whether a processing request corresponding to a preset approval operation service triggered by a user has been received; wherein the processing request carries approval configuration information;

[0016] A first acquisition module is configured to acquire the approval configuration information from the processing request, and extract corresponding approval parameters from the approval configuration information based on a preset parameter type;

[0017] A transfer module, used for transferring the approval parameters to a preset approval component;

[0018] A verification module, configured to verify the approval parameters based on a preset verification strategy;

[0019] A creation module, configured to create a corresponding approval task based on the approval component using the approval parameters if the approval parameters pass verification;

[0020] The sending module is used to send the approval task to the relevant approval personnel so that the approval task can be approved by the approval personnel.

[0021] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned task approval method when executing the computer program.

[0022] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned task approval method are implemented.

[0023] In the scheme implemented by the above-mentioned task approval method, device, computer device and storage medium, it is first determined whether a processing request corresponding to a preset approval operation business is received, which is triggered by a user; wherein the processing request carries approval configuration information; if so, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on a preset parameter type; then the approval parameters are passed to a preset approval component; then the approval parameters are verified based on a preset verification strategy; if the approval parameters pass the verification, the approval component uses the approval parameters to create a corresponding approval task; finally, the approval task is sent to the relevant approval personnel for the approval personnel to approve the approval task. When the present application receives a processing request corresponding to a preset approval operation business triggered by a user, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on the use of parameter types, and then the approval parameters are passed to the preset approval component. When the approval parameters pass the verification based on the use of the verification strategy, the approval component uses the approval parameters to create a corresponding approval task, and finally, the approval task is sent to the relevant approval personnel for the approval personnel to approve the approval task. This application can realize the efficient and intelligent generation and approval processing of approval tasks through the use of approval components, which can meet the needs of different business scenarios, effectively improve the approval efficiency, and reduce the development workload of the business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the solutions in this application, a brief introduction will be given below to the drawings required for use in the description of the embodiments of this application. Obviously, the drawings described below are some embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0025] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0026] Figure 2 is a flowchart of an embodiment of a task approval method according to the present application;

[0027] Figure 3 is a structural diagram of an embodiment of a task approval device according to the present application;

[0028] Figure 4It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0030] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0031] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0032] like Figure 1 As shown, system architecture 100 may include a terminal device 101, a network 102, and a server 103. Terminal device 101 may be a laptop computer 1011, a tablet computer 1012, or a mobile phone 1013. Network 102 is a medium for providing a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0033] The user can use the terminal device 101 to interact with the server 103 via the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0034] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing. In addition to the laptop computer 1011, tablet computer 1012 or mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a laptop computer and a desktop computer, etc.

[0035] The server 103 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal device 101 .

[0036] It should be noted that the task approval method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the task approval device is generally set in the server / terminal device.

[0037] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0038] Continue to refer Figure 2 , shows a flowchart of an embodiment of the task approval method according to the present application. According to different needs, the order of the steps in the flowchart can be changed, and some steps can be omitted. The task approval method provided in the embodiment of the present application can be applied to any scenario that requires task approval, and the task approval method can be applied to products in these scenarios, for example, task approval processing scenarios in the financial field and the medical field. The task approval method includes the following steps:

[0039] Step S201 : determining whether a processing request corresponding to a preset approval operation service triggered by a user is received; wherein the processing request carries approval configuration information.

[0040] In this embodiment, the task approval method is executed on the electronic device (eg Figure 1The server / terminal device shown in the figure) can obtain a user-triggered processing request corresponding to a preset approval operation business through a wired connection or a wireless connection. It should be noted that the above-mentioned wireless connection method may include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (Ultra Wide Band) connection, and other wireless connection methods currently known or developed in the future. The execution entity of this application is specifically a task approval system, which can be simply referred to as the system. The system has a pre-built approval component. The above-mentioned processing request is a request to initiate approval when a user has a need to perform task approval processing on a certain approval operation business. The above-mentioned processing request carries approval configuration information, which includes at least a new approval chain entered by the user, a new approval task type, a new approval policy, and a new approval business type. Specifically, the new approval chain includes: configuring status flow conditions for each approval node according to the business approval process requirements (for example, a node must meet specific business conditions before it can flow to the next node) and specifying the role responsible for review at that node (such as department manager, financial director, etc.). New approval task types include: defining different approval task types, such as "supplier basic information review", "product listing review", "advertising banner configuration review", etc., and giving each task type a specific business meaning and identification. New approval strategies include: configuring the default task type for each approval chain, and setting the approval notification sending strategy, including the notification method (such as email, internal message, etc.), notification time (such as when the task is assigned, the approval is about to time out, etc.), and notification objects (such as approvers, CCs, etc.). New approval business types include: in the front-end workbench, classifying approval tasks according to business type, such as "My To-Do" (approval tasks that the current user needs to handle), "My Tracking" (the current progress of approval tasks initiated by users), "My Approvals" (approval tasks that users have completed), etc. Different business types correspond to different approval page display logic and operation entrances.

[0041] This application can be applied to task approval processing scenarios in the financial and medical fields. For example, in the financial field, the approval tasks required to be created for the above-mentioned approval operation business may include customer insurance limit approval tasks, insurance claim application approval tasks, insurance product rate adjustment approval tasks, etc. In the medical field, the approval tasks required to be created for the above-mentioned approval operation business may include drug clinical trial project approval tasks, doctor remote consultation permission activation approval tasks, patient electronic medical record decryption application approval tasks, etc.

[0042] Step S202: If yes, obtain the approval configuration information from the processing request, and extract corresponding approval parameters from the approval configuration information based on a preset parameter type.

[0043] In this embodiment, the corresponding approval configuration information can be extracted by parsing the processing request. The parameter types include at least process name type, business type, business key type, approval processing description type, approval chain common parameter type, and business snapshot data type. Specifically, the parameters required for initiating task approval can be extracted from the approval configuration information using the initiate review interface provided by the approval component. These parameters include the process name (specifying the name of the approval chain to which the approval task follows), the business type (indicating the specific business type of the approval task, such as "supplier basic information review"), the business key (used to uniquely identify the business data corresponding to the approval task, such as the supplier ID or product ID), the approval processing description (a brief description of the approval matter when initiating the approval, to facilitate the approver's understanding of the approval background), the approval chain common parameters (which may include some common parameters in the approval chain process, such as approval priority and urgency), and the business snapshot data (when initiating the approval, the current business data status is saved and transmitted in snapshot form for review and comparison during the approval process. Furthermore, the transmitted parameters can be used to implement a duplicate prevention function to prevent the repeated initiation of the same approval task).

[0044] Among them, when calling the initiate review interface, the process name parameter that needs to be passed is obtained from the approval chain configuration. It specifies the approval chain that the approval task will follow; the business type parameter that needs to be passed is obtained from the approval task type configuration. It indicates the specific business type to which this approval task belongs; the approval chain public parameters (such as approval priority and urgency) are obtained from the approval policy; the business key and business snapshot data usually come from the specific business operations of the business system. The business key is used to uniquely identify business data, ensure the uniqueness of the approval task and prevent duplicate processing; the business snapshot data is a status snapshot of the current business data, which is used to provide contextual information during the approval process.

[0045] Step S203: passing the approval parameters to a preset approval component.

[0046] In this embodiment, the approval component is a pre-built core module used to support the efficient and standardized operation of the approval process. By providing flexible configuration capabilities, standardized interface interaction, process monitoring and traceability functions, and data security mechanisms, it realizes the automation, decoupling, and standardization of the approval process. The following are the core functions of the approval component and their detailed explanation:

[0047] 1. Approval chain and policy configuration. Functional goal: To achieve flexible definition and policy-driven approval process. Approval chain configuration: Supports the definition of multi-node approval process through a visual interface or configuration file, including node status flow conditions (such as amount threshold, risk level), role permissions (such as financial director, department manager) and branch logic (such as parallel approval, conditional jump). Approval policy management: Provides the ability to configure default task type binding, notification policies (email / internal letter templates, timeout reminder rules) and approval time limits (such as automatic upgrade if not processed within 24 hours). Business value: Quickly adapt to the approval needs of different business scenarios and reduce hard-coding development costs.

[0048] 2. Approval Task Type Management. Functional Objective: Implement standardized classification of approval scenarios. Task Type Definition: Supports the creation of types such as "Supplier Review" and "Contract Approval," associating business fields (such as supplier ID and contract amount) with process templates. Business Value: Improves cross-departmental collaboration efficiency through unified approval entry points and field specifications.

[0049] 3. Approval Initiation Interface. Functional Objective: Provide standardized access capabilities to support rapid integration of business systems. Interface Parameter Design: Process Identifier: Bind to a preconfigured approval chain. Business Metadata: Convey business keys (such as order IDs), approval instructions, and snapshot data (such as supplier qualification documents). Anti-Duplicate Verification: Determine duplicate initiation based on the business key + snapshot hash value. Business Value: Decouple the approval process from business logic, reducing system coupling.

[0050] 4. Approval execution engine. Functional objective: Drive automated approval processes. Core capabilities: Node state machine: Automatically advance processes based on flow conditions (e.g., "Budgets exceeding 100,000 require approval from the general manager"). Permission verification: Integrates with the RBAC model to verify whether the operator belongs to the specified role. Multi-person collaboration: Supports co-signature (requires unanimous approval), signature (any one agrees), and designated modification permissions (e.g., legal affairs department modifying contract terms). Business value: Reduces manual intervention and operational risks.

[0051] 5. Operation Logging and Auditing. Functional Objective: Ensure traceability of the approval process. Operation Log: Record each approval action (operator, time, results, comments) and data changes (such as the supplier name before and after the modification). Approval Chain Traceability: Provides a visual flowchart showing the node flow path, approval time, and key comments. Business Value: Meet compliance audit requirements and quickly identify process bottlenecks.

[0052] 6. Message Notification Mechanism. Functional Objective: Enable real-time synchronization of approval status changes. MQ Message Push: Event Types: Supports events such as task assignment, timeout warning, and approval completion. Subscription Mode: Business systems subscribe to topics (such as approval.task.created) and process on demand (e.g., updating an order status to "pending approval"). Business Value: Reduces polling queries and improves system response efficiency.

[0053] 7. General Verification Module. Functional Objective: Ensure the standardization of the approval process and data accuracy. Verification Rules: Permission Verification: Verify that the operator is in the approval node role list. Data Verification: Check required fields (such as contract amount), format (such as email format), and logical consistency (such as end date > start date). Anti-tampering Verification: Compare snapshot data with current business data to prevent malicious data modification during the approval process. Business Value: Intercept abnormal operations and reduce the risk of process interruption.

[0054] 8. Front-end workbench integration. Functional goal: Provide a user-friendly approval operation interface. Core functions: To-do task aggregation: Classified display by business type (My To-do / My Tracking / My Approval), support sorting by urgency and initiation time. Snapshot data preview: Display business data (such as supplier business license, product pictures) in the form of cards or tables. Approval operation panel: Provides "Approve", "Reject", and "Transfer" buttons and an opinion input box, and supports uploading attachments. Business value: Improve the operating efficiency of approvers and reduce learning costs.

[0055] 9. Scalability Design. Functional Objective: Support future changes in business requirements. Open API: Provides RESTful interfaces for third-party systems to access functions such as approval chain queries and task status updates. Plug-in Architecture: Supports custom validation rules (such as integrating with risk control systems) and notification methods. Business Value: Reduces system upgrade costs and enables rapid response to market changes.

[0056] Step S204: verify the approval parameters based on a preset verification strategy.

[0057] In this embodiment, the specific implementation process of verifying the approval parameters based on the preset verification strategy will be further described in detail in subsequent specific embodiments of this application and will not be elaborated on here.

[0058] Step S205: If the approval parameters pass the verification, a corresponding approval task is created based on the approval component using the approval parameters.

[0059] In this embodiment, upon detecting that the approval parameters have passed verification, the approval component creates a new approval task based on the verified approval parameters. The approval task is assigned a unique identifier, typically a UU ID or other unique ID, to facilitate tracking and management throughout the approval process. The approval component determines the initial status of the approval task based on the configuration of the approval chain. It also determines the flow path of the approval task, specifically the order and conditions under which the approval task will flow to the next approval node. Furthermore, the approval component stores the newly created approval task information in a database, including detailed information about the approval task, its current status, and its flow path. This stored information will be used for subsequent approval process management and tracking.

[0060] Step S206: Send the approval task to the relevant approval personnel so that the approval personnel can approve the approval task.

[0061] In this embodiment, the specific implementation process of sending the approval task to the relevant approval personnel will be further described in detail in subsequent specific embodiments of this application and will not be elaborated on here.

[0062] The present application first determines whether a processing request corresponding to a preset approval operation business triggered by a user is received; wherein the processing request carries approval configuration information; if so, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on a preset parameter type; the approval parameters are then passed to a preset approval component; the approval parameters are then verified based on a preset verification strategy; if the approval parameters pass the verification, the approval component uses the approval parameters to create a corresponding approval task; and finally, the approval task is sent to the relevant approval personnel for the approval personnel to approve the approval task. When the present application receives a processing request corresponding to a preset approval operation business triggered by a user, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on the use of parameter types, and then the approval parameters are passed to the preset approval component. When the approval parameters pass the verification based on the use of the verification strategy, the approval component uses the approval parameters to create a corresponding approval task, and finally, the approval task is sent to the relevant approval personnel for the approval personnel to approve the approval task. This application can realize the efficient and intelligent generation and approval processing of approval tasks through the use of approval components, which can meet the needs of different business scenarios, effectively improve the approval efficiency, and reduce the development workload of the business system.

[0063] In some optional implementations, step S204 includes the following steps:

[0064] Perform an integrity check on the approval parameters.

[0065] In this embodiment, an integrity check can be performed on the obtained approval parameters to ensure that all required parameters have been provided, and a corresponding integrity check result can be generated, wherein the integrity check result includes whether the approval parameters pass the integrity check or fail the integrity check.

[0066] If the approval parameter passes the integrity check, the approval parameter is repeatedly checked.

[0067] In this embodiment, the approval component pays special attention to the business key and anti-duplicate parameters, which are used to prevent duplicate approval tasks. Specifically, the approval component uses the business key and anti-duplicate parameters to query the system to check whether the same approval task already exists. If not, the approval parameters are deemed to have passed the validity check; otherwise, the approval parameters are deemed to have failed the validity check. The business key is typically a unique identifier for the business data, such as a supplier ID or product ID, to ensure that the same business data is not repeatedly approved.

[0068] If the approval parameter passes the repeated verification, the validity of the approval parameter is verified.

[0069] In this embodiment, the validity of the approval parameters can be checked to determine whether the values ​​of the approval parameters comply with business rules and constraints. For example, the validity of the process name and whether the business type is supported can be verified. If they comply, the approval parameters are determined to have passed the validity check; otherwise, the approval parameters are determined to have failed the validity check.

[0070] If the approval parameter passes the legality check, it is determined that the approval parameter passes the check; otherwise, it is determined that the approval parameter fails the check.

[0071] In this embodiment, only when it is detected that the approval parameters have passed the integrity check, the duplication check and the legality check at the same time, will the approval parameters be determined to have passed the verification; otherwise, it will be determined that the approval parameters have failed the verification.

[0072] This application performs an integrity check on the approval parameters; if the approval parameters pass the integrity check, the approval parameters are repeatedly checked; if the approval parameters pass the repeated check, the approval parameters are then checked for legality; if the approval parameters pass the legality check, the approval parameters are determined to have passed the check, otherwise, the approval parameters are determined to have failed the check. This application combines multiple verification strategies corresponding to integrity verification, repeated verification, and legality verification to perform verification processing on the approval parameters, effectively ensuring the accuracy and standardization of the verification results.

[0073] In some optional implementations of this embodiment, step S206 includes the following steps:

[0074] Acquire the approval policy from the approval configuration information.

[0075] In this embodiment, after creating an approval task, the approval component reads the pre-configured approval configuration information and obtains the configured approval policy from the approval configuration information. The approval policy includes detailed information on the notification sending policy, such as the notification method, notification time, and notification recipient.

[0076] Obtain a notification sending policy from the approval policy.

[0077] In this embodiment, further information acquisition can be performed through the approval policy to obtain the required notification sending policy.

[0078] The approval personnel and notification method corresponding to the approval task are determined based on the notification sending strategy.

[0079] In this embodiment, the relevant personnel who need to receive notifications can be identified based on the configuration of the notification delivery policy described above and serve as the approval personnel. Notification recipients typically include approvers and may also include copy recipients, etc. The specific roles and personnel are determined by the actual configuration of the approval chain. Furthermore, the notification method configured in the approval policy can be obtained and the appropriate notification channel can be selected. Common notification methods include email, internal messages, and SMS messages, with the specific method determined by business needs and system capabilities.

[0080] Generate notification information corresponding to the approval task.

[0081] In this embodiment, corresponding notification information may be generated according to the above-mentioned approval task. Specifically, the content of the notification information may include brief information about the approval task, details of the approval task that the approver needs to handle, approval deadline, etc.

[0082] Based on the notification method, the notification information is sent to the approval personnel.

[0083] In this embodiment, the generated notification information can be sent to the relevant reviewers via the selected notification method. The delivery process must ensure the timeliness and reliability of the notification to avoid delays in the review process due to notification failures. Furthermore, the delivery of the notification information can be recorded, including the time, method, and recipient. A notification log can be created for subsequent auditing and troubleshooting, ensuring traceability of the notification process.

[0084] This application obtains the approval policy from the approval configuration information; obtains the notification sending policy from the approval policy; then determines the approver and notification method corresponding to the approval task based on the notification sending policy; then generates notification information corresponding to the approval task; and subsequently sends the notification information to the approver based on the notification method. This application obtains the approval policy from the approval configuration information, obtains the notification sending policy from the approval policy, then determines the approver and notification method corresponding to the approval task based on the use of the notification sending policy; then generates notification information corresponding to the approval task; and subsequently sends the notification information to the approver based on the use of the notification method, thereby effectively improving the intelligence and standardization of the sending of notification information corresponding to the approval task.

[0085] In some optional implementations, after step S206, the electronic device may further perform the following steps:

[0086] Determine whether an approval action for the approval task issued by the approval person has been received.

[0087] In this embodiment, when the approver has the authority to approve a received approval task, an approval action corresponding to the approval task is triggered, such as clicking an approval button corresponding to the approval task. If a click of the approval button corresponding to the approval task is detected, it can be determined that an approval action for the approval task issued by the approver has been received.

[0088] If yes, display the default approval page.

[0089] In this embodiment, the above-mentioned approval page is a pre-built visual page for assisting relevant personnel, ie, the approval personnel, in performing task approval processing.

[0090] The business snapshot data corresponding to the approval task is obtained based on a preset general snapshot data query interface.

[0091] In this embodiment, the general snapshot data query interface is a functional interface provided by the approval component for users to obtain business snapshot data. The business snapshot data of the approval task can be queried by using the general snapshot data query interface.

[0092] The task details of the approval task are obtained based on the preset approval initiation interface.

[0093] In this embodiment, the initiating approval interface is a functional interface provided by the approval component for obtaining task details. The task details of the approval task can be queried by using the initiating approval interface.

[0094] The business snapshot data and the task details are displayed on the approval page.

[0095] In this embodiment, the business snapshot data and task details associated with the approval task are displayed on the approval page. Thus, by viewing the business snapshot data and task details on the approval page, the reviewer can understand the background and specific content of the approval matter, providing a basis for the reviewer's approval operation. This allows the reviewer to conveniently view and process approval tasks, thereby facilitating the approval process.

[0096] This application determines whether the approval action for the approval task issued by the approval personnel has been received; if so, the preset approval page is displayed; then the business snapshot data corresponding to the approval task is obtained based on the preset general snapshot data query interface; and the task details of the approval task are obtained based on the preset initiation approval interface; and the business snapshot data and the task details are subsequently displayed on the approval page. When this application receives the approval action for the approval task issued by the approval personnel, it will automatically obtain the business snapshot data and task details corresponding to the approval task based on the general snapshot data query interface, and will intelligently display the business snapshot data and task details on the preset approval page, so that the reviewer can easily view and process the approval task, thereby promoting the approval process, which is conducive to improving the work experience and work efficiency of the approval personnel, and thereby improving the approval efficiency of the approval task.

[0097] In some optional implementations, after the step of displaying the business snapshot data and the task detailed information on the approval page, the electronic device may further perform the following steps:

[0098] During the process of the approval personnel approving the approval task, an approval operation issued by the approval personnel is obtained.

[0099] In this embodiment, during the process of the approver approving the above-mentioned approval task, each approval operation issued by the approver will be recorded.

[0100] The approval operation is verified to determine whether the approval operation is an abnormal operation.

[0101] In this embodiment, the abnormal operation includes an unauthorized operation (e.g., an approval operation performed by a non-designated approver) or an erroneous operation (e.g., a data format error, a logical error, etc.). The approval operation can be detected to determine whether it is an unauthorized operation or an erroneous operation. If so, the approval operation is determined to be an abnormal operation; otherwise, the approval operation is determined not to be an abnormal operation.

[0102] If so, generate a reminder message corresponding to the abnormal operation.

[0103] In this embodiment, the target operation information corresponding to the abnormal operation can be obtained and filled into a preset reminder information template to generate the corresponding reminder information. The template content of the reminder information template is not specifically limited and can be constructed based on actual business needs. In addition, the target operation information can include the operator, operation information, operation type, etc.

[0104] Feedback the reminder information to the approval personnel.

[0105] In this embodiment, there is no limitation on the feedback method of the reminder information, and it can be selected according to actual business needs, for example, by using email notification, page window display, etc.

[0106] This application obtains the approval operation issued by the approving personnel during the process of the approving personnel approving the approval task; then verifies the approval operation to determine whether the approval operation is an abnormal operation; if so, generates reminder information corresponding to the abnormal operation; and subsequently feeds back the reminder information to the approving personnel. This application automatically obtains and verifies the approval operation issued by the approving personnel during the process of the approving personnel approving the approval task. If the approval operation is detected to be an abnormal operation, it automatically generates reminder information corresponding to the abnormal operation, and feeds back the reminder information to the approving personnel. This application can effectively prevent the approving personnel from making abnormal operations by verifying the approval operation issued by the approving personnel during the approval operation of the approval task, thereby effectively ensuring the legality and compliance of the approval operation, and thereby improving the reliability and stability of the system.

[0107] In some optional implementations of this embodiment, after the step of verifying the approval operation and determining whether the approval operation is an abnormal operation, the electronic device may further perform the following steps:

[0108] If the approval operation is not an abnormal operation, a preset message generation strategy is obtained.

[0109] In this embodiment, the message generation strategy specifically implements an MQ messaging mechanism corresponding to approval operations. MQ (Message Queue) is an asynchronous communication mechanism that allows different systems or components to communicate by sending and receiving messages. The MQ messaging mechanism decouples the approval component from the business system, improving system flexibility and scalability. The message generation strategy includes generating and sending an MQ message for each approval action taken by the approver.

[0110] Based on the message generation strategy, an MQ message corresponding to the approval operation is generated.

[0111] In this embodiment, an MQ message corresponding to the approval operation can be generated based on the policy content of the message generation policy, containing information about the status change of the approval task. The content of the MQ message may include the approval task ID, operation result, operation time, operator, etc. For example, an MQ message may include the following information: Approval task ID: uniquely identifies the approval task. Operation result: "Approved" or "Rejected." Operation time: the time when the approval operation was completed. Operator: the user ID or user name performing the approval operation.

[0112] Determine the target system corresponding to the approval task.

[0113] In this embodiment, the target system refers to a business system that subscribes to the MQ message queue sent by the approval component.

[0114] Send the MQ message to the target system.

[0115] In this embodiment, after the MQ message is sent to the target system, the target system will perform corresponding business processing according to the message content after receiving the MQ message, such as updating the business data status, notifying the initiator of the approval result, etc.

[0116] If the present application detects that the approval operation is not an abnormal operation, it obtains a preset message generation strategy; then, based on the message generation strategy, it generates an MQ message corresponding to the approval operation; then, based on the message generation strategy, it determines the target system corresponding to the approval task; and subsequently sends the MQ message to the target system. When the present application detects that the approval operation is not an abnormal operation, it intelligently generates an MQ message corresponding to the approval operation based on the use of the message generation strategy, and sends the MQ message to the target system corresponding to the approval task. By sending MQ messages, the task approval system can effectively manage and track the approval process, ensuring the timely delivery of approval results and the status update of the business system. In addition, the MQ message sending mechanism plays a bridging role in the approval process, allowing the approval component and the business system to operate independently while maintaining information synchronization and consistency.

[0117] In some optional implementations of this embodiment, after step S206, the electronic device may further perform the following steps:

[0118] After the approving personnel completes the approval process for the approval task and submits the corresponding approval result, the approval operation information corresponding to the approving personnel is recorded.

[0119] In this embodiment, when the approver is approving the approval task, he / she will process the approval task according to the business requirements and approval standards. The approver can choose operations such as "approval" or "rejection", and the specific options are determined by the approval policy and business rules. In some cases, the approver can also fill in approval opinions or suggestions for the initiator's reference. Among them, the approver will submit the approval result after completing the approval operation. After receiving the approval result submitted by the approver, the system will automatically record the approval operation information corresponding to the approver. The recorded approval operation information usually includes the operator (i.e., the current approver), operation time (i.e., submission time), operation result (such as "approval" or "rejection"), approval opinion, etc.

[0120] The approval operation information is stored and processed.

[0121] In this embodiment, the recorded approval operation information can be stored in a database to ensure the traceability of the approval process. The operation log of the approval operation can also be associated with the approval task to facilitate subsequent query and audit.

[0122] Get the initial task status of the approval task.

[0123] In this embodiment, the current status of the approval task may be queried to obtain the corresponding initial task status.

[0124] The initial task status of the approval task is updated based on the approval result.

[0125] In this embodiment, the status of the approval task can be updated according to the approval result. For example, if the approval result is "approved", the approval task may be transferred to the next approval node; if it is "rejected", the approval task may be terminated or returned to the initiator for modification.

[0126] After the approving personnel completes the approval process for the approval task and submits the corresponding approval result, this application records the approval operation information corresponding to the approving personnel; then stores and processes the approval operation information; then obtains the initial task status of the approval task; and subsequently updates and processes the initial task status of the approval task based on the approval result. After the approving personnel completes the approval process for the approval task and submits the corresponding approval result, this application automatically and intelligently records the approval operation information corresponding to the approving personnel, and stores and processes the approval operation information, thereby ensuring the security of the approval operation information and the traceability of the approval process. In addition, the initial task status of the approval task will be automatically updated based on the obtained approval result, thereby ensuring the accuracy and timeliness of the task status of the approval task, so that the task approval system can effectively manage and track the approval process.

[0127] In some optional implementations, the user information obtained is obtained with the user's consent and complies with relevant laws and policies.

[0128] In addition, any software tools or components not provided by our company that appear in the embodiments of this application are merely examples and do not represent actual use.

[0129] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0130] It should be emphasized that in order to further ensure the privacy and security of the above-mentioned approval tasks, the above-mentioned approval tasks can also be stored in a node of a blockchain.

[0131] The blockchain referred to in this application refers to a new application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of the information (to prevent counterfeiting) and generate the next block. Blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0132] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Artificial Intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to achieve optimal results.

[0133] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware via computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes in the above-described method embodiments. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0134] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0135] Further references Figure 3 , as a response to the above Figure 2 In order to realize the method shown in the figure, the present application provides an embodiment of a task approval device. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0136] like Figure 3 As shown, the task approval device 300 of this embodiment includes: a first judgment module 301, a first acquisition module 302, a transmission module 303, a verification module 304, a creation module 305 and a sending module 306.

[0137] The first determination module 301 is configured to determine whether a processing request corresponding to a preset approval operation service triggered by a user has been received; wherein the processing request carries approval configuration information;

[0138] A first obtaining module 302 is configured to obtain the approval configuration information from the processing request and extract corresponding approval parameters from the approval configuration information based on a preset parameter type;

[0139] The transmission module 303 is used to transmit the approval parameters to the preset approval component;

[0140] Verification module 304, used to verify the approval parameters based on a preset verification strategy;

[0141] A creation module 305 is configured to create a corresponding approval task using the approval parameters based on the approval component if the approval parameters pass verification;

[0142] The sending module 306 is used to send the approval task to the relevant approval personnel so that the approval personnel can approve the approval task.

[0143] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0144] In some optional implementations of this embodiment, the verification module 304 includes:

[0145] A first check submodule, configured to perform integrity check on the approval parameters;

[0146] A second check submodule is configured to repeat the check on the approval parameter if the approval parameter passes the integrity check;

[0147] A third verification submodule is configured to perform a validity verification on the approval parameter if the approval parameter passes the repeated verification;

[0148] The determination submodule is configured to determine that the approval parameter has passed the verification if the approval parameter has passed the legality verification, and otherwise determine that the approval parameter has failed the verification.

[0149] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0150] In some optional implementations of this embodiment, the sending module 306 includes:

[0151] A first acquisition submodule is used to acquire the approval policy from the approval configuration information;

[0152] A second acquisition submodule is used to acquire a notification sending policy from the approval policy;

[0153] A determination submodule, configured to determine the approval personnel and notification method corresponding to the approval task based on the notification sending strategy;

[0154] A generation submodule, configured to generate notification information corresponding to the approval task;

[0155] The sending submodule is used to send the notification information to the approval personnel based on the notification method.

[0156] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0157] In some optional implementations of this embodiment, the task approval device further includes:

[0158] The second judgment module is used to judge whether the approval action for the approval task issued by the approval person has been received;

[0159] The first display module is used to display the preset approval page if yes;

[0160] A second acquisition module is used to acquire the business snapshot data corresponding to the approval task based on a preset general snapshot data query interface;

[0161] A third acquisition module is used to obtain task details of the approval task based on a preset approval initiation interface;

[0162] The second display module is used to display the business snapshot data and the task detailed information on the approval page.

[0163] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0164] In some optional implementations of this embodiment, the task approval device further includes:

[0165] A fourth acquisition module is used to acquire the approval operation issued by the approval personnel during the process of the approval personnel approving the approval task;

[0166] A third judgment module is used to verify the approval operation and determine whether the approval operation is an abnormal operation;

[0167] A first generating module, configured to generate, if yes, a reminder message corresponding to the abnormal operation;

[0168] The feedback module is used to feed back the reminder information to the approval personnel.

[0169] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0170] In some optional implementations of this embodiment, the task approval device further includes:

[0171] a fifth acquisition module, configured to acquire a preset message generation strategy if the approval operation is not an abnormal operation;

[0172] A second generating module is used to generate an MQ message corresponding to the approval operation based on the message generation strategy;

[0173] A determination module, configured to determine a target system corresponding to the approval task;

[0174] A sending module is used to send the MQ message to the target system.

[0175] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0176] In some optional implementations of this embodiment, the task approval device further includes:

[0177] A recording module is used to record the approval operation information corresponding to the approving personnel after the approving personnel completes the approval process for the approval task and submits the corresponding approval result;

[0178] A storage module, used for storing and processing the approval operation information;

[0179] A sixth acquisition module, configured to acquire the initial task status of the approval task;

[0180] An updating module is used to update the initial task status of the approval task based on the approval result.

[0181] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task approval method in the aforementioned embodiment, and are not described in detail here.

[0182] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0183] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0184] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.

[0185] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash memory card, etc. equipped on the computer device 4. Of course, the memory 41 may also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of the task approval method. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0186] In some embodiments, the processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions or process data stored in the memory 41, such as the computer-readable instructions for executing the task approval method.

[0187] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0188] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0189] In an embodiment of the present application, upon receiving a processing request triggered by a user corresponding to a preset approval operation business, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on the use of parameter types. The approval parameters are then passed to the preset approval component, and when the approval parameters are detected to have passed the verification based on the use of the verification strategy, the corresponding approval task is created using the approval parameters based on the approval component, and finally the approval task is sent to the relevant approval personnel so that the approval personnel can approve the approval task. This application can realize the efficient and intelligent generation and approval processing of approval tasks based on the use of the approval component, which can meet the needs of different business scenarios, effectively improve the approval efficiency, and reduce the development workload of the business system.

[0190] The present application also provides another embodiment, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the task approval method as described above.

[0191] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0192] In an embodiment of the present application, upon receiving a processing request triggered by a user corresponding to a preset approval operation business, the approval configuration information is obtained from the processing request, and the corresponding approval parameters are extracted from the approval configuration information based on the use of parameter types. The approval parameters are then passed to the preset approval component, and when the approval parameters are detected to have passed the verification based on the use of the verification strategy, the corresponding approval task is created using the approval parameters based on the approval component, and finally the approval task is sent to the relevant approval personnel so that the approval personnel can approve the approval task. This application can realize the efficient and intelligent generation and approval processing of approval tasks based on the use of the approval component, which can meet the needs of different business scenarios, effectively improve the approval efficiency, and reduce the development workload of the business system.

[0193] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0194] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.

Claims

1. A task approval method, characterized in that: The steps include: Determine whether a processing request corresponding to a preset approval operation service triggered by a user is received; wherein the processing request carries approval configuration information; If yes, obtaining the approval configuration information from the processing request, and extracting corresponding approval parameters from the approval configuration information based on a preset parameter type; Passing the approval parameters to a preset approval component; Verifying the approval parameters based on a preset verification strategy; If the approval parameters pass the verification, then based on the approval component, a corresponding approval task is created using the approval parameters; The approval task is sent to the relevant approval personnel so that the approval task can be approved by the approval personnel.

2. The task approval method according to claim 1, characterized in that: The step of verifying the approval parameters based on a preset verification strategy specifically includes: Performing integrity check on the approval parameters; If the approval parameter passes the integrity check, the approval parameter is repeatedly checked; If the approval parameters pass the repeated verification, the validity of the approval parameters is verified; If the approval parameter passes the legality check, it is determined that the approval parameter passes the check; otherwise, it is determined that the approval parameter fails the check.

3. The task approval method according to claim 1, characterized in that: The step of sending the approval task to the relevant approval personnel specifically includes: Acquiring an approval policy from the approval configuration information; Obtaining a notification sending strategy from the approval strategy; Determine the approval personnel and notification method corresponding to the approval task based on the notification sending strategy; Generating notification information corresponding to the approval task; Based on the notification method, the notification information is sent to the approval personnel.

4. The task approval method according to claim 1, characterized in that: After the step of sending the approval task to the relevant approval personnel, the method further includes: Determining whether an approval action for the approval task issued by the approver has been received; If yes, display the preset approval page; Acquiring business snapshot data corresponding to the approval task based on a preset general snapshot data query interface; and Obtaining detailed information of the approval task based on a preset approval initiation interface; The business snapshot data and the task details are displayed on the approval page.

5. The task approval method according to claim 4, characterized in that: After the step of displaying the business snapshot data and the task details on the approval page, the method further includes: During the process of the approval task being approved by the approval personnel, obtaining the approval operation issued by the approval personnel; Verifying the approval operation to determine whether the approval operation is an abnormal operation; If so, generating a reminder message corresponding to the abnormal operation; Feedback the reminder information to the approval personnel.

6. The task approval method according to claim 5, characterized in that: After the step of verifying the approval operation and determining whether the approval operation is an abnormal operation, the method further includes: If the approval operation is not an abnormal operation, obtaining a preset message generation strategy; Based on the message generation strategy, generate an MQ message corresponding to the approval operation; Determining a target system corresponding to the approval task; Send the MQ message to the target system.

7. The task approval method according to claim 1, characterized in that: After the step of sending the approval task to the relevant approval personnel, the method further includes: After the approving personnel completes the approval process for the approval task and submits the corresponding approval result, recording the approval operation information corresponding to the approving personnel; Storing and processing the approval operation information; Obtaining the initial task status of the approval task; The initial task status of the approval task is updated based on the approval result.

8. A task approval device, characterized in that: include: A first determination module is configured to determine whether a processing request corresponding to a preset approval operation service triggered by a user has been received; wherein the processing request carries approval configuration information; A first acquisition module is configured to acquire the approval configuration information from the processing request, and extract corresponding approval parameters from the approval configuration information based on a preset parameter type; A transfer module, used for transferring the approval parameters to a preset approval component; A verification module, configured to verify the approval parameters based on a preset verification strategy; A creation module, configured to create a corresponding approval task based on the approval component using the approval parameters if the approval parameters pass verification; The sending module is used to send the approval task to the relevant approval personnel so that the approval task can be approved by the approval personnel.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the task approval method according to any one of claims 1 to 7 when executing the computer-readable instructions.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the task approval method according to any one of claims 1 to 7.

Images