Examination and approval workflow processing method, device and equipment and computer readable storage medium

By receiving and updating the configuration information of card messages in the workflow processing system, the problem of error flow due to fixed format in card messages is solved, and the normal flow of card messages is achieved.

CN119005873APending Publication Date: 2024-11-22TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310551499.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-16
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The problem of fixed card message format in the existing workbench causes the approver to erroneously flow of the associated application form after clicking the agree, reject or all consent button, and cannot be updated or withdrawn in real time.

Method used

By receiving the approval request from the client, a card message is generated, and the second client displays it. After receiving the verification request, the update configuration information of the card message is obtained from the database, and the checksum control flow is performed based on the configuration information to ensure that even if the configuration information is modified, the configuration information is modified. , can also update card messages based on the latest information.

Benefits of technology

Ensure that card messages are always circulated based on the latest configuration information during the circulation process, avoid errors caused by configuration information modification, and ensure normal circulation of application forms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119005873A_ABST
    Figure CN119005873A_ABST
Patent Text Reader

Abstract

The invention provides an approval workflow processing method and device, electronic equipment, a computer program product and a computer readable storage medium. The method comprises the steps of receiving an approval request of a first client; generating a card message corresponding to the approval request; the card message is sent to a second client, so that the second client displays the card message, and the card message is used for the second client to receive the approval operation; a verification request sent by a second client is received, and the verification request is sent after the second client receives approval operation of agreeing at least one card message; acquiring updated configuration information of each card message from a database; and performing first verification based on the configuration information, and controlling circulation of the card message based on an obtained first verification result. According to the invention, normal circulation of the card message can be ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to computer technology, and in particular to an approval workflow processing method, apparatus, device and computer-readable storage medium. Background Art

[0002] When a user submits an application for leave, invoice reimbursement, etc. on the workbench, the message center will push a card message to the workbench of the approver and the copy recipient based on the application data, so that the approver can quickly process the application associated with the card message and the copy recipient can understand the application associated with the card message. The approver can click to approve or reject the application, or can process all the messages on the workbench with one click and agree to them all.

[0003] However, the format of the card message in the workbench is currently fixed. Once sent to the workbench, it cannot be withdrawn or the format modified. After the card message is pushed to the workbench of the approver and the cc recipient, if the associated configuration information of the card message has been modified by the administrator on the web page, when the approver clicks the Agree, Reject, and Agree to All buttons through the card message, it will cause the associated application form to flow incorrectly. Summary of the invention

[0004] The embodiments of the present application provide an approval workflow processing method, device, electronic device, computer-readable storage medium and computer program product, which can ensure the normal flow of card messages.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present application provides a method for processing an approval workflow, the method comprising:

[0007] receiving an approval request from a first client;

[0008] generating a card message corresponding to the approval request;

[0009] Sending the card message to the second client so that the second client displays the card message, wherein the card message is used for the second client to receive an approval operation;

[0010] receiving a verification request sent by the second client, wherein the verification request is sent by the second client after receiving the approval operation of approving at least one of the card messages;

[0011] Obtaining updated configuration information of each of the card messages from a database;

[0012] A first check is performed based on the configuration information, and the flow of the card message is controlled based on the obtained first check result.

[0013] The present application provides an approval workflow processing device, the device comprising:

[0014] A first receiving module, used to receive an approval request from a first client;

[0015] A generating module, used for generating a card message corresponding to the approval request;

[0016] A sending module, used for sending the card message to the second client, so that the second client displays the card message, wherein the card message is used for the second client to receive an approval operation;

[0017] A second receiving module is used to receive a verification request sent by the second client, wherein the verification request is sent by the second client after receiving the approval operation of approving at least one of the card messages;

[0018] An acquisition module, used for acquiring updated configuration information of each of the card messages from a database;

[0019] The verification module is used to perform a first verification based on the configuration information, and control the flow of the card message based on the obtained first verification result.

[0020] An embodiment of the present application provides an electronic device, the electronic device comprising:

[0021] A memory for storing computer executable instructions;

[0022] The processor is used to implement the approval workflow processing method provided in the embodiment of the present application when executing the computer executable instructions stored in the memory.

[0023] An embodiment of the present application provides a computer-readable storage medium storing a computer program or computer-executable instructions for implementing the approval workflow processing method provided in the embodiment of the present application when executed by a processor.

[0024] An embodiment of the present application provides a computer program product, including a computer program or computer executable instructions. When the computer program or computer executable instructions are executed by a processor, the approval workflow processing method provided in the embodiment of the present application is implemented.

[0025] The embodiments of the present application have the following beneficial effects:

[0026] After the second client receives the card message corresponding to the approval request and performs the approval operation on the card message, the card message is verified by obtaining the updated configuration information from the database, thereby ensuring that after the card message is sent to the second client, even if the configuration information of the card message is modified, the card message can still be updated based on the modified configuration information, thereby ensuring that the updated configuration information can be timely affected by the circulation of the card message. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of the architecture of the approval workflow processing system provided in the embodiment of the present application;

[0028] Figure 2 It is a schematic diagram of the structure of the server provided in the embodiment of the present application;

[0029] Figure 3 It is a flowchart of the approval workflow processing method provided in the embodiment of the present application;

[0030] Figure 4 This is a schematic diagram of the workbench approval window provided in the embodiment of the present application;

[0031] Figure 5 It is a flow chart of document error flow provided by the embodiment of the present application;

[0032] Figure 6 It is a schematic diagram of the process of correct flow of optimized documents provided in the embodiment of the present application;

[0033] Figure 7 It is a flow chart of the server twice verifying the card message associated configuration information provided by the embodiment of the present application;

[0034] Figure 8 It is a schematic diagram of enterprise document information in a query database provided by an embodiment of the present application;

[0035] Fig. 9 This is a schematic diagram of the operator identity provided in the embodiment of the present application;

[0036] Fig.10 is a schematic diagram of the switch configuration provided by an embodiment of the present application;

[0037] Fig.11 This is a schematic diagram of a pop-up window for filling in a signature provided in an embodiment of the present application;

[0038] Fig.12 This is a schematic diagram of a pop-up window for filling in a signature provided in an embodiment of the present application;

[0039] Fig.13 This is a schematic diagram of a pop-up window for clicking the Agree All button provided in an embodiment of the present application;

[0040] Fig.14 This is a schematic diagram of pushing a card by clicking the All Agree button provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0042] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0043] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0044] It should be pointed out that the data collection and processing in this application should be strictly in accordance with the requirements of relevant national laws and regulations when applied in practice, and the informed consent or separate consent of the personal information subject should be obtained, and subsequent data use and processing should be carried out within the scope of authorization of laws and regulations and the personal information subject.

[0045] Unless otherwise defined, all technical and scientific terms used in the embodiments of the present application have the same meanings as those commonly understood by those skilled in the art. The terms used in the embodiments of the present application are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0046] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0047] 1) Workbench: It is a page for displaying and using enterprise applications. Most functions of office applications are based on the workbench to enter the application operation, so that administrators / employees can easily find the corresponding functions, such as approval, log, attendance punching, etc.

[0048] 2) Card messages: There are static card messages and interactive card messages. Static card messages provide rich text styles, graphic layout modules, colorful card titles, etc. to send users eye-catching notifications, article lists with pictures and texts, and other messages. Interactive card messages use the interactive components provided by card messages. Users only need to click on the card to submit information, so they can quickly complete system operations such as office automation (OA) approval, voting statistics, and alarm processing without leaving the chat session.

[0049] 3) Data serialization: converting objects or data structures into a specific format so that they can be transmitted over the network or stored in memory or files. Deserialization is the opposite operation, restoring the object from the serialized data. The data format after object serialization can be binary, Extensible Markup Language (XML), or lightweight data exchange format (JavaScript Object Notation, JSON) and any other format. The focus of object or data serialization is on data exchange and transmission, such as in remote call technology, or in graphical user interface (GUI) control development, etc.

[0050] See also Figure 4 , Figure 4 It is a schematic diagram of the workbench approval window provided in the embodiment of the present application. The approver can view the information card on the workbench and click the Agree or Reject button for a single card message to agree or disagree with the application corresponding to the card message, or click the Agree All button in the workbench to agree to all applications corresponding to the unapproved card messages in the workbench at the same time. However, the card message format in the workbench of the related technology is fixed and cannot be updated in real time. Once sent to the workbench, it cannot be withdrawn and the format cannot be modified. If the card message associated configuration information is modified by the administrator on the web page after the applicant of the card message submits the card message to the workbench, and then the approver clicks the Agree, Reject or Agree All button through the card message, it will cause the associated application form of the card message to flow incorrectly.

[0051] The embodiments of the present application provide an approval workflow processing method, device, electronic device, computer-readable storage medium, and computer program product, which can ensure the normal flow of card messages. The exemplary application of the electronic device provided by the embodiments of the present application is described below. The electronic device provided by the embodiments of the present application can be implemented as a server. The exemplary application when the device is implemented as a server will be described below.

[0052] See also Figure 1 , Figure 1 It is a schematic diagram of the architecture of the approval workflow processing system provided in an embodiment of the present application. To support an approval workflow processing application, a terminal (terminal 200-1 and terminal 200-2 are shown as examples) is connected to a server 400 via a network 300. The network 300 may be a wide area network or a local area network, or a combination of the two.

[0053] The first client (for example, an instant messaging client for individuals or enterprises) runs in the terminal 200-1 and sends an approval request to the server 400 through the network 300. After receiving the approval request, the server 400 generates a card message corresponding to the approval request and sends it to the second client running in the terminal 200-2 through the network 300. After receiving the card message, the terminal 200-2 displays the card message on the display interface 210-2. The user operates the second client running in the terminal 200-2 and sends a verification request to the server 400 through the network 300. After receiving the verification request, the server 400 obtains the updated configuration information of the card message from the database 500, then performs a first verification based on the configuration information, and controls the flow of the card message based on the first verification result obtained.

[0054] Server 400 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. Terminals 200-1 and 200-2 can be smart phones, tablet computers, laptops, desktop computers, smart speakers, smart watches, and car terminals, etc., but are not limited to these. The terminal and the server can be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of the present application.

[0055] See also Figure 2 , Figure 2 is a schematic diagram of the structure of the server provided in the embodiment of the present application, Figure 2 The server 400 shown includes: at least one processor 410, a memory 430, and at least one network interface 420. The various components in the terminal 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 2 Various buses are labeled as bus system 440 .

[0056] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0057] The memory 430 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical drives, etc. The memory 430 may optionally include one or more storage devices that are physically remote from the processor 410.

[0058] The memory 430 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 430 described in the embodiments of the present application is intended to include any suitable type of memory.

[0059] In some embodiments, memory 430 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.

[0060] Operating system 431, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

[0061] A network communication module 432, used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 include: Bluetooth, Wireless Compatibility Authentication (WiFi), and Universal Serial Bus (USB), etc.;

[0062] In some embodiments, the device provided in the embodiments of the present application can be implemented in software. Figure 2 The approval workflow processing device 433 stored in the memory 430 is shown, which can be software in the form of a program and a plug-in, including the following software modules: a first receiving module 4331, a generating module 4332, a sending module 4333, a second receiving module 4334, an acquiring module 4335, and a checking module 4336. These modules are logical, and therefore can be arbitrarily combined or further split according to the functions implemented. The functions of each module will be described below.

[0063] The approval workflow processing method provided in the embodiment of the present application will be explained in combination with the exemplary application and implementation of the server provided in the embodiment of the present application.

[0064] The following describes the approval workflow processing method provided in the embodiment of the present application. As mentioned above, the execution subject of the approval workflow processing method in the embodiment of the present application may be the server 400. Therefore, the execution subject of each step will not be repeatedly described below.

[0065] See also Figure 3 , Figure 3 This is a flowchart of the approval workflow processing method provided in the embodiment of the present application, which will be combined with Figure 3 The steps shown are explained.

[0066] In step 101, an approval request from a first client is received.

[0067] In some embodiments, the approval request is an application document submitted by the applicant on the first client for approval. The approval request can be sent after being filled out on the workbench of the first client, or can be sent through the first client after being filled out on other terminals. The application documents submitted here may include various types of documents, such as financial applications (travel expense reimbursement, loan payment, invoice issuance, project funding application, general reimbursement, commission payment, etc.), personnel management applications (position change applications, recruitment forms, training assessment forms, regularization applications, salary payment, dismissal applications, resignation applications, personnel change applications, etc.), business-related applications (order applications, procurement applications, contract signing applications, business entertainment applications, etc.), and the types of documents for approval include but are not limited to the above-mentioned contents.

[0068] Taking the example of an applicant submitting a leave application, the application document that the applicant needs to fill out may include the following contents: leave type (such as personal leave, sick leave), leave start time, leave end time, leave reason, approver and cc, etc.

[0069] In step 102, a card message corresponding to the approval request is generated.

[0070] In some embodiments, after receiving the approval request of the first client, a corresponding card message template can be selected from the card message template according to the type of the submitted approval request, and the content of the application document corresponding to the approval request can be filled into the card message template to generate a card message of the corresponding approval request. The card message template here can include a title template, a description template, a picture template, a button template, etc., so that the message recipient can more intuitively understand and process the received card information. The card message can contain various types of content, such as OA approval, voting statistics, alarm processing, notifications and article lists. The card message generated here can be a static card message, that is, the card message can only display text messages or mixed text and image messages, and does not support interaction; it can also be an interactive card message, for example, the generated card message supports interaction by clicking the button in the card message, including jump links, form submission, dynamic display of information and other operations.

[0071] For example, in response to an approval request for a leave application submitted by an applicant, the card message generated by the server may include the following: title (XX's leave application), picture (can be a preset picture), body content (the reason for leave in the application document filled out by the applicant), form (leave start time, leave end time, total leave duration, leave type, etc. in the application document filled out by the applicant), attachments (can be certification documents such as a medical certificate in the applicant's application document), card message author name (i.e. the applicant's name), and operation buttons (including an approval button and a rejection approval button).

[0072] In step 103, a card message is sent to the second client so that the second client displays the card message.

[0073] In some embodiments, the card message is used for the second client to receive the approval operation. After the server generates the card message corresponding to the approval request, it sends the card message to the second client of the approver and the copy recipient, so that the card message is displayed on the workbench of the second client of the approver and the copy recipient. For the card message displayed on the second client of the approver, the approver can approve or reject the card message on the workbench; for the card message displayed on the second client of the copy recipient, the copy recipient can only view the content of the card message on the workbench, and cannot approve or reject the card message.

[0074] For example, in response to an approval request for a leave application submitted by an applicant, the content of the card message sent to the cc recipient's second client includes the title, picture, body content, form, attachment, the name of the card message author, etc., but does not include an operation button; while the content of the card message sent to the approver's second client includes both the above content and an approval button, so that the cc recipient can only view the content of the card message, while the approver can also agree to approve or reject the card message.

[0075] In step 104, a verification request sent by the second client is received.

[0076] In some embodiments, the verification request is sent by the second client after receiving the approval operation of approving at least one card message. Usually, there are multiple card messages to be approved or reviewed in the workbench of the second client of the approver or the copy recipient at the same time. When the approver clicks the approve button or the reject button for one of the card messages, or clicks the approve all button for multiple card messages in the workbench, the second client will send a secondary verification request to the server to verify the approval operation of approving one card message or all card messages.

[0077] For example, for the approval requests for leave applications submitted by applicants A and B, the server sends two corresponding card messages to the workstation of the approver's second client in succession. When the approver enters the workstation to process the two card messages, he can click the Agree Approval button or the Reject Approval button respectively. At this time, the second client sends a secondary verification request for the two card messages to the server respectively; he can also click the One-Click Agree All Approval button in the workstation. At this time, the second client still sends a secondary verification request for the two card messages to the server respectively.

[0078] In step 105, updated configuration information of each card message is obtained from the database.

[0079] In some embodiments, different card messages correspond to different document identifiers; before step 105, that is, before obtaining the updated configuration information of each card message from the database, a configuration update request sent by a third client or web page can also be received, wherein the configuration update request carries the updated configuration information, and the updated configuration information is submitted by the administrator on the third client or web page for the document identifier corresponding to the card message; the updated configuration information and the document identifier are synchronized to the database, for example, a key-value pair with the document identifier as the key and the updated configuration information as the value is synchronized to the database.

[0080] After the card message is sent to the workstation of the second client of the approver and the CC recipient, and until the approver enters the workstation to approve the card message so that the second client sends a verification request to the server, the administrator may modify the configuration information of the card message through a third client or a web page, and synchronize the modified configuration information to the database. The configuration information may include the identity information of the operator of the card message, for example, the original approver of card message a is A, and the CC recipient is B, but the administrator modifies it to approver C, and CC recipients A and B; it may also include the switch information of the card message, for example, the original switch information of the card message "only relevant persons can view" is in the off state, but the administrator modifies it to the on state; it may also include the style of the card message, such as size, font, font size and color.

[0081] In some embodiments, the verification request carries a document identification, as well as information such as an enterprise identification, an operator identification, and a card message identification; obtaining updated configuration information for each of the card messages from a database can be achieved in the following manner: performing a second verification on the document identification; in response to the second verification result obtained indicating that the document identification meets the parameter value conditions, querying the database using the document identification as an index to obtain configuration information associated with the document identification.

[0082] When the server receives the verification request sent by the second client, it will first perform parameter verification on the document identifier to verify the legitimacy of the document identifier parameter. Specifically, the verification rules are formulated through the Validator, and the verification is automatically completed: first, the fields that need to be verified in the parameters are annotated, and each annotation corresponds to a different verification rule. For example, @DecimalMax indicates that the parameter cannot exceed the set maximum value, and @Digits indicates that the parameter must be a number and the number of digits of the integer and the number of decimals must be within the specified range; and the prompt message after the verification fails can be formulated, such as "parameter error". After the verification rules and error prompt messages are configured, the @Valid annotation is added to the parameters that need to be verified in the interface, and the legitimacy of the parameters submitted by the front-end page can be verified through the Controller layer. For example, if the document identifier must be ten digits, if the parameter verification result indicates that the document identifier is nine digits, then the prompt "parameter error" is prompted, and the document identifier is refused to be used as an index to query the database to obtain the configuration information.

[0083] In some embodiments, querying the database using the document identifier as an index to obtain configuration information associated with the document identifier can be achieved in the following ways: in response to a verification request sent by the second client after receiving an approval operation for agreeing to a card message, querying the database using the document identifier corresponding to the card message as an index to obtain configuration information associated with the document identifier; in response to a verification request sent by the second client after receiving an approval operation for agreeing to multiple card messages, querying the database using the document identifiers corresponding to the multiple card messages as indexes to obtain multiple configuration information associated with the document identifiers respectively.

[0084] For example, in response to the approval requests for leave applications submitted by applicants A and B, the server sends the corresponding card messages a and b to the workstation of the approver's second client in turn. When the approver enters the workstation to process the two card messages, he or she can click the approve button or the reject button respectively. For example, if the approve button is clicked for card message a, the second client sends a secondary verification request for card message a to the server. At this time, the server uses the document identifier corresponding to card message a as an index to query the database, and obtains the configuration information associated with the document identifier of card message a; or the approver can also click the one-click approve all button in the workstation. At this time, the second client will send secondary verification requests for card message a and card message b to the server respectively. At this time, the server uses the document identifiers corresponding to card message a and card message b as indexes to query the database, and obtains the configuration information associated with the document identifiers of card message a and card message b respectively.

[0085] In some embodiments, querying a database using the document identification as an index to obtain configuration information associated with the document identification can also be achieved in the following ways: querying a database using the document identification as an index to obtain serialized data of the configuration information associated with the document identification; deserializing the serialized data to obtain the configuration information associated with the document identification.

[0086] In an embodiment of the present application, the security of the data received by the server can be guaranteed by performing parameter verification on the document identification; at the same time, the database is queried separately for the document identifications corresponding to multiple card messages, which can ensure that even if the administrator changes the configuration information of the card message, the server can still query the latest configuration information, thereby ensuring the normal flow of documents.

[0087] In step 106, a first check is performed based on the configuration information, and the flow of the card message is controlled based on the obtained first check result.

[0088] In some embodiments, the configuration information includes the style of the card message, and the style of the card message includes at least one of the following style parameters: size, font, font size, etc.; the embodiment of the present application can also generate a new card message based on the style of the card message; send the new card message to the second client, so that the second client performs a refresh operation based on the new card message.

[0089] When the administrator modifies the size, font, font size and other style parameters of the card message through a third client or a web page, the server can generate a new card message based on the style parameters in the configuration information associated with the document identifier obtained from the database, and send the new card message to the second client, so that the second client can perform a refresh operation based on the new card message, thereby ensuring that the style parameters of the card message displayed on the workbench of the second client are the latest, so as to avoid the incorrect flow of parameters.

[0090] In some embodiments, the configuration information includes operator identity information and switch information of the card message, wherein the operator identity information includes approver identity information and carbon copy identity information; controlling the flow of the card message based on the first verification result obtained can be achieved in the following ways: in response to the identity information associated with the second client being the approver identity information, sending a pop-up message to the second client so that the second client displays the pop-up message, wherein the pop-up message includes switch information; in response to the identity information associated with the second client being the carbon copy identity information, notifying the second client to place the approval entry in the displayed card message in an unavailable state.

[0091] In some embodiments, the switch information includes at least one of the following: whether to notify members after publishing, whether only relevant people can view it, whether revocation is allowed after approval, whether additional signatures are allowed, whether approval opinions are required, and whether electronic signatures are required when agreeing.

[0092] If the server sends a card message m to the workstation of the operator's second client, and the identity information of the operator M is the approver, then the operator M has the authority to click the buttons of the card message m to approve, reject approval, and approve all with one click. However, before the operator M clicks the button, the administrator modifies the identity information of the operator M to the carbon copy, and modifies the identity information of the carbon copy N to the approver through the third client or the web page. Since the associated configuration information of the card message is not updated before the operator M clicks the approval button, the operator M can still click the approval button, so that the second client sends a verification request to the server, and the server obtains the modified configuration information of the card message m from the database; in the modified configuration information, the identity information of the operator M is the carbon copy, so the server will send a pop-up message to the second client of the operator M to notify the second client of the operator M to put the approval entry in the card message m in an unavailable state; and send a pop-up message to the second client of the approver N, so that the second client of the approver N displays the pop-up message including the switch information.

[0093] In some embodiments, the switch information includes the following options: whether the approval opinion is required and whether an electronic signature is required for approval; the way in which the second client displays a pop-up message includes: in response to any option in the switch information being in the on state, displaying a pop-up message indicating that the card message is in a state where approval cannot be directly agreed to; in response to all options in the switch information being in the off state, displaying a pop-up message indicating that the card message is in a state where approval can be directly agreed to; in response to any card message being in a state where approval cannot be directly agreed to, displaying a pop-up message indicating that all card messages cannot be directly agreed to for approval; in response to all card messages being in a state where approval can be directly agreed to, displaying a pop-up message indicating that all card messages can be directly agreed to for approval.

[0094] In some embodiments, the way in which the second customer displays a pop-up message includes: responding to the switch information including the following options: whether the approval opinion corresponding to the card message is required, and when the switch information is in the on state, a pop-up message is displayed to prompt that the approval opinion needs to be clicked on the card message and filled in when agreeing to the approval; responding to the switch information including the following options: whether an electronic signature is required for the approval corresponding to the card message, and when the switch information is in the on state, a pop-up message is displayed to prompt that the approval need to be clicked on the card message and filled in the signature.

[0095] When either of the two switch information, whether the approval opinion corresponding to the card message is required or whether an electronic signature is required when agreeing, is in the on state, then when the operator clicks the Agree to Approval button of the card message, the pop-up message displayed will prompt that the card message is in a state where the approval cannot be directly agreed; or when the operator clicks the One-Click Agree All button, the pop-up message displayed will prompt that the card message cannot be directly agreed to for approval; that is, the operator is prompted that when agreeing to the approval or agreeing to all with one click, the approval opinion of the corresponding card message must be filled in (whether the approval opinion is required is in the on state) or the electronic signature must be filled in (whether an electronic signature is required when agreeing is in the on state), and when the operator clicks the Agree to Approval, Reject Approval, or One-Click Agree All button, the interface for filling in the approval opinion or the electronic signature will be jumped to.

[0096] When the two switch information of whether the approval opinion corresponding to the card message is required and whether an electronic signature is required when agreeing are both in the off state, the pop-up message displays the content to prompt that the card message is in a state where approval can be directly agreed, that is, the operator can directly agree to the approval of one or more card messages by clicking the Agree Approval button or the One-Click Agree All button.

[0097] In some embodiments, in response to any card message being in a state where it cannot be directly approved, and receiving all direct approval requests from the second client, the card messages that are in a state where they can be directly approved are approved, and the card messages that cannot be directly approved are aggregated and processed to obtain an aggregated card message, which is sent to the second client.

[0098] When there is any card message that is in a state where it cannot be directly approved, and the pop-up message has prompted the operator that the card message is in a state where it cannot be directly approved, but the operator still clicks the one-click Agree All button, that is, the server receives all direct approval requests from the second client, then the server will approve the card messages that are in a state where they can be directly approved (that is, both the switch information of whether the approval opinion of the card message is required and whether an electronic signature is required when agreeing are in a closed state), and then summarize the card messages that cannot be directly approved (that is, either the switch information of whether the approval opinion corresponding to the card message is required or whether an electronic signature is required when agreeing is in an open state) to obtain a summarized card message, which includes the title of the card message that cannot be directly approved, and a prompt that the approval opinion needs to be filled in or the electronic signature needs to be filled in, and then the summarized card message is sent to the second client so that the operator can fill in the approval opinion or the electronic signature when agreeing to approve the corresponding card message.

[0099] The following is an explanation of an exemplary application of the embodiments of the present application in a practical application scenario.

[0100] It should be noted that the client in this application scenario is the first client in the embodiment of the present application, and the workbench is a functional interface of the second client in the embodiment of the present application, which is used to receive and display card messages sent by the server and complete approval operations for card messages, and the client and the workbench run in different terminals.

[0101] See also Figure 4 , Figure 4 It is a schematic diagram of the workbench approval window provided in the embodiment of the present application. The approver can view the information card on the workbench and click the Agree or Reject button for a single card message to agree or disagree with the application corresponding to the card message, or click the Agree All button in the workbench to agree to all applications corresponding to the unapproved card messages in the workbench at the same time. However, the format of the card message in the workbench is currently fixed and cannot be updated in real time. Once sent to the workbench, it cannot be withdrawn and the format cannot be modified. If the card message associated configuration information is modified by the administrator on the web page after the applicant of the card message submits the card message to the workbench, and then the approver clicks the Agree, Reject or Agree All button through the card message, it will cause the associated application form of the card message to flow incorrectly.

[0102] See also Figure 5 , Figure 5 is a flowchart of document error flow provided by an embodiment of the present application, Figure 5 The client and workbench in the application can be regarded as terminals. The operating subject corresponding to the client is the applicant, and the operating subject corresponding to the workbench is the operator, who can be the approver or the CC recipient. The background server, message center and web page can all be regarded as servers.

[0103] In step 501, the client submits an application to the backend server.

[0104] The applications submitted here are document applications, such as financial applications (travel expense reimbursement, loan payment, invoice issuance, project funding application, general reimbursement, commission payment, etc.), personnel management applications (position change application, recruitment form, training assessment form, regularization application, salary payment, dismissal application, resignation application, personnel change application, etc.), business-related applications (order application, procurement application, contract signing, business entertainment application, etc.). The types of document applications include but are not limited to the contents listed above.

[0105] Taking an applicant submitting a leave application as an example, the application form that the applicant needs to fill out may include: leave type (such as personal leave, sick leave), leave start time, leave end time, leave reason, approver and cc, etc.

[0106] In step 502, the backend server executes the bill of lading process.

[0107] Extract the associated configuration information of the card message corresponding to the document application from the database, including 1) the style of the card message, for example, some card messages have two buttons, Agree and Reject, and some card messages have no button, as well as the size of the card message and the font color of the text displayed in the card message; 2) the jump link after clicking the card message, that is, when clicking the Agree button of the card message to agree to the approval, it may automatically jump to another interface to fill in the signature or confirm the approval related information, such as Fig.12 Schematic diagram of the card message jumping to the signature page shown in ; 3) The switch configuration corresponding to the application form, including whether to notify members after release, whether only relevant people can view it, whether revocation is allowed after approval, whether additional signatures are allowed, whether approval opinions are required, whether electronic signatures are required when agreeing, etc.; 4) The authority of the operator, for example, user A is the approver of the application form and has the authority to click the approval button and the rejection button of the card message; user B is the cc person of the application form and can only view the card message but does not have the authority to click the button.

[0108] After the background server extracts the card message associated configuration information from the database, it will perform the first verification of the card message associated information, including the style of the card message, the jump link after clicking the card message, the switch configuration corresponding to the application form, the operator's permissions, etc., to confirm whether the information required for the card message push is missing, and whether the format of the above information complies with the card message push specifications, such as determining whether the size of the card message meets the size required by the workbench.

[0109] In step 503, the backend server returns a successful bill of lading message to the client.

[0110] That is, after successfully filing the bill, the backend server returns a message of successful application to the client to notify the applicant.

[0111] In step 504, the backend server applies to the message center for message push.

[0112] That is, the background server sends the card message association configuration information to the message center, and requests the message center to push the card message to the workstations of the approver and the copy recipient according to the association configuration information.

[0113] In step 505, the message center pushes the card message to the workbench.

[0114] That is, the message center pushes card messages to the workstations of approvers and copy recipients according to the card message association configuration information.

[0115] In step 506, the web page obtains a request from the administrator to modify the card message associated configuration information.

[0116] That is, the administrator modifies the style of the card message, the jump link after clicking the card message, the switch configuration corresponding to the application form, the operator's authority and other information on the web page, such as modifying the font color of the text in the card message and the size of the card message; or modifies the switch configuration information. Each item of information in the switch configuration information here has only two states, on and off, that is, the administrator can only modify the switch configuration between on and off, such as changing "whether an electronic signature is required when agreeing" from off to on; or modifies the operator's authority, such as changing the authority of the approver A to the authority of the cc person.

[0117] In step 507, the workbench receives an operation request from an operator to click a card message button.

[0118] That is, after the card message is pushed to the operator's workstation, the operator enters the workstation and clicks the "Agree" or "Reject" button in the card message to agree or reject the application of the corresponding card message, or clicks the "Agree All" button to agree to the applications in all card messages.

[0119] In step 508, the workbench returns a document error flow message to the client.

[0120] Since the card message format in the workbench is fixed and cannot be modified, after the administrator modifies the card message associated configuration information on the web page, clicking the Agree, Agree All, or Reject button of the card message can no longer process the application form. Therefore, the workbench will return a document error flow message to the client.

[0121] In response to the above problems, the embodiment of the present application provides an approval workflow processing method. After the applicant submits the application through the client, the background server displays a successful bill of lading and creates a related card message, associates the card message with the application form, and pushes the card message to the workbench. At this time, the approver of the card message is A; before approver A approves the card message on the workbench, the administrator modifies the card message association configuration information in the background (for example, changes "whether electronic signature is required when agreeing" from no to yes), or modifies the approval authority of approver A, and synchronizes the modified card message association configuration information and approval authority to the database. When approver A enters the workbench and clicks to agree, a secondary verification of the background server will be triggered. This secondary verification can ensure the normal flow of documents under the premise that the card message association configuration information (including configuration switches) and the operator (including approvers and cc recipients) permissions have been modified. See. Figure 6 , Figure 6 It is a flow chart of the correct flow of optimized documents provided in the embodiment of the present application.

[0122] Figure 6See the above for steps 601 to 607. Figure 5 The description of steps 501 to 507 in the above description will not be repeated here.

[0123] In step 608, the workstation applies for secondary verification from the backend server.

[0124] After the operator clicks the Agree, Reject, or Agree All buttons of the card message, the workbench sends a secondary verification application for the card message associated configuration information to the backend server. That is, after the workbench obtains click stream information such as the enterprise ID, operator ID, card message ID, and card message associated document ID, it packages the click stream information and then sends the data packet to the backend server.

[0125] In step 609, the background server checks the associated configuration information for a second time.

[0126] That is, after the backend server receives the secondary verification request sent by the workstation, it performs secondary verification on the associated configuration information of the card message. Specifically, step 609 can be performed by Figure 7 Steps 701 to 707 shown in FIG. Figure 7 , Figure 7 This is a flow chart of the server's secondary verification of card message associated configuration information provided in the embodiment of the present application. It should be noted that: Figure 7 The Svr side and the Logic side shown in Figure 6 The functional modules in the background server are shown in FIG.

[0127] In step 701, the Svr side performs parameter verification.

[0128] That is, after the Common Gateway Interface (CGI) on the Svr side of the background server receives the secondary verification request sent by the workstation, it first performs parameter verification, that is, verifies the click stream information such as the enterprise ID, operator ID, card message ID, card message associated document ID in the data packet sent by the workstation. For example, for the card message associated document ID, if the set integer number of digits is 10, or the setting is greater than 1111111111 and less than 9999999999, then if the card message associated document ID received by the Svr side is not ten digits, or is not within the preset value range, the card message associated document ID is considered illegal, and a message indicating that the parameter verification is illegal is returned to the workstation.

[0129] In step 702, the Logic side obtains document submission event information from the database.

[0130] After the Svr end performs parameter verification to confirm that the parameters in the received data packet are legal, the Logic end executes the logic. The Logic end first uses the card message associated with the document ID in the incoming clickstream information as the Unique index to query the corporate document information in the database. If the operator clicks "Agree" to a card message, only the corporate document information corresponding to the card message will be queried in the database; if the operator clicks "Agree to All", the corporate document information corresponding to all card messages will be queried in the database. Figure 8 , Figure 8 It is a schematic diagram of querying enterprise document information in a database provided by an embodiment of the present application. Record1 and RecordN in the figure represent multiple enterprise document information stored in the database. After the Logic end takes out the serialized content data in the enterprise document information, it performs a deserialization operation to obtain SpEventInfo, which represents the latest detailed information of this enterprise document record, such as document ID (sp_number), enterprise ID (corpid), document application time (apply_time), card message template ID (template_id), card message template data (template_data), and the flow node (template_id) of the document (the node includes the approver and cc information), etc.

[0131] In step 703, the Logic side calculates the user identity.

[0132] SpEventInfo will record the complete approval chain of the document. There are multiple nodes in the chain. Each node will store the identity information of the operator. It is stored in the database through a 64-bit unsigned number. Each bit represents an identity. The identity of the operator can be read through this information.

[0133] The operator ID in the clickstream information is compared with the operator identity saved in SpEventInfo to determine the operator, and then the latest identity of the operator can be determined based on the information in SpEventInfo. Fig. 9 , Fig. 9 This is a schematic diagram of the operator identity provided in the embodiment of the present application. For the application submitted by the applicant "Xiao Wang", the approver is "User A" or "User B"; the copy recipient is "User C".

[0134] In step 704, the Logic end obtains switch storage information from the database.

[0135] After confirming the user's identity and permissions, the Logic side starts to query the card message related configuration information, including the switch information of the corresponding document configuration. The switch information includes: whether to notify members after publishing, whether only relevant people can view it, whether revocation is allowed after approval, whether additional signatures are allowed, whether approval opinions are required, whether electronic signatures are required when agreeing, etc. See Fig.10 , Fig.10 This is a schematic diagram of the switch configuration provided in an embodiment of the present application. The switch information can only have two states: on and off, so the switch information in the stored card message association configuration is also optimized into a 64-bit unsigned number. Each bit represents the state of each switch, 0 represents off, and 1 represents on. When inverting a switch bit, only a bit XOR operation is required, which ensures the efficiency of the system.

[0136] In step 705, the Logic side verifies the user's authority.

[0137] The operator ID in the click stream information is compared with the operator identity saved in SpEventInfo to determine the operator. Then, the operator's latest identity can be determined based on the information in SpEventInfo. The operator's authority is determined based on the operator's identity. For example, the approver can click the Agree, Reject, and Agree All buttons, while the CC recipient can only view the card message and does not have the authority to click these buttons.

[0138] In step 706, the Logic end sends a pop-up message to the message center along with the verification result.

[0139] After calculating the user's identity authority and the card message-related configuration information (including configuration switch information, operator's authority information, and the latest style information of the card message), the Logic side carries it as a parameter and sends a pop-up message request to the message center.

[0140] In step 707, the message center sends a pop-up message to the workstation according to the verification result.

[0141] The message center first refreshes the card message according to the card message style information to update the card message style, and then pops up a window prompt to the user according to the configuration switch information and the operator's permission information: 1) If the operator is initially an approver, but is changed to a cc by the administrator, that is, the operator has no permission, then a pop-up window prompts the operator that the operator has no approval permission; 2) If the operator has approval permission and the operator clicks "Agree", see Fig.11 , Fig.11This is a schematic diagram of a pop-up window for filling in a signature provided in an embodiment of the present application. Taking the switch as an example where the signature is required, the workbench will pop up a window prompt: "A signature is required before agreeing to this application. Please click the card message and go to the details page to sign and confirm." At the same time, a jump uniform resource locator (URL) link is set for the card so that it can directly jump to the signature page for signing. See Fig.12 , Fig.12 is a schematic diagram of a pop-up window for filling in a signature provided in an embodiment of the present application; 3) See Fig.13 , Fig.13 1 is a schematic diagram of a pop-up window for clicking the Agree All button provided in an embodiment of the present application. When the user clicks Agree All, the card messages that can be directly agreed to and those that cannot be agreed to will be determined first, that is, whether each card needs to be signed when agreeing. If there is a card that needs to be signed, not all can be agreed to. The card needs to be agreed to separately after signing, and is displayed in a pop-up window; see Fig.14 , Fig.14 This is a schematic diagram of pushing a card by clicking the All Agree button provided in an embodiment of the present application. If the user still clicks All Agree, the results of all the agreement will be summarized and the card will be sent to the user again.

[0142] Continue to see Figure 6 In step 610, the backend server returns the correct document information to the workbench.

[0143] The background server updates the card message based on the correct document information obtained from the database, including the approval authority of the operator who updates the card message, the switch configuration information of the card message, and the style parameter information of the card message, and then sends the updated card message to the workbench so that the workbench refreshes the card message.

[0144] In step 611, the workbench returns a message to the client indicating that the document has been correctly transferred.

[0145] When the backend server sends the updated card message to the workbench and the workbench refreshes the card message, the workbench will return a message to the client indicating that the document has been correctly circulated, prompting the applicant that the card message has been modified and has been circulated normally.

[0146] Through the above method, after the operator receives the card message corresponding to the approval request and performs the approval operation on the card message, the card message is verified by obtaining the updated configuration information from the database to update the card information, thereby ensuring that after the card message is sent to the second client, even if the associated configuration information of the card message is modified, the card message can still be updated based on the modified associated configuration information, thereby ensuring the normal flow of the card message after the configuration information is updated.

[0147] It is understandable that in the embodiments of the present application, related data such as user information is involved. When the embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0148] The following is a description of an exemplary structure of the approval workflow processing device 433 provided in the embodiment of the present application implemented as a software module. In some embodiments, Figure 2 As shown, the software modules stored in the approval workflow processing device 433 of the memory 440 may include:

[0149] The first receiving module 4331 is used to receive an approval request from a first client; the generating module 4332 is used to generate a card message corresponding to the approval request; the sending module 4333 is used to send the card message to the second client so that the second client displays the card message, wherein the card message is used for the second client to receive an approval operation; the second receiving module 4334 is used to receive a verification request sent by the second client, wherein the verification request is sent by the second client after receiving the approval operation of agreeing to at least one of the card messages; the acquiring module 4335 is used to obtain updated configuration information of each of the card messages from a database; the verification module 4336 is used to perform a first verification based on the configuration information, and control the flow of the card message based on the first verification result obtained.

[0150] In some embodiments, the second receiving module 4334 is also used to receive a configuration update request sent by a third client or a web page, wherein the configuration update request carries the updated configuration information, and the updated configuration information is submitted by the third client or the web page for the document identifier corresponding to the card message; and the updated configuration information and the document identifier are synchronized to the database.

[0151] In some embodiments, the acquisition module 4335 is also used to perform a second verification on the document identifier; in response to the second verification result obtained indicating that the document identifier meets the parameter value conditions, the database is queried using the document identifier as an index to obtain the configuration information associated with the document identifier.

[0152] In some embodiments, the acquisition module 4335 is also used to query the database with the document identifier corresponding to one of the card messages as an index in response to the verification request being sent by the second client after receiving the approval operation agreeing to one of the card messages, and obtain the configuration information associated with the document identifier; in response to the verification request being sent by the second client after receiving the approval operation agreeing to multiple card messages, query the database with the document identifiers corresponding to the multiple card messages as indexes, and obtain multiple configuration information associated with the document identifiers respectively.

[0153] In some embodiments, the acquisition module 4335 is also used to query the database using the document identifier as an index to obtain serialized data of the configuration information associated with the document identifier; and deserialize the serialized data to obtain the configuration information associated with the document identifier.

[0154] In some embodiments, the verification module 4336 is further used to generate a new card message based on the style of the card message; and send the new card message to the second client so that the second client performs a refresh operation based on the new card message.

[0155] In some embodiments, the verification module 4336 is also used to send a pop-up message to the second client in response to the identity information associated with the second client being the approver identity information, so that the second client displays the pop-up message, wherein the pop-up message includes the switch information; and in response to the identity information associated with the second client being the cc identity information, notify the second client to place the approval entry in the displayed card message in an unavailable state.

[0156] In some embodiments, the verification module 4336 is also used to respond to the switch information including the following options: whether the approval opinion is required and whether an electronic signature is required for approval, and the switch information is in the on state, display a pop-up message indicating that the card message is in a state where approval cannot be directly agreed to; in response to the switch information being in the off state, display a pop-up message indicating that the card message is in a state where approval can be directly agreed to; in response to any card message being in a state where approval cannot be directly agreed to, display a pop-up message indicating that all card messages cannot be directly agreed to; in response to all card messages being in a state where approval can be directly agreed to, display a pop-up message indicating that all card messages can be directly agreed to.

[0157] In some embodiments, the verification module 4336 is also used to respond to any of the card messages being in a state where they cannot be directly approved and have received all direct approval requests from the second client, by approving the card messages that are in a state where they can be directly approved and aggregating the card messages that cannot be directly approved to obtain a summarized card message, and send the summarized card message to the second client.

[0158] In some embodiments, the verification module 4336 is also used to respond to the switch information including the following options: whether the approval opinion corresponding to the card message is required, and when the switch information is in the on state, a pop-up message is displayed to prompt that the approval opinion needs to be clicked on the card message and filled in when agreeing to the approval; respond to the switch information including the following options: whether an electronic signature is required for the approval corresponding to the card message, and when the switch information is in the on state, a pop-up message is displayed to prompt that the approval needs to be clicked on the card message and filled in with the signature.

[0159] The embodiment of the present application provides a computer program product, which includes a computer program or a computer executable instruction, and the computer program or the computer executable instruction is stored in a computer-readable storage medium. The processor of the electronic device reads the computer executable instruction from the computer-readable storage medium, and the processor executes the computer executable instruction, so that the electronic device executes the above-mentioned approval workflow processing method of the embodiment of the present application.

[0160] The present application embodiment provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions or computer programs are stored. When the computer-executable instructions or computer programs are executed by a processor, the processor will execute the approval workflow processing method provided by the present application embodiment, for example, Figure 3 The approval workflow processing method is shown.

[0161] In some embodiments, the computer-readable storage medium may be a memory such as RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

[0162] In some embodiments, computer executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0163] As an example, computer-executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0164] As an example, computer executable instructions may be deployed to be executed on one electronic device, or on multiple electronic devices located at one site, or on multiple electronic devices distributed at multiple sites and interconnected by a communication network.

[0165] To summarize, after the operator receives the card message corresponding to the approval request and performs the approval operation on the card message, the card message is verified by obtaining the updated configuration information from the database to update the card message, thereby ensuring that after the card message is sent to the second client, even if the associated configuration information of the card message is modified, the card message can still be updated based on the modified associated configuration information, thereby ensuring the normal flow of the card message after the updated configuration information.

[0166] The above is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for processing approval workflow, characterized in that: The method comprises: receiving an approval request from a first client; generating a card message corresponding to the approval request; Sending the card message to the second client so that the second client displays the card message, wherein the card message is used for the second client to receive an approval operation; receiving a verification request sent by the second client, wherein the verification request is sent by the second client after receiving the approval operation of approving at least one of the card messages; Obtaining updated configuration information of each of the card messages from a database; A first check is performed based on the configuration information, and the flow of the card message is controlled based on the obtained first check result.

2. The method according to claim 1, characterized in that Different card messages correspond to different document identifiers; Before acquiring updated configuration information of each card message from the database, the method further includes: Receiving a configuration update request sent by a third client or a web page, wherein the configuration update request carries the updated configuration information, and the updated configuration information is submitted by the third client or the web page for the document identifier corresponding to the card message; The updated configuration information and the document identification are synchronized to the database.

3. The method according to claim 2, characterized in that The verification request carries the document identifier; The acquiring updated configuration information of each card message from the database includes: Performing a second verification on the document identifier; In response to the second verification result obtained indicating that the document identifier meets the parameter value condition, the database is queried using the document identifier as an index to obtain the configuration information associated with the document identifier.

4. The method according to claim 3, characterized in that The querying of the database using the document identifier as an index to obtain the configuration information associated with the document identifier includes: In response to the verification request being sent by the second client after receiving the approval operation of approving a card message, querying the database using a document identifier corresponding to a card message as an index to obtain the configuration information associated with the document identifier; In response to the verification request, the second client sends the approval operation after receiving the approval of multiple card messages, and queries the database using the document identifiers corresponding to the multiple card messages as indexes to obtain multiple configuration information associated with the document identifiers.

5. The method according to claim 4, characterized in that The querying of the database using the document identifier as an index to obtain the configuration information associated with the document identifier includes: Using the document identifier as an index to query the database, and obtain serialized data of the configuration information associated with the document identifier; The serialized data is deserialized to obtain the configuration information associated with the document identifier.

6. The method according to claim 1, characterized in that The configuration information includes the style of the card message, wherein the style includes at least one of the following style parameters: size, font; The method further comprises: Based on the style of the card message, generate a new card message; The new card message is sent to the second client, so that the second client performs a refresh operation based on the new card message.

7. The method according to claim 1, characterized in that The configuration information includes the operator identity information and switch information of the card message, wherein the operator identity information includes the approver identity information and the copy recipient identity information; The controlling the flow of the card message based on the obtained first verification result includes: In response to the identity information associated with the second client being the approver identity information, sending a pop-up message to the second client so that the second client displays the pop-up message, wherein the pop-up message includes the switch information; In response to the identity information associated with the second client being the identity information of the carbon copy recipient, the second client is notified to place the approval entry in the displayed card message in an unavailable state.

8. The method according to claim 7, characterized in that The switch information includes at least one of the following: Whether members will be notified after release, whether only relevant people can view it, whether revocation is allowed after approval, whether additional signatures are allowed, whether approval opinions are required, and whether electronic signatures are required when agreeing.

9. The method according to claim 7 or 8, characterized in that: The manner in which the second client displays the pop-up message includes: In response to the switch information including the following options: whether the approval opinion is required and whether an electronic signature is required when agreeing, and the switch information is in the on state, a pop-up message is displayed to indicate that the card message is in a state where approval cannot be directly agreed; In response to the switch information being in the off state, displaying a pop-up message indicating that the card message is in a state that can be directly approved; In response to any card message being in a state where it cannot be directly approved, displaying a pop-up message indicating that all of the card messages cannot be directly approved; In response to all the card messages being in a state where they can be directly approved, a pop-up message is displayed to indicate that all the card messages can be directly approved.

10. The method according to claim 9, characterized in that The method further comprises: In response to any of the card messages being in a state where the approval cannot be directly approved, and receiving all the direct approval requests from the second client, approving the card messages in a state where the approval can be directly approved, and The card messages that cannot be directly approved are aggregated to obtain an aggregated card message, and the aggregated card message is sent to the second client.

11. The method according to claim 9, characterized in that The manner in which the second client displays the pop-up message includes: In response to the switch information including the following options: whether the approval opinion corresponding to the card message is required, and when the switch information is in the on state, a pop-up message is displayed to prompt that the card message needs to be clicked and the approval opinion needs to be filled in when agreeing to the approval; In response to the switch information, the following options are included: whether an electronic signature is required for the consent corresponding to the card message, and when the switch information is in the on state, a pop-up message is displayed to prompt that the card message needs to be clicked and the signature needs to be filled in when agreeing to the approval.

12. An approval workflow processing device, characterized in that: The device comprises: A first receiving module, used to receive an approval request from a first client; A generating module, used for generating a card message corresponding to the approval request; A sending module, used for sending the card message to the second client, so that the second client displays the card message, wherein the card message is used for the second client to receive an approval operation; A second receiving module is used to receive a verification request sent by the second client, wherein the verification request is sent by the second client after receiving the approval operation of approving at least one of the card messages; An acquisition module, used for acquiring updated configuration information of each of the card messages from a database; The verification module is used to perform a first verification based on the configuration information, and control the flow of the card message based on the obtained first verification result.

13. An electronic device, characterized in that: The electronic device comprises: A memory for storing computer executable instructions; The processor is used to implement the approval workflow processing method described in any one of claims 1 to 11 when executing the computer executable instructions or computer programs stored in the memory.

14. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that: When the computer executable instructions or computer program are executed by a processor, the approval workflow processing method according to any one of claims 1 to 11 is implemented.

15. A computer program product comprising computer executable instructions or a computer program, characterized in that When the computer executable instructions or computer program are executed by a processor, the approval workflow processing method according to any one of claims 1 to 11 is implemented.