aPaaS-based approval process building method and system, electronic device and storage medium

Abstract

The present disclosure relates to an aPaaS-based approval process building method and system, electronic equipment and storage medium, the method comprising: triggering a business process; connecting the upstream automation nodes of the approval process, preprocessing the approval data; passing the process parameters of the business main process to the approval process; obtaining the preprocessed approval data, setting the data structure of the approval data in the approval process; entering the approval process to approve, fill out, copy, condition judge, cross-table query and enable the approval result branch node of the approval data; feeding back the approval result to the business main process, and connecting the downstream automation nodes of the approval process. The present disclosure can realize the complete customization of the approval process, and the automatic nodes of the upstream and downstream are connected to make the business process fully automatic, reduce the development workload and cost of enterprises, and greatly improve the operation efficiency of the business process.

Description

Technical Field

[0001] This disclosure relates to the field of workflow, specifically to a method, system, electronic device, and storage medium for building an approval process based on aPaaS. Background Technology

[0002] The approval process frameworks provided by mainstream aPaaS platforms on the market currently have the following shortcomings:

[0003] All of these approval processes start with "the initiator submits the form" and end with "the last node is completed". Therefore, the logic for executing these approval processes is the same: when an approval node is rejected, the form status will immediately change to "rejected" and the approval process will immediately stop.

[0004] It cannot support two or more approval processes operating on a single form at the same time;

[0005] All are limited to using the data from the approval form (i.e., this form) as dynamic parameters (approver, deadline, notification content, etc.) for manual nodes in the approval process;

[0006] It does not support automated transaction processing capabilities before or after the start of the approval process.

[0007] However, users will have the following needs when using these approval process frameworks:

[0008] The rejection of a form at a certain approval stage does not mean that the form has been completely rejected. Instead, it needs to be distributed to other business departments for further approval.

[0009] Once an approval process for a certain matter is initiated, each department simultaneously begins its own approval process, and finally the statements from each pipeline are summarized.

[0010] When there is a complex approval process, the administrator pre-stores the configuration of a series of dynamic parameters of manual nodes as a data table. After the approval is initiated, the administrator retrieves the corresponding configuration data based on the specific conditions and uses the configuration data to execute the corresponding manual node. At this time, the approval process needs to provide the ability to query data across tables.

[0011] When there is an approval process for a complex matter, the dynamic parameters required for this configuration come from variables generated in other processes. In this case, the approval process and the main business process need to have the ability to pass parameters.

[0012] Before an approval process is initiated, data preprocessing and form locking must be performed before the formal approval process can begin. After the approval process is completed, the approval form needs to be automatically printed and the data archived.

[0013] Therefore, we urgently need to provide a method, system, electronic device, and storage medium for building approval processes that can fully customize the approval process and connect upstream and downstream automated data processing nodes to automate the business process, reducing enterprise development workload and costs while greatly improving the operational efficiency of the business process. Summary of the Invention

[0014] This disclosure provides a method, system, electronic device, and storage medium for building an approval process based on aPaaS, in order to at least solve at least one technical problem existing in the above-mentioned background art.

[0015] In a preferred embodiment of this disclosure, this application provides a method for building an approval process based on aPaaS, the method comprising:

[0016] Trigger the business process;

[0017] Connect to the automated nodes upstream of the approval process to preprocess the approval data;

[0018] Pass the process parameters of the main business process to the approval process;

[0019] Obtain the preprocessed approval data and set the data structure of the approval data in the approval process;

[0020] The approval process involves approving, filling in, copying, conditionally judging, cross-table querying, and enabling branch nodes for approval results.

[0021] The approval results are fed back to the main business process and connected to the downstream automated nodes of the approval process.

[0022] Furthermore, the triggering of business processes includes: triggering various types of business processes by automatic triggers, wherein the business processes include main business processes and approval processes, and the automatic triggers include worksheet event triggers, timed triggers, triggers by date field, organizational personnel event triggers, external user time triggers, and Webhook triggers.

[0023] Furthermore, the process parameter refers to a parameter object defined in the process to store data. This data includes attribute values ​​from a query object, results from calculation nodes in the process, and parameter values ​​received from other processes, such as approver, deadline, and notification content. The process parameter can be referenced by any node within its scope as a dynamic parameter. Furthermore, the automated nodes connecting the upstream of the approval process include:

[0024] Before entering the approval process, the main business process completes tasks based on the connected automated nodes. These tasks include calculations, data operations, notifications, and script processing.

[0025] Furthermore, the data structure for setting approval data in the approval process includes:

[0026] Each approval data item corresponds to n approval processes, and each approval process corresponds to m specific execution instances, where m≥n≥1. Optimize the presentation of each execution instance on the record details page and adjust the comparison rules of the approval display column.

[0027] Furthermore, the optimization of the presentation of each execution instance on the record details page includes: when m=1, the information of each execution instance is initialized and presented in the style of a single timeline; when m≥2, the information of each execution instance is initialized and presented in the style of a card. The adjustment of the comparison rules of the approval display column includes: when m=1, the approval display column corresponds to the traditional "one-to-one process", and the information presented in each cell is the information of the currently ongoing unique approval process; when m≥2, the information presented in each cell is the information of the most recently updated approval process among multiple approval processes.

[0028] Furthermore, the process of entering the approval process to approve, fill in, copy, perform conditional judgments, cross-table queries, and enable branch nodes for approval results includes:

[0029] Acquire data nodes, including record data nodes, personnel data nodes, and department data nodes;

[0030] Use the acquired data nodes to query approval data across tables;

[0031] The process parameters passed to the approval process and the results obtained from cross-table queries are used as parameters for manual nodes, which include approval nodes, filling nodes, and copy nodes.

[0032] Based on the field values ​​of the approval data or the results of the manual node operation, condition judgments are made, and different branch nodes are run according to the results of the condition judgments.

[0033] Furthermore, the step of performing conditional judgments based on field values ​​of approval data or the execution results of approval nodes, and executing different branch nodes according to the results of the conditional judgments, includes:

[0034] When the field value of the approval data meets a certain condition, the data branch node is executed; otherwise, the data branch node is not executed. For example, it may be equal to the condition value or not empty.

[0035] When approval data is rejected at the approval node, it is determined whether to enable the approval result branch node; if enabled, the process will not stop immediately after the approval node is rejected, but will continue to execute the approval result branch node according to the approval result of the approval node.

[0036] Furthermore, the cross-table query is used to set query conditions, sorting rules, and boundary rules according to the type of the entity object selected for query, and the query results are used as dynamic parameters of the approval node.

[0037] Furthermore, the entity objects include personnel objects, department objects, and other data table objects other than approval objects.

[0038] Furthermore, setting query conditions refers to setting filter condition values. Multiple condition values ​​can be combined using "AND" or "OR". The condition values ​​include fixed values ​​entered manually and dynamic values ​​from node objects.

[0039] Furthermore, the setting of sorting rules refers to the ability to set sorting rules or obtain data randomly when the entity being queried consists of multiple approval records.

[0040] Furthermore, the setting of boundary rules refers to setting the execution mode of the approval process to ensure that the approval process cannot be interrupted or suspended when no approval data is found. The execution mode includes:

[0041] Continue execution. If no query results are found, continue execution to the next node. If the next node uses the content of this object, it will be skipped or returned as empty.

[0042] Add new data and continue execution. If there are no query results, you can directly add a new data record to the database. If subsequent nodes use the content of this object, they will directly use the newly added data record.

[0043] The process was suspended.

[0044] Furthermore, the approval result branch node includes two fixed branches, "Pass" and "Reject," which allow users to customize the subsequent flow logic of the approval process when approval data is rejected.

[0045] Furthermore, the automated nodes connecting the downstream of the approval process include:

[0046] After the process approval is completed, the main business process completes the tasks according to the connected automated nodes. The tasks include calculation, data operation, notification and script processing.

[0047] Furthermore, the automated node includes:

[0048] Data processing nodes, including nodes that perform add / delete / modify / query operations on approval data;

[0049] Message notification nodes include in-site notification sending nodes, SMS sending nodes, email sending nodes, service account message sending nodes, and interface push nodes;

[0050] The computation / component type nodes include branch nodes, delay nodes, calculation nodes, sub-process nodes, and automatic printing nodes;

[0051] Developer-related nodes include Webhook nodes, code block nodes, and business process invocation nodes.

[0052] In a preferred embodiment of this disclosure, this application also provides an approval workflow construction system based on aPaaS, including:

[0053] Trigger module, the trigger module is used to trigger business processes;

[0054] An upstream module for the approval process is used to connect the automated nodes upstream of the approval process and to preprocess the approval data.

[0055] A parameter passing module is used to pass the process parameters of the main business process to the approval process.

[0056] The data structure setting module is used to obtain the preprocessed approval data, set the data structure of the approval data in the approval process, and enter the approval node.

[0057] The approval process module is used to enter the approval process to approve, fill in, copy, judge conditions, query across tables, and enable branch nodes of approval results.

[0058] The downstream module of the approval process is used to feed back the approval results to the main business process and connect the downstream automation nodes of the approval process.

[0059] In a preferred embodiment of this disclosure, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described aPaaS-based approval process construction method.

[0060] In a preferred embodiment of this disclosure, the present application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the above-described aPaaS-based approval process construction method.

[0061] The beneficial effects of this disclosure are as follows: The aPaaS-based approval workflow construction method provided in this disclosure acquires approval data nodes, workflow parameter modules, manual nodes, and branch nodes (data branch nodes / approval result branch nodes), and maps each piece of approval data to multiple approval workflows, thus constructing an aPaaS-based approval workflow system. Users can query cross-table data using the acquired approval data nodes, or use the workflow parameter module to directly pass various types of approval data from the main business workflow to the parameters of the approval workflow. The data obtained through these two methods is then used as parameters for manual nodes, such as approver, deadline, and notification content. Simultaneously, the approval workflow supports dynamic conditional judgments, with judgment dimensions including field values ​​of business data and the execution results of approval nodes. Different branch nodes are executed when different conditions are met. After approval data is rejected at a certain approval node, the workflow can be customized to either immediately stop or continue execution. Furthermore, after the approval workflow ends, it supports connecting to automated nodes for publishing approval results and archiving the workflow. The above methods enable complete customization of the approval process and connect upstream and downstream automated data processing nodes to automate the entire business process, reducing enterprise development workload and costs while greatly improving the operational efficiency of the business process. Attached Figure Description

[0062] Figure 1 A flowchart for an approval process built on aPaaS;

[0063] Figure 2 A diagram showing the data structure relationships among the three (approval data, approval process, and operational instance);

[0064] Figure 3 A card rendering diagram for running instances;

[0065] Figure 4 A flowchart for creating an example of an approval process;

[0066] Figure 5 A diagram showing the components of a system for building an approval workflow based on aPaaS. Detailed Implementation

[0067] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0068] Example 1

[0069] Please see the appendix Figure 1According to the exemplary embodiments of this disclosure, the method for building an approval process based on aPaaS passes the process parameters of the main business process to the approval process, and assigns each piece of approval data to multiple approval processes. It also supports cross-table queries in the approval process. When the approval data is rejected at a certain approval node, the process can be customized to either stop immediately or continue to execute. Furthermore, it connects upstream and downstream automated nodes in the approval process to handle transactions.

[0070] The implementation process of the aPaaS-based approval workflow construction method, as an example, includes the following steps:

[0071] In the aPaaS platform, various types of business processes (including approval processes) are triggered by automatic triggers. These automatic triggers include worksheet event triggers, timed triggers, triggers based on date fields, triggers based on organizational personnel events, triggers based on external user time events, and webhook triggers. A trigger is the switch that determines whether a workflow can start; the business process can only begin if the trigger's conditions are met.

[0072] After a business process is triggered but before entering the approval process, it can be connected to automated nodes to preprocess the approval data. The upstream of the approval process is the first part of the business process that is automatically executed. Tasks such as calculations, data operations, notifications, and script processing can be completed according to the corresponding nodes. Automated nodes include:

[0073] (1) Data processing nodes: These are the basic nodes for adding, deleting, modifying, and querying form data.

[0074] (2) Message notification nodes: such as sending in-site notifications, sending SMS messages, sending emails, sending service account messages, and interface push notifications;

[0075] (3) Operation and component-type nodes: such as branches, delays, calculations, sub-processes, automatic printing, etc.;

[0076] (4) Developer-related nodes: namely, Webhooks, code blocks, and business process calling nodes;

[0077] The builders of all the above node business systems can choose flexibly according to their own needs.

[0078] The process parameter system allows you to pass parameters from the main business workflow to the approval workflow. It defines a parameter object within the workflow to store data. This data can come from attribute values ​​of a query object, results of calculated nodes within the workflow, or values ​​received from other workflows, such as approver, deadline, and notification content. Workflow parameters can be referenced as dynamic parameters by any node within their scope. Their lifecycle begins with the workflow's execution and ends when the workflow is terminated (i.e., the parameter values ​​are cleared upon workflow termination). Using the process parameter system, the main business workflow can pass parameters to the approval workflow, making the configuration of the approval workflow more flexible and powerful. This disclosure provides five types of workflow parameters for aPaaS platform-based businesses: text, numeric, date / time, personnel, and department type.

[0079] This paper obtains preprocessed approval data and sets the data structure for the approval data in the approval process. This disclosure departs from the conventional thinking of traditional approval process system design. In this disclosure, one record can correspond to n approval processes (n≥1), and n approval processes correspond to m specific execution instances (m≥n≥1). The data structure relationship between the three is as follows: Figure 2 As shown. Optimize the presentation of each instance on the record details page: when m=1, the information of each instance is initialized and presented in a single timeline style; while when m≥2, the information of each instance is initialized and presented in a card style, such as... Figure 3 As shown. Adjust the rules for the approval display column in the view for users to quickly retrieve information: When m=1, the approval display column corresponds to the traditional "1-to-1 process", that is, the information presented in each cell is the information of the only process currently in progress; while when m≥2, the information presented in each cell is the information of the most recently updated process among multiple processes.

[0080] By designing the data structure relationship of approval data in the approval process, the approval process and approval data disclosed in this invention are completely decoupled. The presentation of approval information on the data side is dynamically written by the process engine, thus supporting extremely complex business scenarios for users, such as multiple approval processes being processed simultaneously.

[0081] The approval process involves approving, filling out, copying, conditionally judging, cross-table queries, and enabling branch nodes for approval results. This approval process is the part of the workflow requiring manual review. The results of cross-table queries can be used as dynamic parameters for approval nodes, including:

[0082] 1. Obtain data nodes, including record data nodes, personnel data nodes, and department data nodes.

[0083] 2. Use the acquired data nodes to query approval data across tables; cross-table queries support querying three types of entity objects, including personnel objects, department objects, and other data table objects besides approval objects.

[0084] The configuration steps are as follows:

[0085] ① Select the type of query object: personnel object, department object, or data table object;

[0086] ② Set query conditions: This involves setting filter conditions based on condition values. These conditions can be fixed values ​​entered manually or dynamic values ​​from node objects. Multiple condition combinations are supported, and their relationships can be uniformly expressed as "AND" or "OR".

[0087] ③ Set sorting rules: If the query object consists of multiple data entries, you can set sorting rules to retrieve data in a certain predetermined order; or you can leave it unsorted, in which case the data will be retrieved randomly.

[0088] ④ Set boundary rules: This involves setting the execution method of the process when no data is found. This step is to meet the requirement that the process cannot be interrupted or stopped. There are three sub-setting methods:

[0089] 1) Continue execution

[0090] If no query results are found, continue executing the subsequent nodes; if the subsequent nodes use the content of this object, they will be skipped or returned as null.

[0091] 2) Add new data and continue execution

[0092] If there are no query results, you can directly add a new data record to the database. If any subsequent nodes use the content of this object, they will directly use the newly added data record.

[0093] 3) Termination of process

[0094] If no results are found, the process can be stopped.

[0095] By designing process parameters (cross-process) and cross-table queries, the barriers between different processes and between forms are broken down, enhancing the ability to obtain data in the approval process. In other products, if the approval process needs data from a cross-entity entity, it is often stored by pre-querying and writing it into a form field before initiating the approval process. Since the field is only used during the approval process, this results in field redundancy. However, by using process parameter passing and cross-table queries for approval data, users can easily obtain cross-table and cross-process data at low cost, and can even obtain it on demand at any time during the approval process, thus demonstrating the flexibility of this product's system design.

[0096] 3. The process parameters passed to the approval process and the results obtained from cross-table queries are used as parameters for manual nodes, which include approval nodes, filling nodes, and copy nodes;

[0097] 4. Based on the field values ​​of the approval data or the results of the manual node execution, conditional judgments are performed, and different branch nodes are executed according to the results of the conditional judgments. When the field value of the approval data meets a certain condition, the data branch node is executed; otherwise, the data branch node is not executed. For example, it must be equal to the conditional judgment value or not empty. When the approval data is rejected at the approval node, it is determined whether to enable the approval result branch node. If enabled, the approval process will not stop immediately after the approval node is rejected, but will continue to execute the approval result branch node according to the approval result of the approval node. The approval result branch node has two fixed branches: "Pass" and "Reject". The existence of the approval result branch node determines whether the approval process will immediately terminate when a certain piece of approval data is rejected (it will return to the downstream part of the main business process to execute the approval process). If this branch is enabled below the approval node, the system will determine that the node will not stop immediately after rejection, but will continue to execute its respective branch according to the approval result of each node. The existence of the result branch does not affect the overall result of the approval process, which is still determined by the result of the last executed node.

[0098] The design of the approval result branch determines whether the approval process will immediately terminate when it is rejected, enabling this disclosure to support complex scenarios, such as when the process continues to execute after a node is rejected, and the approval form is distributed to other nodes for further approval.

[0099] After approval, the approval result is fed back to the main business process. The main business process can connect to automated nodes after the approval process. The downstream of the approval process is the second part of the business process that is automatically executed. The required calculations, data operations, notifications, script processing and other tasks can be completed according to the corresponding nodes. The supported nodes are the same as the automated nodes upstream of the approval process.

[0100] By automating the upstream and downstream nodes of the approval process, this disclosure supports linking the approval process with its upstream and downstream components, outputting an integrated business process canvas. This facilitates administrators in coordinating and optimizing their company's processes, while also effectively supporting the internal information management of the organization. While other products also support some automated operations before and after the approval process is completed, they are often hidden in other functional modules, making them too fragmented from the perspective of coordinating business processes and unable to be integrated into a unified whole. Furthermore, their automation capabilities are not as powerful as those of this disclosure.

[0101] To better illustrate this disclosure, a scenario involving the approval of group projects will be used as an example, such as... Figure 4 As shown.

[0102] First, the group's planning department establishes a project and submits data. At this point, a new record is created to trigger a worksheet time trigger, thereby initiating the business process.

[0103] Before the formal approval process begins, the approximate cost, including time and money, needs to be calculated by the computing node based on the submitted data upstream of the approval process. The approval form is then locked through data business rules, and once the locking node is set, manual modification of the data is no longer permitted.

[0104] Once the formal approval process begins, Business Unit A will be given priority in reviewing the project. If Business Unit A approves, it means they agree to take on the project, and they can further break down the project details and distribute them to their subordinate departments. If Business Unit A fails to approve, Business Unit B will then be assigned to review it. If Business Unit B fails to approve, Business Unit C will then be assigned, and so on. If no business unit takes on the project, it will be rejected.

[0105] After approval, regardless of whether it passes or fails, the approval result needs to be fed back to the Group Planning Department via a notification node downstream of the approval process. If any business unit approves the project, the project should be broken down into sub-tasks via a data processing node, and then the sub-tasks should be automatically distributed to the sub-departments via a notification node, depending on the circumstances.

[0106] Example 2

[0107] like Figure 5 As shown, the aPaaS-based approval workflow building system, as an example, includes:

[0108] The trigger module is used in the aPaaS platform to automatically trigger various types of business processes (including approval types). The automatic triggers include worksheet event triggers, timed triggers, triggers by date field, organizational personnel event triggers, external user time triggers, and Webhook triggers. The trigger is the switch that determines whether a workflow can be started; the business process can only be started if the trigger's conditions are met.

[0109] The upstream module of the approval process is used to connect with automated nodes after the business process is triggered but before entering the approval process. It preprocesses the approval data. The upstream module is the first module that is automatically executed in the business process. The necessary calculations, data operations, notifications, script processing, and other tasks can be completed according to the corresponding nodes. Automated nodes include:

[0110] (1) Data processing nodes: These are the basic nodes for adding, deleting, modifying, and querying form data.

[0111] (2) Message notification nodes: such as sending in-site notifications, sending SMS messages, sending emails, sending service account messages, and interface push notifications;

[0112] (3) Operation and component-type nodes: such as branches, delays, calculations, sub-processes, automatic printing, etc.;

[0113] (4) Developer-related nodes: namely, Webhooks, code blocks, and business process calling nodes;

[0114] The builders of all the above node business systems can flexibly choose according to their own needs;

[0115] The parameter passing module is used to pass process parameters from the main business process to the approval process. The process parameter system refers to defining a parameter object within the process to store certain data. This data can come from attribute values ​​of a query object, results of calculated nodes in the process, or values ​​received from other processes, such as approver, deadline, and notification content. Process parameters can be referenced by any node within their scope as dynamic parameters. Their lifecycle begins with the execution of the process and ends when the process is terminated (i.e., the process terminates and parameter values ​​are cleared). Using the process parameter system, the main business process can pass parameters to the approval process, making the configuration of the approval process more flexible and powerful. This disclosure provides five types of process parameters for aPaaS platform-based businesses: text, numeric, date / time, personnel, and department type.

[0116] The data structure setting module is used to acquire preprocessed approval data and set the data structure of the approval data in the approval process. This disclosure departs from the conventional thinking of traditional approval process system design. In this disclosure, one record can correspond to n approval processes (n≥1), and n approval processes correspond to m specific execution instances (m≥n≥1). The data structure relationship between the three is as follows: Figure 2 As shown; optimize the presentation of each instance on the record details page: when m=1, the information of each instance is initialized and presented in a single timeline style; while when m≥2, the information of each instance is initialized and presented in a card style, such as... Figure 3 As shown; adjust the comparison rules of the approval display column on the view for users to quickly retrieve information: when m=1, the approval display column corresponds to the traditional "1-to-1 process", that is, the information presented in each cell is the information of the only process currently in progress; while when m≥2, the information presented in each cell is the information of the most recently updated process among multiple processes;

[0117] The approval process module is used to enter the approval process to approve, fill in, copy, judge conditions, query across tables, and enable branch nodes of approval results. The approval process module is the part of the process that requires manual review. The results of cross-table queries can be used as dynamic parameters of approval nodes.

[0118] The downstream module of the approval process is used to feed back the approval result to the main business process after the approval is completed. The main business process can connect to the automated nodes after the approval stage. The downstream module of the approval process is the second module that is automatically executed in the business process. The required calculations, data operations, notifications, script processing and other tasks can be completed according to the corresponding nodes. The supported nodes are the same as the automated nodes in the upstream of the approval process.

[0119] Furthermore, the approval process module includes a data node acquisition module, a cross-table query module, a manual node module, and a condition judgment module.

[0120] Furthermore, the data node acquisition module is used to acquire data nodes, which include record data nodes, personnel data nodes, and department data nodes.

[0121] Furthermore, the cross-table query module is used to query approval data across tables using the acquired data nodes; the cross-table query module supports queries on three types of entity objects, including personnel objects, department objects, and other data table objects besides approval objects.

[0122] Furthermore, the cross-table query module includes a query object selection module, a query condition setting module, a sorting rule setting module, and a boundary rule setting module.

[0123] Furthermore, the query object selection module is used to select the type of query object: namely, personnel object, department object, or data table object.

[0124] Furthermore, the query condition setting module is used to set condition value filtering conditions. The condition values ​​can be fixed values ​​entered manually or dynamic values ​​from node objects. The query condition setting module supports multiple condition combinations, and their relationship can be uniformly "AND" or uniformly "OR".

[0125] Furthermore, the sorting rule setting module is used to set sorting rules when the query object consists of multiple data entries, so as to obtain data in a regular order according to a certain predetermined order; alternatively, no sorting rules can be set, in which case the data is obtained randomly.

[0126] Furthermore, the boundary rule setting module is used to set the execution mode of the process when no data is found. This module is designed to meet the requirement that the process cannot be interrupted or stopped, and has the following three detailed setting methods:

[0127] 1) Continue execution

[0128] If no query results are found, continue executing the subsequent nodes; if the subsequent nodes use the content of this object, they will be skipped or returned as null.

[0129] 2) Add new data and continue execution

[0130] If there are no query results, you can directly add a new data record to the database. If any subsequent nodes use the content of this object, they will directly use the newly added data record.

[0131] 3) Termination of process

[0132] If no results are found, the process can be stopped.

[0133] Furthermore, the manual node module is used to take the process parameters passed to the approval process and the results obtained from cross-table queries as parameters for the manual nodes, which include approval nodes, filling nodes, and copy nodes.

[0134] Furthermore, the condition judgment module is used to make condition judgments based on the field values ​​of the approval data or the running results of the manual nodes, and to run different branch nodes according to the results of the condition judgments.

[0135] Furthermore, the condition judgment module includes a data branch module and an approval result branch module.

[0136] Furthermore, the data branch module is used to execute a data branch node when the field value of the approval data meets a certain condition, otherwise the data branch node is not executed, for example, equal to the condition judgment value or not empty, etc.

[0137] Furthermore, the approval result branch module is used to determine whether to enable an approval result branch node when approval data is rejected at an approval node. If enabled, the approval process will not stop immediately after the approval node is rejected, but will continue to execute the approval result branch node according to the approval result of the previous approval node. The approval result branch node has two fixed branches: "Pass" and "Reject". The existence of the approval result branch node determines whether the approval process immediately terminates (returns to the downstream part of the main business process) when a certain piece of approval data is rejected. If this branch is enabled below an approval node, the system will determine that the process will not stop immediately after the node is rejected, but will continue to execute its respective branch according to the approval result of each node. The existence of the result branch does not affect the overall result of the approval process, which is still determined by the result of the last executed node.

[0138] Example 3

[0139] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the aPaaS-based approval process construction method in Embodiment 1.

[0140] Embodiment 1 of this disclosure is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this disclosure.

[0141] Electronic devices can take the form of general-purpose computing devices, such as server devices. Components of an electronic device may include, but are not limited to: at least one processor, at least one memory, and buses connecting different system components (including memory and processor).

[0142] The bus includes a data bus, an address bus, and a control bus.

[0143] The memory may include volatile memory, such as random access memory (RAM) and / or cache memory, and may further include read-only memory (ROM).

[0144] The memory may also include program tools having a set (at least one) of program modules, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0145] The processor performs various functional applications and data processing by running computer programs stored in memory.

[0146] Electronic devices can also communicate with one or more external devices (such as keyboards, pointing devices, etc.). This communication can be achieved through input / output (I / O) interfaces. Furthermore, electronic devices can communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapters. The network adapter communicates with other modules of the electronic device via a bus. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.

[0147] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0148] Example 4

[0149] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the aPaaS-based approval process construction method in Embodiment 1.

[0150] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0151] In a possible implementation, this disclosure can also be implemented as a program product comprising program code, which, when the program product is run on a terminal device, is used to cause the terminal device to perform the steps of implementing the aPaaS-based approval process construction method described in Embodiment 1.

[0152] The program code for executing this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0153] Although embodiments of the present disclosure have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the present disclosure, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for building an approval process based on aPaaS, characterized in that, The method includes: Trigger the business process; Connect to the automated nodes upstream of the approval process to preprocess the approval data; Pass the process parameters of the main business process to the approval process; Obtain preprocessed approval data and set the data structure of the approval data in the approval process; wherein, setting the data structure of the approval data in the approval process includes: each piece of approval data corresponds to n approval processes, each approval process corresponds to m specific execution instances, where m≥n≥1, so as to support multiple approval processes to act on a single approval data record at the same time, optimize the presentation of each execution instance on the record details page, and adjust the comparison rules of the approval display column; The optimization of the presentation of each execution instance on the record details page includes: when m=1, the information of each execution instance is initialized and presented in the style of a single timeline; when m≥2, the information of each execution instance is initialized and presented in the style of a card. The rules for adjusting the approval display column include: when m=1, each cell in the approval display column displays the information of the currently ongoing unique approval process; when m≥2, each cell displays the information of the most recently updated approval process among multiple approval processes. The approval process involves approving, filling in, copying, conditionally judging, cross-table querying, and enabling branch nodes for approval results. The approval results are fed back to the main business process and connected to the downstream automated nodes of the approval process.

2. The method for building an approval process based on aPaaS as described in claim 1, characterized in that, The triggered business process includes: Various types of business processes are triggered by automatic triggers, including main business processes and approval processes. The automatic triggers include worksheet event triggers, timed triggers, triggers by date field, organizational personnel event triggers, external user time triggers, and Webhook triggers.

3. The method for building an approval process based on aPaaS as described in claim 1, characterized in that, The process parameter refers to a parameter object defined in the process to store data. The data includes attribute values ​​from a certain query object, the results of calculation nodes in the process, and parameter values ​​passed from other processes. The process parameter can be referenced by any node in its scope as a dynamic parameter.

4. The method for building an approval process based on aPaaS as described in claim 1, characterized in that, The automated nodes connecting the upstream and downstream of the approval process include: Before entering the approval process / after the approval process is completed, the main business process completes tasks according to the connected automated nodes. These tasks include calculation, data operation, notification, and script processing. The automated node mentioned above includes: Data processing nodes, including nodes that perform add / delete / modify / query operations on approval data; Message notification nodes include in-site notification sending nodes, SMS sending nodes, email sending nodes, service account message sending nodes, and interface push nodes; The computation / component type nodes include branch nodes, delay nodes, calculation nodes, sub-process nodes, and automatic printing nodes; Developer-related nodes include Webhook nodes, code block nodes, and business process invocation nodes.

5. The method for building an approval process based on aPaaS as described in claim 1, characterized in that, The process of entering the approval process involves approving, filling in, copying, conditionally judging, cross-table querying, and enabling branch nodes for approval results, including: Acquire data nodes, including record data nodes, personnel data nodes, and department data nodes; Use the acquired data nodes to query approval data across tables; The process parameters passed to the approval process and the results obtained from cross-table queries are used as parameters for manual nodes, which include approval nodes, filling nodes, and copy nodes. Based on the field values ​​of the approval data or the results of the manual node operation, condition judgments are made, and different branch nodes are run according to the results of the condition judgments.

6. The method for building an approval process based on aPaaS as described in claim 1, characterized in that: The cross-table query is used to set query conditions, sorting rules and boundary rules according to the type of the selected entity object, and the query results are used as dynamic parameters of the approval node. The approval result branch node includes two fixed branches, "Pass" and "Reject," which allow users to customize the subsequent flow logic of the approval process when approval data is rejected.

7. An approval process construction system based on aPaaS, characterized in that, include: The trigger module is used to trigger business processes; The upstream module of the approval process is used to connect the automated nodes upstream of the approval process and preprocess the approval data; The parameter passing module is used to pass the process parameters of the main business process to the approval process; The data structure setting module is used to obtain preprocessed approval data, set the data structure of the approval data in the approval process, and enter the approval node. The data structure for setting approval data in the approval process includes: each piece of approval data corresponds to n approval processes, and each approval process corresponds to m specific execution instances, where m≥n≥1, to support multiple approval processes acting on a single approval data record simultaneously, optimize the presentation of each execution instance on the record details page, and adjust the comparison rules of the approval display column; The optimization of the presentation of each execution instance on the record details page includes: when m=1, the information of each execution instance is initialized and presented in the style of a single timeline; when m≥2, the information of each execution instance is initialized and presented in the style of a card. The rules for adjusting the approval display column include: when m=1, each cell in the approval display column displays the information of the currently ongoing unique approval process; when m≥2, each cell displays the information of the most recently updated approval process among multiple approval processes. The approval process module is used to enter the approval process to approve, fill in, copy, judge conditions, query across tables, and enable branch nodes of approval results; The downstream module of the approval process is used to feed back the approval results to the main business process and connect the downstream automation nodes of the approval process.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the aPaaS-based approval process construction method as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the aPaaS-based approval process construction method as described in any one of claims 1 to 6.

Images