Business process execution method, device and apparatus, and computer readable storage medium

Abstract

This invention discloses a business process execution method, apparatus, device, and computer-readable storage medium. The method includes: a process engine based on an ECA model listening to business flow events in multiple business scenarios and acquiring each business event within the business flow events; acquiring target process nodes corresponding to each business event from preset process nodes corresponding to multiple business scenarios, and executing target H5 pages corresponding to the event nodes of each business event based on the target process nodes; determining the next pending event corresponding to each business event in each target process node based on the event nodes of each business event; using the pending event as the business event, and returning to execute the step of the process engine acquiring the target process nodes corresponding to each business event. This invention realizes the execution control of H5 page flow, thereby freeing the front-end of the business scenario from concern with business process logic control, improving the convenience of front-end development.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a business process execution method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] Existing open access systems, such as interface platforms and capability open platforms, can provide interfaces / capabilities to conduct business and offer open capabilities to users. These capabilities are primarily provided through APIs, H5 pages, messages, and files. For a complete business process, multiple business capabilities are provided to the front-end access system. The relationship between each business interface / capability is controlled by the front-end itself, with the interface platform / capability platform operating independently for each interface / capability.

[0003] Currently, the commonly used approach is to use individual H5 page capabilities. H5 page capabilities are page functions generated at the granularity of a single touch interaction. A business process contains multiple touch interactions, which requires the use of multiple H5 page capabilities. There are business dependencies between multiple H5 pages, but the existing open form cannot realize the logical control between multiple H5 page capabilities contained in the business process.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a business process execution method, apparatus, device, and computer-readable storage medium, which aims to solve the technical problem that the open form of existing open systems cannot realize logical control between the capabilities of multiple H5 pages included in a business process.

[0006] To achieve the above objectives, the present invention provides a business process execution method, the business process execution method comprising the following steps:

[0007] The process engine based on the ECA model listens to business flow events in multiple business scenarios and obtains each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events;

[0008] In the preset process nodes corresponding to multiple business scenarios, obtain the target process node corresponding to each business event, and execute the target H5 page corresponding to the event node of each business event based on the target process node;

[0009] Based on the event nodes of each business event, determine the next event to be processed corresponding to each business event in each target process node;

[0010] The pending events are treated as business events, and the process engine is returned to retrieve the target process nodes corresponding to each business event.

[0011] Furthermore, in one embodiment, the step of the process engine determining the next event to be processed corresponding to each business event in each target process node based on the event node of each event includes:

[0012] Based on the event nodes of each business event and the H5 page, the corresponding target message event is determined;

[0013] Based on the target message event, determine the next event to be processed corresponding to each business event in each target process node.

[0014] Furthermore, in one embodiment, the step of determining the corresponding target message event based on the event nodes of each business event and the H5 page includes:

[0015] Based on the event nodes of each business event, determine whether the target process node has a completed process node that has been executed.

[0016] If it does not exist, the corresponding target message event is determined based on the event nodes of each event and the H5 page.

[0017] Furthermore, in one embodiment, after determining whether the target process node has a completed process node based on the event nodes of each business event, the method further includes:

[0018] If they exist, then based on the completed process nodes, determine the unfinished business events corresponding to the event nodes of each business event;

[0019] Based on the event nodes of incomplete business events and the H5 page, the corresponding target message event is determined.

[0020] Furthermore, in one embodiment, the step of obtaining the target process node corresponding to each business event among preset process nodes corresponding to multiple business scenarios includes:

[0021] Identify the target business scenario corresponding to each business event, and obtain the target process node corresponding to the target business scenario from the preset process nodes corresponding to multiple business scenarios.

[0022] Furthermore, in one embodiment, before the step of the ECA-based process engine listening to business flow events in multiple business scenarios, the method further includes:

[0023] Obtain H5 pages corresponding to multiple business scenarios, and use each H5 page as an ECA node of the process engine;

[0024] Based on the ECA node, preset process nodes corresponding to the business function processes of each business scenario are generated.

[0025] Furthermore, in one embodiment, the step of obtaining H5 pages corresponding to multiple business scenarios includes:

[0026] Obtain H5 page capabilities corresponding to multiple business scenarios, and set the trigger events and execution conditions for each H5 page capability to obtain H5 pages corresponding to multiple business scenarios.

[0027] Furthermore, to achieve the above objectives, the present invention also provides a business process execution apparatus, the business process execution apparatus comprising:

[0028] The listening module is used to listen to business flow events in multiple business scenarios and obtain each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events;

[0029] The acquisition module is used to acquire the target process node corresponding to each business event in the preset process nodes corresponding to multiple business scenarios, and execute the target H5 page corresponding to the event node of each business event based on the target process node;

[0030] The determination module is used to determine the next event to be processed for each business event in each target process node based on the event node of each business event.

[0031] The loop module is used to treat the event to be processed as the business event and return to the step of executing the process engine to obtain the target process node corresponding to each business event.

[0032] In addition, to achieve the above objectives, the present invention also provides a business process execution device, the business process execution device comprising: a memory, a processor, and a business process execution program stored in the memory and executable on the processor, wherein the business process execution program, when executed by the processor, implements the steps of the aforementioned business process execution method.

[0033] In addition, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a business process execution program, which, when executed by a processor, implements the steps of the aforementioned business process execution method.

[0034] This invention utilizes an ECA-based process engine to monitor business flow events across multiple business scenarios and acquire various business events within these events, including input flow events, page request flow events, and / or message events. Next, within preset process nodes corresponding to multiple business scenarios, it identifies the target process node for each business event and executes the target H5 page corresponding to the event node of each business event based on the target process node. Then, based on the event node of each business event, it determines the next pending event for each business event within each target process node. Finally, it uses the pending event as the business event and returns to the process engine to acquire the target process node corresponding to each business event. This achieves execution control of the H5 page flow, using the execution data stream returned from the previous H5 page node as the trigger event for subsequent nodes, and the execution result as the execution condition for the next node, thus realizing H5 page flow control. This eliminates the need for the front-end of the business scenario to concern itself with business flow logic control, improving the convenience of front-end development. Furthermore, for business processes, the H5 page flow control is independent of the front-end of the business scenario, reducing the control risk of the business process and the front-end's control requirements for business capabilities. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of the structure of the business process execution device in the hardware operating environment involved in the embodiments of the present invention;

[0036] Figure 2 This is a flowchart illustrating the first embodiment of the business process execution method of the present invention;

[0037] Figure 3 This is a schematic diagram of the functional modules of an embodiment of the business process execution device of the present invention.

[0038] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0039] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0040] like Figure 1 As shown, Figure 1 This is a schematic diagram of the structure of the business process execution device in the hardware operating environment involved in the embodiments of the present invention.

[0041] In this embodiment of the invention, the device for executing the business process can be a PC. For example... Figure 1As shown, the device executing this business process may include: a processor 1001, such as a CPU; a network interface 1004; a user interface 1003; a memory 1005; and a communication bus 1002. The communication bus 1002 is used to establish communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0042] Optionally, the process execution device may also include a camera, RF (Radio Frequency) circuitry, sensors, audio circuitry, a WiFi module, and so on. Of course, the process execution device may also be configured with other sensors such as barometers, hygrometers, thermometers, and infrared sensors, which will not be elaborated upon here.

[0043] Those skilled in the art will understand that Figure 1 The terminal structure shown does not constitute a limitation on the equipment for executing business processes and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0044] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a business process execution program.

[0045] exist Figure 1 In the terminal shown, the network interface 1004 is mainly used to connect to the backend server and communicate with the backend server; the user interface 1003 is mainly used to connect to the client (user terminal) and communicate with the client; and the processor 1001 can be used to call the business process execution program stored in the memory 1005.

[0046] In this embodiment, the business process execution device includes: a memory 1005, a processor 1001, and a business process execution program stored in the memory 1005 and executable on the processor 1001. When the processor 1001 calls the business process execution program stored in the memory 1005, it executes the steps of the business process execution methods in the following embodiments.

[0047] This invention also provides a business process execution method, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the business process execution method of the present invention.

[0048] In this embodiment, the business process execution method includes:

[0049] Step S101: The process engine based on the ECA model listens to business flow events of multiple business scenarios and obtains each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events;

[0050] In this embodiment, the ECA-based process engine includes EventListen: an event trigger listener that currently mainly implements input stream events, page request stream events, and message events, covering the current capability development methods. Condition parsing executor: uses a JavaScript script engine to execute expressions, obtaining data from the scenario process context and performing boolean type output comparisons. Action: invokes system capabilities aggregated in the middle platform through the capability execution engine. Before executing the business process, multiple preset process nodes for business scenarios are set. Each preset process node includes multiple event nodes, and each event node corresponds to an H6 page.

[0051] In this embodiment, the process engine listens to business flow events in multiple business scenarios and obtains each business event in the business flow events. The business flow events include input flow events, page request flow events, and / or message events. Input flow events include multiple input events, page request flow events include multiple page request events, and message events include multiple events. That is, business events include input events, page request events, and / or message events.

[0052] Step S102: In the preset process nodes corresponding to multiple business scenarios, obtain the target process node corresponding to each business event, and execute the target H5 page corresponding to the event node of each business event based on the target process node;

[0053] In this embodiment, when each business event in the business flow event is obtained, the process engine obtains the target process node corresponding to each business event from the preset process nodes corresponding to multiple business scenarios. Specifically, step S102 includes: determining the target business scenario corresponding to each business event, and obtaining the target process node corresponding to the target business scenario from the preset process nodes corresponding to multiple business scenarios.

[0054] In this embodiment, the process engine can first determine the target business scenario corresponding to each business event, and then obtain the target process node corresponding to the target business scenario from the preset process nodes corresponding to multiple business scenarios.

[0055] Next, the process engine executes the target H5 page corresponding to the event node of each business event based on the target process node. Specifically, the process engine determines the event node of each business event in the target process node, obtains the target H5 page corresponding to the event node of each business event, and then executes the corresponding target H5 page to realize the execution control of multiple H5 page nodes.

[0056] Step S103: Based on the event nodes of each business event, determine the next event to be processed corresponding to each business event in each target process node;

[0057] In this embodiment, when the target H5 page is completed, the process engine determines the next pending event corresponding to each business event in each target process node based on the event nodes of each business event. The process engine determines the next pending event corresponding to each business event through the Action module.

[0058] Step S104: Treat the event to be processed as the business event, and return to the step of executing the process engine to obtain the target process node corresponding to each business event.

[0059] In this embodiment, when the next event to be processed corresponding to each business event is obtained, the event to be processed is taken as the business event, and the process engine is returned to obtain the target process node corresponding to each business event. In this way, each event node can be completed in sequence according to the target process node, and the complete execution of the business scenario can be achieved.

[0060] The business process execution method proposed in this embodiment monitors business flow events in multiple business scenarios using an ECA-based process engine and acquires each business event within these events. These business flow events include input flow events, page request flow events, and / or message events. Next, within preset process nodes corresponding to multiple business scenarios, the method acquires the target process node corresponding to each business event and executes the target H5 page corresponding to the event node of each business event based on the target process node. Then, based on the event node of each business event, the method determines the next pending event corresponding to each business event within each target process node. Finally, the pending event is used as the business event, and the process engine returns to acquire the target process node corresponding to each business event. This achieves execution control of the H5 page flow. The execution data stream returned by the previous H5 page node serves as the trigger event for subsequent nodes, and the execution result serves as the execution condition for the next node, thus realizing process control of the H5 page. This eliminates the need for the front-end of the business scenario to concern itself with business process logic control, improving the convenience of front-end development. Furthermore, for business processes, the H5 page's process control does not depend on the front-end of the business scenario, reducing the control risk of the business process and the front-end's control requirements for business capabilities.

[0061] Based on the first embodiment, a second embodiment of the business process execution method of the present invention is proposed. In this embodiment, step S103 includes:

[0062] Step S201: Based on the event nodes of each business event and the H5 page, determine the corresponding target message event;

[0063] Step S202: Based on the target message event, determine the next event to be processed corresponding to each business event in each target process node.

[0064] In this embodiment, the process engine determines the corresponding target message event based on the event nodes of each business event and the H5 page. The target message event includes the process of taking the event nodes of the business events as input events and the execution and invocation process of the H5 page.

[0065] Next, based on the target message event, the process engine determines the next event to be processed corresponding to each business event in each target process node, that is, the event of the next event node corresponding to the currently executed business event in the target process node.

[0066] Specifically, the InputEvent of EventListen is used for input events, and PageInvoke is used for page invocation. Then, the target message event is obtained through the EventListen of the process engine. The message event MsgEvent of EventListen is passed to the Action of the process engine through the IConditop of the process engine. The Action uses the message event (MsgEvent) to form the event action that needs to be constructed for the business event, including BeanAction and ServiceAction. The Action determines the next event to be processed (the next Action) through the event action.

[0067] The business process execution method proposed in this embodiment determines the corresponding target message event based on the event nodes of each business event and the H5 page; then, based on the target message event, it determines the next pending event corresponding to each business event in each target process node. It can accurately obtain the next pending event according to the target message event, realize the use of the execution data stream returned by the previous H5 page node as the trigger event of the subsequent node, and the execution result as the execution condition of the next node, thereby realizing the process control of multiple H5 pages.

[0068] Based on the second embodiment, a third embodiment of the business process execution method of the present invention is proposed. In this embodiment, step S201 includes:

[0069] Step S301: Based on the event nodes of each business event, determine whether the target process node has a completed process node that has been executed.

[0070] Step S302: If it does not exist, determine the corresponding target message event based on the event nodes of each event and the H5 page.

[0071] In this embodiment, when the H5 page finishes execution, the process engine determines whether there is a completed process node for the target process node based on the event nodes of each business event. Specifically, it determines whether there is a completed process node for the target process node corresponding to the current business event. For each business event, it can determine whether the event node of the business event is the tail node (last event node) of its corresponding target process node. If it is the tail node, it is determined that the target process node corresponding to the business event has been completed; otherwise, it is determined that the target process node corresponding to the business event has not been completed.

[0072] If no process node has been completed, then the corresponding target message event is determined based on the event node of each event and the H5 page.

[0073] Furthermore, in one embodiment, after step S301, the method further includes:

[0074] Step S303: If it exists, then based on the completed process nodes, determine the unfinished business events corresponding to the event nodes of each business event.

[0075] Step S304: Based on the event nodes of the incomplete business events and the H5 page, determine the corresponding target message event.

[0076] In this embodiment, if there are completed process nodes, the unfinished business events corresponding to the event nodes of each business event are determined. Specifically, the completed process nodes are removed from the target process nodes to obtain the unfinished process nodes. The event nodes that match the unfinished process nodes in the event nodes of each business event are the unfinished event nodes. Thus, the unfinished business events of the unfinished event nodes are the unfinished business events corresponding to the event nodes of each business event.

[0077] Then, the process engine determines the corresponding target message event based on the event nodes of the incomplete business events and the H5 page.

[0078] The business process execution method proposed in this embodiment determines whether the target process node has a completed process node based on the event nodes of each business event. If not, it determines the corresponding target message event based on the event nodes of each event and the H5 page. This method can accurately determine the target message event based on the completed process node, and then accurately obtain the next event to be processed based on the target message event. It realizes the use of the execution data stream returned by the previous H5 page node as the trigger event for the subsequent node, and the execution result as the execution condition for the next node, thereby realizing the process control of multiple H5 pages.

[0079] Based on the above embodiments, a fourth embodiment of the business process execution method of the present invention is proposed. In this embodiment, before step S101, the business process execution method further includes:

[0080] Step S401: Obtain H5 pages corresponding to multiple business scenarios, and use each H5 page as an ECA node of the process engine;

[0081] Step 4102: Generate preset process nodes corresponding to the business function processes of each business scenario based on the ECA node.

[0082] In this embodiment, the process engine obtains H5 pages corresponding to multiple business scenarios and uses each H5 page as an ECA node of the process engine. Specifically, it obtains the H5 pages (H5 page capabilities) of the events corresponding to the functions of each business scenario.

[0083] Next, the workflow engine generates preset workflow nodes corresponding to the business function processes of each business scenario based on the ECA node. In other words, the workflow engine generates preset workflow nodes corresponding to the business function processes of each business scenario based on the ECA node.

[0084] Further, in one embodiment, step S401 includes:

[0085] Step S103: Obtain H5 page capabilities corresponding to multiple business scenarios, and set the trigger events and execution conditions for each H5 page capability to obtain H5 pages corresponding to multiple business scenarios.

[0086] In this embodiment, H5 page capabilities corresponding to multiple business scenarios are first obtained, and trigger events and execution conditions for each H5 page capability are set. When the process engine detects a certain trigger event, it determines the business event of the corresponding H5 page capability based on the trigger event. The execution conditions include the execution result of the preceding H5 page capability of the H5 page capability. If the execution result of the preceding H5 page capability of the H5 page capability is completed, the process engine can execute the H5 page capability.

[0087] The business process execution method proposed in this embodiment obtains multiple H5 pages corresponding to business scenarios and uses each H5 page as an ECA node of the process engine; then, based on the ECA nodes, it generates preset process nodes corresponding to the business function processes of each business scenario. By generating preset process nodes according to H5 pages, it is convenient to realize process control of H5 pages.

[0088] The present invention also provides a business process execution device, with reference to Figure 3 The business process execution device includes:

[0089] The listening module 10 is used to listen to business flow events in multiple business scenarios and obtain each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events;

[0090] The acquisition module 20 is used to acquire the target process node corresponding to each business event in the preset process nodes corresponding to multiple business scenarios, and execute the target H5 page corresponding to the event node of each business event based on the target process node;

[0091] The determination module 30 is used to determine the next event to be processed corresponding to each business event in each target process node based on the event node of each business event.

[0092] The loop module 40 is used to treat the event to be processed as the business event and return to the step of executing the process engine to obtain the target process node corresponding to each business event.

[0093] The methods executed by the above-mentioned program units can be referred to in the various embodiments of the business process execution method of the present invention, and will not be repeated here.

[0094] The present invention also provides a computer-readable storage medium.

[0095] The present invention provides a computer-readable storage medium storing a business process execution program, which, when executed by a processor, implements the steps of the business process execution method described above.

[0096] The method implemented when the business process execution program running on the processor is executed can be referred to in various embodiments of the business process execution method of the present invention, and will not be repeated here.

[0097] Furthermore, embodiments of the present invention also propose a computer program product, which includes a business process execution program. When the business process execution program is executed by a processor, it implements the steps of the business process execution method described above.

[0098] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0099] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0100] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0101] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A business process execution method, characterized in that, The business process execution method includes the following steps: The process engine based on the ECA model listens to business flow events in multiple business scenarios and obtains each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events; In the preset process nodes corresponding to multiple business scenarios, the target process node corresponding to each business event is obtained, and the target H5 page corresponding to the event node of each business event is executed based on the target process node. Each preset process node includes multiple event nodes, and each event node corresponds to an H5 page. Based on the event nodes of each business event, determine the next event to be processed corresponding to each business event in each target process node; The pending events are treated as business events, and the process engine is returned to execute the steps of obtaining the target process nodes corresponding to each business event. The process engine determines the next event to be processed corresponding to each business event in each target process node based on the event nodes of each event. The steps include: When the target H5 page is completed, based on the event nodes of each business event, determine whether there is a completed process node in the target process node. If it does not exist, the corresponding target message event is determined based on the event nodes of each business event and the H5 page; Based on the target message event, the Action module determines the next event to be processed for each business event in each target process node.

2. The business process execution method as described in claim 1, characterized in that, After determining whether the target process node has a completed process node based on the event nodes of each business event, the method further includes: If they exist, then based on the completed process nodes, determine the unfinished business events corresponding to the event nodes of each business event; Based on the event nodes of incomplete business events and the H5 page, the corresponding target message event is determined.

3. The business process execution method as described in claim 1, characterized in that, The step of obtaining the target process node corresponding to each business event from the preset process nodes corresponding to multiple business scenarios includes: Identify the target business scenario corresponding to each business event, and obtain the target process node corresponding to the target business scenario from the preset process nodes corresponding to multiple business scenarios.

4. The business process execution method as described in any one of claims 1 to 3, characterized in that, Before the step of the process engine based on the ECA model listening to business flow events in multiple business scenarios, it also includes: Obtain H5 pages corresponding to multiple business scenarios, and use each H5 page as an ECA node of the process engine; Based on the ECA node, preset process nodes corresponding to the business function processes of each business scenario are generated.

5. The business process execution method as described in claim 4, characterized in that, The steps for obtaining H5 pages corresponding to multiple business scenarios include: Obtain H5 page capabilities corresponding to multiple business scenarios, and set the trigger events and execution conditions for each H5 page capability to obtain H5 pages corresponding to multiple business scenarios.

6. A business process execution device, characterized in that, The business process execution device includes: The listening module is used to listen to business flow events in multiple business scenarios and obtain each business event in the business flow events, wherein the business flow events include input flow events, page request flow events and / or message events; The acquisition module is used to acquire the target process node corresponding to each business event in the preset process nodes corresponding to multiple business scenarios, and execute the target H5 page corresponding to the event node of each business event based on the target process node. Each preset process node includes multiple event nodes, and each event node corresponds to an H5 page. The determination module is used to determine the next event to be processed for each business event in each target process node based on the event node of each business event. The loop module is used to treat the event to be processed as the business event and return to the execution process engine to obtain the steps of the target process node corresponding to each business event; The determining module is further configured to: When the target H5 page is completed, based on the event nodes of each business event, determine whether there is a completed process node in the target process node. If it does not exist, the corresponding target message event is determined based on the event nodes of each business event and the H5 page; Based on the target message event, the Action module determines the next event to be processed for each business event in each target process node.

7. A business process execution device, characterized in that, The business process execution device includes: a memory, a processor, and a business process execution program stored in the memory and executable on the processor. When the business process execution program is executed by the processor, it implements the steps of the business process execution method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a business process execution program, which, when executed by a processor, implements the steps of the business process execution method as described in any one of claims 1 to 5.

Images