CN106528066B - A business process operation method and device - Google Patents

Abstract

The method and device for running a business process disclosed in the present application, when it is determined according to the information of the to-be-executed link in the first business process instance that a static collaboration link is preset in the to-be-executed link, it is judged whether there is a second The business process instance cooperates with the first business process instance, and if it exists, searches for the second business process instance, and executes the second business process instance, until the execution of the static collaboration link in the second process instance is completed. After that, the to-be-executed link is executed again, and if it does not exist, the to-be-executed link is executed. Based on the above method and device, if the two links of two process instances with a static collaboration relationship are to be coordinated during the operation of the business process, the two process instances will be executed dependently, and if they do not need to be coordinated, the two process instances can still be executed independently , can adapt to various application scenarios, greatly improve the user experience.

Description

A business process operation method and device

technical field

The present application relates to the technical field of business process management, and in particular, to a method and device for running a business process.

Background technique

The BPM (Business Process Management, business process management) system generally includes two aspects of business process modeling and business process driving. Among them, the business process modeling is generally in charge of the BPM Integrated Development Environment (BPM Integrated Development Environment), and the business process driving Generally by the BPM process engine (BPMEngine) is responsible. Through the BPM system, various BPM flow charts can be created for enterprises in line with their business development, which greatly facilitates enterprise management and makes great contributions to enterprise development.

Each graphic element on the BPM flow chart is generally called "link". Based on the existing BPM system, it is usually necessary to separate one link in an independent process (assuming that it is the link that initiates collaboration, named as link 1) and another independent process. A link in the process (assumed to be a coordinated link, named link 2) is strongly associated to establish cross-process collaboration. During the operation of the process, in the two interrelated links, if link 2 is not executed, link 1 will not be executed, and the independent process corresponding to link 1 will be stagnant in link 1 and cannot continue to be executed. That is, as long as cross-process collaboration is established, during the running of the process, the process that initiates the collaboration must be executed depending on the execution state of the coordinated link, and cannot be executed independently.

However, in some scenarios, such as the telecommunications field, if a user wants to buy a mobile phone, there will be an order process, a logistics process, a card opening process, a business processing process, etc. If the coordination between the logistics process and the card opening process is established, the process During operation, the card opening process can only be executed after a certain link in the logistics process is completed. However, in fact, the user can execute the card opening process alone, and the previously established cross-process collaboration will cause the card opening process to be forcibly linked to the card opening process. The logistics process, which ultimately leads to the restriction of the independent execution of the card opening process.

That is to say, the collaborative relationship between processes in the BPM system in the prior art is fixed, and during the running of the process, the processes with the collaborative relationship cannot be executed independently, and the applicability to various application scenarios is poor, which greatly affects the user experience.

SUMMARY OF THE INVENTION

The purpose of the present application is to provide a method and device for running a business process, so as to solve the problem that the collaborative relationship between the processes in the BPM system in the prior art is fixed, and during the process operation, the process with the collaborative relationship cannot be executed independently. The applicability of various application scenarios is poor, which greatly affects the user experience.

To achieve the above purpose, the application provides the following solutions:

According to a first possible implementation manner of the first aspect of the present application, the present application provides a method for running a business process, the method comprising:

Obtain the information of the links to be executed in the first business process instance;

According to the to-be-executed link information, determine whether the to-be-executed link is preset with a static collaborative link;

If the to-be-executed link is not preset with a static collaborative link, execute the to-be-executed link;

If the to-be-executed link is preset with a static coordination link, acquiring the coordination identifier of the first business process instance;

Judging, according to the collaboration identifier of the first business process instance, whether there is a second business process instance that cooperates with the first business process instance;

If there is, search for the second business process instance, and execute the second business process instance, until the static coordination link in the second business process instance is executed, and then execute the to-be-executed link;

If it does not exist, execute the to-be-executed link.

In conjunction with the second possible implementation manner of the first aspect, the method further includes:

The static collaboration relationship of the specified link in the business process definition is specified in advance through the message flow Message Flow.

With reference to the third possible implementation manner of the first aspect, the determining whether the to-be-executed link is pre-set with a static collaborative link according to the to-be-executed link information specifically includes:

Determine whether there is a Message Flow in the information of the link to be executed;

If it exists, the link to be executed is preset with a static coordination link;

If it does not exist, the to-be-executed link is not preset with a static coordination link.

With reference to the fourth possible implementation manner of the first aspect, determining whether there is a second business process instance to cooperate with the first business process instance according to the collaboration identifier of the first business process instance specifically includes:

If the collaboration identifier of the first business process instance is empty, there is no collaboration between the second business process instance and the first business process instance;

If the collaboration identifier of the first business process instance is not empty, there is a second business process instance that cooperates with the first business process instance.

With reference to the fifth possible implementation manner of the first aspect, before acquiring the information on the links to be executed in the first business process instance, the method further includes:

Parse the business process definition, and create a business process instance list according to the business process definition;

Any business process instance in the business process instance list is selected as the first business process instance.

With reference to the sixth possible implementation manner of the first aspect, the searching for the second business process instance specifically includes:

Searching for a business process instance with the same collaboration identifier as the collaboration identifier of the first business process instance from the list of business process instances as the second business process instance.

According to the first possible implementation manner of the second aspect of the present application, the present application provides an apparatus for running a business process, the apparatus comprising:

a first obtaining unit, configured to obtain information on links to be executed in the first business process instance;

a first judging unit for judging whether a link to be executed is preset with a static coordination link according to the link information to be executed; if the link to be executed is not preset with a static coordination link, trigger the second execution unit; if the link to be executed is not preset with a static coordination link If the link to be executed is preset with a static coordination link, the second acquisition unit is triggered;

a second obtaining unit, configured to obtain the collaborative identifier of the first business process instance;

a second judging unit, configured to judge whether there is a second business process instance to cooperate with the first business process instance according to the collaboration identifier of the first business process instance; if there is, trigger the first execution unit;

A first execution unit, configured to search for the second business process instance, and execute the second business process instance, until the static coordination link in the second business process instance is executed, and then execute the to-be-executed link ;

The second execution unit is configured to execute the link to be executed.

With reference to the second possible implementation manner of the second aspect, the apparatus further includes:

The pre-setting unit is used to pre-specify the static coordination relationship of the specified link in the business process definition through the message flow Message Flow.

In combination with the third possible implementation manner of the second aspect, the first judgment unit is specifically used for:

Determine whether there is a Message Flow in the information of the link to be executed;

If it exists, the link to be executed is preset with a static coordination link;

If it does not exist, the to-be-executed link is not preset with a static coordination link.

In combination with the fourth possible implementation manner of the second aspect, the second judgment unit is specifically used for:

If the collaboration identifier of the first business process instance is empty, there is no collaboration between the second business process instance and the first business process instance;

If the collaboration identifier of the first business process instance is not empty, there is a second business process instance that cooperates with the first business process instance.

With reference to the fifth possible implementation manner of the second aspect, the apparatus further includes:

a first business process instance determining unit, configured to parse the business process definition before acquiring the information on the links to be executed in the first business process instance, and create a list of business process instances according to the business process definition; select the business process Any business process instance in the process instance list is the first business process instance.

With reference to the sixth possible implementation manner of the second aspect, the first execution unit is specifically configured to:

Searching for a business process instance with the same collaboration identifier as the collaboration identifier of the first business process instance from the list of business process instances as the second business process instance.

According to the specific embodiments provided by the application, the application discloses the following technical effects:

The method and device for running a business process disclosed in the present application, when it is determined according to the information of the to-be-executed link in the first business process instance that a static collaboration link is preset in the to-be-executed link, it is judged whether there is a second The business process instance cooperates with the first business process instance, and if it exists, searches for the second business process instance, and executes the second business process instance, until the execution of the static collaboration link in the second process instance is completed. After that, the to-be-executed link is executed again, and if it does not exist, the to-be-executed link is executed. Based on the above method and device, if the two links of two process instances with a static collaboration relationship are to be coordinated during the operation of the business process, the two process instances will be executed dependently, and if they do not need to be coordinated, the two process instances can still be executed independently , can adapt to various application scenarios, greatly improve the user experience.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the accompanying drawings required in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some of the present application. In the embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative labor.

1 is a flowchart of Embodiment 1 of a business process operation method of the present application;

FIG. 2 is a flowchart of Embodiment 2 of the business process operation method of the present application;

3 is a schematic diagram of an example of a business process operation method of the present application;

FIG. 4 is a structural diagram of Embodiment 1 of a business process running device of the present application;

FIG. 5 is a structural diagram of Embodiment 2 of a business process running device of the present application;

FIG. 6 is a structural diagram of a computing node of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In order to make the above objects, features and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and specific embodiments.

Referring to FIG. 1, FIG. 1 is a flowchart of Embodiment 1 of a business process operation method provided by the present invention, and the business process operation method includes:

S101. Acquire information of links to be executed in the first business process instance.

When the link to be executed is preset with a static coordination link, the information of the link to be executed may include a static coordination identification, and the static coordination identification may specifically be a message flow.

S102. According to the information of the to-be-executed link, determine whether the to-be-executed link is preset with a static coordination link; if the to-be-executed link is not preset with a static coordination link, execute S106; if the to-be-executed link is preset with a static coordination link link, then execute S103.

S103. Acquire the collaboration identifier of the first business process instance.

S104. Determine, according to the collaboration identifier of the first business process instance, whether there is a second business process instance that cooperates with the first business process instance; if so, execute S105; if not, execute S106.

S105, searching for the second business process instance, and executing the second business process instance, and executing the to-be-executed link until the static collaboration link in the second business process instance is executed;

S106. Execute the to-be-executed link.

In the business process operation method disclosed in this embodiment, when it is determined that the to-be-executed link is preset with a static collaboration link according to the information of the to-be-executed link in the first business process instance, it is judged whether there is a second business according to the collaboration identifier of the first business process instance The process instance cooperates with the first business process instance, and if it exists, searches for the second business process instance, and executes the second business process instance, until the static collaboration link in the second process instance is executed. , and then execute the to-be-executed link, if not, execute the to-be-executed link. Based on the above method, if the two links of two process instances with a static collaborative relationship are to be coordinated during the operation of the business process, the two process instances will be executed dependently. Adapt to various application scenarios, greatly improving the user experience.

Referring to FIG. 2, FIG. 2 is a flowchart of Embodiment 2 of a business process operation method provided by the present invention, and the business process operation method includes:

S201 , pre-specify the static collaboration relationship of the specified link in the business process definition through the message flow Message Flow.

BPM IDE (BPM integrated development environment, BPM integrated development environment) introduces independent business processes through swimlanes, and specifies the static collaborative relationship between the specified links of any two independent business processes through the message flow Message Flow. Static collaboration means that two links may have a collaborative relationship, but it is uncertain which two process instances have collaboration between the above two links.

S202: Acquire information of links to be executed in the first business process instance.

Before acquiring the link information to be executed in the first business process instance, the BPM process engine parses the business process definition, and creates a business process instance list according to the business process definition;

Any business process instance in the business process instance list is selected as the first business process instance.

S203, determine whether there is a Message Flow in the information of the link to be executed; if so, it means that the link to be executed is preset with a static coordination link, and execute S204; if not, it means that the link to be executed is not preset with a static coordination link, Execute S207.

S204. Obtain the collaboration identifier of the first business process instance.

When creating a business process instance, the BPM process engine provides a business process instance specified by API binding, as shown in the following code, public void collaborate Process Instances(Set<String>collaborating PIs,String collaboration Key); among them, the first The parameter is the list of business process instances that need to be coordinated, which can be in the form of an array or a collection class. The second parameter is the collaborative identifier of these business process instances, which can be in the form of a string. The collaborative identifier generally has business semantics, such as an order number.

S205. Determine, according to the collaboration identifier of the first business process instance, whether there is a second business process instance that cooperates with the first business process instance; if so, execute S206; if not, execute S207.

Specifically, if the collaboration identifier of the first business process instance is empty, for example, the character string is NULL, there is no collaboration between the second business process instance and the first business process instance;

If the collaboration identifier of the first business process instance is not empty, for example, the string part has a specific value, there is a second business process instance that cooperates with the first business process instance.

S206: Search for the second business process instance, and execute the second business process instance, and execute the to-be-executed link until the static coordination link in the second business process instance is executed.

The searching for the second business process instance specifically includes:

Searching for a business process instance with the same collaboration identifier as the collaboration identifier of the first business process instance from the list of business process instances as the second business process instance.

S207. Execute the to-be-executed link.

It should be noted that, in this embodiment, the link to be executed is a coordinated link, and the static coordination link is an initiating coordination link.

Based on the above embodiments, the present application discloses a business process operation example, which is as follows:

As shown in Figure 3, the swimming lane diagram refers to the specified business process definition. Three independent business process definitions are configured in the three swimming lanes, pool1, pool2, and pool3—order application, order opening, and logistics.

Use Message Flow to specify the static collaborative relationship of the specified link of the business process definition. For example, the "outbound" link of the order opening process in pool2 has to wait for the "logistics result notification" of the logistics process in pool3, so the "logistics result notification" is established. The message flow from the link to the "outbound" link. The "logistics result notification" link is the link that initiates the collaboration, and the "outbound" link is the link that is coordinated.

The BPM engine provides API: public void collaborate Process Instances (Set<String>collaborating PIs, String collaboration Key); to help users in the running state to realize the specific process instances created by the three processes of order application, order opening, and logistics during the running period, For example, "Zhang San applies for the iphone5 package" will create an order application process instance numbered ××××, the id is 0001, and then there will be an instance of the logistics process for delivering the iphone5, the id is 0002, and there will also be an activation mobile phone number And the order opening process example of the tariff package, the id is 0003, the program only needs to pass 0001, 0002, 0003 to the BPM engine into the first parameter, and pass in the order number ×××× into the second parameter, you can It shows that the business process instances corresponding to 0001, 0002, and 0003 need to be coordinated, and the coordination identifier is the order number ×××× (the second parameter). The BPPM engine will generate several collaborative relationship records corresponding to business process instances and store them in the database.

When the order opening process instance (0003) is executed to the "outbound" link, it is found that the message flow is associated, and it will search for the logistics business process instance (0002) with the same collaborative ID, and wait for the "logistics result notification" of the logistics business process instance. After the execution of the link, the "outbound" link of the order opening process instance can be executed.

If the BPM engine does not set the business process instances corresponding to 0001, 0002, and 0003 to be coordinated, the order opening process instance (0003) does not know which specific logistics business process instance to wait for when it executes the "outbound" link. , the instance of the order opening process will flow on by itself.

This embodiment uses Message Flow to realize the static collaboration relationship between the specified links in the business process definition, and binds the same collaboration identifier to all business process instances to be coordinated, and finally realizes the dynamic dynamic between independent business process instances during operation. Synergy.

Referring to FIG. 4 , FIG. 4 is a structural diagram of Embodiment 1 of a business process running device provided by the present invention. The business process running device includes:

a first obtaining unit 11, configured to obtain information on links to be executed in the first business process instance;

The first judging unit 12 is configured to judge whether the to-be-executed link is preset with a static collaborative link according to the to-be-executed link information; if the to-be-executed link is not preset with a static collaborative link, trigger the second execution unit 16; if the to-be-executed link is not preset with a static collaborative link The to-be-executed link is preset with a static coordination link, then triggers the second acquisition unit 13;

a second obtaining unit 13, configured to obtain the collaboration identifier of the first business process instance;

The second judging unit 14 is configured to judge whether there is a second business process instance to cooperate with the first business process instance according to the collaboration identifier of the first business process instance; if so, trigger the first execution unit;

The first execution unit 15 is configured to search for the second business process instance, and execute the second business process instance, and execute the to-be-executed until the static coordination link in the second business process instance is executed. link;

The second execution unit 16 is configured to execute the link to be executed.

It should be noted that, the functional implementation of the above-mentioned units has been described in detail in the method embodiment, which is not repeated in this embodiment.

Referring to FIG. 5, FIG. 5 is a structural diagram of Embodiment 1 of a business process running device provided by the present invention. The business process running device includes:

The presetting unit 21 is configured to pre-specify the static coordination relationship of the specified link in the business process definition through the message flow Message Flow.

The first business process instance determining unit 22 is configured to parse the business process definition before acquiring the information on the links to be executed in the first business process instance, and create a list of business process instances according to the business process definition; select the Any business process instance in the business process instance list is the first business process instance.

a first obtaining unit 23, configured to obtain information on links to be executed in the first business process instance;

The first judging unit 24 is specifically configured to: judge whether the MessageFlow exists in the information of the link to be executed; if so, it means that the link to be executed is preset with a static coordination link, and triggers the second acquisition unit 25; if not, the second obtaining unit 25 is triggered. It means that the link to be executed is not preset with a static coordination link, and the second execution unit 28 is triggered.

A second obtaining unit 25, configured to obtain the collaboration identifier of the first business process instance;

The second judging unit 26 is configured to judge whether there is a second business process instance that cooperates with the first business process instance according to the collaboration identifier of the first business process instance; if it exists, trigger the first execution unit 27; if it does not exist , the second execution unit 28 is triggered.

The second judgment unit is specifically used for:

If the collaboration identifier of the first business process instance is empty, there is no collaboration between the second business process instance and the first business process instance;

If the collaboration identifier of the first business process instance is not empty, there is a second business process instance that cooperates with the first business process instance.

The first execution unit 27 is configured to search for the second business process instance, and execute the second business process instance, and execute the to-be-executed until the static coordination link in the second business process instance is executed. link.

The first execution unit is specifically used for:

Searching for a business process instance with the same collaboration identifier as the collaboration identifier of the first business process instance from the list of business process instances as the second business process instance.

The second execution unit 28 is configured to execute the link to be executed.

It should be noted that, the functional implementation of the above-mentioned units has been described in detail in the method embodiment, which is not repeated in this embodiment.

In addition, an embodiment of the present application also provides a computing node, and the computing node may be a host server containing computing capabilities, or a personal computer PC, or a portable portable computer or terminal, etc. The specific embodiments of the present application are not correct The specific implementation of the computing node is limited.

FIG. 6 is a structural diagram of a computing node of the present application. As shown in FIG. 6, the computing node 700 includes:

A processor 710 , a Communications Interface 720 , a memory 730 , and a bus 740 .

The processor 710 , the communication interface 720 , and the memory 730 communicate with each other through the bus 740 .

The processor 710 is used for executing the program 732 .

Specifically, the program 732 may include program code including computer operation instructions.

The processor 710 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

The memory 730 is used to store the program 732 . The memory 730 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory. The program 732 may specifically include:

The method steps in the embodiments shown in FIGS. 1 , 2 and 3 are not repeated here.

For the specific implementation of each unit in the program 732, refer to the corresponding units in the embodiments shown in FIG. 4-FIG. 5, which will not be repeated here.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary hardware platform, and of course all can be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, all or part of the contributions made by the technical solutions of the present application to the background technology can be embodied in the form of software products, and the computer software products can be stored in storage media, such as ROM/RAM, magnetic disks, optical disks, etc. , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of the present application.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. For the system disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method.

The principles and implementations of the present application are described herein by using specific examples. The descriptions of the above embodiments are only used to help understand the methods and core ideas of the present application. There will be changes in the specific implementation and application scope. In conclusion, the content of this specification should not be construed as a limitation on the present application.

Claims (10)

1. A method for operating a business process, the method comprising:

specifying a static cooperative relationship of a specified link in a service Flow definition in advance through a Message Flow;

acquiring information of a link to be executed in a first business process instance;

judging whether a static cooperative link is preset in the link to be executed according to the information of the link to be executed;

if the link to be executed is not preset with a static cooperative link, executing the link to be executed;

if the link to be executed is preset with a static cooperative link, acquiring a cooperative identification of the first business process instance;

judging whether a second business process example is cooperated with the first business process example or not according to the cooperation identifier of the first business process example;

if the static collaborative link exists in the second business process instance, searching the second business process instance, executing the second business process instance until a link before the static collaborative link in the second business process instance and the link to be executed are executed completely;

and if the link to be executed does not exist, executing the link to be executed.

2. The method according to claim 1, wherein the determining whether the link to be executed is provided with a static cooperative link in advance according to the link to be executed information specifically includes:

judging whether Message Flow exists in the link information to be executed;

if the link exists, a static cooperative link is preset in the link to be executed;

and if the link to be executed does not exist, the static cooperative link is not preset in the link to be executed.

3. The method according to claim 1, wherein the determining, according to the cooperation identifier of the first business process instance, whether there is cooperation between a second business process instance and the first business process instance specifically includes:

if the cooperation identifier of the first business process instance is null, the cooperation of a second business process instance and the first business process instance does not exist;

and if the cooperation identifier of the first business process example is not null, the cooperation of a second business process example and the first business process example exists.

4. The method according to any one of claims 1 to 3, wherein before the obtaining of the link information to be executed in the first business process instance, the method further comprises:

analyzing the service process definition, and creating a service process instance list according to the service process definition;

and selecting any business process instance in the business process instance list as a first business process instance.

5. The method according to claim 4, wherein the searching for the second business process instance specifically includes:

and searching the business process example with the cooperative identification which is the same as the cooperative identification of the first business process example from the business process example list to be used as a second business process example.

6. A business process execution apparatus, comprising:

the system comprises a presetting unit, a service Flow defining unit and a service processing unit, wherein the presetting unit is used for presetting the static cooperative relationship of a designated link in the service Flow definition through a Message Flow;

the first acquisition unit is used for acquiring information of links to be executed in a first business process instance;

the first judging unit is used for judging whether the link to be executed is provided with a static cooperative link in advance according to the information of the link to be executed; if the link to be executed is not preset with a static cooperative link, triggering a second execution unit; if the link to be executed is preset with a static cooperative link, triggering a second acquisition unit;

a second obtaining unit, configured to obtain a cooperative identifier of the first business process instance;

a second judging unit, configured to judge whether there is cooperation between a second business process instance and the first business process instance according to the cooperation identifier of the first business process instance; if yes, triggering the first execution unit;

a first execution unit, configured to search for the second business process instance, execute the second business process instance, and execute the to-be-executed link until a link before the static collaborative link in the second business process instance and after the static collaborative link is executed;

and the second execution unit is used for executing the link to be executed.

7. The apparatus according to claim 6, wherein the first determining unit is specifically configured to:

judging whether Message Flow exists in the link information to be executed;

if the link exists, a static cooperative link is preset in the link to be executed;

and if the link to be executed does not exist, the static cooperative link is not preset in the link to be executed.

8. The apparatus according to claim 6, wherein the second determining unit is specifically configured to:

if the cooperation identifier of the first business process instance is null, the cooperation of a second business process instance and the first business process instance does not exist;

and if the cooperation identifier of the first business process example is not null, the cooperation of a second business process example and the first business process example exists.

9. The apparatus of any one of claims 6 to 8, further comprising:

a first business process instance determining unit, configured to, before the obtaining of the link information to be executed in the first business process instance, parse the business process definition, and create a business process instance list according to the business process definition; and selecting any business process instance in the business process instance list as a first business process instance.

10. The apparatus of claim 9, wherein the first execution unit is specifically configured to:

and searching the business process example with the cooperative identification which is the same as the cooperative identification of the first business process example from the business process example list to be used as a second business process example.

Images