CN106528066B - Business process operation method and device - Google Patents
Business process operation method and device Download PDFInfo
- Publication number
- CN106528066B CN106528066B CN201510585029.5A CN201510585029A CN106528066B CN 106528066 B CN106528066 B CN 106528066B CN 201510585029 A CN201510585029 A CN 201510585029A CN 106528066 B CN106528066 B CN 106528066B
- Authority
- CN
- China
- Prior art keywords
- business process
- link
- executed
- process instance
- static
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The method and the device for operating the business process determine that a static collaborative link is preset in a link to be executed according to information of the link to be executed in a first business process example, judge whether a second business process example is collaborative with the first business process example according to a collaborative identifier of the first business process example, if the static collaborative link exists, search the second business process example, execute the second business process example until the static collaborative link in the second business process example is executed, and execute the link to be executed if the static collaborative link does not exist. Based on the method and the device, the two links of the two process instances with the static cooperative relationship are dependent to execute if the two process instances need to cooperate during the operation of the business process, and can still be independently executed if the two process instances do not need to cooperate, so that the method and the device can adapt to various application scenes, and the use experience of a user is greatly improved.
Description
Technical Field
The present application relates to the field of business process management technologies, and in particular, to a business process operation method and apparatus.
Background
A Business Process Management (BPM) system generally includes two aspects of modeling a Business Process and driving the Business Process, where the modeling of the Business Process is generally handled by a BPM integrated Development Environment (BPM integrated Development Environment), and the driving of the Business Process is generally handled by a BPM Process engine (BPMEngine). Through the BPM system, various BPM flow charts which accord with business development of enterprises can be created, the enterprise management is greatly facilitated, and great contribution is made to the enterprise development.
Each primitive on the BPM flowchart is generally called a "link", and based on the existing BPM system, it is usually necessary to strongly associate a link (assumed to be a link initiating the cooperation and named link 1) in one independent process with a link (assumed to be a link being cooperated and named link 2) in another independent process, so as to establish the cooperation across the processes. In the process running period, in two links which are related to each other, if the link 2 is not executed, the link 1 is not executed, and the independent process corresponding to the link 1 is stopped at the link 1 and cannot be executed continuously. That is, as long as the cross-flow cooperation is established, the flow initiating the cooperation must be executed depending on the execution state of the links being cooperated during the flow operation, and cannot be executed alone.
However, in some scenarios, such as the telecommunication field, if a user wants to purchase a mobile phone, there are an order flow, a logistics flow, a card opening flow, a business handling flow, and the like, if a cooperation between the logistics flow and the card opening flow is established, the card opening flow can be executed only after a certain link in the logistics flow is executed during the running of the flow, but actually, the user can execute the card opening flow alone, and the card opening flow is forcibly associated with the logistics flow due to the cross-flow cooperation established before, which finally results in the limitation of the independent execution of the card opening flow.
That is to say, in the BPM system in the prior art, the coordination relationship between the processes is fixed, and during the process operation, the processes having the coordination relationship cannot be executed independently, so that the applicability to various application scenarios is poor, and the use experience of the user is greatly influenced.
Disclosure of Invention
The application aims to provide a business process operation method and a business process operation device, and the business process operation method and the business process operation device are used for solving the problems that in the prior art, the cooperative relationship among processes in a BPM system is fixed, and in the process operation period, the processes with the cooperative relationship cannot be independently executed, the applicability to various application scenes is poor, and the use experience of a user is greatly influenced.
In order to achieve the above purpose, the present 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 operating a business process, where the method includes:
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, and executing the second business process instance until the static collaborative link in the second business process instance is executed, and then executing the link to be executed;
and if the link to be executed does not exist, executing the link to be executed.
With reference to the second possible implementation manner of the first aspect, the method further includes:
and specifying the static cooperative relationship of the specified link in the service Flow definition in advance through the Message Flow.
With reference to the third possible implementation manner of the first aspect, the determining, according to the information of the to-be-executed link, whether a static cooperative link is preset in the to-be-executed link 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.
With reference to the fourth possible implementation manner of the first aspect, the determining, according to the cooperation identifier of the first business process instance, whether a second business process instance cooperates with the first business process instance 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.
With reference to the fifth possible implementation manner of the first aspect, before the obtaining of the to-be-executed link information in the first business process instance, the method further includes:
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.
With reference to the sixth possible implementation manner of the first aspect, 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.
According to a first possible implementation manner of the second aspect of the present application, the present application provides a business process running apparatus, including:
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;
the first execution unit is used for searching the second business process example and executing the second business process example until the static collaborative link in the second business process example is executed, and then executing the link to be executed;
and the second execution unit is used for executing the link to be executed.
With reference to the second possible implementation manner of the second aspect, the apparatus further includes:
the preset unit is used for appointing the static cooperative relationship of the appointed links in the service Flow definition in advance through the Message Flow.
With reference to the third possible implementation manner of the second aspect, 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.
With reference to the fourth possible implementation manner of the second aspect, 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.
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, 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.
With reference to the sixth possible implementation manner of the second aspect, 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.
According to the specific embodiments provided herein, the present application discloses the following technical effects:
the method and the device for operating the business process determine that a static collaborative link is preset in a link to be executed according to information of the link to be executed in a first business process example, judge whether a second business process example is collaborative with the first business process example according to a collaborative identifier of the first business process example, if the static collaborative link exists, search the second business process example, execute the second business process example until the static collaborative link in the second business process example is executed, and execute the link to be executed if the static collaborative link does not exist. Based on the method and the device, the two links of the two process instances with the static cooperative relationship are dependent to execute if the two process instances need to cooperate during the operation of the business process, and can still be independently executed if the two process instances do not need to cooperate, so that the method and the device can adapt to various application scenes, and the use experience of a user is greatly improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for a person skilled in the art to obtain other drawings without any inventive exercise.
Fig. 1 is a flowchart of a business process operation method embodiment 1 of the present application;
fig. 2 is a flowchart of a business process operation method embodiment 2 of the present application;
FIG. 3 is a schematic diagram illustrating an exemplary method for operating a business process according to the present application;
fig. 4 is a structural diagram of a business process operation apparatus embodiment 1 of the present application;
fig. 5 is a structural diagram of a business process execution apparatus embodiment 2 of the present application;
fig. 6 is a structural diagram of a computing node of the present application.
Detailed Description
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, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
Referring to fig. 1, fig. 1 is a flowchart of an embodiment 1 of a service flow operation method provided by the present invention, where the service flow operation method includes:
s101, obtaining information of a link to be executed in a first business process instance.
When the link to be executed is preset with a static cooperative link, the information of the link to be executed may include a static cooperative identifier, where the static cooperative identifier may specifically be a Message Flow.
S102, judging whether a 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, executing S106; and if the link to be executed is preset with a static cooperative link, executing S103.
S103, acquiring the cooperative identification of the first business process instance.
S104, 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 so, executing S105; if not, S106 is executed.
S105, searching the second business process example, executing the second business process example until the static coordination link in the second business process example is executed, and then executing the link to be executed;
and S106, executing the link to be executed.
In the method for operating the business process disclosed in this embodiment, it is determined according to information of a to-be-executed link in a first business process instance that a static collaborative link is preset in the to-be-executed link, it is determined according to a collaborative identifier of the first business process instance whether a second business process instance is collaborative with the first business process instance exists, if so, the second business process instance is searched for, and the second business process instance is executed until the static collaborative link in the second business process instance is executed, the to-be-executed link is executed, and if not, the to-be-executed link is executed. Based on the method, the two links of the two process instances with the static cooperative relationship are dependent to execute if the two process instances need to cooperate during the operation of the business process, and can still be independently executed if the two process instances do not need to cooperate, so that the method can adapt to various application scenes and greatly improve the use experience of users.
Referring to fig. 2, fig. 2 is a flowchart of an embodiment 2 of a service flow operation method provided by the present invention, where the service flow operation method includes:
s201, specifying the static cooperative relationship of the specified links in the business process definition in advance through Message Flow.
BPM IDE (BPM integrated development environment) introduces independent business processes through lanes, and specifies the static cooperative relationship between the specified links of any two independent business processes through Message Flow. Static cooperation means that two links may have a cooperation relationship, but it is uncertain which two process instances have cooperation between the two links.
S202, obtaining information of links to be executed in the first business process instance.
Before the link information to be executed in the first business process instance is obtained, a BPM process engine analyzes the business process definition and creates 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.
S203, judging whether Message Flow exists in the link information to be executed; if yes, the link to be executed is preset with a static cooperative link, and S204 is executed; if not, the to-be-executed link is not preset with a static cooperative link, and S207 is executed.
And S204, acquiring the cooperative identification of the first business process instance.
The BPM flow engine provides an API binding-specified business flow instance while creating the business flow instance, and as shown in the following code, a public void format Process instance (Set < String > format PIs, String format Key); the first parameter is a list of service process instances that need to be coordinated, and can be in an array or set type, the second parameter is a coordination identifier of the service process instances, and can be in a character string type, and the coordination identifier generally has service semantics, such as an order number.
S205, 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 so, executing S206; if not, S207 is performed.
Specifically, if the cooperation identifier of the first business process instance is NULL, for example, the character string is NULL, there is no cooperation between the second business process instance and the first business process instance;
and if the cooperation identifier of the first business process instance is not null, for example, the character string part has a specific value, the cooperation of a second business process instance and the first business process instance exists.
S206, searching the second business process example, executing the second business process example until the static cooperative link in the second business process example is executed, and then executing the link to be executed.
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.
And S207, executing the link to be executed.
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 specifically includes:
as shown in fig. 3, the lane diagram refers to the specified business process definition, and three lanes pool1, pool2, and pool3 are respectively configured with three independent business process definitions, namely, order application, order fulfillment, and logistics.
The static collaborative relationship of the designated link defined by the business process is designated by using the Message Flow, for example, the "ex warehouse" link of the order opening process in the pool2 waits for the "logistics result notification" of the logistics process in the pool3, so that the Message Flow from the "logistics result notification" link to the "ex warehouse" link is established. The logistics result notification link is a link for initiating the cooperation, and the ex-warehouse link is a link to be cooperated.
The BPM engine provides the API: public void volume protocol Process Instances (Set < String > formatting PIs, String formatting Key); the method is used for helping a user to realize a specific flow example created by three flows of order application, order fulfillment and logistics in a running period in a running state, for example, if an order application flow example with the number of xxx is created in a three-year-round application iphone5 package, id is 0001, then a logistics flow example with the number of iphone5 is delivered, id is 0002, an order fulfillment flow example with the number of a mobile phone and a tariff package is created, id is 0003, a program only needs to transmit order numbers xxx to a BPM engine 0001, 0002 and 0003 to a first parameter and transmit order numbers xxx to a second parameter, and therefore, the business flow examples corresponding to 0001, 0002 and 0003 need to be coordinated and the coordination mark is the order numbers xxx (the second parameter). The BPPM engine can generate a plurality of collaborative relation records corresponding to the business process instances and store the collaborative relation records in the database.
When the order opening Flow example (0003) is executed to the ex-warehouse link, the Message Flow is found to be associated, the logistics business Flow example (0002) with the same cooperative identification is searched, and the ex-warehouse link of the order opening Flow example can be executed after the logistics result notification link of the logistics business Flow example is executed.
If the BPM engine does not set that the business process instances corresponding to 0001, 0002, and 0003 are needed to be coordinated, the order fulfillment process instance (0003) does not know which specific logistics business process instance to wait for notification when executing the "ex-warehouse" link, and the order fulfillment process instance will flow on its own.
In this embodiment, a static cooperation relationship between service Flow definition designated links is realized by using Message Flow, and the same cooperation identifier is bound to all service Flow instances to be cooperated, so that a dynamic cooperation between independent service Flow instances is finally realized during operation.
Referring to fig. 4, fig. 4 is a structural diagram of an embodiment 1 of a service flow operation device provided in the present invention, where the service flow operation device includes:
a first obtaining unit 11, configured to obtain information of a link to be executed in a first business process instance;
a first judging unit 12, configured to judge whether a static cooperative link is preset in the to-be-executed link according to the to-be-executed link information; if the link to be executed is not preset with a static cooperative link, triggering a second execution unit 16; if the link to be executed is preset with a static cooperative link, triggering a second obtaining unit 13;
a second obtaining unit 13, configured to obtain a cooperative identifier of the first business process instance;
a second determining unit 14, configured to determine whether there is a collaboration between a second business process instance and the first business process instance according to the collaboration identifier of the first business process instance; if yes, triggering 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 until the static collaborative link in the second business process instance is executed, and then execute the to-be-executed link;
and the second execution unit 16 is configured to execute the link to be executed.
It should be noted that, the function implementation of each unit is described in detail in the method embodiment, and this embodiment is not described again.
Referring to fig. 5, fig. 5 is a structural diagram of an embodiment 1 of a service flow operation device provided in the present invention, where the service flow operation device includes:
the presetting unit 21 is configured to specify a static coordination relationship of a specified link in the service Flow definition in advance through a Message Flow.
A first business process instance determining unit 22, configured to, before the information of the link to be executed in the first business process instance is obtained, analyze 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.
A first obtaining unit 23, configured to obtain information of a link to be executed in a first business process instance;
the first judging unit 24 is specifically configured to: judging whether the MessageFlow exists in the link information to be executed or not; if the link to be executed is the static collaborative link, triggering a second obtaining unit 25; if the static cooperative link does not exist, the static cooperative link is not preset in the link to be executed, and the second execution unit 28 is triggered.
A second obtaining unit 25, configured to obtain a cooperative identifier of the first business process instance;
a second determining unit 26, configured to determine 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 so, triggering the first execution unit 27; if not, the second execution unit 28 is triggered.
The second judging 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.
The first executing unit 27 is configured to search for the second business process instance, and execute the second business process instance until the static collaborative link in the second business process instance is executed, and then execute the to-be-executed link.
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.
And a second execution unit 28, configured to execute the link to be executed.
It should be noted that, the function implementation of each unit is described in detail in the method embodiment, and this embodiment is not described again.
In addition, the embodiment of the present application also provides a computing node, where the computing node may be a host server including computing capability, or a personal computer PC, or a portable computer or a terminal, and the like.
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 (processor)710, a communication Interface 720, a memory 730, and a bus 740.
In particular, the program 732 may include program code that includes computer operational 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 embodiments of the present application.
A memory 730 for storing a program 732. Memory 730 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The procedure 732 may specifically include:
the method steps in the embodiments shown in fig. 1, 2, and 3 are not described herein again.
The specific implementation of each unit in the procedure 732 refers to corresponding units in the embodiments shown in fig. 4 to fig. 5, which are not described herein again.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus a necessary hardware platform, and certainly can be implemented by hardware, but in many cases, the former is a better embodiment. With this understanding in mind, the technical solutions of the present application may be embodied in whole or in part in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes 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 the embodiments or some parts of the embodiments of the present application.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific embodiments and the application range may be changed. In view of the above, the description should not be taken as limiting the 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.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510585029.5A CN106528066B (en) | 2015-09-15 | 2015-09-15 | Business process operation method and device |
| PCT/CN2016/089928 WO2017045473A1 (en) | 2015-09-15 | 2016-07-13 | Business process operation method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510585029.5A CN106528066B (en) | 2015-09-15 | 2015-09-15 | Business process operation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106528066A CN106528066A (en) | 2017-03-22 |
| CN106528066B true CN106528066B (en) | 2020-01-17 |
Family
ID=58288219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510585029.5A Active CN106528066B (en) | 2015-09-15 | 2015-09-15 | Business process operation method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106528066B (en) |
| WO (1) | WO2017045473A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111260433A (en) * | 2020-01-07 | 2020-06-09 | 中国联合网络通信集团有限公司 | Service order processing method and device |
| CN111309294B (en) | 2020-02-29 | 2022-06-07 | 苏州浪潮智能科技有限公司 | Business processing method and device, electronic equipment and storage medium |
| CN112182000A (en) * | 2020-09-26 | 2021-01-05 | 中国建设银行股份有限公司 | Flow engine implementation method and device, electronic equipment and readable storage medium |
| CN114489855A (en) * | 2022-01-27 | 2022-05-13 | 北京索为系统技术股份有限公司 | Process node control method and device and computer equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101976386A (en) * | 2010-10-12 | 2011-02-16 | 大唐软件技术股份有限公司 | Cooperative controlling method of processes |
| CN103208046A (en) * | 2012-12-31 | 2013-07-17 | 广州奥凯信息咨询有限公司 | Workflow engine architecture method and system based on interactive dynamic flow diagram |
| CN103455324A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Model for business development process |
| CN103500372A (en) * | 2013-08-08 | 2014-01-08 | 机械工业第六设计研究院有限公司 | Collaborative design method and system based on SOA |
| CN104463508A (en) * | 2014-12-30 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Coordination method and device between multiple workflow systems |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5960404A (en) * | 1997-08-28 | 1999-09-28 | International Business Machines Corp. | Mechanism for heterogeneous, peer-to-peer, and disconnected workflow operation |
| CN101132401A (en) * | 2006-08-25 | 2008-02-27 | 华为技术有限公司 | Business interactive processing method and system |
-
2015
- 2015-09-15 CN CN201510585029.5A patent/CN106528066B/en active Active
-
2016
- 2016-07-13 WO PCT/CN2016/089928 patent/WO2017045473A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101976386A (en) * | 2010-10-12 | 2011-02-16 | 大唐软件技术股份有限公司 | Cooperative controlling method of processes |
| CN103208046A (en) * | 2012-12-31 | 2013-07-17 | 广州奥凯信息咨询有限公司 | Workflow engine architecture method and system based on interactive dynamic flow diagram |
| CN103455324A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Model for business development process |
| CN103500372A (en) * | 2013-08-08 | 2014-01-08 | 机械工业第六设计研究院有限公司 | Collaborative design method and system based on SOA |
| CN104463508A (en) * | 2014-12-30 | 2015-03-25 | 山东中创软件商用中间件股份有限公司 | Coordination method and device between multiple workflow systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106528066A (en) | 2017-03-22 |
| WO2017045473A1 (en) | 2017-03-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019061991A1 (en) | Multi-element universal model platform modeling method, electronic device, and computer readable storage medium | |
| CN106528066B (en) | Business process operation method and device | |
| CN107766344B (en) | Template rendering method and device and browser | |
| CN104579909B (en) | Method and equipment for classifying user information and acquiring user grouping information | |
| CN110688598A (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| US20240146650A1 (en) | Creating endpoints | |
| EP3693894A1 (en) | Service process starting method and apparatus | |
| CN104679824A (en) | Webpage generating method and webpage generating system of network platform | |
| CN116523457A (en) | Workflow processing method, device, equipment and storage medium based on business process | |
| CN109087129B (en) | User evaluation method, device and computer-readable storage medium | |
| CN106776266B (en) | Configuration method of test tool and terminal equipment | |
| CN106658666A (en) | Method and device for building wireless connection | |
| CN112035676B (en) | User operation behavior knowledge graph construction method and device | |
| CN108959294B (en) | Method and device for accessing search engine | |
| CN110781375B (en) | User state identification determining method and device | |
| CN108268545B (en) | Method and device for establishing hierarchical user label library | |
| CN115481334A (en) | Protocol-based route skipping method and device, electronic equipment and storage medium | |
| CN111177593B (en) | Data communication method and system | |
| CN113094283A (en) | Data acquisition method, device, equipment and storage medium | |
| CN111178044B (en) | Method and device for determining target text elements | |
| CN111078711A (en) | Block chain data storage and acquisition method and device based on data index | |
| CN104408551A (en) | Equipment registration method and system | |
| CN104852996B (en) | Web information processing method and device | |
| CN115604000B (en) | Override detection method, device, equipment and storage medium | |
| CN117008890B (en) | Extended application development system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |