An end-to-end business process approval method, device and medium

Abstract

The application provides an end-to-end business process approval method and device and a medium, and belongs to the technical field of computers. The method determines each document node corresponding to a corresponding full business process based on a first business flow design operation from a user terminal; generates node form attributes corresponding to each document node based on a second business flow design operation on each document node; wherein the node form attributes at least include workflow configuration attributes. Based on the node form attributes of each document node, determine the document relationship between each document node to generate the corresponding full business process; the document relationship is used to generate a business approval document for the corresponding document node; after receiving a business approval driving operation corresponding to the full business process, the corresponding business approval document is sequentially approved, and the full business process is executed. Through the above method, the documents between each document node are connected, and efficient document circulation and end-to-end full business process are realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an end-to-end business process approval method, device and medium. Background Technology

[0002] A business process is a series of activities jointly completed by different people to achieve a specific value goal. These activities not only have a strict sequential order, but their content, methods, and responsibilities must also be clearly arranged and defined to enable the handover of different activities between different roles. The transfer between activities can span a considerable distance in time and space.

[0003] The significance of business processes for enterprises lies not only in describing key business operations, but also in guiding business operations. This significance is reflected in the optimization of resources, the optimization of organizational structure, and a series of changes to management systems.

[0004] Currently, business processes involve a large number of documents, and document management in these processes often spans multiple modules, systems, and departments. On the one hand, the flow of documents within the process is complex; on the other hand, data consistency across departments or systems is difficult to maintain during data transfer in existing business processes. This makes it difficult to connect documents, hindering efficient document flow and end-to-end business process management. Furthermore, if problems arise in existing business processes, significant manual intervention is required to identify the issues and adjust the processes, resulting in high human resource costs. Summary of the Invention

[0005] This application provides an end-to-end business process approval method, device, and medium to address the difficulties in connecting documents in existing business processes, the inability to achieve efficient document transfer and end-to-end full business processes, and the need for extensive manual intervention to adjust existing business processes when problems arise.

[0006] On the one hand, embodiments of this application provide an end-to-end business process approval method, the method comprising:

[0007] Based on the first business flow design operation from the user terminal, determine the document nodes corresponding to the corresponding full business process;

[0008] Based on the second business flow design operation for each of the document nodes, node form attributes corresponding to each document node are generated; wherein, the node form attributes include at least workflow configuration attributes.

[0009] Based on the node form attributes of each document node, the document relationships between each document node are determined to generate the corresponding full business process; the document relationships are used to generate business approval documents for the corresponding document nodes.

[0010] Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

[0011] In one implementation of this application, based on the first business flow design operation from the user terminal, the document nodes corresponding to the corresponding full business process are determined, specifically including:

[0012] The system acquires user editing operations on the canvas display area of ​​the user terminal via the toolbar and element box; wherein the toolbar includes at least edit, save, cancel, publish, and close functions; and the element box includes at least start element, gateway element, document element, manual operation element, notification element, service element, signal capture element, message element, and end element.

[0013] Once the editing operation instruction is received, each of the document nodes in the canvas display area is determined.

[0014] In one implementation of this application, based on the second business flow design operation for each of the document nodes, node form attributes corresponding to each document node are generated, specifically including:

[0015] Select any of the document nodes mentioned above that the user selects in the canvas display area as the selected document node;

[0016] The preset attribute display area displays the form attributes to be configured for the selected document node;

[0017] Based on the user's selection operation on the form attribute to be configured, the node form attribute of the selected document node is determined; the list of node form attributes includes at least process level, node level, and connection level.

[0018] In one implementation of this application, the document relationships between the document nodes are determined based on the node form attributes of each document node to generate the corresponding full business process, specifically including:

[0019] Based on the node form attributes of each document node and at least two document nodes selected by the user, a corresponding type display option is determined; the type display option includes a relationship type used to establish document relationships between each document node;

[0020] When a user selects any relationship type in the type display options, the document relationships between each document node are determined to generate the full business process; the document relationships include at least: generating a target document through a document generation process, generating or obtaining a target document through a component, and obtaining a target document through an expression.

[0021] In one implementation of this application, the method further includes:

[0022] When the document relationship is such that the target document is generated through a document generation process, the business approval document corresponding to each document node is generated according to the document generation operation corresponding to the document relationship; wherein, the document generation operation includes at least automatic document generation, pull document generation, and push document generation; the automatic document generation is used to generate downstream documents according to preset conversion rules and upstream documents; the pull document generation and the push document generation generate corresponding business approval documents based on the operation of the document generation administrator of the pushed task.

[0023] In one implementation of this application, the method further includes:

[0024] When the document relationship is that the target document is generated or obtained through a component, the corresponding business approval document is determined according to the user's manual document generation operation for the corresponding document node;

[0025] When the document relationship is such that the target document is obtained through an expression, the user input expression of the corresponding document node is obtained, and the target document corresponding to the user input expression is called to generate the business approval document.

[0026] In one implementation of this application, the method further includes:

[0027] When the full business process is executed, the workflow corresponding to each document node is approved sequentially through the pre-built workflow engine.

[0028] After the workflow approval at the upstream document node is completed, the workflow approval at the downstream document node is executed.

[0029] In one implementation of this application, the entire business process is executed through a pre-built process engine to push the workflow corresponding to each document node and notify the corresponding user approval node.

[0030] On the other hand, embodiments of this application also provide an end-to-end business process approval device, the device comprising:

[0031] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0032] Based on the first business flow design operation from the user terminal, determine the document nodes corresponding to the corresponding full business process;

[0033] Based on the second business flow design operation for each of the document nodes, node form attributes corresponding to each document node are generated; wherein, the node form attributes include at least workflow configuration attributes.

[0034] Based on the node form attributes of each document node, the document relationships between each document node are determined to generate the corresponding full business process; the document relationships are used to generate business approval documents for the corresponding document nodes.

[0035] Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

[0036] Furthermore, embodiments of this application also provide a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0037] Based on the first business flow design operation from the user terminal, determine the document nodes corresponding to the corresponding full business process;

[0038] Based on the second business flow design operation for each of the document nodes, node form attributes corresponding to each document node are generated; wherein, the node form attributes include at least workflow configuration attributes.

[0039] Based on the node form attributes of each document node, the document relationships between each document node are determined to generate the corresponding full business process; the document relationships are used to generate business approval documents for the corresponding document nodes.

[0040] Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

[0041] Through the above technical solution, this application utilizes visualized business process design and establishes relationships between various document nodes to generate documents with sequential relationships, realizing an end-to-end business process. This simplifies the connection between business process documents and saves on the manual costs invested in connecting documents. It solves the problems of difficulty in connecting documents in existing business processes, the inability to achieve efficient document flow and end-to-end full business processes, and the need for extensive manual intervention to adjust existing business processes when problems arise. Attached Figure Description

[0042] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0043] Figure 1 This is a flowchart illustrating an end-to-end business process approval method according to an embodiment of this application.

[0044] Figure 2 This is a schematic diagram of a process design interface in an end-to-end business process approval method according to an embodiment of this application.

[0045] Figure 3 This is a schematic diagram of another process design interface in an end-to-end business process approval method according to an embodiment of this application.

[0046] Figure 4 This is a schematic diagram of another process design interface in an end-to-end business process approval method according to an embodiment of this application.

[0047] Figure 5 This is a schematic diagram of the structure of an end-to-end business process approval device in an embodiment of this application. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0049] This application provides an end-to-end business process approval method, device, and medium to solve the problems of difficulty in connecting documents in existing business processes, difficulty in achieving efficient document flow and end-to-end full business processes, and the need for a large amount of manual intervention to complete business process adjustments once problems occur in existing business processes.

[0050] The various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0051] This application provides an end-to-end business process approval method, such as... Figure 1 As shown, the method may include steps S101-S104:

[0052] S101, the server designs operations based on the first business flow from the user terminal and determines the corresponding document nodes for the entire business process.

[0053] It should be noted that the server, as the executor of the end-to-end business process approval method, is merely an example; the executor is not limited to the server, and this application does not specifically limit it. The executor runs the process designer and process engine, capable of executing the entire business process and completing the corresponding business approval process.

[0054] In this embodiment of the application, based on the first business flow design operation from the user terminal, the document nodes corresponding to the corresponding full business process are determined, specifically including:

[0055] The system captures user editing operations performed on the user's terminal canvas display area via the toolbar and element box. The toolbar includes at least the functions for editing, saving, canceling, publishing, and closing. The element box includes at least the elements for starting, gateway, document, manual operation, notification, service, signal capture, message, and ending. Upon receiving an editing operation instruction, the system identifies each document node within the canvas display area.

[0056] like Figure 2 As shown, when the entire business process in this application is a standard procurement process, the business flow designer of this application includes a toolbar 201, which includes at least controls for editing, saving, canceling, publishing, and closing. It also includes an element box 202 for generating the flowchart of the entire business process. The element box contains basic elements such as start elements, gateway elements, document elements, manual operation elements, notification elements, service elements, signal capture elements, message elements, and end elements. Among these, notification and message elements can send notification messages and notification reminders to designated recipients, supporting multiple reminder methods such as email and SMS, thus accelerating the business operation process.

[0057] Area 203 is the canvas display area. Various document nodes can be displayed in this area based on user actions such as dragging or clicking basic elements in the element box and using controls in the toolbar. Document nodes include submissions, purchase requisitions, and purchase orders.

[0058] S102, the server generates the node form attributes corresponding to each document node based on the second business flow design operation of each document node.

[0059] The node form attributes mentioned above should include at least workflow configuration attributes.

[0060] Specifically, based on the second business flow design operation for each document node, the node form attributes corresponding to each document node are generated, including:

[0061] Select any document node chosen by the user in the canvas display area as the selected document node. The pre-defined attribute display area shows the form attributes to be configured for the selected document node. Based on the user's selection of the form attributes to be configured, the node form attributes of the selected document node are determined. The list of corresponding node form attributes includes at least three levels: process level, node level, and connection level.

[0062] In other words, users can use their terminals to click on any document node in the canvas display area and configure form attributes for that node. These node form attributes can include, for example... Figure 3 List 301 shows the ability to set the process level, node level, and connection level, which are determined by the user and are not specifically limited in this application. Users can configure the workflow 302 and specify the workflow engine to perform workflow approval for that document node.

[0063] S103, the server determines the document relationships between document nodes based on the node form attributes of each document node, so as to generate the corresponding full business process.

[0064] The above document relationships are used to generate business approval documents for the corresponding document nodes.

[0065] In this embodiment, the document relationships between document nodes are determined based on the node form attributes of each document node to generate the corresponding full business process, specifically including:

[0066] Based on the node form attributes of each document node and at least two document nodes selected by the user, the corresponding type display options are determined. These type display options include the relationship types used to establish document relationships between document nodes. Upon receiving any relationship type selected by the user from the type display options, the document relationships between document nodes are determined to generate the entire business process. Document relationships at least include: generating the target document through a document generation process, generating or obtaining the target document through a component, and obtaining the target document through an expression.

[0067] In other words, users can select multiple document nodes, such as Figure 4 As shown, by selecting the connection between the purchase receipt and the accounts payable, the server can determine the type display options between the two document nodes. These include generating the target document through a document generation process, generating or retrieving the target document through components, and retrieving the target document through expressions.

[0068] When the document relationship involves generating the target document through a document generation process, the business approval document corresponding to each document node is generated based on the document generation operations of each document node corresponding to the document relationship. The document generation operations include at least automatic document generation, pull-based document generation, and push-based document generation. Automatic document generation is used to generate downstream documents based on preset conversion rules and upstream documents. Pull-based and push-based document generation generate corresponding business approval documents based on the operations of the document generation administrator of the pushed task.

[0069] In the automatic order generation process, upstream documents such as purchase receipts are upstream documents, while the corresponding financial accounts payable are downstream documents.

[0070] In cases where the document relationship is that the target document is generated or obtained through components, the corresponding business approval document is determined based on the user's manual document generation operation at the corresponding document node.

[0071] When the document relationship is such that the target document is obtained through an expression, the user input expression of the corresponding document node is obtained, and the target document corresponding to the user input expression is called to generate the business approval document.

[0072] In other words, this application configures different document relationships, and can execute the document generation process of document nodes based on different document relationships. When actually using the full business process of this application, it can complete the document generation of each document node in a timely manner based on the document relationship matched with each document node, thereby realizing the conversion of upstream and downstream documents and linking documents across businesses and modules, that is, associating documents between various document nodes.

[0073] S104. After receiving the business approval-driven operation corresponding to the entire business process, the server will approve the corresponding business approval documents in sequence and execute the entire business process.

[0074] When executing a full business process, a pre-built workflow engine sequentially approves the workflows corresponding to each document node. After the workflow at the upstream document node is approved, the workflow approval for the downstream document node is executed.

[0075] Workflow engines, such as Activiti and Camunda, are used to generate the entire business process according to steps S101-S103. After this process is generated, it is executed through a pre-built workflow engine. For example, the workflow engine can be used to push and notify the corresponding user approval nodes for each document node. This completes the generation and approval of all documents in the entire business process. Workflow engines include workflow engines, business process management engines, and rule engines, which can be specifically configured by the user; this application does not impose specific limitations on them.

[0076] This application abstracts business operations into document operations within the business workflow. By orchestrating cross-business documents and operations, it enables the flow of business documents across departments and systems, thereby eliminating process breakpoints, achieving end-to-end data connectivity, and streamlining the entire process. This application utilizes a visual, drag-and-drop workflow designer, allowing users to edit workflow definitions online. The workflow designer includes common activities found in business processes, such as start, gateway, document, manual operation, service, notification, and message. Gateways enable the splitting and merging of workflows; document nodes carry information about business documents, enabling document approval processes by linking them to workflows, and allowing the conversion of upstream and downstream documents through document relationship calculations, thus connecting cross-business documents; notifications and messages can inform and remind recipients. The workflow engine drives the workflow definition, ensuring the workflow executes according to predetermined steps, achieving end-to-end business flow, proactively pushing tasks and notifications, and seamlessly connecting each stage. In this way, it is possible to orchestrate single business operations as well as link documents across businesses, thereby achieving end-to-end business orchestration.

[0077] Through the above technical solution, this application utilizes visualized business process design and establishes relationships between various document nodes to generate documents with sequential relationships, realizing an end-to-end business process. This simplifies the connection between business process documents and saves on the manual costs invested in connecting documents. It solves the problems of difficulty in connecting documents in existing business processes, the inability to achieve efficient document flow and end-to-end full business processes, and the need for extensive manual intervention to adjust existing business processes when problems arise.

[0078] Figure 5 This application provides a schematic diagram of the structure of an end-to-end business process approval device, as shown in the embodiment of the present application. Figure 5 As shown, the device includes:

[0079] At least one processor; and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0080] Based on the first business flow design operation from the user terminal, the document nodes corresponding to the full business process are determined. Based on the second business flow design operation for each document node, node form attributes corresponding to each document node are generated. These node form attributes include at least workflow configuration attributes. Based on the node form attributes of each document node, the document relationships between the document nodes are determined to generate the corresponding full business process. These document relationships are used by the corresponding document nodes to generate business approval documents. Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

[0081] This application embodiment also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0082] Based on the first business flow design operation from the user terminal, the document nodes corresponding to the full business process are determined. Based on the second business flow design operation for each document node, node form attributes corresponding to each document node are generated. These node form attributes include at least workflow configuration attributes. Based on the node form attributes of each document node, the document relationships between the document nodes are determined to generate the corresponding full business process. These document relationships are used by the corresponding document nodes to generate business approval documents. Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

[0083] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0084] The devices, media, and methods provided in this application are one-to-one correspondences. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0085] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0086] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. An end-to-end business process approval method, characterized in that, The method includes: Based on the first business flow design operation from the user terminal, determine the document nodes corresponding to the corresponding full business process; Based on the second business flow design operation for each of the document nodes, node form attributes corresponding to each document node are generated; wherein, the node form attributes include at least workflow configuration attributes. Based on the node form attributes of each document node, the document relationships between the document nodes are determined to generate the corresponding full business process; the document relationships are used to generate business approval documents for the corresponding document nodes; specifically, this includes: determining corresponding type display options based on the node form attributes of each document node and at least two document nodes selected by the user; the type display options include relationship types for establishing document relationships between the document nodes; when the user selects any relationship type in the type display options, the document relationships between the document nodes are determined to generate the full business process; The document relationship includes at least: generating a target document through a document generation process, generating or obtaining a target document through a component, and obtaining a target document through an expression; when the document relationship is that the target document is generated through a document generation process, a business approval document corresponding to the corresponding document node is generated according to the document generation operation of each document node corresponding to the document relationship; wherein, the document generation operation includes at least automatic document generation, pull document generation, and push document generation; the automatic document generation is used to generate a downstream document according to preset conversion rules and upstream documents; the pull document generation and the push document generation generate corresponding business approval documents based on the operation of the document generation administrator of the pushed task; Upon receiving a business approval-driven operation corresponding to the full business process, the corresponding business approval documents are approved sequentially, and the full business process is executed.

2. The end-to-end business process approval method according to claim 1, characterized in that, Based on the first business flow design operation from the user terminal, the document nodes corresponding to the full business process are determined, specifically including: The system acquires user editing operations on the canvas display area of ​​the user terminal via the toolbar and element box; wherein the toolbar includes at least edit, save, cancel, publish, and close functions; and the element box includes at least start element, gateway element, document element, manual operation element, notification element, service element, signal capture element, message element, and end element. Once the editing operation instruction is received, each of the document nodes in the canvas display area is determined.

3. The end-to-end business process approval method according to claim 1, characterized in that, Based on the second business flow design operation for each of the aforementioned document nodes, node form attributes corresponding to each of the aforementioned document nodes are generated, specifically including: Select any of the document nodes mentioned above that the user selects in the canvas display area as the selected document node; The preset attribute display area displays the form attributes to be configured for the selected document node; Based on the user's selection operation on the form attribute to be configured, the node form attribute of the selected document node is determined; the list of node form attributes includes at least process level, node level, and connection level.

4. The end-to-end business process approval method according to claim 1, characterized in that, The method further includes: When the document relationship is that the target document is generated or obtained through a component, the corresponding business approval document is determined according to the user's manual document generation operation for the corresponding document node; When the document relationship is such that the target document is obtained through an expression, the user input expression of the corresponding document node is obtained, and the target document corresponding to the user input expression is called to generate the business approval document.

5. The end-to-end business process approval method according to claim 1, characterized in that, The method further includes: When the full business process is executed, the workflow corresponding to each document node is approved sequentially through the pre-built workflow engine. After the workflow approval at the upstream document node is completed, the workflow approval at the downstream document node is executed.

6. The end-to-end business process approval method according to claim 1, characterized in that, The entire business process is driven by a pre-built process engine to push the workflow corresponding to each document node and notify the relevant user approval nodes.

7. An end-to-end business process approval device, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform an end-to-end business process approval method as described in any one of claims 1-6.

8. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are capable of executing an end-to-end business process approval method as described in any one of claims 1-6.

Images