KR102261064B1 - workflow based business process processing system - Google Patents

Abstract

A workflow-based business automation system using business process management (BPM) is disclosed. Based on the structured workflow model, the process progress is controlled by calculating the trigger condition of the event attached to the flow element as state information. A save point is defined among the flow elements of the workflow model. When the process starts, state information is saved for each savepoint. When a rollback instruction is input to a specific save point, the state information of the process is changed to the state information saved at that save point.

Description

Workflow-based business automation system {workflow based business process processing system}

Disclosed are computing technologies, particularly those for automating business processes.

As BPM (Business Process Management) technology has been introduced into corporate business processing systems, companies are seeking to improve business efficiency through BPM-based management. BPM technology models the business process of an enterprise as a structured workflow. The elements of this structured workflow model include swimlane objects that represent participants in a process, flow elements that are interconnected to form a business workflow, and connections that connect them. It includes connecting objects and data required or generated as a result of executing business processes.

A swimlane object has pools and lanes. In a pool, there is a workflow that consists of flow elements that are processed by that participant. When a pool represents a tissue, lanes may be included in that pool to represent sub-organisms.

Flow elements include activities, events, and gateways. The activity element includes a task that defines a basic task that is no longer indivisible, and a sub-process that can be divided into a plurality of tasks. Events contain execution conditions called triggers and can be attached to activities or gateways. A gateway represents a branch or focus in business process modeling.

A connection object has a sequence flow and a message flow. A sequence flow connects flow elements. Message flows represent communication between pools. In addition, there is an attribute association in the connection object.

When processing a task based on this workflow model, the process progresses according to the passage of time. However, in the actual work process, there are cases where it is necessary to go back to a specific past point in the process of work. Due to the nature of a company's diverse business, it is difficult for all processes to proceed only according to a predefined procedure, and various exceptions may occur. Compensation and cancellation techniques can be used to handle this situation based on the workflow model. Compensation is to compensate for the problems that have arisen by mobilizing other methods. For example, if an error occurs, you can log that error and provide a way to reprocess it later. Cancel is a method of ignoring the corresponding operation and processing it as if it did not exist.

However, in all of these methods, changes are made to the original process, so it is impossible to completely roll back to a specific point in time.

Another way is to completely terminate the process, create a new copy process, and force the same process to proceed from the beginning until the point where you want to go back. In this method, there are problems such as loss of consistency between the original process and the copy process, and falsification of work processing logs and various business states.

The purpose of the proposed invention is to propose a technique for solving an exception that is not defined in advance in a workflow model-based work automation system.

Furthermore, the proposed invention has another object to handle exceptional situations that occur while avoiding redundant input of time and cost in business processing.

Furthermore, the proposed invention has another purpose to handle the exception that occurred without causing contradiction or failure in the interface with other systems.

According to an aspect, the progress of a process is controlled by calculating a trigger condition of an event attached to a flow element as state information based on a structured workflow model. A save point is defined among the flow elements of the workflow model. When the process starts, state information is saved for each savepoint. When a rollback instruction is input to a specific save point, the state information of the process is changed to the state information saved at that save point.

According to a further aspect, the storage point may include an activity among flow elements and a gateway. Furthermore, the state information may include process meta information, activity meta information, and gateway meta information.

According to a further aspect, the state information stored in the process may be deleted after the process is terminated.

According to the proposed invention, as it is easily possible to return to a specific point in time during the progress of the process, the range of applicable tasks in the workflow model-based task automation system can be expanded.

1 is a block diagram illustrating the configuration of a work automation system according to an embodiment.
2 shows an exemplary business process modeling for explaining the proposed invention.
3 is a flowchart illustrating a configuration of a workflow-based work processing method according to an embodiment.

The foregoing and additional aspects are embodied through the embodiments described with reference to the accompanying drawings. It is understood that various combinations of elements of each of the embodiments are possible as long as there is no contradiction between them or other references. Hereinafter, these aspects will be described in detail through embodiments described with reference to the accompanying drawings.

1 is a block diagram illustrating the configuration of a work automation system according to an embodiment. The illustrated business automation system may be implemented as a computer and a program running on the computer. The work automation system can be implemented by a plurality of computers by dividing the related functions. In addition, it can be implemented as a plurality of programs divided by function.

As shown, the work automation system according to an embodiment includes a workflow modeling database 120 , a manager interface 70 , and a process execution control unit 110 . Each block in the drawing may be a functional unit of a computer program. Each block may be written as one subroutine of a program, or may be implemented with a plurality of subroutines or a plurality of program modules.

The workflow modeling database 120 manages a structured workflow model. The manager interface 70 provides system information to the manager and receives instructions. The manager interface 70 provides information such as a calculation result of an ongoing system through an output form of the work automation system on the display screen, and receives an operation instruction from the manager through an input device.

The process execution control unit 110 controls the progress of the process by calculating a trigger condition of an event attached to a flow element as state information with reference to a workflow modeling database. When a trigger condition of a start event of a specific process is satisfied, the process execution control unit starts execution of the corresponding process. The execution subject of the swimlane to which the process belongs is determined by referring to the workflow modeling database, and the execution of the flow elements belonging to the swimlane proceeds according to the structure. Each activity or intermediate event attached to the gateway is checked, and the trigger condition is calculated with the status information. The flow element to be executed next is determined according to the result of the trigger condition. In this way, the execution of the flow elements is controlled. When the trigger condition of the attached end event is satisfied in the last flow element, the process is terminated.

In order to process an activity among flow elements, the process execution control unit 110 may be linked with the business processing unit 30 . The business processing unit 30 is a business processing system for processing a business corresponding to an activity, and may be a part of the proposed invention or an external system. The business processing unit 30 stores results such as documents generated as a result of processing the corresponding activity in the business database 50 .

The work automation system may further include a workflow editing unit 170 . The workflow editing unit 170 supports to modify an existing workflow stored in the workflow modeling database 120 through the manager interface 70 or to create a new workflow. Commercially available tools that support drawing a workflow based on BPM (Business Process Model) are known.

According to an aspect, the work automation system according to an embodiment may further include a state backup unit 130 and a revert processing unit 150 . The state backup unit 130 stores state information for each process at each save point of the flow element for which the process execution control unit 110 controls the progress. In the illustrated embodiment, state information is stored in state backup memory 140, which is a permanent memory. State information of a plurality of processes being executed is stored in the state backup memory 140 . The save point refers to a flow element in which the state backup unit 130 backs up information necessary for process progress control.

According to another aspect, the storage point may include an activity among flow elements and a gateway. An activity refers to an activity of the smallest unit (atomic) that is either fully performed or not performed at all. A gateway indicates various alternate flows or simultaneous flows of a process, and controls the division of processes or the re-merging of divided flows. These flow elements determine the next flow element to proceed by calculating the trigger condition of the event attached to that flow element.

State information is the input of these trigger conditions. In the place where the save point is designated, the state information of the process at the moment the relevant activity is executed is extracted as if taking a snapshot and recorded in the permanent recording device. The stored state information records all necessary state information to enable the process to proceed without any additional information when the process proceeds again at the corresponding save point. Here, the business results managed by the business processing unit 30, that is, those called business data in business process modeling, and state information should be clearly distinguished. The business data means a document or form generated as a result of business processing, and is a product of the business processing unit 30, and the status information is information temporarily maintained by the process execution control unit 110 to control the execution of a specific process. In general, it is temporary information that is created for every activity as the process progresses, and then deleted when moving on to the next activity.

According to a further aspect, the state information may include process meta information and gateway meta information. The process meta information may include a process identifier (ID), various timestamps including a process start date, and an activity internal variable value. The gateway meta information may include a gateway identifier (ID), called action information, branch trigger conditions and input values, and the like.

In response to an instruction from the manager interface 70 , the rollback processing unit 150 changes the state information of the process execution controller 110 to the state information stored in the rollback instruction storage point. At this time, if the process proceeds while reverting the process, the integrity of the process state data may be damaged, so the process is performed in a locked state. While reverting the process, the process execution control unit 110 is unable to proceed with the process. The undo process is completed, and the process execution control unit 110 controls the process to proceed again from the indicated storage point. In the rollback process, the stored state information is used to return the stored state as it is. The work results of the activities processed before the save point remain in the work database 50, and the continuity of the process is ensured.

In an embodiment, the log of the ones that have been previously carried out as activities after the storage point or the business results generated by the business processing unit 30 processing the activities may be deleted. In another embodiment, the log of those previously performed as activities after the storage point or the business results generated by the business processing unit 30 processing the activities may be maintained as they are. In this case, the process information can be managed with different identifiers for the activities that have been performed since the save point and those that have progressed before. In another embodiment, the log of those previously performed as activities after the storage point may be deleted, and business results generated by processing the activities by the business processing unit 30 may be maintained. As the aborted results are maintained, they can be used for future audits or business inspections.

According to another aspect, the process execution control unit 110 may delete the stored state information in the process after the end of the process. If the state information stored in the process is not deleted even after the process is terminated, the completely terminated process can be returned to the in-progress state. Since this is not desirable in most business situations, the state information stored in the process may be deleted after the process is terminated in consideration of the business situation.

2 shows an exemplary business process modeling for explaining the proposed invention. The illustrated business process is a product sales business process that handles order reception and delivery. When an order is received (211), an inventory check activity (213) is executed, if in stock, a shipping activity (235) is executed, followed by a payment processing activity (270). If there is no stock, if the cause check activity 250 is executed and delivery is not possible, the customer notification activity 263 is executed and then the deletion activity 265 is executed from the catalog to delete the product from the catalog, and delayed delivery is possible A customer notification activity 261 is executed.

Here, the order reception 211 indicates a start event that starts with a message trigger. Also, inventory check 213 , shipping 235 , payment processing 270 , cause check 250 , notification 261 , notification 263 , and delete from catalog 265 are all activities. In addition, the stock determination 230 indicates a gateway. Arrows connecting activities and gateways are all connecting objects. Also attached to the cause check activity 250 are the non-delivery event 251 and the delayed delivery event 253 .

In FIG. 1 , when an order message is received and a start event occurs, the process execution control unit 110 starts from the order reception event 211 and executes each flow element along the connection object. Automation tools related to the activities are requested to the task processing unit 30 and provided to the corresponding participants (participants), and the activity of the process is performed. At this time, the state backup unit 130 stores state information at a storage point among the respective flow elements. In the illustrated embodiment, inventory check (213), delivery (235), payment processing (270), cause check (250), notification (261), notification (263), delete from catalog (265) activities and stock determination (230) A gateway may be a save point. For example, the gateway 230 may store the input of the inventory check activity 213 result trigger condition in the current business process, and identifiers of activities to be executed for each result value of the trigger condition.

For example, when the process is in progress, the product that has been ordered is out of stock, and the delayed delivery event 253 is executed in the cause check activity 250 and the notification activity 261 is processed. In this case, the remaining notification activity 261 of processing the product delayed may be continued, but an instruction to return to the inventory check activity 213 may be given. In this case, the order receipt event cannot happen again, so the revert processing unit 1500 executes the revert process to the inventory check activity 213 so that the process proceeds again from there.

3 is a flowchart illustrating a configuration of a workflow-based work processing method according to an embodiment. As shown, the workflow-based business processing method according to an aspect includes a flow element execution control step 310, a state information storage step 320, a revert instruction input step 330, and a revert processing step ( 350). In the flow element execution control step 310, the computing device refers to the workflow modeling database and inputs state information to an event attached to the flow element to calculate a trigger condition, and then the flow to be executed. determine the elements. Here, the status information may include process meta information and gateway meta information.

In the state information storage step 320, the computing device stores the current state information in the permanent memory in association with the corresponding flow element of the corresponding process. According to a further aspect, the storage point may include an activity among flow elements and a gateway. In step 330 of inputting the reverting instruction, the computing device checks whether a reverting instruction from the administrator interface to the storage point is input. When the undo instruction is input, the computing device reads the state information stored in the corresponding storage point from the permanent memory and loads it as the current state information in the undo processing step 350 . After that, it returns to the flow element execution control step 310 .

If the revert instruction is not input, the computing device checks whether the process has ended, that is, an end event has occurred ( 370 ). If the process has not ended, it returns to the flow element execution control step 310 to execute the next flow element. Since the processing contents of steps 310 , 320 , 330 , and 350 have been described with reference to FIG. 1 , a detailed description thereof will be omitted.

According to an additional aspect, the workflow-based business processing method may further include a state information deletion step 390 . If the process is terminated in step 370, the computing device deletes the state information stored in the process in step 390 of deleting state information.

Although the present invention has been described above with reference to the accompanying drawings, the present invention is not limited thereto, and it should be construed to encompass various modifications that can be apparent from those skilled in the art. The claims are intended to cover such modifications.

10: control unit 30: business processing unit
50: business database 70: administrator interface
110: process execution control unit 120: workflow modeling database
130: state backup unit 140: state backup database 140
150: undo processing unit 170: workflow editing unit

Claims (8)

a workflow modeling database that manages a structured workflow model;
an administrator interface that provides system information to an administrator and receives instructions;
By referring to the workflow modeling database, the trigger condition of the event attached to the flow element is calculated as state information, and the flow element to be executed next is determined according to the result value of the trigger condition to proceed with the process. Process execution control unit to control;
A business automation system comprising:
a state backup unit for storing state information for each process at each save point of a flow element for which the process execution control unit controls progress;
a rollback processing unit that, in response to an instruction from the manager interface, changes the state information of the process execution control unit to the state information stored at the storage point instructed to roll back;
A workflow-based business automation system that further includes.
The system according to claim 1, wherein the storage point includes an activity among flow elements and a gateway.
The system of claim 2, wherein the status information includes process meta information and gateway meta information.
The system of claim 1, wherein the process execution control unit deletes the state information stored in the process after the process is terminated. A workflow-based business processing method implemented with program instructions executed on at least one computer, the method comprising:
A flow that refers to a workflow modeling database and calculates a trigger condition by inputting status information to an event attached to a flow element, and determines the next flow element to be executed according to the result value of the trigger condition element execution control step;
a state information storage step of storing the current state information in a permanent memory in association with a corresponding flow element of the corresponding process;
a return instruction input step of receiving an instruction to return to the save point from the manager interface;
a reverting processing step of reading the state information stored in the storage point from the permanent memory and returning to the flow element execution control step as the current state information;
A workflow-based business processing method that includes.
The method of claim 5 , wherein the storage point includes an activity among flow elements and a gateway.
The method of claim 6 , wherein the status information includes process meta information and gateway meta information. 6. The method of claim 5, wherein the method comprises:
When the execution of the corresponding process is terminated, a state information deletion step of deleting the state information stored in the process; a workflow-based business processing method further comprising a.

Images