CN112258139A - Method and device for multi-layer gateway rollback - Google Patents
Method and device for multi-layer gateway rollback Download PDFInfo
- Publication number
- CN112258139A CN112258139A CN202010967861.2A CN202010967861A CN112258139A CN 112258139 A CN112258139 A CN 112258139A CN 202010967861 A CN202010967861 A CN 202010967861A CN 112258139 A CN112258139 A CN 112258139A
- Authority
- CN
- China
- Prior art keywords
- gateway
- fallback
- activity
- path
- rollback
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
Abstract
The invention relates to a method and a device for gateway multilayer rollback, belongs to process modeling and operation, and solves the problems that the existing process engine defaults to rollback and needs to draw rollback connecting lines and does not process other matters. The method for gateway multi-layer rollback comprises the following steps: checking whether parameters exist, wherein the parameters comprise a task to be rolled back, a rolling back target activity and a participant; acquiring an effective execution path of the flow; checking a rollback mode, wherein the rollback mode is a cross-link rollback mode or an on-demand rollback mode; collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and when it is checked that the fallback target activity is within the range of the fallback activity, fallback to the fallback target activity and compensating for the service activity. In the modeling period, backspacing does not need to draw backspacing connecting lines, and when backspacing operation is performed, a user can select nodes on a walking flow path to perform backspacing operation, and flow business operation is convenient and fast to operate.
Description
Technical Field
The invention relates to the technical field of process modeling and operation, in particular to a method and a device for gateway multilayer rollback.
Background
In any link of the process running of different business systems, business operation errors may occur, and after subsequent approval or business inspection is found, items need to be returned to the error link for processing. The flow engine defaults to rollback and needs to draw a rollback connection. Because the connecting line needs to be drawn in a backspace manner, basically every link needs to be drawn, which increases the drawing workload and also leads to greatly reduced flow readability.
In addition, in a scenario where multiple paths and parallel gateways are one-to-many, the flow engine defaults to not processing other items. Therefore, when the parallel and multi-way gateways exit from the gateways, the process engine does not process other items by default, which may cause inconsistency between the approved service information and the information that is approved last.
Disclosure of Invention
In view of the foregoing analysis, embodiments of the present invention are directed to a method and an apparatus for gateway multi-layer fallback, so as to solve the problem that the existing flow engine default fallback requires drawing a fallback connection and does not handle other issues.
In one aspect, an embodiment of the present invention provides a method for multi-layer gateway fallback, including: checking whether parameters exist, wherein the parameters comprise a task to be rolled back, a rolling back target activity and a participant; acquiring an effective execution path of the flow; checking a rollback mode, wherein the rollback mode is a trans-ring rollback or an on-demand rollback; collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and when it is checked that the fallback target activity is within the range of the fallback activity, fallback to the fallback target activity and compensating for the service activity.
The beneficial effects of the above technical scheme are as follows: according to the method for the multilayer gateway backspacing, backspacing does not need to draw backspacing connecting lines in the modeling period, and the flow chart is drawn simply and clearly; and during the rollback operation, the user can select the nodes on the walking flow path to perform the rollback operation, and the flow service operation is convenient and fast.
Based on a further improvement of the above method, when the fallback mode is inter-ring fallback, collecting information of fallback activities based on the execution path further includes: look for human activities that can be rolled back and service activities that are passed through in the execution path.
Based on the further improvement of the above method, finding a fallback-able manual activity and a passed service activity in the execution path further comprises: traversing the execution path from the to-be-handled event to the starting node direction; when the manual activity or the service activity is traversed, collecting the manual activity or the service activity and recording the manual activity or the service activity as the backspacing activity; when traversing to the parallel starting gateway or the multi-path starting gateway, the traversing is terminated; when traversing to the parallel ending gateway or the multi-path ending gateway, skipping the internal paired gateways and continuing to traverse forwards; and when traversing to the start node, the traversing terminates.
Based on a further improvement of the above method, when traversing to a parallel ending gateway or a multi-path ending gateway, skipping interior paired gateways comprises: when traversing to a parallel ending gateway or a multi-path ending gateway, setting a non-collection manual activity mark, and not recording the manual activity and the service activity as the rollback activity; and continuously traversing to a parallel start gateway or a multi-path start gateway paired with the parallel end gateway or the multi-path end gateway, and removing the non-collection artificial live mark.
Based on a further improvement of the above method, when the fallback mode is an on-demand fallback mode and the to-do activities are a plurality of to-do activities, collecting information of the fallback activities based on the execution path further includes: searching for retrogradable artificial activities and service activities passing through the first execution path along the first execution path where the first to-be-processed activity is located in the same mode of cross-link retrogradion; and searching the to-do events needing to be terminated along other execution paths where the other to-do events are located.
Based on the further improvement of the method, finding the to-be-handled event to be terminated along the other execution path where the other to-be-handled event is located further includes: traversing the other execution paths in a direction from the fallback target activity to an end node; when the to-do activity or the service activity is traversed, collecting the to-do activity or the service activity and recording the to-do activity or the service activity as the backspacing activity; when traversing to a parallel start gateway or a multi-path start gateway and a parallel end gateway or a multi-path end gateway of an internal paired gateway, traversing the internal paired gateway and continuously traversing backwards; and if the traversal node has no execution path, the traversal is terminated.
Based on a further improvement of the above method, traversing an interior pair of gateways and continuing the backward traversal when traversing to a parallel start gateway or a multi-way start gateway and a parallel end gateway or a multi-way end gateway of the interior pair of gateways further comprises: when traversing to a parallel start gateway or a multi-path start gateway, recording the parallel start gateway or the multi-path start gateway, counting the number of the parallel start gateway or the multi-path start gateway, and traversing backwards; when traversing to a parallel ending gateway or a multi-path ending gateway, if one or more recorded parallel starting gateways or multi-path starting gateways exist and the type of the last recorded parallel starting gateway or multi-path starting gateway is consistent with that of the parallel ending gateway or the multi-path ending gateway, removing the last recorded parallel starting gateway or multi-path starting gateway, reducing the number of the last recorded parallel starting gateway or multi-path starting gateway by 1, and continuing traversing backwards.
Based on the further improvement of the method, if the type of the parallel start gateway or the multi-path start gateway recorded last is consistent with the type of the parallel end gateway or the multi-path end gateway, the parallel start gateway or the multi-path start gateway and the parallel end gateway or the multi-path end gateway are internal paired gateways.
Based on the further improvement of the method, after the to-do-events needing to be terminated are searched, the collected to-do-events are further terminated.
In another aspect, an embodiment of the present invention provides a device for multi-layer gateway fallback, including: the system comprises a checking module, a judging module and a judging module, wherein the checking module is used for checking whether parameters exist, and the parameters comprise a task to be rolled back, a rolling back target activity and participants; the execution path acquisition module is used for acquiring an effective execution path of the flow; a rollback mode checking module, configured to check a rollback mode, where the rollback mode is a cross-ring rollback or an on-demand rollback; a fallback activity collection module for collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and a rollback and compensation module for performing rollback from the current to-do activity and service activity compensation when it is checked that the rollback target activity is within the range of the rollback activity.
Compared with the prior art, the invention can realize at least one of the following beneficial effects:
1. when the fallback mode is cross-ring fallback, the traversal is terminated when traversing to the parallel start gateway or the multi-path start gateway, and the inner paired gateways are skipped when traversing to the parallel end gateway or the multi-path end gateway, the cross-ring fallback can be allowed, but the fallback in the multi-branch gateway is not allowed to be out of the gateway.
2. In the modeling period, backspacing does not need to draw backspacing connecting lines, and the flow chart is simple and clear to draw;
3. the method comprises the steps of backspacing operation, wherein a user can select a node on a walking flow path to perform backspacing operation, and the flow service operation is convenient and fast; and
4. in the operation period, if unprocessed flow items exist in the backspacing link, the incomplete flow items can be automatically terminated, and the incomplete flow items can be regenerated when being transmitted again, so that the consistency of the approved service is ensured.
In the invention, the technical schemes can be combined with each other to realize more preferable combination schemes. Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and drawings.
Drawings
The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, wherein like reference numerals are used to designate like parts throughout.
Fig. 1 is a flowchart of a method for gateway multi-layer fallback according to an embodiment of the present invention.
Fig. 2 is a specific flowchart of a method for multi-layer gateway fallback according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of a backtracking approval process path of a standard procurement process according to an embodiment of the invention.
Fig. 4 is a diagram illustrating a rollback success and a termination process of a standard procurement process according to an embodiment of the invention.
FIG. 5 is a diagram illustrating a new approval event resulting from the re-delivery of a standard procurement process according to an embodiment of the invention.
Fig. 6 is a block diagram of an apparatus for gateway multi-layer fallback according to an embodiment of the present invention.
Detailed Description
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate preferred embodiments of the invention and together with the description, serve to explain the principles of the invention and not to limit the scope of the invention.
The invention discloses a method for multi-layer rollback of a gateway. Referring to fig. 1, the method for gateway multi-layer fallback includes: step S102, checking whether parameters exist, wherein the parameters comprise a task to be rolled back, a rolling back target activity and participants; step S104, acquiring an effective execution path of the process; step S106, checking a rollback mode, wherein the rollback mode is a cross-ring rollback mode or an on-demand rollback mode; step S108, collecting information of fallback activities based on the execution path, wherein the fallback activities comprise manual activities and service activities; and a step S110 of fallback to the fallback target activity and compensating for the service activity when it is checked that the fallback target activity is within the range of the fallback activity.
Compared with the prior art, the method for gateway multilayer rollback provided by the embodiment has the advantages that during the modeling period, rollback does not need to draw rollback connecting lines, and the flow chart is simple and clear to draw; and during the rollback operation, the user can select the nodes on the walking flow path to perform the rollback operation, and the flow service operation is convenient and fast.
Hereinafter, a method of gateway multi-layer fallback will be described in detail with reference to fig. 1 to 5.
The gateway multi-layer rollback method comprises a step S102 of checking whether parameters exist, wherein the parameters comprise tasks to be rolled back, rollback target activities and participants. Specifically, it is checked whether a task to be rolled back exists, whether a rolling back target activity exists, and whether a user has a right to participate in the checking, which are called participants. For example, as shown in fig. 3, the department review link is a rollback target activity.
After checking whether the parameter exists, the process proceeds to step S104, and a valid execution path of the flow is acquired. Specifically, all valid execution paths of the instance where the query task is located do not include the execution paths that are repeatedly rolled back, i.e., the latest execution path. For example, referring to FIG. 3, the first execution path is the execution path in which the financial audit is located; the second execution path is an execution path where the fund audit is located; and the third execution path is the execution path of the purchase audit.
After obtaining the valid execution path of the flow, step S106 is entered, and a fallback mode is checked, where the fallback mode is a cross-ring fallback mode or an on-demand fallback mode. Specifically, the rollback modes set by the current task activities are acquired from the flow chart objects, and then the corresponding rollback modes are executed respectively. For example, the following three fallback modes can be set during the modeling period: only go-back links, allow cross-link back, and back on demand. Only allowing inter-ring fallback and fallback on demand are described in detail herein.
After checking the fallback mode, step S108 is entered, and information of fallback activities is collected based on the execution path, where the fallback activities include manual activities and service activities. Specifically, the rollback processing object collects rollback-capable manual activities and service activities that need compensation according to the execution path of the process instance, and different rollback processing objects collect some other information, such as pending to be terminated.
Hereinafter, for the fallback modes, which are cross-ring fallback respectively, information of the fallback activities based on the execution path collection is described in detail.
When the fallback mode is cross-ring fallback, collecting information of fallback activities based on the execution path further includes: look for human activities that can be rolled back and service activities that are traversed in the execution path. Specifically, finding fallback-able manual activities and executing the passed service activities in the path further comprises: and traversing the execution path from the to-do event to the starting node. When traversing to a manual activity or a service activity, the manual activity or the service activity is collected and recorded as a fallback activity. When traversing to the parallel start gateway or the multi-path start gateway, the traversing is terminated. When traversing to the parallel ending gateway or the multi-path ending gateway, skipping the inner paired gateways and continuing to traverse forwards. Specifically, when traversing to a parallel ending gateway or a multi-path ending gateway, setting a non-collection manual activity mark, and recording manual activity and service activity as rollback activity; and continuing to traverse to a parallel start gateway or a multi-way start gateway paired with the parallel end gateway or the multi-way end gateway, and removing the non-collection artificial live mark. When traversing to the start node, the traversal terminates.
After collecting information of the fallback activities based on the execution path, the process proceeds to step S110, and when it is checked that the fallback target activity is within the range of the fallback activity, the fallback to the fallback target activity and the service activity is compensated. Specifically, whether the rollback target activity is within the range of the rollback-capable activity is checked, service activity compensation and backlog are executed, and other processes such as termination of related backlogs are executed by different rollback processing objects.
Compared with the prior art, in the method for multi-layer gateway fallback provided by this embodiment, when the fallback mode is cross-ring fallback, traversal is terminated when traversing to a parallel start gateway or a multi-path start gateway, and when traversing to a parallel end gateway or a multi-path end gateway, an interior paired gateway is skipped, so that cross-ring fallback can be allowed, but the multi-branch gateway is not allowed to be rolled back inside and outside the gateway.
For the respective fallback modes as on-demand fallback, information of the fallback activities is collected based on the execution path for detailed description.
When the fallback mode is fallback on demand and the to-do activities are a plurality of to-do activities, collecting information of the fallback activities based on the execution path further includes: searching for retrogradable artificial activities and service activities passing through the first execution path along the first execution path where the first to-be-processed activity is located in the same mode of cross-link retrogradion; and searching the to-do events needing to be terminated along other execution paths where the other to-do events are located.
Hereinafter, the search for the retrogradable manual activity and the service activity passed through in the first execution path, and the search for the to-do activity to be terminated are respectively described in detail.
In an embodiment, finding the rollback-capable artificial activities and the passed service activities in the first execution path along the first execution path where the first to-be-processed activity is located in the same manner as the cross-ring rollback further includes: and traversing the execution path from the to-do event to the starting node. When traversing to a manual activity or a service activity, the manual activity or the service activity is collected and recorded as a fallback activity. When traversing to the parallel start gateway or the multi-path start gateway, the traversing is terminated. When traversing to the parallel ending gateway or the multi-path ending gateway, skipping the inner paired gateways and continuing to traverse forwards. Specifically, when traversing to a parallel ending gateway or a multi-path ending gateway, setting a non-collection manual activity mark, and recording manual activity and service activity as rollback activity; and continuing to traverse to a parallel start gateway or a multi-way start gateway paired with the parallel end gateway or the multi-way end gateway, and removing the non-collection artificial live mark. When traversing to the start node, the traversal terminates.
In an embodiment, the searching for the to-do event to be terminated along the other execution path where the other to-do event is located further includes: traversing other execution paths from the rollback target activity to the end node direction. Next, when traversing to a backlog event or service event, collecting the backlog event or service event and recording the backlog event. Next, when traversing to the parallel start gateway or the multi-way start gateway and the parallel end gateway or the multi-way end gateway of the interior paired gateways, traversing the interior paired gateways and continuing the backward traversal. Specifically, traversing an interior pair of gateways and continuing the backward traversal when traversing to a parallel start gateway or a multi-way start gateway and a parallel end gateway or a multi-way end gateway of the interior pair of gateways further comprises: when traversing to the parallel start gateway or the multi-path start gateway, recording the parallel start gateway or the multi-path start gateway, counting the number of the parallel start gateway or the multi-path start gateway, and continuously traversing backwards; when traversing to the parallel ending gateway or the multi-path ending gateway, if one or more recorded parallel starting gateways or multi-path starting gateways exist and the type of the last recorded parallel starting gateway or multi-path starting gateway is consistent with that of the parallel ending gateway or the multi-path ending gateway, removing the last recorded parallel starting gateway or multi-path starting gateway, reducing the number of the last recorded parallel starting gateway or multi-path starting gateway by 1, and continuing traversing backwards. And if the type of the last recorded parallel starting gateway or multi-path starting gateway is consistent with that of the parallel ending gateway or multi-path ending gateway, the parallel starting gateway or multi-path starting gateway and the parallel ending gateway or multi-path ending gateway are internal paired gateways. And finally, if the traversal node has no execution path, the traversal is terminated.
After collecting information of the fallback activities based on the execution path, the process proceeds to step S110, and when it is checked that the fallback target activity is within the range of the fallback activity, the fallback to the fallback target activity and the service activity is compensated. Specifically, whether the rollback target activity is within the rollback range of the rollback target activity is checked, then service activity compensation and backtracking to be done are executed, and the group audit is successfully backtracked to department audit from the group audit so as to terminate the group audit on the first execution path.
And after the searching for the to-do events needing to be terminated is completed, terminating the collected to-do events. In addition, other processes such as terminating the related backlog are executed by different rollback processing objects. Referring to FIG. 4, in addition, the associated to-Do activity is terminated, i.e., the funding review on the second execution path and the purchase sponsor on the third execution path are terminated.
After the collected to-do event is terminated, the new approval item is generated again. Referring to FIG. 5, the re-transfer of the generation of the new approval transaction includes a financial review on the first execution path, a funding review on the second execution path, and a procurement review on the third execution path.
Compared with the prior art, in the method for multi-layer gateway fallback provided by the embodiment, when the fallback mode is the on-demand fallback, the cross-ring fallback is allowed, and the multi-branch gateway is allowed to fall back to the outside of the gateway. After the retrogradable manual activities and the passed service activities in the first execution path are searched, the to-be-handled activities needing to be terminated are searched, the unfinished flow items are automatically terminated, and the to-be-handled activities are regenerated when being transmitted again, so that the business consistency of approval can be ensured.
And providing a flow path algorithm, supporting positioning to a backspacing link, and terminating the subsequent related unprocessed items of the backspacing link.
1. The modeling period provides for the setting of three fallback modes:
and returning only the upper link: links not allowing selection of fallback
Allowing a span link to retreat: allowing cross-ring fallback but not allowing multi-drop intra-gateway fallback outside of gateways
Backing off according to needs: allowing cross-ring rollback and allowing multi-branch intra-gateway rollback and extra-gateway rollback
2. Run-time flow path algorithm
The process engine management realizes the function of introducing configuration to the business system rule, and the configuration can realize the butt joint with the business system rule service.
3. And in the operation period, the backspacing operation interface can select a specific backspacing link according to a backspacing mode, execute backspacing and generate flow items of the backspacing link, and if relevant unprocessed items follow the backspacing link, terminate processing. When the transaction is passed again, a new approval item is generated.
Hereinafter, with reference to fig. 2, the general flow of the gateway multi-layer fallback method, the cross-ring fallback method, and the on-demand fallback method are described in detail by way of specific examples.
1. Parameter verification
And checking whether the task to be backed exists or not, checking whether the target activity and the participator exist or not, and constructing a backspacing related context such as a task object and a flow chart object after the checking is passed.
2. Obtaining efficient execution paths for process instances
All effective execution paths of the instance where the query task is located do not include the execution path of the repeated rollback, namely the latest execution path.
3. Checking rollback mode
And acquiring the backspacing mode set by the current task activity from the flow chart object, and then respectively executing the processing objects corresponding to the backspacing modes.
4. Fallback activity information collection
The rollback processing object calculates rollback-capable artificial activities and service activities that need compensation according to the execution path of the flow instance, and different rollback processing objects collect some other information, such as backlog that needs to be terminated.
5. Rollback execution
Whether the backspacing target activity is within the backspacing activity range is checked, then service activity compensation and backtracking are executed, and other processes such as related backtracking are executed by different backspacing processing objects.
First, span ring back
1. Acquiring an effective execution path of a process instance;
2. searching for retrogradable manual activities and service activities passing through in the execution path;
A. traversing an execution path from the activity to be dealt with to the direction of starting the activity;
B. if the manual activity or the service activity is traversed, collecting the manual activity or the service activity;
C. if the traversal node is a parallel or multi-path starting gateway, the traversal is terminated;
D. if traversing to the parallel ending gateway, setting a mark of not collecting manual activities, and not adding activities in the parallel gateway into the retroversion activities, removing the mark until traversing to the starting gateway, and continuing traversing;
E. if the traversal reaches the starting node, the traversal is terminated; and
F. returning the collected manual activities and service activities;
3. checking whether the rollback target activity is within the range of the artificial activity collected in the step 2, otherwise, ending the rollback; if yes, executing the process of returning to the target activity; and
4. and executing the compensation service of the service activity collected in the step 2.
Second, rollback on demand
1. Acquiring an effective execution path of a process instance;
2. searching for retrogradable manual activities and service activities passing through in the execution path;
A. traversing an execution path from the activity to be dealt with to the direction of starting the activity;
B. if the manual activity or the service activity is traversed, collecting the manual activity or the service activity;
C. if traversing to the parallel ending gateway, setting a mark of not collecting manual activities, and not adding activities in the parallel gateway into the retroversion activities, removing the mark until traversing to the starting gateway, and continuing traversing;
D. if the traversal reaches the starting node, the traversal is terminated; and
E. returning the collected manual activities and service activities;
3. searching for the to-do to be terminated: other events to be handled in the same gateway with the current event to be handled;
A. traversing an execution path from a rollback target activity to an end activity direction;
B. if the to-do event or the service event is traversed, collecting the to-do event or the service event;
C. if traversing to the parallel or multi-path starting gateway, adding the gateway into the stack A, wherein the value of the gateway is the number B of outgoing lines of the gateway, and then continuously traversing backwards;
D. if the parallel or multi-path end gateway is traversed, if the stack A is not empty, acquiring a stack top node, if the stack top node and the current traversal node are the same type gateway, subtracting 1 from the B value of the stack top node, and after subtracting 1, if the B value is 0, indicating that the stack top node passes through a paired gateway, and removing the stack top node;
E. if the traversal node has no execution path, the traversal is terminated; and
F. returning the collected to-do activities and service activities;
4. checking whether the rollback target activity is in the range of the artificial activity collected in the step 2, if not, stopping rollback, and if so, executing rollback to the target activity;
5. executing compensation service of the service activity collected in the step 2; and
6. and terminating the backlogs to be terminated collected in the step 3.
The invention discloses a gateway multi-layer rollback device. Referring to fig. 6, an apparatus of gateway multi-layer fallback includes: a checking module 602, configured to check whether parameters exist, where the parameters include a task to be rolled back, a rolling back target activity, and a participant; an execution path obtaining module 604, configured to obtain an effective execution path of the flow; a rollback mode checking module 606, configured to check a rollback mode, where the rollback mode is a cross-ring rollback or an on-demand rollback; a fallback activity collection module 608 for collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and a rollback and compensation module 610 for performing rollback from the current to-do activity and service activity compensation when it is checked that the rollback target activity is within the range of the rollback activity.
Compared with the prior art, the invention can realize at least one of the following beneficial effects:
1. when the fallback mode is cross-ring fallback, the traversal is terminated when traversing to the parallel start gateway or the multi-path start gateway, and the inner paired gateways are skipped when traversing to the parallel end gateway or the multi-path end gateway, the cross-ring fallback can be allowed, but the fallback in the multi-branch gateway is not allowed to be out of the gateway.
2. In the modeling period, backspacing does not need to draw backspacing connecting lines, and the flow chart is simple and clear to draw;
3. the method comprises the steps of backspacing operation, wherein a user can select a node on a walking flow path to perform backspacing operation, and the flow service operation is convenient and fast; and
4. in the operation period, if unprocessed flow items exist in the backspacing link, the incomplete flow items can be automatically terminated, and the incomplete flow items can be regenerated when being transmitted again, so that the consistency of the approved service is ensured.
Those skilled in the art will appreciate that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program, which is stored in a computer readable storage medium, to instruct related hardware. The computer readable storage medium is a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention.
Claims (10)
1. A method for multi-layer gateway fallback, comprising:
checking whether parameters exist, wherein the parameters comprise a task to be rolled back, a rolling back target activity and a participant;
acquiring an effective execution path of the flow;
checking a rollback mode, wherein the rollback mode is a trans-ring rollback or an on-demand rollback;
collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and
when it is checked that the fallback target activity is within the range of the fallback activity, fallback to the fallback target activity and compensating for the service activity.
2. The method for gateway multi-layer fallback according to claim 1, wherein when the fallback mode is cross-ring fallback, collecting information of fallback activities based on the execution path further comprises: look for human activities that can be rolled back and service activities that are passed through in the execution path.
3. The method for gateway multi-tier fallback according to claim 2, wherein finding fallback-able manual activities and traversed service activities in the execution path further comprises:
traversing the execution path from the to-be-handled event to the starting node direction;
when the manual activity or the service activity is traversed, collecting the manual activity or the service activity and recording the manual activity or the service activity as the backspacing activity;
when traversing to the parallel starting gateway or the multi-path starting gateway, the traversing is terminated;
when traversing to the parallel ending gateway or the multi-path ending gateway, skipping the internal paired gateways and continuing to traverse forwards; and
when traversing to the start node, the traversal terminates.
4. The method of gateway multi-tier fallback according to claim 3, wherein skipping inner paired gateways when traversing to a parallel end gateway or a multi-way end gateway comprises:
when traversing to a parallel ending gateway or a multi-path ending gateway, setting a non-collection manual activity mark, and not recording the manual activity and the service activity as the rollback activity; and
and continuously traversing to a parallel start gateway or a multi-path start gateway paired with the parallel end gateway or the multi-path end gateway, and removing the non-collection artificial live mark.
5. The method of gateway multi-tier fallback of claim 4, wherein when the fallback mode is on-demand fallback and the to-do activity is a plurality of to-do activities, collecting information of fallback activities based on the execution path further comprises:
searching for retrogradable artificial activities and service activities passing through the first execution path along the first execution path where the first to-be-processed activity is located in the same mode of cross-link retrogradion; and
and searching the to-do events needing to be terminated along other execution paths where the other to-do events are located.
6. The method for gateway multi-layer fallback according to claim 5, wherein finding the to-do-event to be terminated along the other execution path where the other to-do-event is located further comprises:
traversing the other execution paths in a direction from the fallback target activity to an end node;
when the to-do activity or the service activity is traversed, collecting the to-do activity or the service activity and recording the to-do activity or the service activity as the backspacing activity;
when traversing to a parallel start gateway or a multi-path start gateway and a parallel end gateway or a multi-path end gateway of an internal paired gateway, traversing the internal paired gateway and continuously traversing backwards;
and if the traversal node has no execution path, the traversal is terminated.
7. The method for gateway multi-tier fallback of claim 6, wherein traversing an interior paired gateway and continuing backward traversal when traversing to a parallel start gateway or a multi-way start gateway and a parallel end gateway or a multi-way end gateway of the interior paired gateway further comprises:
when traversing to a parallel start gateway or a multi-path start gateway, recording the parallel start gateway or the multi-path start gateway, counting the number of the parallel start gateway or the multi-path start gateway, and traversing backwards;
when traversing to a parallel ending gateway or a multi-path ending gateway, if one or more recorded parallel starting gateways or multi-path starting gateways exist and the type of the last recorded parallel starting gateway or multi-path starting gateway is consistent with that of the parallel ending gateway or the multi-path ending gateway, removing the last recorded parallel starting gateway or multi-path starting gateway, reducing the number of the last recorded parallel starting gateway or multi-path starting gateway by 1, and continuing traversing backwards.
8. The method for gateway multi-layer fallback according to claim 7, wherein if the type of the last recorded concurrent start gateway or multi-way start gateway is the same as the type of the concurrent end gateway or multi-way end gateway, the concurrent start gateway or the multi-way start gateway and the concurrent end gateway or the multi-way end gateway are internal paired gateways.
9. The gateway multi-layer fallback method as claimed in claim 5, further comprising terminating the collected pending events after searching for the pending events to be terminated.
10. An apparatus for multi-layer fallback for a gateway, comprising:
the system comprises a checking module, a judging module and a judging module, wherein the checking module is used for checking whether parameters exist, and the parameters comprise a task to be rolled back, a rolling back target activity and participants;
the execution path acquisition module is used for acquiring an effective execution path of the flow;
a rollback mode checking module, configured to check a rollback mode, where the rollback mode is a cross-ring rollback or an on-demand rollback;
a fallback activity collection module for collecting information of fallback activities based on the execution path, wherein the fallback activities include manual activities and service activities; and
and the backspacing and compensating module is used for executing backspacing and service activity compensation from the current to-do activity when the backspacing target activity is checked to be in the range of the backspacing activity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010967861.2A CN112258139A (en) | 2020-09-15 | 2020-09-15 | Method and device for multi-layer gateway rollback |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010967861.2A CN112258139A (en) | 2020-09-15 | 2020-09-15 | Method and device for multi-layer gateway rollback |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112258139A true CN112258139A (en) | 2021-01-22 |
Family
ID=74232522
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010967861.2A Pending CN112258139A (en) | 2020-09-15 | 2020-09-15 | Method and device for multi-layer gateway rollback |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112258139A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020180810A1 (en) * | 2001-05-30 | 2002-12-05 | International Business Machines Corporation | Compensation of workflow applications |
| CN101615269A (en) * | 2009-08-11 | 2009-12-30 | 用友软件股份有限公司 | Backing method in a kind of Workflow Management System and device |
| CN110619473A (en) * | 2019-09-19 | 2019-12-27 | 福建博思软件股份有限公司 | Method for realizing reverse circulation based on Activiti workflow |
-
2020
- 2020-09-15 CN CN202010967861.2A patent/CN112258139A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020180810A1 (en) * | 2001-05-30 | 2002-12-05 | International Business Machines Corporation | Compensation of workflow applications |
| CN101615269A (en) * | 2009-08-11 | 2009-12-30 | 用友软件股份有限公司 | Backing method in a kind of Workflow Management System and device |
| CN110619473A (en) * | 2019-09-19 | 2019-12-27 | 福建博思软件股份有限公司 | Method for realizing reverse circulation based on Activiti workflow |
Non-Patent Citations (3)
| Title |
|---|
| 曹双;刘琳岚;张恒锋;: "一种多步流程回退方法的研究与实现", 计算机工程, no. 21, pages 67 - 70 * |
| 苏展等: "基于jBPM4的临时动态性需求研究", 微型机与应用, vol. 29, no. 3, pages 4 - 7 * |
| 陈佳露: "支持动态流程的工作流引擎MedicalBPM的设计与实现", 中国优秀博硕士学位论文全文数据库 信息科技辑, pages 25 - 27 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Awad et al. | Efficient compliance checking using BPMN-Q and temporal logic | |
| CN110362632B (en) | Data synchronization method, device, equipment and computer readable storage medium | |
| US7475275B2 (en) | Method for fault handling in a co-operative workflow environment | |
| Buijs et al. | Improving business process models using observed behavior | |
| van der Aalst | Distributed process discovery and conformance checking | |
| Seeliger et al. | Detecting concept drift in processes using graph metrics on process graphs | |
| US20080091486A1 (en) | Program, method, and apparatus for analyzing group work activities in a project | |
| CN108460598A (en) | A kind of real-time automation supervision reporting system based on double-strand framework block chain | |
| Genga et al. | Discovering anomalous frequent patterns from partially ordered event logs | |
| CN112559626B (en) | Synchronous method and synchronous system of DDL operation based on log analysis | |
| CN112559300B (en) | Fault cause determining system, method and device | |
| CN103678591B (en) | The automatic apparatus and method for performing multiple services bills statistical disposition | |
| CN114281877A (en) | Data management system and method | |
| CN106126634A (en) | A kind of master data duplicate removal treatment method based on live industry and system | |
| JP2000112893A (en) | System and method for overlooking activity state and recording medium recording activity state overlooking program | |
| CN110011853B (en) | Cross fault troubleshooting method and device for multiple platforms and clusters | |
| Kalinowski et al. | A computational framework for supporting software inspections | |
| CN112258139A (en) | Method and device for multi-layer gateway rollback | |
| CN111798311A (en) | Bank risk analysis library platform based on big data, building method and readable medium | |
| CN116501761A (en) | Query optimization method, device and storage medium | |
| CN102918507A (en) | Transaction processing system | |
| CN116737736A (en) | Data consistency checking and repairing method, device, equipment, medium and product | |
| CN107045466A (en) | Auditing method, the apparatus and system of business datum | |
| CN114064801A (en) | Knowledge graph-based block chain data supervision method and system and computer equipment | |
| Tsoury et al. | How well did it recover? Impact-aware conformance checking |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |