Business process driving method and device, medium and equipment

Abstract

This invention provides a business process driving method, apparatus, medium, and device. The method includes multiple driving processes, each corresponding to a business workflow process. Each driving process includes: approving a current node document generated by a document generation program; after approval, querying task parameters configured for the current node document; wherein the task parameters include task participants; determining the driving task corresponding to the current node document based on the task parameters; and pushing the driving task to the task participant, so that the task participant, upon receiving the driving task, obtains the current node document and generates a next node document based on the current node document; wherein the next node document serves as the current node document for the next driving process. This invention can improve business workflow efficiency.

Description

Technical Field

[0001] This invention relates to the field of business process technology, and in particular to a business process driving method, apparatus, medium, and equipment. Background Technology

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

[0003] Because business process management documents often cross modules, systems, and departments, the flow between these documents becomes complex. Currently, collaboration between documents mostly adopts a point-to-point conversion method. After the upstream document is approved, the upstream document administrator pushes down to generate the downstream document, or the downstream document administrator pulls up to generate the downstream document, which is the traditional "people looking for things" model.

[0004] Because administrators cannot push or delete tasks in a timely manner, the "people looking for tasks" model will affect the efficiency of process execution, which is undoubtedly a major loss for complex business processes. Summary of the Invention

[0005] To address at least one of the above-mentioned technical problems, embodiments of the present invention provide a business process driving method, apparatus, medium, and device.

[0006] According to a first aspect, the business process driving method provided by the embodiments of the present invention includes multiple driving processes, each driving process corresponding to a business flow process, and each driving process including:

[0007] Approve the current node document generated by the document generation program;

[0008] After approval, query the task parameters configured for the current node document; wherein, the task parameters include task participants;

[0009] Based on the task parameters, determine the driving task corresponding to the current node document;

[0010] The driving task is pushed to the task participant, so that when the task participant receives the driving task, it obtains the current node document and generates the next node document based on the current node document; wherein the next node document serves as the current node document for the next driving process.

[0011] In one embodiment, the query is configured with task parameters for the current node document, including:

[0012] The query retrieves the push task parameters configured for the current node document; correspondingly, the task participant is the push task participant, and the driving task determined according to the push task parameters is the push task.

[0013] In one embodiment, the order push task parameters further include a first task menu processing entry; wherein, when the order push task participant receives the order push task, he enters the first task processing interface of the order generation program through the first task menu processing entry, and generates the next node document based on the current node document in the first task processing interface.

[0014] In one embodiment, the query is configured with task parameters for the current node document, including:

[0015] The query specifies the order-pull task parameters configured for the current node document; correspondingly, the task participant is the order-pull task participant, and the driving task determined according to the order-pull task parameters is the order-pull task.

[0016] In one embodiment, the order-pushing task parameters further include a second task menu processing entry and a downstream document editing interface entry; wherein, when the order-pushing task participant receives the order-pushing task, he enters the second task processing interface through the second task menu processing entry, generates an initial next node document based on the current node document in the second task processing interface, and edits and modifies the initial next node document through the downstream document editing interface entry to obtain the final next node document.

[0017] In one embodiment, the task processing interface has a "Create Task" button, a "Terminate Task Creation" button, and an "Exit" button; wherein:

[0018] After the task participant triggers the "Generate Order" button, the "Generate Order" program is used to generate the next node order based on the current node order according to the order generation logic.

[0019] After the task participant triggers the "Terminate Order Generation" button, the order generation program is used to cancel the driving task.

[0020] When the exit button is triggered by the task participant, the order generation program exits the driving task, but the driving task is not canceled.

[0021] In one embodiment, the "Terminate Order Generation" button is applicable to scenarios where there is a direct business flow process between the previous node document and the next node document of the current node document.

[0022] In a second aspect, embodiments of the present invention provide a business process driving device, including a plurality of driving modules, each driving module being used to execute a driving process, each driving process corresponding to a business flow process, and each driving module including:

[0023] The document approval unit is used to approve the documents generated by the document generation program at the current node.

[0024] The parameter query unit is used to query the task parameters configured for the current node document after approval; wherein, the task parameters include task participants;

[0025] The task determination unit is used to determine the driving task corresponding to the current node document based on the task parameters.

[0026] The task push unit is used to push the driving task to the task participant, so that the task participant can obtain the current node document when it receives the driving task, and generate the next node document based on the current node document; wherein the next node document serves as the current node document of the next driving module.

[0027] In one embodiment, the parameter query unit is specifically used to: query the push task parameters configured for the current node document; correspondingly, the task participant is a push task participant, and the driving task determined according to the push task parameters is a push task.

[0028] In one embodiment, the order push task parameters further include a first task menu processing entry; wherein, when the order push task participant receives the order push task, he enters the first task processing interface of the order generation program through the first task menu processing entry, and generates the next node document based on the current node document in the first task processing interface.

[0029] In one embodiment, the parameter query unit is specifically used to: query the order-pulling task parameters configured for the current node document; correspondingly, the task participant is the order-pulling task participant, and the driving task determined according to the order-pulling task parameters is the order-pulling task.

[0030] In one embodiment, the order-pushing task parameters further include a second task menu processing entry and a downstream document editing interface entry; wherein, when the order-pushing task participant receives the order-pushing task, he enters the second task processing interface through the second task menu processing entry, generates an initial next node document based on the current node document in the second task processing interface, and edits and modifies the initial next node document through the downstream document editing interface entry to obtain the final next node document.

[0031] In one embodiment, the task processing interface has a "Create Task" button, a "Terminate Task Creation" button, and an "Exit" button; wherein:

[0032] After the task participant triggers the "Generate Order" button, the "Generate Order" program is used to generate the next node order based on the current node order according to the order generation logic.

[0033] After the task participant triggers the "Terminate Order Generation" button, the order generation program is used to cancel the driving task.

[0034] When the exit button is triggered by the task participant, the order generation program exits the driving task, but the driving task is not canceled.

[0035] In one embodiment, the "Terminate Order Generation" button is applicable to scenarios where there is a direct business flow process between the previous node document and the next node document of the current node document.

[0036] According to a third aspect, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method provided in the first aspect.

[0037] According to a fourth aspect, the computing device provided in the embodiments of the present invention includes a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, it implements the method provided in the first aspect.

[0038] The business process driving method, apparatus, medium, and equipment provided in the embodiments of the present invention have the following beneficial effects, individually or in combination:

[0039] (1) Each driving process includes: approving the current node document generated by the document generation program; after approval, querying the task parameters configured for the current node document; determining the driving task corresponding to the current node document based on the task parameters; and pushing the driving task to the task participant so that the task participant can obtain the current node document upon receiving the driving task and generate the next node document based on the current node document. It can be seen that after approval, the task participant is notified through the driving task, thus ensuring timely notification and task processing to generate the next node document. This is a task-to-person model, which ensures that the task participant of the next node can be notified promptly after the approval of a node document, thereby greatly improving the efficiency of business flow.

[0040] (2) In one embodiment, the driving task can be pushed to participants in the push task or to participants in the pull task. The push task parameters include a first task menu processing entry, and the pull task parameters include a second task menu processing entry and a downstream document editing interface entry. Participants can access the corresponding first task processing interface and second task processing interface through the first task menu processing entry and the second task menu processing entry, and then generate the next node document at the corresponding task processing node. Moreover, participants in the pull task can also access the editing and modification page of the next node document through the downstream document editing interface entry, and can edit the next node document according to their own needs, making the generation of the next node document more flexible.

[0041] (3) In one embodiment, the task processing interface has a task creation button, a task termination button and an exit button to meet different user needs. Attached Figure Description

[0042] Figure 1 This is a flowchart illustrating a business process-driven method according to an embodiment of the present invention. Detailed Implementation

[0043] Firstly, embodiments of the present invention provide a business process-driven method. This method includes multiple driving processes, each corresponding to one business flow process. That is, the entire business process-driven method includes multiple driving processes, and each driving process can drive the document flow in one business flow process. See also... Figure 1 Each drive process includes the following steps S110 to S140:

[0044] S110. Approve the current node document generated by the document generation program;

[0045] Among them, the document generation program refers to a program with document generation function. The purpose of the document generation function is to generate corresponding documents for each node.

[0046] The method provided in this embodiment of the invention can be executed by any computing device.

[0047] Understandably, when a node is designated as the current node, the document generated by the document generation program for the current node is called the current node document. The computing device approves the current node document, that is, it reviews whether the current node document meets the requirements. If it meets the requirements, the subsequent steps can be carried out; otherwise, the document needs to be regenerated.

[0048] For example, the order generation program generates sales documents based on sales data entered by sales personnel. After approving the sales documents, they are pushed to the outbound personnel so that they can enter relevant information. This allows the order generation program to generate outbound documents based on the sales documents. The sales documents are the upstream documents of the outbound documents, and the sales personnel are the upstream personnel of the outbound personnel.

[0049] S120. After approval, query the task parameters configured for the current node document; wherein, the task parameters include task participants;

[0050] The task participants can include push task participants and pull task participants. The task participants in the task parameters queried in S120 are one of the push task participants and pull task participants. That is to say, the current node's document is pushed to either the push task participant or the pull task participant, not both.

[0051] Understandably, the current node document can be pushed to the pushing person (i.e., the pushing task participant), or it can be pushed to the pulling person (i.e., the pulling task participant). In the example above, the pulling task participant is the outbound personnel, who are downstream of the sales personnel. The pushing task participant, on the other hand, is someone on the same side as the sales personnel.

[0052] Both push order and pull order participants can generate outbound documents using the document generation program. However, push order participants are unaware of the outbound personnel information when generating outbound documents from sales documents, while pull order participants are aware of the outbound personnel information. Furthermore, pull order participants can edit and modify outbound documents within the document generation program, but push order participants can only have their outbound documents generated by the document generation program according to a fixed pattern.

[0053] S130. Determine the driving task corresponding to the current node document based on the task parameters;

[0054] In other words, after querying the task parameters through S120, the corresponding driving task is formed based on the task parameters.

[0055] S140. Push the driving task to the task participant, so that the task participant can obtain the current node document when it receives the driving task, and generate the next node document based on the current node document; wherein the next node document serves as the current node document of the next driving process.

[0056] In other words, the driving task is sent to the corresponding task participants. When the task participants receive the reminder message of the driving task, they will obtain the current node document from the driving task and then generate the next node document based on the current node document in the document generation program.

[0057] At this point, the driving task of one node is completed. Then, the document of the next node is used as the document of the current node, and the above steps S110 to S130 are executed to realize the driving task of the next node. By repeating this process, S110 to S130 are executed in a loop to drive the entire business process.

[0058] In one embodiment, querying the task parameters configured for the current node document in S120 may include: querying the push task parameters configured for the current node document; correspondingly, the task participant is the push task participant.

[0059] Correspondingly, the driving task identified in S130 is the order-pushing task. The order-pushing task includes the aforementioned order-pushing task participants.

[0060] Furthermore, the order push task parameters may also include a first task menu processing entry; wherein, when the order push task participant receives the order push task, he enters the first task processing interface of the order generation program through the first task menu processing entry, and generates the next node document based on the current node document in the first task processing interface.

[0061] In other words, in S120, the queried task parameters include not only the participants in the order-pushing task but also the entry point for the first task menu. The resulting order-pushing task includes not only the participants but also the entry point for the first task menu. The entry point for the first task menu is the address of the first task processing interface. Participants in the order-pushing task can only access the first task processing interface through this entry point, and then generate the next node document based on the current node document within the first task processing interface.

[0062] As can be seen, when participants in the order placement task receive the reminder message, they will enter the first task processing interface through the first task menu, and then generate the next node document in the first task processing interface.

[0063] In one embodiment, querying the task parameters configured for the current node document in S120 may specifically include: querying the order-pulling task parameters configured for the current node document; correspondingly, the task participant is the order-pulling task participant.

[0064] Correspondingly, the driving task determined in S130 is the order-pushing task, which includes the aforementioned order-pushing task participants.

[0065] Furthermore, the order-pushing task parameters may also include a second task menu processing entry and a downstream document editing interface entry; wherein, when the order-pushing task participant receives the order-pushing task, he enters the second task processing interface through the second task menu processing entry, generates an initial next node document based on the current node document in the second task processing interface, and edits and modifies the initial next node document through the downstream document editing interface entry to obtain the final next node document.

[0066] In other words, the order-pull task parameters retrieved in S120 include not only the order-pull task participants, but also the entry point for the second task menu and the entry point for the downstream document editing interface. The resulting order-pull task includes not only the order-pull task participants, but also the entry point for the second task menu and the entry point for the downstream document editing interface. The entry point for the second task menu is the address of the entry point to the second task processing interface; access to the second task processing interface is only possible through this entry point. Similarly, access to the downstream document editing interface is only possible through this entry point, meaning the downstream document editing interface is the entry point to the modification and editing page of the next node document.

[0067] As can be seen, when a participant in a task-pulling process receives the task, they obtain the entry point for the second task menu and the entry point for the downstream document editing interface from the task. They then enter the second task processing interface through the second task menu entry point, and generate the next node document based on the current node document. Finally, they enter the document editing page through the downstream document editing interface entry point, where they modify and edit the generated next node document to obtain the final next node document.

[0068] Furthermore, a "Generate Document" button can be set on the first and second task processing interfaces. When a task participant clicks the "Generate Document" button, the document generation program can generate the next node document for the current node document. Of course, the document generation program can not only generate the next node document, but also cancel the driving task and temporarily exit the driving task. Therefore, the task processing interface can have a "Generate Document" button, a "Terminate Document Generation" button, and an "Exit" button. Different purposes can be achieved by triggering different buttons.

[0069] When the "Generate Order" button is triggered by the task participant, the "Generate Order" program is used to generate the next node order based on the current node order according to the order generation logic.

[0070] As can be seen, the function of the "Generate Order" button is to trigger the order generation process, causing it to enter the flow of generating the next node's document based on the current node's document. That is, when a task participant triggers the "Generate Order" button, the order generation process will generate the next node's document.

[0071] When the "Terminate Order Generation" button is triggered by the task participant, the order generation program is used to cancel the driving task.

[0072] As you can see, the function of the "Terminate Order Generation" button is to cancel the driving task. Once a driving task is canceled, it will no longer exist, and therefore the next node document will not be generated.

[0073] The "Terminate Order Generation" button has multiple application scenarios. For example, the current driving task is the business flow from node A to node B, and the next driving task is from node B to node C. However, another branch also includes a business flow from node A to node C. This indicates a direct business flow from node A to node C. Therefore, the business flows from node A to node B and from node B to node C are unnecessary. Thus, when the flow reaches node B, the driving task from node A to node B is canceled, and subsequent business drives within that branch are no longer executed; only the business drive from node A to node C is retained.

[0074] That is, the "Terminate Order Generation" button can be triggered in scenarios where there is a direct business flow between the previous and next node documents of the current node document.

[0075] When the exit button is triggered by the task participant, the order generation program exits the driving task, but the driving task is not canceled.

[0076] In other words, when a task participant does not want to generate the next node document, they can click the exit button. After exiting, the driving task will still be retained. When the task participant wants to generate the next node document, they can re-enter the task processing interface.

[0077] As can be seen, this invention addresses the problem of delayed message delivery affecting process execution efficiency in the previous "people find tasks" model by proposing a "task finds people" driving method, which promptly issues driving tasks and notifies task participants, thereby improving process flow efficiency.

[0078] In a second aspect, embodiments of the present invention provide a business process driving device, including a plurality of driving modules, each driving module being used to execute a driving process, each driving process corresponding to a business flow process, and each driving module including:

[0079] The document approval unit is used to approve the documents generated by the document generation program at the current node.

[0080] The parameter query unit is used to query the task parameters configured for the current node document after approval; wherein, the task parameters include task participants;

[0081] The task determination unit is used to determine the driving task corresponding to the current node document based on the task parameters.

[0082] The task push unit is used to push the driving task to the task participant, so that the task participant can obtain the current node document when it receives the driving task, and generate the next node document based on the current node document; wherein the next node document serves as the current node document of the next driving module.

[0083] In one embodiment, the parameter query unit is specifically used to: query the push task parameters configured for the current node document; correspondingly, the task participant is a push task participant, and the driving task determined according to the push task parameters is a push task.

[0084] In one embodiment, the order push task parameters further include a first task menu processing entry; wherein, when the order push task participant receives the order push task, he enters the first task processing interface of the order generation program through the first task menu processing entry, and generates the next node document based on the current node document in the first task processing interface.

[0085] In one embodiment, the parameter query unit is specifically used to: query the order-pulling task parameters configured for the current node document; correspondingly, the task participant is the order-pulling task participant, and the driving task determined according to the order-pulling task parameters is the order-pulling task.

[0086] In one embodiment, the order-pushing task parameters further include a second task menu processing entry and a downstream document editing interface entry; wherein, when the order-pushing task participant receives the order-pushing task, he enters the second task processing interface through the second task menu processing entry, generates an initial next node document based on the current node document in the second task processing interface, and edits and modifies the initial next node document through the downstream document editing interface entry to obtain the final next node document.

[0087] In one embodiment, the task processing interface has a "Create Task" button, a "Terminate Task Creation" button, and an "Exit" button; wherein:

[0088] After the task participant triggers the "Generate Order" button, the "Generate Order" program is used to generate the next node order based on the current node order according to the order generation logic.

[0089] After the task participant triggers the "Terminate Order Generation" button, the order generation program is used to cancel the driving task.

[0090] When the exit button is triggered by the task participant, the order generation program exits the driving task, but the driving task is not canceled.

[0091] In one embodiment, the "Terminate Order Generation" button is applicable to scenarios where there is a direct business flow process between the previous node document and the next node document of the current node document.

[0092] It is understood that explanations, specific implementation methods, beneficial effects, examples, etc. of the contents of the apparatus provided in the embodiments of the present invention can be found in the corresponding parts of the method provided in the first aspect, and will not be repeated here.

[0093] Thirdly, embodiments of the present invention provide a computer-readable medium storing computer instructions, which, when executed by a processor, cause the processor to perform the method provided in the first aspect.

[0094] Specifically, a system or apparatus equipped with a storage medium may be provided, on which software program code implementing the functions of any of the embodiments described above is stored, and the computer (or CPU or MPU) of the system or apparatus may read and execute the program code stored in the storage medium.

[0095] In this case, the program code read from the storage medium can itself implement the function of any of the above embodiments, and therefore the program code and the storage medium storing the program code constitute part of the present invention.

[0096] Examples of storage media used to provide program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer via a communication network.

[0097] Furthermore, it should be clear that not only can the program code read by the computer be executed, but also the operating system or other components operating on the computer can be instructed based on the program code to perform some or all of the actual operations, thereby realizing the function of any of the embodiments described above.

[0098] Furthermore, it is understood that the program code read from the storage medium is written to the memory set in the expansion board inserted into the computer or to the memory set in the expansion module connected to the computer. Then, based on the instructions of the program code, the CPU or other components installed on the expansion board or expansion module execute some and all of the actual operations, thereby realizing the function of any of the above embodiments.

[0099] It is understood that explanations, specific implementation methods, beneficial effects, examples, etc. of the contents in the computer-readable medium provided in the embodiments of the present invention can be found in the corresponding parts of the method provided in the first aspect, and will not be repeated here.

[0100] Fourthly, one embodiment of this specification provides a computing device including a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, it implements the method of any embodiment of the specification.

[0101] The various embodiments in this specification 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 apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0102] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this invention can be implemented using hardware, software, widgets, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium.

[0103] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

1. A business process-driven method, characterized in that, It includes multiple driving processes, each corresponding to one business flow process. Each driving process includes: Approve the current node document generated by the document generation program; After approval, query the task parameters configured for the current node document; wherein, the task parameters include task participants; Based on the task parameters, determine the driving task corresponding to the current node document; The driving task is pushed to the task participant, so that when the task participant receives the driving task, it obtains the current node document and generates the next node document based on the current node document; wherein, the next node document serves as the current node document for the next driving process; The query specifies the task parameters configured for the current node's document as push order task parameters and pull order task parameters: Query the push task parameters configured for the current node document; correspondingly, the task participant is the push task participant, and the driving task determined according to the push task parameters is the push task. The query specifies the order-pull task parameters configured for the current node document; correspondingly, the task participant is the order-pull task participant, and the driving task determined according to the order-pull task parameters is the order-pull task.

2. The method according to claim 1, characterized in that, The order push task parameters also include a first task menu processing entry; wherein, when the order push task participant receives the order push task, he enters the first task processing interface of the order generation program through the first task menu processing entry, and generates the next node document based on the current node document in the first task processing interface.

3. The method according to claim 2, characterized in that, The order-pulling task parameters also include a second task menu processing entry and a downstream document editing interface entry; wherein, when the order-pulling task participant receives the order-pulling task, he enters the second task processing interface through the second task menu processing entry, generates an initial next node document based on the current node document in the second task processing interface, and edits and modifies the initial next node document through the downstream document editing interface entry to obtain the final next node document.

4. The method according to claim 2 or 3, characterized in that, The first and second task processing interfaces have a "Generate Order" button, a "Terminate Order Generation" button, and an "Exit" button. in: After the task participant triggers the "Generate Order" button, the "Generate Order" program is used to generate the next node order based on the current node order according to the order generation logic. After the task participant triggers the "Terminate Order Generation" button, the order generation program is used to cancel the driving task. When the exit button is triggered by the task participant, the order generation program exits the driving task, but the driving task is not canceled.

5. The method according to claim 4, characterized in that, The "Terminate Order Generation" button is applicable in scenarios where there is a direct business flow between the previous and next node documents of the current node document.

6. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed in a computer, causes the computer to perform the method described in any one of claims 1-4.

7. A computing device, characterized in that, The method includes a memory and a processor, wherein the memory stores executable code, and the processor executes the executable code to implement the method described in any one of claims 1-4.

Images