CN118297553A

CN118297553A - Approval process rollback method, device, equipment, storage medium and program product

Info

Publication number: CN118297553A
Application number: CN202410485914.5A
Authority: CN
Inventors: 陈佳山; 曾天喻; 易文峰; 徐红艳; 李伊梦; 伍思豪
Original assignee: China Southern Power Grid Digital Platform Technology Guangdong Co ltd
Current assignee: China Southern Power Grid Digital Platform Technology Guangdong Co ltd
Priority date: 2024-04-22
Filing date: 2024-04-22
Publication date: 2024-07-05

Abstract

The application relates to an approval process rollback method, an approval process rollback device, an approval process rollback equipment, a storage medium and a program product. The circulation path of the approval process comprises a target parallel gateway, a first branch node and at least one second branch node, wherein the first branch node and the at least one second branch node are connected with the target parallel gateway, and the method comprises the following steps: after receiving an approval process rollback request sent by a first branch node, obtaining rollback configuration information of the first branch node, wherein the rollback configuration information comprises rollback type configuration information and rollback node configuration information; if the first branch node triggers the non-cooperative rollback event according to the rollback type configuration information, the approval process is non-cooperative rollback to the target rollback node corresponding to the rollback node configuration information, wherein under the condition that the first branch node does not perform the non-cooperative rollback, the approval process events of the first branch node and each second branch node are not affected. The method can improve the utilization rate of resources.

Description

Approval process rollback method, device, equipment, storage medium and program product

Technical Field

The present application relates to the field of computer technologies, and in particular, to an approval process rollback method, an apparatus, a device, a storage medium, and a program product.

Background

Along with the continuous development of computer technology, approval process management has become an important component in daily management of domestic and foreign enterprises, and also becomes one of the important means for realizing modern management for enterprises. In the process of the approval process circulation, if the approved node is found to have errors, the approval process can be returned to the node so that the node can correct the errors in time.

In the traditional technology, the whole workflow is rolled back from the current state to the previous state at a certain moment, so that the approval process starts from the previous state at a certain moment and then is rolled back, and the situation that the whole approval process is invalid and the approval process needs to be restarted due to the fact that a certain node in the middle of the approval process is in error is avoided.

However, in the actual application process, any one of the branch nodes corresponding to the parallel gateway triggers an approval process rollback event, which results in invalid approval operations completed by all the branch nodes corresponding to the parallel gateway, and after the approval process flows again, the approval process needs to be repeatedly approved, thus resulting in waste of human resources and time resources.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an approval process rollback method, apparatus, device, storage medium, and program product that can improve resource utilization.

In a first aspect, the present application provides a method for returning an approval process, where a circulation path of the approval process includes a target parallel gateway, and a first branch node and at least one second branch node that connect the target parallel gateway, and the method includes:

After receiving an approval process rollback request sent by the first branch node, obtaining rollback configuration information of the first branch node, wherein the rollback configuration information comprises rollback type configuration information and rollback node configuration information;

if the first branch node triggers the non-cooperative rollback event according to the rollback type configuration information, the approval process is non-cooperative rollback to a target rollback node corresponding to the rollback node configuration information, wherein the approval process events of the first branch node and each second branch node are not affected each other under the condition that the first branch node does not perform the cooperative rollback.

In one embodiment, after the non-cooperative rollback of the approval process to the target rollback node corresponding to the rollback node configuration information, the method further includes:

After determining that the approval process flows again from the target rollback node to the target parallel gateway, the approval process flows from the target parallel gateway to the first branch node.

In one embodiment, after determining that the approval process flows from the target fallback node to the target parallel gateway again, the flowing the approval process from the target parallel gateway to the first branch node includes:

Acquiring a first flow path, wherein the first flow path is a flow path of the approval process from the target rollback node to the first branch node, and comprises a first flow path section from the target rollback node to the target parallel gateway, a first branch path section from the target parallel gateway to the first branch node, and a second branch path section from the target parallel gateway to each of the second branch nodes;

Deleting all second branch sections in the first diversion path to obtain a second diversion path;

And according to the second forwarding path, the approval process flows from the target rollback node to the target parallel gateway, and flows from the target parallel gateway to the first branch node.

In one embodiment, after the acquiring the fallback configuration information of the first branch node, the method further includes:

If the first branch node triggers cooperative rollback according to the rollback type configuration information, the approval process is rolled back to a target rollback node corresponding to the rollback node configuration information from the first branch node and each second branch node in a cooperative manner;

After determining that the approval process flows again from the target rollback node to the target parallel gateway, the approval process flows to the first branch node and each second branch node respectively.

In one embodiment, the target rollback node includes a plurality of approval units, and the non-cooperative rollback of the approval process to the target rollback node corresponding to the rollback node configuration information includes:

Under the condition that target approval unit information is searched from the rollback node configuration information, positioning a target approval unit according to the target approval unit information, and rolling back the approval process from the first branch node to the target approval unit;

and under the condition that the target approval unit information is not found out from the rollback node configuration information, rolling back the approval process from the first branch node to each approval unit on the target rollback node.

In one embodiment, before the obtaining the fallback configuration information of the first branch node, the method further includes:

After receiving a flow definition request, outputting a flow definition interface, wherein the flow definition interface comprises a flow chart drawing area and a node attribute configuration area, and the node attribute configuration area comprises a rollback type configuration element and a rollback node configuration element;

Generating a target parallel gateway element and a first branch node element connected with the target parallel gateway element on the flow chart drawing area in response to a preset first operation of an interface defined for the flow chart;

Generating the rollback type configuration information of the first branch node in response to a preset second operation for the rollback type configuration element and generating the rollback node configuration information of the first branch node in response to a preset third operation for the rollback node configuration element under the condition that the first branch node element is determined to be in a selected state.

In a second aspect, the present application further provides an approval process rollback device, where a circulation path of the approval process includes a target parallel gateway, and a first branch node and at least one second branch node that connect the target parallel gateway, where the device includes:

The obtaining module is used for obtaining the rollback configuration information of the first branch node after receiving the approval process rollback request sent by the first branch node, wherein the rollback configuration information comprises rollback type configuration information and rollback node configuration information;

and the non-cooperative rollback module is used for non-cooperative rollback of the approval process to a target rollback node corresponding to the rollback node configuration information if the first branch node triggers the non-cooperative rollback event according to the rollback type configuration information, wherein the approval process events of the first branch node and each second branch node are not affected each other under the condition that the first branch node does not cooperative rollback.

In a third aspect, the present application also provides a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:

In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

In a fifth aspect, the application also provides a computer program product comprising a computer program which, when executed by a processor, performs the steps of:

The above method, device, equipment, storage medium and program product for examining and approving the flow rollback are applied to any one of a plurality of branch nodes connected with a target parallel gateway, the branch node which initiates the examining and approving the flow rollback request can be used as a first branch node, the other branch nodes except the first branch node are used as a second branch node, in this case, rollback configuration information of the first branch node is firstly obtained, according to rollback node configuration information in the rollback node configuration information, a target rollback node needing to be rolled back by the first branch node can be determined, and according to rollback type configuration information in the rollback node configuration information, whether the first branch node triggers a non-cooperative rollback event can be judged; furthermore, if the first branch node triggers the non-cooperative fallback event according to the fallback type configuration information, the approval process is non-cooperative fallback to the target fallback node corresponding to the fallback node configuration information, and the approval process events of the plurality of branch nodes connected with the target parallel gateway can be not affected by each other in a non-cooperative fallback mode, that is, when the first branch node triggers the non-cooperative fallback event, the second branch node does not perform fallback together with the first branch node, and operations such as approval and fallback can still be normally performed. Therefore, by means of non-cooperative rollback, decoupling of the rollback function of the approval process of each branch node under the parallel gateway can be achieved, so that the approved second branch node does not need to be influenced by the rollback event triggered by the first branch node to repeatedly execute the approval step, unnecessary repeated approval steps are reduced, manpower resources and time resources are saved, and the resource utilization rate is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the related art, the drawings that are needed in the description of the embodiments of the present application or the related technologies will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other related drawings may be obtained according to these drawings without inventive effort to those of ordinary skill in the art.

FIG. 1 is a schematic diagram of an approval process according to an embodiment of an approval process rollback method;

FIG. 2 is a schematic diagram of an approval process according to another embodiment;

FIG. 3 is a schematic diagram of a flow definition interface in one embodiment;

FIG. 4 is a schematic diagram of an extended properties tab page in another embodiment;

FIG. 5 is a block diagram illustrating a configuration of an approval process rollback apparatus in one embodiment;

fig. 6 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

In an exemplary embodiment, as shown in fig. 1, an approval process rollback method is provided, and this embodiment is applied to a terminal for illustration, where the terminal may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, projection devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The head-mounted device may be a Virtual Reality (VR) device, an augmented Reality (Augmented Reality, AR) device, smart glasses, or the like. It will be appreciated that the method may also be applied to a server, and may also be applied to a system comprising a terminal and a server, and implemented by interaction of the terminal and the server. In this embodiment, the circulation path of the approval process includes a target parallel gateway, and a first branch node and at least one second branch node connected to the target parallel gateway, and the method includes the following steps S10-S20. Wherein:

step S10, after receiving the approval process back-off request sent by the first branch node, obtaining back-off configuration information of the first branch node, where the back-off configuration information includes back-off type configuration information and back-off node configuration information.

In this embodiment, it should be noted that, in the conventional technology, the approval process is rolled back from the current state of the whole workflow to the previous state of a certain moment, so that the approval process starts from the previous state of a certain moment and proceeds to the subsequent rotation, thus any one branch node corresponding to the parallel gateway triggers the approval process rollback event, which can cause that all branch nodes corresponding to the parallel gateway have completed approval operations to be invalid, and after the approval process is again circulated, the approval process needs to be repeated once again. However, each branch node of the parallel gateway may independently examine and approve different contents in the same examination and approval process, that is, after the content examined and approved by any branch node is modified, the examination and approval task of other branch nodes will not be affected, for example, an administrative department, a financial department and a technical department examine and approve the same task in parallel, the administrative department is responsible for examining and approving the administrative matters in the task, the financial department is responsible for examining and approving the financial matters in the task, the technical department is responsible for examining and approving the technical matters in the task, wherein, both the administrative department and the technical department pass the examination and approval, but the financial department needs to return to the previous node to examine and approve a certain financial matters examined and approved by the prior node, but the modification of the financial matters will not affect the examination and approval of the administrative matters and the technical matters. In this case, the conventional method for returning the approval process increases unnecessary repeated approval steps, resulting in waste of human resources and time resources.

The parallel gateway is a gateway which can execute all output paths simultaneously and allows the approval process to flow downwards after all input paths are summarized after being executed, and nodes on the output paths of the parallel gateway are branch nodes corresponding to the parallel gateway. The embodiment is applied to any branch node on the output path of the parallel gateway, and initiates the condition of the approval process rollback request, namely, after the approval process flows out from the starting node, the approval process flows through at least one prior node, flows to the target parallel gateway, branches into a plurality of branch nodes from the target parallel gateway, and further, any branch node initiates the approval process rollback request, and the branch node initiating the approval process rollback request is a first branch node, and other branch nodes not initiating the approval process rollback request are second branch nodes.

In a possible implementation manner, a plurality of branch nodes may initiate an approval process rollback request and trigger a non-cooperative rollback event, in this case, each branch node initiating the approval process rollback request may respectively perform non-cooperative rollback, each branch node initiating the approval process rollback request may be used as a first branch node in its corresponding non-cooperative rollback event, and the approval process may be non-cooperative rolled back to its corresponding target rollback node, while other branch nodes not triggering the non-cooperative rollback event may not be affected, and operations such as process approval and rollback may be continued.

In a possible implementation manner, the first branch node may be an unverified branch node, or may be an approved branch node, and for the parallel gateway, it is required that each branch node is approved and the circulation condition is met to allow the approval process to flow downwards, so if at least one unverified branch node exists among a plurality of branch nodes corresponding to the same parallel gateway, or the circulation condition is not met currently, the approval process remains at each branch node, in this case, any branch node may perform approval process rollback, whether the approval process is finished or not, for example, the approval process flows from the node a to the parallel gateway B, and then flows to the branch nodes B1, B2 and B3 corresponding to the parallel gateway B, where B2 has finished approval and approval process pass, and B1, B2 and B3 may perform approval process rollback.

The fallback configuration information refers to parameter information configured for fallback function related parameters, and includes fallback type configuration information, fallback node configuration information, fallback path configuration information, and the like.

The configuration information of the rollback type refers to configuration information related to a rollback type allowed by the first branch node, the rollback type of the branch node includes non-cooperative rollback, cooperative rollback and the like, the cooperative rollback refers to that a plurality of branch nodes corresponding to the same parallel gateway should rollback together, for example, an approval process flows from a node A to a parallel gateway B and then flows to branch nodes B1, B2 and B3 corresponding to the parallel gateway B, if the B1 initiates an approval process rollback request, the approval process is required to be rolled back to the node A, and at the moment, whether the B2 and the B3 finish approval at present or not, the approval process is returned from the B1, the B2 and the B3 to the node A together; the non-cooperative rollback refers to that each branch node corresponding to the same parallel gateway independently rolls back, for example, the approval process flows from node a to parallel gateway B, and then flows to branch nodes B1, B2 and B3 corresponding to parallel gateway B, where B2 has completed approval and the approval has not yet been performed, if B1 initiates an approval process rollback request, only the approval process flowing to B1 is rolled back to node a, after node a re-approval, the approval process flows again through parallel gateway B to branch nodes B1, B1 will perform approval on the new approval process data after re-approval, and the approval processes at B2 and B3 are not yet rolled back, so that B2 of approval is not required to be performed, and B3 of approval has not yet been performed, and since a rollback request is not initiated, when B3 performs approval, old approval process data after approval is performed. By classifying the rollback types of the branch nodes and presetting a corresponding implementation mode for each rollback type, the rollback types can be set by one key during flow definition, so that the flow definition operation is simplified, and the flow definition efficiency is improved.

The fallback node configuration information refers to configuration information related to a target fallback node that the first branch node allows fallback. In a possible implementation manner, the target rollback node may include a plurality of approval units, and the rollback node configuration information may further include target approval unit information, so that by configuring the rollback node configuration information, the target approval units in the target rollback node can be designated to be rolled back, so that other approval units in the target rollback node do not need to be subjected to repeated approval, unnecessary approval steps are reduced, manpower resources and time resources are saved, and resource utilization is improved.

In an exemplary process of the approval process according to the preset circulation path, each node may initiate an approval process rollback request, if there is a rollback requirement on a first branch node on the output path of the target parallel gateway, the terminal may initiate the approval process rollback request, and after receiving the approval process rollback request sent by the first branch node, the terminal obtains rollback configuration information of the first branch node.

As an example, the fallback configuration information may be set at a flow definition stage; and after receiving the approval process rollback request sent by the first branch node, outputting a configuration interface to acquire rollback configuration information input by a user through the configuration interface. In consideration of different permissions and requirements of different users of different nodes, different configuration permissions may be set in advance for different nodes or different users according to actual requirements, for example, a node with a permission to designate a target rollback node may output a configuration interface after an approval process rollback request is initiated, and a target rollback node configuration element may be set to an allowed input state, so that a user may designate a target rollback node through the target rollback node configuration element of the configuration interface, and for a node without the permission to designate a rollback node, after the approval process rollback request is initiated, the terminal may output the configuration interface, and set the target rollback node configuration element to a forbidden input state, so that the user cannot pass through the designated target rollback node of the target rollback node configuration element of the configuration interface.

As an example, since the rights and requirements of different nodes are different, a target rollback node may be designated for the first branch node in the flow definition stage, and rollback node configuration information may be generated; or after receiving the rollback request of the approval process sent by the first branch node, outputting a rollback node configuration interface corresponding to the first branch node, and obtaining rollback node configuration information input by a user through the rollback node configuration interface.

Step S20, if it is determined that the first branch node triggers a non-cooperative fallback event according to the fallback type configuration information, the approval process is non-cooperative fallback to the target fallback node corresponding to the fallback node configuration information, where the approval process events of the first branch node and each of the second branch nodes do not affect each other when the first branch node does not perform the cooperative fallback.

Illustratively, after the fallback configuration information of the first branch node is obtained, the fallback node configuration information and the fallback type configuration information may be searched for from the fallback configuration information; furthermore, locating the rollback node identification information from the rollback node configuration information, matching the rollback node identification information with the identification information of each node of the approval process flow, determining a target rollback node matched with the rollback node identification information, and synchronously, matching the rollback type configuration information with a preset rollback type to determine the target rollback type; furthermore, under the condition that the target rollback type of the first branch node is determined to be non-cooperative rollback according to the rollback type configuration information, the first branch node is determined to trigger a non-cooperative rollback event, in this case, only the approval process of the first branch node is rolled back to the target rollback node, so that the target rollback node can carry out process approval again, and any second branch node is not processed, so that the second branch node still carries out approval according to the approval process data received originally.

In a possible implementation manner, backlogs of the first branch node may be deleted, corresponding backlogs are generated for the target rollback node, when the approval process flows to the target parallel gateway again, corresponding backlogs are regenerated for the first branch node, and at this time, backlogs are not generated for the second branch node any more, so that the second branch node does not need to perform repeated approval.

In a possible implementation manner, the backlog mode of the approval process may generate backlogs for the nodes needing to be re-approved, and the nodes needing not to be re-approved do not create backlogs, for example, if the first branch node T is to return the approval process to the target rollback node a, the backlog mode may be created for a when the first branch node T is to return to a, and further when the approval process flows to the parallel gateway, only create backlogs for T, but not create backlogs for other branch nodes except T, so that both T and a need to re-perform the process approval; the method of the approval process rollback may also be that a new circulation path is generated according to a preset circulation path from a target rollback node to a first branch node, the new circulation path includes a first circulation path section from the target rollback node to the target parallel gateway and a second circulation path section from the target parallel gateway to the first branch node, wherein the first circulation path section is the same as the preset circulation path, the second circulation path section is a path section from the target parallel gateway to each branch node in the preset circulation path, which flows to the first branch node, and corresponds to a path section of the approval process for approval and circulation again from the target rollback node, only after entering the target parallel gateway, the first circulation path section is circulated to the first branch node only through a branch path section corresponding to the first branch node, and no longer flows to each second branch node.

The above-mentioned approval process backspacing method is applied to any one of a plurality of branch nodes connected with a target parallel gateway, and when the approval process backspacing request is initiated, the branch node initiating the approval process backspacing request can be used as a first branch node, and other branch nodes except the first branch node are used as a second branch node, in this case, firstly backspacing configuration information of the first branch node is obtained, according to backspacing node configuration information in the backspacing node configuration information, a target backspacing node required to be backspacing by the first branch node can be determined, and according to backspacing type configuration information in the backspacing node configuration information, whether the first branch node triggers a non-cooperative backspacing event can be judged; furthermore, if the first branch node triggers the non-cooperative fallback event according to the fallback type configuration information, the approval process is non-cooperative fallback to the target fallback node corresponding to the fallback node configuration information, and the approval process events of the plurality of branch nodes connected with the target parallel gateway can be not affected by each other in a non-cooperative fallback mode, that is, when the first branch node triggers the non-cooperative fallback event, the second branch node does not perform fallback together with the first branch node, and operations such as approval and fallback can still be normally performed. Therefore, by means of non-cooperative rollback, decoupling of the rollback function of the approval process of each branch node under the parallel gateway can be achieved, so that the approved second branch node does not need to be influenced by the rollback event triggered by the first branch node to repeatedly execute the approval step, unnecessary repeated approval steps are reduced, manpower resources and time resources are saved, and the resource utilization rate is improved.

In an exemplary embodiment, after the non-cooperative rollback of the approval process to the target rollback node corresponding to the rollback node configuration information, step S30 is further included. Wherein,

Step S30, after determining that the approval process flows from the target rollback node to the target parallel gateway again, the approval process flows from the target parallel gateway to the first branch node.

In an exemplary embodiment, after the approval process is returned from the first branch node to the target return node, the target return node needs to re-perform the process approval, and after the approval passes, the flow is re-performed, and in the re-performing the flow, the approval process still flows according to the same preset flow path as before, and after the approval process flows to the target parallel gateway, only the approval process flows from the target parallel gateway to the first branch node, and the flow path section from the parallel gateway to the second branch node is not performed any more.

In a possible implementation manner, data generated in the process of flow and rollback of the approval process can be stored, so that after all branch nodes converge, when the flow of the approval process is transferred to a subsequent node, the subsequent node can check as required to know the flow and rollback of the approval process.

In an exemplary embodiment, the step of transferring the approval process from the target parallel gateway to the first branch node after determining that the approval process is transferred from the target fallback node to the target parallel gateway again includes steps S31 to S33. Wherein:

Step S31, obtaining a first flow path, where the first flow path is a flow path of the approval process from the target rollback node to the first branch node, and includes a first flow path section from the target rollback node to the target parallel gateway, a first branch path section from the target parallel gateway to the first branch node, and a second branch path section from the target parallel gateway to each of the second branch nodes.

The first flow path is a flow path from the target rollback node to the first branch node, and is configured in the process of flow definition, and after the target parallel gateway, the first flow path branches to form a plurality of branch road parts, including a first branch road part from the target parallel gateway to the first branch node and a second branch road part from the target parallel gateway to each second branch node. Before the rollback operation is not triggered, after the approval flow flows to the target rollback node, the approval flow flows to the first branch node according to the first flow path. However, if the approval process flows according to the first flow path, after the approval process flows to the parallel gateway, the approval process flows to all the branch nodes at the same time, so after triggering the operation of the non-cooperative fallback event, the non-cooperative fallback function can be realized by adjusting the first flow path.

In an exemplary embodiment, after returning the approval process from the first branch node to the target return node, the target return node needs to re-perform the process approval, and then re-perform the circulation after the approval passes, when re-performing the circulation, the first circulation path may be obtained first, the target parallel gateway may be located in the first circulation path, the branch road parts connected with the target parallel gateway may be determined, whether the first branch node exists in each branch road part may be detected, the branch road parts without the first branch node may be determined as the second branch road parts, and the branch road parts with the first branch node may be determined as the first branch road parts.

And step S32, deleting all second branch sections in the first diversion path to obtain a second diversion path.

Illustratively, all second branch segments in the first flow path are deleted, only the first branch segment flowing through the first branch node is reserved, and the first flow path after deleting the second branch segment is determined as the second flow path.

And step S33, according to the second forwarding path, the approval process flows from the target rollback node to the target parallel gateway, and then flows from the target parallel gateway to the first branch node.

For example, according to the second forwarding path, the approval process flows from the target rollback node to the target parallel gateway, after the approval process flows to the target parallel gateway, the approval process flows only from the target parallel gateway to the first branch node, and since the second forwarding path no longer covers the second branch road segments from the target parallel gateway to each of the second branch nodes, the approval process flows to the target parallel gateway, and then flows only to the first branch node, but not to the second branch node.

In this embodiment, by adjusting the first forwarding path, the approval process can be orderly performed in a non-cooperative manner, without affecting the second branch node, and by planning the second forwarding path, the accuracy of the approval process during automatic execution can be improved.

In an exemplary embodiment, after the step of obtaining the fallback configuration information of the first branch node, steps a10 to a20 are further included. Wherein:

and step A10, if the first branch node is determined to trigger cooperative rollback according to the rollback type configuration information, the approval process is rolled back cooperatively from the first branch node and each second branch node to a target rollback node corresponding to the rollback node configuration information.

It should be noted that, under the condition that each branch node of the parallel gateway jointly performs approval on the same task, approval process events of each branch node are independently executed, but approval ranges may overlap, for example, multiple approval is performed on one technical file, so as to avoid situations of missed approval and wrong approval of single approval. In this case, after any branch node is retracted, the approval contents of other branch nodes may be changed, and the non-cooperative retraction manner is difficult to update the changed approval contents in time, which may cause that a plurality of branch nodes repeatedly check the same error, resulting in waste of human resources and time resources. Therefore, with the complexity of the approval business scenes, the single rollback mode is difficult to meet the actual requirements of different approval business scenes.

For example, in the case that the first branch node triggers the cooperative fallback according to the configuration information of the fallback type, regardless of whether each branch node has completed approval, the approval process is cooperatively fallback to the target fallback node, that is, the approval process flowing to the first branch node is fallback to the target fallback node, and synchronously, the approval process flowing to the second branch node is cooperatively fallback to the target fallback node.

In a possible implementation manner, backlogs corresponding to each branch node may be deleted, corresponding backlogs are generated for the target rollback node, and when the approval process flows to each branch node again, corresponding backlogs are regenerated for each branch node.

Step a20, after determining that the approval process flows from the target rollback node to the target parallel gateway again, the approval process flows to the first branch node and each second branch node respectively.

The method includes that after the approval process is returned from each branch node to the target return node, the target return node needs to carry out process approval again, and after approval passes, circulation is carried out again, in the circulation process again, the approval process still carries out circulation according to the same preset circulation path as before, after circulation is carried out to the target parallel gateway, the approval process is circulated from the target parallel gateway to each branch node including the first branch node, and approval content of each branch node is synchronously updated.

In this embodiment, when the approval ranges of different branch nodes overlap, by adopting a cooperative fallback manner, a cooperative fallback event can be triggered at any one branch node, so that when the approval content changes, the approval content of other branch nodes is synchronously updated, so as to reduce the workload of other branch nodes, save human resources and time resources, and improve the resource utilization rate. On the other hand, by setting different rollback types, the method can adapt to different approval business scenes, improves the adaptability and comprehensiveness of the rollback of the approval process, reduces unnecessary repeated operation and invalid operation, and improves the operation convenience.

In a possible implementation manner, the step of respectively transferring the approval process to the first branch node and each second branch node includes steps a21 to a22. Wherein:

step a21, obtaining a first forwarding path, where the first forwarding path is a forwarding path through which the approval process flows from the target rollback node to the first branch node.

The first flow path is a flow path from the target rollback node to the first branch node, and is configured in the process of flow definition, and after the target parallel gateway, the first flow path branches to form a plurality of branch road parts, including a first branch road part from the target parallel gateway to the first branch node and a second branch road part from the target parallel gateway to each second branch node.

In an exemplary embodiment, after the approval process is returned from each branch node to the target rollback node, the target rollback node needs to re-perform the process approval, and after the approval passes, the flow is re-performed, and when the flow is re-performed, since the current target rollback type is the cooperative rollback, the path re-performed after rollback is not changed, so that the first flow path already configured in the process of defining the process can be directly obtained.

And step A22, according to the first flow path, the approval process flows from the target rollback node to the target parallel gateway, and flows from the target parallel gateway to the first branch node and each second branch node.

Illustratively, according to the first forwarding path, the approval process is forwarded from the target rollback node to the target parallel gateway, and after the approval process is forwarded to the target parallel gateway, the approval process is forwarded from the target parallel gateway to each branch node along each branch.

In an exemplary embodiment, the target rollback node includes a plurality of approval units, and the step of non-cooperatively rolling back the approval process to the target rollback node corresponding to the rollback node configuration information includes steps S21 to S22. Wherein:

Step S21, when the target approval unit information is found from the configuration information of the rollback node, locating a target approval unit according to the target approval unit information, and rolling back the approval process from the first branch node to the target approval unit.

It should be noted that the target rollback node may include a plurality of approval units, for example, the target rollback node may correspond to a department, and the approval unit may correspond to one or more persons of the department. In this way, in the rollback process, if the whole target rollback node has an approval error, the method can rollback to the target rollback node so that all approval units on the whole target rollback node are approved again, if only part of approval units in the target rollback node have an approval error, part of approval units on the target rollback node can be appointed to be approved again, and other approval units in the target rollback node do not need to be approved repeatedly.

For example, after the configuration information of the rollback node is obtained, the target approval unit information may be first searched from the configuration information of the rollback node, and in the case that the target approval unit information is searched from the configuration information of the rollback node, the target approval unit information may be matched with the information of a plurality of approval units in the target rollback node, and a target approval unit matched with the target approval unit information may be determined; and then, only the approval process which flows to the first branch node is returned to the target approval unit so that the target approval unit can carry out process approval again, and the second branch node is not processed, so that the second branch node still carries out approval according to the approval process data which is originally received. In a possible embodiment, after the approval process is backed up to the target back-off node, only the corresponding backlog is generated for the target approval unit, so that the target approval unit performs approval again, and other approval units on the target back-off node do not need repeated approval.

Step S22, in the case that the target approval unit information is not found from the configuration information of the rollback node, rollback the approval process from the first branch node to each approval unit on the target rollback node.

For example, if the target approval unit information is not found from the configuration information of the rollback node, the approval process flowing to the first branch node is rolled back to each approval unit on the target rollback node; after the approval process is backed-off to the target back-off node, a corresponding backlog can be generated for each target approval unit, so that each approval unit on the target back-off node can carry out process approval again.

In an exemplary embodiment, as shown in fig. 2, before the step of obtaining the fallback configuration information of the first branch node, steps B10 to B30 are further included. Wherein:

Step B10, after receiving a flow definition request, outputting a flow definition interface, wherein the flow definition interface comprises a flow chart drawing area and a node attribute configuration area, and the node attribute configuration area comprises a rollback type configuration element and a rollback node configuration element;

It should be noted that, as the scenes of the complex business approval process are increasing, the workflow is also more and more complex. The non-cooperative rollback function also relates to the situations of alternation of new and old approval flows, change of circulation paths and the like, and the editing and defining modes are manually performed one by one, so that the operation is complicated, and the situations of omission, mistakes and the like are easy to occur.

The process definition interface is an interface for performing process definition, and may include a flowchart drawing area, a node attribute configuration area, a toolbar area, etc., where the flowchart drawing area is used to draw an approval flowchart corresponding to a business approval process, for example, when a user draws the approval flowchart, a required task node element may be dragged into the flowchart drawing area, and then a task node is connected by using a sequential flow; the node attribute configuration area is used for setting various attributes of the task node, such as name, authority, rollback type, rollback node, and the like, and includes various attribute configuration elements, such as a name configuration element, an authority configuration element, a rollback type configuration element, a rollback node configuration element, and the like.

In a possible implementation manner, various attribute configuration elements can be displayed in a classified manner by setting a plurality of tab pages, for example, a task tab page can display basic information such as a name and authority, a rollback setting tab page can display information related to batch flow rollback such as a rollback type and a rollback node.

In a possible implementation, the fallback type configuration element may be an input box, a selection box, or the like, and the fallback node configuration element may be an input box, a selection box, or the like.

The user can initiate the flow definition request through the preset flow definition request operation, the terminal outputs a flow definition interface through the display device after receiving the flow definition request, the user can intuitively display the approval flow chart drawing effect through the flow chart drawing area of the flow definition interface, and the user can intuitively display the node attribute configuration information to be configured and configured through the node attribute configuration area.

Step B20, responding to a preset first operation of the flow definition interface, and generating a target parallel gateway element and a first branch node element connected with the target parallel gateway element on the flow chart drawing area;

The first operation is an operation of drawing the target parallel gateway element and connecting multiple branch node elements of the target parallel gateway element, which may be an operation mode of selecting, dragging, and the like, and may specifically be set according to actual needs, which is not limited in this embodiment. The parallel gateway element can be branched to form a plurality of branch paths, and the branch paths are connected with the branch nodes, wherein the first branch node is one of a plurality of branch nodes corresponding to the target parallel gateway, and is positioned on the branch path of the target parallel gateway and connected with the target parallel gateway element.

For example, the user may first draw the target parallel gateway element and the first branch node element on the flow chart drawing area, that is, perform the preset first operation, and after detecting the preset first operation for the flow defining interface, the terminal generates the target parallel gateway element and a plurality of branch node elements connected to the target parallel gateway element on the flow chart drawing area, where the plurality of branch node elements includes the first branch node element.

Step B30, in the case that the first branch node element is determined to be in the selected state, generating the fallback type configuration information of the first branch node in response to a preset second operation for the fallback type configuration element, and generating the fallback node configuration information of the first branch node in response to a preset third operation for the fallback node configuration element.

The second preset operation refers to an operation of inputting the configuration information of the fallback type, and may be an operation manner of manual input, selection input, and the like, and may specifically be set according to actual needs, which is not limited in this embodiment. The third preset operation refers to an operation of inputting configuration information of the fallback node, and may be an operation manner of manual input, selection input, and the like, and may specifically be set according to actual needs, which is not limited in this embodiment.

The method includes the steps that after a target parallel gateway element and branch node elements are generated, a user can select a first branch node element from the branch node elements in a clicking and selecting mode, after detecting that the user selects the first branch node element, a terminal sets the state of the first branch node element to be a selected state, further, node attribute information corresponding to the first branch node element can be filled into a node attribute configuration area to obtain a current node attribute configuration area corresponding to the first branch node element, further, the current node attribute configuration area is output and displayed through a display device, wherein the current node attribute configuration area contains a rollback type configuration element and a rollback node configuration element, and it can be understood that for any configuration element in the node attribute configuration area, if corresponding information is set currently, corresponding information can be displayed in the area corresponding to the configuration element in the current node attribute configuration area, and if any information is not set currently, blank or prompt information to be input is displayed in the area corresponding to the configuration element in the current node attribute configuration area so as to remind the user to configure; furthermore, the user may input the fallback type configuration information through the fallback type configuration element, that is, perform a preset second operation and input the fallback node configuration information through the fallback node configuration element, that is, perform a preset third operation, after detecting the preset second operation, the terminal may obtain the fallback type configuration information input by the user, update the fallback type configuration element in the current node attribute configuration area, and after detecting the preset third operation, the terminal may obtain the fallback node configuration information input by the user, and update the fallback node configuration element in the current node attribute configuration area.

In a possible implementation manner, the rollback type configuration element may be a selection box, that is, it is defined in advance for different rollback types, and when defining the flow, only the corresponding rollback type needs to be selected according to the service requirement, without setting a specific rollback attribute, rollback path or the like manually each time. The flow definition operation is simplified, and the flow definition efficiency is improved.

In a possible implementation manner, the configuration information of the rollback node may specify the target rollback node, in this case, when the first branch node rollbacks the approval process in actual operation, the first branch node does not need to select the target rollback node, and only needs to initiate a rollback request of the approval process, so that the approval process can be rolled back to the target rollback node.

In a possible implementation manner, the rollback node configuration information may set a rollback node range, in which case, when the first branch node rollbacks the actual operation approval process, the first branch node may select a target rollback node from the rollback node range, so that it is beneficial to issue different rollback rights for different nodes, and ensure orderly progress of the rollback approval process.

In this embodiment, by means of dynamic change of the node attribute configuration area along with the selected state of the node element, after a user selects any node, the attribute configuration element corresponding to the node may be intuitively displayed in the node attribute configuration area, and node attribute configuration information of a node that is not selected by the user may not need to be displayed, so that the display space of an interface is saved, so that node attribute information of the node selected by the user may have enough space to be clearly displayed, and thus, the user may perform configuration operation of the node attribute more simply and rapidly.

In an exemplary embodiment, referring to fig. 3, fig. 3 is a schematic diagram of a flow definition interface in this embodiment. As shown in fig. 3, the flow definition interface includes a toolbar area 102, a flow diagram drawing area 104, and a node attribute configuration area 106. Firstly, a user needs to draw an approval flow chart in a flow chart drawing area, and a non-cooperative rollback function can be set for a branch node under the condition that the user draws the parallel gateway and the branch node corresponding to the parallel gateway. In the flowchart drawing area 104 shown in fig. 3, the user draws an approval flowchart with a parallel gateway, and after the approval flowchart flows from the node a through the parallel gateway and branches, the approval flowchart flows through the nodes B1, B2 and B3 simultaneously, and after the approval process converges, the approval flowchart flows to the node C, and after the user selects any node, the node attribute configuration area 106 displays node attribute information of the node, for example, if the user selects the node B1, the node attribute configuration area 106 displays node attribute information of the node B1. The node attribute configuration area 106 includes a task tab page, a rollback setting tab page and an extended attribute tab page, a user clicks the task tab page, so that the basic information such as the name of a node, an approver and the like can be set, and the user clicks the rollback setting tab page, so that the rollback related information of an approval process can be set, and the classified display of the node attribute elements is realized, so that the classified ordered display is realized, and the defect that a large number of node attribute elements of different types are displayed together, so that the display space of each node attribute element is small and inconvenient to view and search is overcome. The extended attribute tag page is shown in fig. 4, where the extended attribute tag page includes an edit button corresponding to a system built-in extended attribute list, a user clicks the edit button, and the terminal outputs the system built-in extended attribute list to allow the user to select and set extended attribute configuration information, where the extended attribute list includes rollback type configuration information, the user may select a square on the non-cooperative rollback left side of sequence number 1, add a non-cooperative rollback extended attribute to a node, and may select an attribute value of the non-cooperative rollback extended attribute through a drop-down frame on the non-cooperative rollback right side, if the user selects true, generate rollback type configuration information of the non-cooperative rollback, and if the user selects false, generate rollback type configuration information of the cooperative rollback. Thus, node attribute configuration can be simply, conveniently and efficiently realized.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides an approval process rollback device for realizing the above-mentioned approval process rollback method. The implementation of the solution to the problem provided by the device is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the approval process rollback device provided below may refer to the limitation of the approval process rollback method hereinabove, and will not be described herein.

In an exemplary embodiment, as shown in fig. 5, there is provided an approval process rollback apparatus, including: an acquisition module 202 and a non-cooperative rollback module 204, wherein:

An obtaining module 202, configured to obtain, after receiving an approval process rollback request sent by the first branch node, rollback configuration information of the first branch node, where the rollback configuration information includes rollback type configuration information and rollback node configuration information;

and the non-cooperative fallback module 204 is configured to, if it is determined that the first branch node triggers a non-cooperative fallback event according to the fallback type configuration information, non-cooperatively fallback the approval process to a target fallback node corresponding to the fallback node configuration information, where, in a case that the first branch node does not perform non-cooperative fallback, the approval process events of the first branch node and each of the second branch nodes do not affect each other.

In an exemplary embodiment, the approval process rollback apparatus further includes a circulation module, and after the non-cooperative rollback of the approval process to the target rollback node corresponding to the rollback node configuration information, the circulation module is configured to:

In one exemplary embodiment, the circulation module is further configured to:

In an exemplary embodiment, the approval process rollback apparatus further includes a cooperative rollback module, and after the obtaining the rollback configuration information of the first branch node, the cooperative rollback module is configured to:

In an exemplary embodiment, the target fallback node includes a plurality of approval units, and the non-cooperative fallback module 204 is further configured to:

In an exemplary embodiment, the approval process rollback apparatus further includes a configuration module, before the obtaining rollback configuration information of the first branch node, the configuration module is configured to:

All or part of the modules in the examination and approval process rollback device can be realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In an exemplary embodiment, a computer device, which may be a terminal, is provided, and an internal structure diagram thereof may be as shown in fig. 6. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The Communication interface of the computer device is used for conducting wired or wireless Communication with an external terminal, and the wireless Communication can be realized through WIFI, a mobile cellular network, near field Communication (NEAR FIELD Communication) or other technologies. The computer program, when executed by a processor, implements an approval process rollback method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structure shown in FIG. 6 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are both information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to meet the related regulations.

Those skilled in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by instructing the associated hardware by a computer program stored on a non-transitory computer-readable storage medium, which when executed may comprise the above-described method embodiments. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile memory and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (RESISTIVE RANDOM ACCESS MEMORY, reRAM), magneto-resistive Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computation, an artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) processor, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the present application.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. The method for returning the approval process is characterized in that a circulation path of the approval process comprises a target parallel gateway, a first branch node and at least one second branch node, wherein the first branch node and the at least one second branch node are connected with the target parallel gateway, and the method comprises the following steps:

2. The method of claim 1, wherein after the non-cooperative rollback of the approval process to the target rollback node corresponding to the rollback node configuration information, the method further comprises:

3. The method of claim 2, wherein after determining that the approval process flows again from the target fallback node to the target parallel gateway, the flowing the approval process from the target parallel gateway to the first branch node comprises:

4. The method of claim 1, wherein after the obtaining the fallback configuration information of the first branch node, the method further comprises:

5. The method of claim 1, wherein the target fallback node includes a plurality of approval units, and the non-cooperative fallback of the approval process to the target fallback node corresponding to the fallback node configuration information includes:

6. The method according to any one of claims 1 to 5, wherein before the obtaining the fallback configuration information of the first branch node, the method further comprises:

7. An approval process rollback device, wherein a circulation path of the approval process includes a target parallel gateway, and a first branch node and at least one second branch node connected with the target parallel gateway, the device includes:

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.