A method, system, device, medium, and product for configuring a task flow.

Abstract

This application provides a method, system, device, medium, and product for configuring task flows. The method, applied to a flow engine, includes: presenting a first task flow and a flow configuration interface; obtaining first configuration information in the flow configuration interface; wherein the first configuration information is used for batch configuration of each task node in the first task flow; responding to a configuration operation on a target task node in the first task flow, presenting second configuration information related to the target task node from the first configuration information in a node configuration interface for configuring the target task node; receiving modification operations related to the second configuration information in the node configuration interface, and determining the target configuration information for the target task node based on the modification operations. This method improves configuration efficiency through flow-level configuration functions and achieves personalized configuration for task nodes through node-level configuration functions.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly to a method, system, electronic device, computer-readable storage medium, and computer program product for configuring a task flow. Background Technology

[0002] With the continuous development of computer technology, workflow engines have emerged. A workflow engine typically refers to a system used to define, execute, and manage task flows (also known as workflows). Users can arrange task nodes and the execution order between them. In this way, the workflow engine can process task nodes sequentially according to their execution order, thus advancing the task flow.

[0003] After orchestrating the task flow, users need to configure the task nodes. Therefore, how to efficiently configure each task node has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method for configuring task flows. This method is designed for task flow configuration scenarios and balances convenience and personalization needs. This application also provides a system, electronic device, computer-readable storage medium, and computer program product corresponding to the above method.

[0005] Firstly, this application provides a method for configuring a task flow, the method comprising:

[0006] Presents the first task flow and flow configuration interface;

[0007] In the process configuration interface, first configuration information is obtained; wherein, the first configuration information is used to perform batch configuration for each task node in the first task process.

[0008] In response to the configuration operation for the target task node in the first task flow, the second configuration information related to the target task node in the first configuration information is presented in the node configuration interface for configuring the target task node;

[0009] In the node configuration interface, a modification operation related to the second configuration information is received, and the target configuration information of the target task node is determined based on the modification operation.

[0010] In some possible implementations, obtaining the first configuration information in the process configuration interface includes:

[0011] In the process configuration interface, a configuration operation for the first task process is received; wherein the configuration operation for the first task process is used to configure the operation type associated with each task node in the first task process.

[0012] Based on the configuration operation for the first task process, the first configuration information is determined.

[0013] In some possible implementations, determining the first configuration information based on the configuration operation for the first task flow includes:

[0014] Based on the configuration operation for the first task flow, first configuration information indicating at least one of the following is determined: whether to allow the execution of an operation corresponding to the operation type, the operation rules of the operation type, or the presentation mode of the operation control corresponding to the operation type.

[0015] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type. The step of receiving a modification operation related to the second configuration information in the node configuration interface, and determining the target configuration information of the target task node based on the modification operation, includes:

[0016] In the node configuration interface, a first modification operation is received for the second configuration information; wherein, the first modification operation is used to change the allowed execution of operations corresponding to the operation type to the disallowed execution of operations corresponding to the operation type;

[0017] Based on the first modification operation, the target configuration information of the target task node is determined, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed.

[0018] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type. The step of receiving modification operations related to the second configuration information in the node configuration interface includes:

[0019] In the node configuration interface, a second modification operation is received for the second configuration information;

[0020] In response to the second modification operation instruction, changing the operation corresponding to the operation type from not allowing execution to allowing execution of the operation type, the second modification operation is not effective.

[0021] In some possible implementations, the method further includes:

[0022] The node configuration interface displays a prompt message indicating that the second modification operation is not allowed.

[0023] In some possible implementations, the second configuration information includes configuration information indicating operation rules for operation types, wherein the operation rules for operation types allow task nodes to configure separately for target operation types;

[0024] The step of receiving modification operations related to the second configuration information in the node configuration interface includes:

[0025] In the node configuration interface, the operation rule configuration operation for the target operation type associated with the target task node is received.

[0026] In some possible implementations, the target task node is an approval node, and the target operation type includes a return type;

[0027] The step of receiving operation rule configuration operations for the target operation type associated with the target task node in the node configuration interface includes:

[0028] In the node configuration interface, an operation rule configuration operation for the return type is received. The operation rule configuration operation is used to configure a return strategy. The return strategy includes at least one of the following: return to the initiator, or return to any preceding node of the approval node in the first task flow.

[0029] In some possible implementations, the method further includes:

[0030] In the node configuration interface, a jump control is presented, which is used to trigger the presentation of the process configuration interface.

[0031] In some possible implementations, the method further includes:

[0032] In response to the execution of the first task process instance to the target task node, the operation page of the target task node is presented according to the target configuration information; wherein, the first task process instance is a task process instance generated after the first task process is triggered.

[0033] In some possible implementations, the target configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the operation page of the target task node presents a target operation control, which is used to trigger the operation corresponding to the allowed operation type.

[0034] Secondly, this application provides a task flow configuration system, which includes:

[0035] The presentation module is used to present the first task flow and the flow configuration interface;

[0036] The acquisition module is used to acquire first configuration information from the process configuration interface; wherein, the first configuration information is used to perform batch configuration for each task node in the first task process;

[0037] The presentation module is further configured to respond to a configuration operation for a target task node in the first task flow, and to present second configuration information related to the target task node in the first configuration information in the node configuration interface for configuring the target task node.

[0038] The determination module is used to receive modification operations related to the second configuration information in the node configuration interface, and determine the target configuration information of the target task node based on the modification operations.

[0039] In some possible implementations, the acquisition module is specifically used for:

[0040] In the process configuration interface, a configuration operation for the first task process is received; wherein the configuration operation for the first task process is used to configure the operation type associated with each task node in the first task process.

[0041] Based on the configuration operation for the first task process, the first configuration information is determined.

[0042] In some possible implementations, the acquisition module is specifically used for:

[0043] Based on the configuration operation for the first task flow, first configuration information indicating at least one of the following is determined: whether to allow the execution of an operation corresponding to the operation type, the operation rules of the operation type, or the presentation mode of the operation control corresponding to the operation type.

[0044] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the determining module is specifically used for:

[0045] In the node configuration interface, a first modification operation is received for the second configuration information; wherein, the first modification operation is used to change the allowed execution of operations corresponding to the operation type to the disallowed execution of operations corresponding to the operation type;

[0046] Based on the first modification operation, the target configuration information of the target task node is determined, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed.

[0047] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the determining module is specifically used for:

[0048] In the node configuration interface, a second modification operation is received for the second configuration information;

[0049] In response to the second modification operation instruction, changing the operation corresponding to the operation type from not allowing execution to allowing execution of the operation type, the second modification operation is not effective.

[0050] In some possible implementations, the presentation module is also used for:

[0051] The node configuration interface displays a prompt message indicating that the second modification operation is not allowed.

[0052] In some possible implementations, the second configuration information includes configuration information indicating operation rules for operation types, wherein the operation rules for operation types allow task nodes to configure separately for target operation types; the determining module is specifically used for:

[0053] In the node configuration interface, the operation rule configuration operation for the target operation type associated with the target task node is received.

[0054] In some possible implementations, the target task node is an approval node, and the target operation type includes a return type; the determining module is specifically used for:

[0055] In the node configuration interface, an operation rule configuration operation for the return type is received. The operation rule configuration operation is used to configure a return strategy. The return strategy includes at least one of the following: return to the initiator, or return to any preceding node of the approval node in the first task flow.

[0056] In some possible implementations, the presentation module is also used for:

[0057] In the node configuration interface, a jump control is presented, which is used to trigger the presentation of the process configuration interface.

[0058] In some possible implementations, the presentation module is also used for:

[0059] In response to the execution of the first task process instance to the target task node, the operation page of the target task node is presented according to the target configuration information; wherein, the first task process instance is a task process instance generated after the first task process is triggered.

[0060] In some possible implementations, the target configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the operation page of the target task node presents a target operation control, which is used to trigger the operation corresponding to the allowed operation type.

[0061] Thirdly, this application provides an electronic device including a processor and a memory. The processor and the memory communicate with each other. The processor is used to execute instructions stored in the memory to cause the electronic device to perform a task flow configuration method as described in the first aspect or any implementation thereof.

[0062] Fourthly, this application provides a computer-readable storage medium storing instructions that instruct an electronic device to execute the configuration method of the task flow described in the first aspect or any implementation thereof.

[0063] Fifthly, this application provides a computer program product containing instructions that, when run on an electronic device, causes the electronic device to execute the configuration method of the task flow described in the first aspect or any implementation thereof.

[0064] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods.

[0065] As can be seen from the above technical solutions, this application has the following advantages:

[0066] This application provides a task flow configuration method applied to a flow engine. First, a first task flow and a flow configuration interface are presented. In the flow configuration interface, first configuration information is obtained, wherein the first configuration information is used for batch configuration of each task node in the first task flow. In response to the configuration operation for the target task node in the first task flow, in the node configuration interface for configuring the target task node, second configuration information related to the target task node in the first configuration information is presented. Then, in the node configuration interface, modification operation related to the second configuration information is received, and the target configuration information of the target task node is determined according to the modification operation.

[0067] In this method, the workflow engine provides both workflow-level and node-level configuration capabilities. After the user completes the workflow-level configuration, the task nodes automatically acquire the workflow-level configuration information. Simultaneously, the workflow engine also allows users to modify the configuration information of task nodes. Thus, the workflow-level configuration capability enables unified configuration for each task node in the workflow, improving configuration efficiency, while the node-level configuration capability enables personalized configuration for each task node, balancing convenience and individual needs. Attached Figure Description

[0068] To more clearly illustrate the technical methods of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below.

[0069] Figure 1 A flowchart illustrating a task flow configuration method provided in an embodiment of this application;

[0070] Figures 2A to 2C A schematic diagram of a task flow configuration page provided in an embodiment of this application;

[0071] Figure 3 A schematic diagram of an operation rule configuration interface provided in an embodiment of this application;

[0072] Figures 4A to 4D A schematic diagram of a task flow configuration page provided in an embodiment of this application;

[0073] Figure 5 A schematic diagram of an operation page provided in an embodiment of this application;

[0074] Figure 6 A schematic diagram of the structure of a task flow configuration system provided in an embodiment of this application;

[0075] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0076] The terms "first" and "second" used in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature.

[0077] First, some technical terms and application scenarios involved in the embodiments of this application will be introduced.

[0078] A workflow engine, also known as a workflow orchestration engine or workflow orchestration tool, is typically used to define, execute, and manage task workflows. Workflow engines usually support visual operations, allowing users (such as workflow orchestrators) to arrange task nodes and generate task workflows through drag-and-drop and connection operations on the workflow orchestration page.

[0079] A task flow, also known as a workflow or process template, can be understood as an execution sequence consisting of a series of task nodes. The dependencies between task nodes can represent the execution order of the task nodes.

[0080] A task node can be understood as a module used to perform tasks, thereby achieving specific functions or providing specific capabilities. Different types of task nodes are used to perform different types of tasks; for example, a form-filling task node can be used to perform form-filling tasks, and an approval node can be used to perform approval tasks.

[0081] During the process of users (such as workflow orchestrators) orchestrating task flows, task handlers can be assigned to task nodes. Considering that task nodes may be processed automatically or manually, the task handler can be set to the system or the task handler. For example, the task handler for filling in a task node can be the initiator, and the task handler for the approval node can be the direct supervisor, department head, etc.

[0082] Process instantiation can be understood as the process of creating an independent task process instance based on a task process. A task process instance represents a specific execution of the task process, including the execution logic of the task process (i.e., each task node and the execution order of the task nodes) and instantiation data. Different task process instances run in parallel, and the running state and instantiation data of each task process instance are independent of each other.

[0083] Task nodes are typically associated with at least one operation type. The operation type associated with a task node can be understood as the action that a task handler can perform on the task node within a task workflow instance. For example, for an approval node, a task handler can perform an "approve" or "reject" operation; the operation types associated with an approval node can include "approve" and "reject" types.

[0084] After orchestrating the task flow, users (such as the orchestrator) can configure the task nodes. For example, users can configure the operation types associated with each task node. Typically, users need to configure each task node individually in its configuration interface. However, this method requires users to perform configuration operations on each task node, which is cumbersome and inefficient for task flow configuration.

[0085] In view of this, this application provides a method for configuring a task flow. This method is applied to a flow engine. First, a first task flow and a flow configuration interface are presented. In the flow configuration interface, first configuration information is obtained, wherein the first configuration information is used for batch configuration of each task node in the first task flow. In response to a configuration operation for a target task node in the first task flow, in the node configuration interface for configuring the target task node, second configuration information related to the target task node from the first configuration information is presented. Then, in the node configuration interface, a modification operation related to the second configuration information is received. Based on the modification operation, the target configuration information of the target task node is determined.

[0086] In this method, the workflow engine provides both workflow-level and node-level configuration capabilities. After the user completes the workflow-level configuration, the task nodes automatically acquire the workflow-level configuration information. Simultaneously, the workflow engine also allows users to modify the configuration information of task nodes. Thus, the workflow-level configuration capability enables unified configuration for each task node in the workflow, improving configuration efficiency, while the node-level configuration capability enables personalized configuration for each task node, balancing convenience and individual needs.

[0087] To facilitate understanding of the technical solutions provided in the embodiments of this application, the following description will be provided in conjunction with the accompanying drawings.

[0088] See Figure 1 The diagram shown is a flowchart of a task flow configuration method provided in this application embodiment. This method can be executed by a flow engine, and the method specifically includes:

[0089] S101: Presents the first task flow and flow configuration interface.

[0090] In this embodiment, the first task flow can be a task flow with process execution logic. That is, the first task flow can be a task flow generated by arranging task nodes and the execution order between task nodes.

[0091] The process configuration interface can be understood as the interface provided by the process engine for configuring the first task process. In this embodiment, the user can configure the first task process at the process level through the process configuration interface. For example, the user can configure the task name, rule events, etc. of the first task process through the process configuration interface.

[0092] This application does not limit the presentation method of the first task flow and the flow configuration interface. In some embodiments, the first task flow and the flow configuration interface can be presented side by side, for example, the first task flow is presented in the left half of the display area, and the flow configuration interface is presented in the right half of the display area. In other embodiments, the first task flow and the flow configuration interface can also be presented overlappingly, for example, the first task flow is presented in the display area, and the flow configuration interface is presented in the display area as a floating box.

[0093] S102: Obtain the first configuration information in the process configuration interface.

[0094] In this embodiment, the first configuration information is used for batch configuration of each task node in the first task flow. Since the flow configuration interface is used for flow-level configuration, the first configuration information can be understood as unified configuration information for each task node in the first task flow, configured at the task flow level.

[0095] In some embodiments, the first configuration information may be related to the operation type. Specifically, in the process configuration interface, a configuration operation for the first task process is received, and then the first configuration information is determined based on the configuration operation for the first task process.

[0096] The configuration options for the first task flow can be used to configure the operation types associated with each task node in the first task flow. In other words, users can perform unified and batch configuration of the operation types associated with each task node in the flow configuration interface.

[0097] In some possible implementations, the process configuration interface can present configuration items related to the operation type in a table format. Specifically, each row in the table represents an operation type, and each column represents a configuration item. Users can trigger configuration operations for the first task process in the table of the process configuration interface.

[0098] In this embodiment of the application, the operation types associated with each task node in the first task flow may include the operation types supported by each task node in the first task flow. For example, the first task flow includes task node A and task node B. The operation types supported by task node A include operation type A1 and operation type A2, and the operation types supported by task node B include operation type B1, operation type B2, and operation type B3. The operation types associated with each task node in the first task flow are operation type A1, operation type A2, operation type B1, operation type B2, and operation type B3.

[0099] With specific examples, the first task flow includes an approval node, a task completion node, and a copy node. The operation types associated with the approval node (i.e., the operation types supported by the approval node) are: agree, reject, return, sign, transfer, copy, initiate group chat, and temporary. The operation types associated with the task completion node (i.e., the operation types supported by the task completion node) are: transfer, copy, initiate group chat, and temporary. The operation type associated with the copy node (i.e., the operation type supported by the copy node) is: initiate group chat. Therefore, the operation types associated with each task node in the first task flow are: agree, reject, return, sign, transfer, copy, initiate group chat, and temporary.

[0100] It should be noted that the embodiments of this application do not limit the source of the operation type. In some embodiments, the operation type can be predefined in the process engine, while in other embodiments, the operation type can be user-defined.

[0101] In some embodiments, the first configuration information may indicate different types of information. Specifically, based on the configuration operation for the first task flow, the first configuration information indicating at least one of the following is determined: whether to allow the execution of an operation corresponding to the operation type, the operation rules of the operation type, or the presentation mode of the operation control corresponding to the operation type.

[0102] In other words, the first configuration information can include information related to multiple configuration items for the operation type. Among these, whether to allow the execution of the operation corresponding to the operation type can be understood as whether the task node enables the operation corresponding to the operation type. The operation rules for the operation type can be understood as the specific implementation method of the operation corresponding to the operation type. The presentation method of the operation controls corresponding to the operation type can be understood as the rules for displaying the operation controls corresponding to the operation type, such as displaying names and display icons.

[0103] Taking the first configuration information indicating whether to allow the execution of the operation corresponding to the operation type as an example, in this embodiment of the application, the operation type associated with each task node in the first task process includes the operation types that each task node in the first task process supports to execute. Users can configure whether to enable the operation corresponding to the operation type that each task node in the first task process supports to execute.

[0104] For example, when the operation types associated with each task node in the first task flow include operation type A1, operation type A2, and operation type B1, the first configuration information can indicate that the operation corresponding to operation type A1 is not allowed, the operation corresponding to operation type A2 is allowed, and the operation corresponding to operation type B1 is allowed.

[0105] Continuing from the previous example, when the configuration items related to the operation type are presented in the form of a table in the process configuration interface, the table includes rows corresponding to operation type A1, operation type A2 and operation type B1, as well as columns used to configure whether to allow the execution of operations corresponding to the operation type. Users can perform configuration operations for each operation type in the table to generate the first configuration information.

[0106] S103: In response to the configuration operation for the target task node in the first task process, the second configuration information related to the target task node in the node configuration interface for configuring the target task node is presented in the first configuration information.

[0107] In this embodiment of the application, since the first configuration information is process-level configuration information for each task node in the first task process, after the user performs process-level configuration and generates the first configuration information, the first configuration information will be automatically provided to the task nodes in the first task process as the initial configuration information for each task node in the first task process.

[0108] The target task node can be any task node in the first task process. The configuration operation for the target task node in the first task process can be understood as the node-level configuration operation for the target task node. The node configuration interface can be understood as the interface provided by the process engine for configuring the target task node.

[0109] This application does not limit the presentation method of the node configuration interface. For example, the node configuration interface can be presented in association with the first task flow.

[0110] The second configuration information is the information related to the target task node in the first configuration information; that is, the second configuration information is at least a portion of the information in the first configuration information. Specifically, when the first configuration information includes information related to multiple configuration items of the operation type, the second configuration information may include the operation type information associated with the target task node in the first configuration information.

[0111] For example, when the operation types associated with each task node in the first task flow include operation type A1, operation type A2 and operation type B1, the first configuration information includes the configuration information related to operation type A1, operation type A2 and operation type B1. The operation types associated with the target task node are operation type A1 and operation type A2. At this time, the second configuration information is the configuration information related to operation type A1 and operation type A2 in the first configuration information.

[0112] Similarly, the node configuration interface can also present the second configuration information in a table format. Continuing the previous example, the table in the node configuration interface includes rows corresponding to operation type A1 and operation type A2. The content presented in the table in the node configuration interface is the same as the configuration information related to operation type A1 in the first configuration information. For example, the first configuration information indicates that the operation corresponding to operation type A1 is not allowed, and the operation corresponding to operation type A2 is allowed. The second configuration information also indicates that the operation corresponding to operation type A1 is not allowed, and the operation corresponding to operation type A2 is allowed.

[0113] Thus, in this embodiment of the application, by providing a process-level configuration function, each task node in the first task process is uniformly configured, and the first configuration information at the process level is automatically assigned to the task node, realizing batch configuration of each task node in the task process. When configuring the node at the node level for the target task node, the first configuration information is used as the initial configuration information of the target task node, presenting the process-level configuration information related to the target node.

[0114] S104: In the node configuration interface, receive modification operations related to the second configuration information, and determine the target configuration information of the target task node based on the modification operations.

[0115] The modification operations related to the second configuration information can be understood as operations that modify the second configuration information. In this embodiment, the process engine provides node-level configuration functionality, allowing users to modify process-level configuration information related to the target node to achieve more granular, node-level configuration, thereby completing the configuration for the target task node.

[0116] Therefore, for task flow configurations without personalized requirements, users can use the flow-level configuration function to achieve unified configuration for each task node in the task flow, improving configuration efficiency. For task flow configurations with personalized configuration requirements, after configuring at the flow level, users can also configure the task nodes with personalized configuration needs at the node level, meeting diverse business requirements and improving the applicability of task flow configurations.

[0117] In some embodiments, the second configuration information includes configuration information indicating whether the execution of an operation corresponding to the operation type is allowed. In the node configuration interface, a first modification operation is received regarding the second configuration information. Then, based on the first modification operation, the target configuration information for the target task node is determined. The first modification operation is used to change the setting from allowing the execution of operations corresponding to the operation type to disallowing the execution of operations corresponding to the operation type. The target configuration information indicates that the execution of operations corresponding to the operation type is disallowed.

[0118] In other words, when the process-level configuration allows the execution of operations corresponding to the operation type, the user can modify the node-level configuration to disallow the execution of operations corresponding to the operation type on the target task node. For example, the operation types associated with the target task node include operation type A1 and operation type A2. The configuration information related to operation type A1 and operation type A2 in the first configuration information (i.e., the second configuration information) indicates that the execution of operations corresponding to operation type A1 and operation type A2 is allowed. The user can modify the second configuration information so that the target configuration information of the target task node indicates that the execution of operations corresponding to operation type A1 and / or operation type A2 is not allowed.

[0119] Thus, when a task node in the first task process needs to enable certain operation types, but the target task node does not need to enable these operation types, the second configuration information can be modified through node-level configuration to disable the operation types of the target task node, thereby meeting the personalized configuration needs of the task node.

[0120] In other embodiments, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type. In the node configuration interface, a second modification operation is received regarding the second configuration information. In response to the second modification operation, the disallowed execution of the operation corresponding to the operation type is changed to allowed execution of the operation corresponding to the operation type. The second operation does not take effect.

[0121] In other words, when the process-level configuration disallows operations corresponding to the operation type, the user cannot modify the node-level configuration to allow the target task node to execute operations corresponding to the operation type. For example, if the operation types associated with the target task node include operation type A1 and operation type A2, and the second configuration information related to operation type A1 and operation type A2 in the first configuration information indicates that operations corresponding to operation type A1 and operation type A2 are not allowed, the user cannot modify the second configuration information, and the target configuration information of the target task node will still indicate that operations corresponding to operation type A1 and operation type A2 are not allowed.

[0122] Furthermore, a prompt message can be displayed in the node configuration interface. This prompt message indicates that the second modification operation is not allowed. In other words, when a user attempts to change an operation of a prohibited type to an allowed type in the node-level configuration, the prompt message informs the user that modification is not possible and that the target configuration information of the target task node is identical to the second configuration information.

[0123] Thus, process-level configuration takes precedence over node-level configuration. If certain operation types have been disabled in the process-level configuration, then each task node in the first task process cannot enable that operation type, thus enabling batch disabling of operation types at the process level.

[0124] In other embodiments, the second configuration information includes configuration information indicating the operation rules for the operation type, wherein the operation rules for the operation type allow task nodes to configure separately for the target operation type. That is, in the embodiments of this application, the process-level configuration can configure a specific implementation method of an operation corresponding to an operation type for each task node in the first task process, and also supports different task nodes to configure operation rules separately for the same operation type (i.e., the target operation type).

[0125] In practice, the node configuration interface receives operation rule configuration operations for the target operation type associated with the target task node. In other words, for target operation types that support separate configuration of operation rules for different task nodes, users can configure operation rules individually in the node configuration interface. Thus, for the same operation type, different operation rules can be configured based on the specific business needs of the task node, meeting personalized requirements.

[0126] Specifically, the target task node can be an approval node, and the target operation type includes return types. In other words, the process-level configuration allows different task nodes to be configured with operation rules for return types.

[0127] In this case, the node configuration interface receives operation rule configuration operations for the return type. These operation rule configuration operations are used to configure the return strategy, which includes at least one of the following: return to the initiator, or return to any preceding node of the approval node in the first task flow.

[0128] In other words, in this embodiment of the application, different operation rules are allowed for different approval nodes. For some approval nodes, the return policy can be configured to allow return to the initiator, while for other approval nodes, the return policy can be configured to allow return to any preceding node of the approval node in the first task flow.

[0129] Furthermore, this application embodiment also supports jumping to process-level configuration when performing node-level configuration. Specifically, a jump control is presented in the node configuration interface, which is used to trigger the presentation of the process configuration interface.

[0130] By providing a jump control in the node configuration interface, users can quickly switch to the process configuration interface when configuring nodes. This allows users to quickly modify process-level configuration information at any time.

[0131] In this method, the workflow engine provides both workflow-level and node-level configuration capabilities. After the user completes the workflow-level configuration, the task nodes automatically acquire the workflow-level configuration information. Simultaneously, the workflow engine also allows users to modify the configuration information of task nodes. Thus, the workflow-level configuration capability enables unified configuration for each task node in the workflow, improving configuration efficiency, while the node-level configuration capability enables personalized configuration for each task node, balancing convenience and individual needs.

[0132] After configuring the first task process using the process-level and node-level configurations provided in this application embodiment, the page can be presented based on the target configuration information of the target task node during the execution of the first task process. Specifically, in response to the execution of the first task process instance to the target task node, the operation page of the target task node is presented according to the target configuration information. Here, the first task process instance is the task process instance generated after the first task process is triggered.

[0133] In other words, when the first task process instance executes to the target task node, the operation page of the task handler of the target task node is rendered based on the target configuration information, so that the content displayed on the operation page of the target task node matches the target configuration information.

[0134] In some possible implementations, the target configuration information includes configuration information indicating whether to allow the execution of operations corresponding to the operation type. The operation page of the target task node displays target operation controls, which are used to trigger operations corresponding to the allowed operation types.

[0135] In other words, the types of operations allowed to be executed by the target task node are configured through process-level and node-level configurations. The target task node's operation page then displays the target operation controls corresponding to the allowed operation types.

[0136] For example, the target configuration information of the target task node indicates that the allowed operation types include operation type A1 and operation type A2. The operation page of the target task node displays target operation controls for triggering the operation corresponding to operation type A1 and the operation corresponding to operation type A2. Thus, the task handler of the target task node can trigger the corresponding operation through the target operation controls on the target task node's operation page.

[0137] Furthermore, the target configuration information can also indicate the presentation method of the operation controls corresponding to the operation type. In this case, the presentation method of the target operation controls on the operation page of the target task node can match the target configuration information, for example, the target operation controls can be presented with the presentation name and presentation icon indicated by the target configuration information.

[0138] The configuration method for the task flow provided in this application has been introduced above. The following will explain it in conjunction with specific scenarios.

[0139] See Figures 2A to 2C The diagram shown illustrates the task flow configuration page. Figure 2A In the task flow configuration page 20, there are a first task flow presentation area 21 and a flow configuration interface 22. The first task flow includes four task nodes: "Employee fills out form", "Direct supervisor approves", "Finance manager approves", and "Finance director approves". The flow configuration interface 22 is used to configure the flow at the flow level for the first task flow.

[0140] Specifically, users can configure the task flow name and the operation type associated with each task node in the first task flow in the process configuration interface 22. The process configuration interface 22 presents the configuration items related to the operation type in the form of a table. The operation types associated with each task node in the first task flow include agree type, refuse type, transfer type, return type, initiate group chat type, save form type, initiator cancel type, and initiator reminder type. The configuration items include whether to allow the operation corresponding to the operation type to be executed (i.e., the column corresponding to "operation type"), the presentation name of the operation control (i.e., the column corresponding to "button text"), the presentation icon of the operation control (i.e., the column corresponding to "button style"), and the operation rules of the operation type (i.e., the column corresponding to "advanced configuration item settings").

[0141] Taking the transfer type and return type as examples, in the first configuration information at the process level, it indicates that the operation corresponding to the transfer type is not allowed to be executed, the operation corresponding to the return type is allowed to be executed, the operation control corresponding to the return type is presented as "presentation name is rejection, presentation style is style D", and the operation rule for the return type is "allow task nodes to configure operation rules for return types respectively".

[0142] like Figure 2B As shown, when the first configuration information indicates that the operation corresponding to the operation type (i.e., the transfer type) is not allowed to be executed, if the user triggers a configuration operation at the process level for that operation type, the message "Please allow editing after operation" will be displayed, informing the user that subsequent configuration can only be performed after the operation type is executed.

[0143] like Figure 2CAs shown, for situations like "button style" where there are multiple options, multiple options are presented to the user by displaying the first drop-down menu 222. The user can select from these options to complete the process-level configuration.

[0144] In some embodiments, if there is only one option for the operation type, the user can directly input configuration information to complete the process-level configuration by configuring in place.

[0145] In other embodiments, a configuration interface for configuration items is provided for process-level configuration. See also Figure 3 The diagram shown illustrates the operation rule configuration interface. In the operation rule configuration interface 30, users can configure operation rules for initiating group chats. Users can enter the group name and select the robot to initiate the group chat in the operation rule configuration interface 30. After the user completes the configuration, the configuration information in the operation rule configuration interface 30 is semantically backfilled into the process configuration interface 22. For example, the process configuration interface 22 may display "Create group using default application".

[0146] See Figures 4A to 4D The diagram shown illustrates the task flow configuration page, as follows: Figure 4A As shown, in the node configuration interface 41 of the task flow configuration page 40, the second configuration information of the target task node is presented in a table format. Among them, the operation types associated with the target task node include agree type, refuse type, transfer type, return type, initiate group chat type, and save form type. The configuration items of the operation types associated with the target task node in the second configuration information are the same as those in the first configuration information.

[0147] like Figure 4B As shown, the second configuration information indicates that the operation corresponding to the transfer type is not allowed to be executed. At this time, if the user triggers the second modification operation on the second configuration information, that is, changes the operation that is not allowed to be executed to the operation that is allowed to be executed, the prompt message 401 will be displayed, informing the user that the second modification operation is not allowed to be executed.

[0148] The 401 error message may include a jump control (i.e., the text "Process Configuration"), which the user can trigger to display the process configuration interface. For example... Figure 4C As shown, after the jump control is triggered, the task flow configuration page 40 displays the node configuration interface 42 and the flow configuration interface 43 side by side.

[0149] Specifically, if the second configuration information indicates that the operation rule for the return type is to allow different task nodes to configure the return type separately, the user can modify the operation rule for the return type of the target task node in the node configuration interface 42. By presenting the second drop-down menu 402, the user can select the operation rule for the return type in the second drop-down menu 402, such as returning to the initiator or returning to any preceding node of the approval node in the first task process.

[0150] like Figure 4D As shown, if the second configuration information indicates that the operation rule for the return type is to return to the initiator, that is, different task nodes are not allowed to configure the return type separately, the user cannot configure the operation rule for the return type in the target task node in the node configuration interface. When the user triggers the modification operation for the operation rule of the return type, the prompt message 403 will be displayed, informing the user that the operation rule needs to be changed in the process-level configuration before the operation rule can be configured separately for the same operation type of different task nodes.

[0151] After configuring the first task flow, an instance of the first task flow is generated in response to its triggering operation. For example... Figure 5 As shown, in response to the execution of the first task process instance reaching the target task node, the operation page 50 of the target task node is presented according to the target configuration information. When the target configuration information indicates that the operation corresponding to the agree type, refuse type, transfer type, return type, and initiate group chat type is allowed, the operation page 50 presents the target operation controls corresponding to the agree type, refuse type, transfer type, return type, and initiate group chat type. In this way, the task handler of the target task node can trigger the corresponding operation through the target operation controls.

[0152] The above text combined Figures 1 to 5 The configuration method of the task flow provided in the embodiments of this application has been described in detail. The system and device provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0153] See Figure 6 The diagram shows the structure of the task flow configuration system. The system 60 includes:

[0154] Presentation module 601 is used to present the first task flow and the flow configuration interface;

[0155] The acquisition module 602 is used to acquire first configuration information from the process configuration interface; wherein, the first configuration information is used to perform batch configuration for each task node in the first task process;

[0156] The presentation module 601 is also configured to respond to a configuration operation for a target task node in the first task flow, and to present second configuration information related to the target task node in the first configuration information in the node configuration interface for configuring the target task node.

[0157] The determination module 603 is used to receive modification operations related to the second configuration information in the node configuration interface, and determine the target configuration information of the target task node based on the modification operations.

[0158] In some possible implementations, the acquisition module 602 is specifically used for:

[0159] In the process configuration interface, a configuration operation for the first task process is received; wherein the configuration operation for the first task process is used to configure the operation type associated with each task node in the first task process.

[0160] Based on the configuration operation for the first task process, the first configuration information is determined.

[0161] In some possible implementations, the acquisition module 602 is specifically used for:

[0162] Based on the configuration operation for the first task flow, first configuration information indicating at least one of the following is determined: whether to allow the execution of an operation corresponding to the operation type, the operation rules of the operation type, or the presentation mode of the operation control corresponding to the operation type.

[0163] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the determining module 603 is specifically used for:

[0164] In the node configuration interface, a first modification operation is received for the second configuration information; wherein, the first modification operation is used to change the allowed execution of operations corresponding to the operation type to the disallowed execution of operations corresponding to the operation type;

[0165] Based on the first modification operation, the target configuration information of the target task node is determined, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed.

[0166] In some possible implementations, the second configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the determining module 603 is specifically used for:

[0167] In the node configuration interface, a second modification operation is received for the second configuration information;

[0168] In response to the second modification operation instruction, changing the operation corresponding to the operation type from not allowing execution to allowing execution of the operation type, the second modification operation is not effective.

[0169] In some possible implementations, the presentation module 601 is further configured to:

[0170] The node configuration interface displays a prompt message indicating that the second modification operation is not allowed.

[0171] In some possible implementations, the second configuration information includes configuration information indicating operation rules for operation types, wherein the operation rules for operation types allow task nodes to be configured separately for target operation types; the determining module 603 is specifically used for:

[0172] In the node configuration interface, the operation rule configuration operation for the target operation type associated with the target task node is received.

[0173] In some possible implementations, the target task node is an approval node, and the target operation type includes a return type; the determining module 603 is specifically used for:

[0174] In the node configuration interface, an operation rule configuration operation for the return type is received. The operation rule configuration operation is used to configure a return strategy. The return strategy includes at least one of the following: return to the initiator, or return to any preceding node of the approval node in the first task flow.

[0175] In some possible implementations, the presentation module 601 is further configured to:

[0176] In the node configuration interface, a jump control is presented, which is used to trigger the presentation of the process configuration interface.

[0177] In some possible implementations, the presentation module 601 is further configured to:

[0178] In response to the execution of the first task process instance to the target task node, the operation page of the target task node is presented according to the target configuration information; wherein, the first task process instance is a task process instance generated after the first task process is triggered.

[0179] In some possible implementations, the target configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type, and the operation page of the target task node presents a target operation control, which is used to trigger the operation corresponding to the allowed operation type.

[0180] The task flow configuration system 60 according to the embodiments of this application can correspond to the execution of the methods described in the embodiments of this application, and the above and other operations and / or functions of each module / unit of the task flow configuration system 60 are respectively for implementing Figure 1 For the sake of brevity, the corresponding processes of each method in the illustrated embodiments will not be described in detail here.

[0181] This application also provides an electronic device. This electronic device is specifically used to implement, as described above. Figure 6 The illustrated embodiment shows the function of the task flow configuration system 60.

[0182] Figure 7 A structural schematic diagram of an electronic device 700 is provided, such as... Figure 7 As shown, the electronic device 700 includes a bus 701, a processor 702, a communication interface 703, and a memory 704. The processor 702, the memory 704, and the communication interface 703 communicate with each other via the bus 701.

[0183] The 701 bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0184] The processor 702 can be any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processor (DSP).

[0185] Communication interface 703 is used for external communication. For example, communication interface 703 can be used to communicate with a terminal.

[0186] Memory 704 may include volatile memory, such as random access memory (RAM). Memory 704 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0187] The memory 704 stores executable code, and the processor 702 executes the executable code to perform the configuration method of the aforementioned task flow.

[0188] Specifically, in achieving Figure 6 In the case of the illustrated embodiment, and Figure 6 When the modules or units of the task flow configuration system 60 described in the embodiment are implemented in software, the execution... Figure 6 The software or program code required for the functions of each module / unit can be partially or wholly stored in memory 704. Processor 702 executes the program code corresponding to each unit stored in memory 704 and executes the configuration method of the aforementioned task flow.

[0189] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the configuration method for the task flow applied to the configuration system 60 of the task flow described above.

[0190] This application also provides a computer program product comprising one or more computer instructions. When the computer instructions are loaded and executed on a computing device, all or part of the processes or functions described in this application are generated.

[0191] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, or data center to another website, computer, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0192] When the computer program product is executed by a computer, the computer performs any of the configuration methods of the aforementioned task flow. The computer program product can be a software installation package; when any of the configuration methods of the aforementioned task flow is required, the computer program product can be downloaded and executed on the computer.

[0193] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0194] The units described in the embodiments of this application can be implemented in software or hardware. The names of the units / modules do not necessarily limit the specific unit itself.

[0195] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0196] In the context of embodiments of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0197] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

[0198] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0199] 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 any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0200] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0201] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for configuring a task flow, characterized in that, Applied to a process engine, the method includes: Presents the first task flow and flow configuration interface; In the process configuration interface, first configuration information is obtained; wherein, the first configuration information is used to perform batch configuration for each task node in the first task process. In response to the configuration operation for the target task node in the first task flow, the second configuration information related to the target task node in the first configuration information is presented in the node configuration interface for configuring the target task node; In the node configuration interface, a modification operation related to the second configuration information is received, and the target configuration information of the target task node is determined based on the modification operation. In the node configuration interface, receiving modification operations related to the second configuration information, and determining the target configuration information of the target task node based on the modification operations, includes: When the second configuration information includes configuration information indicating that the operation corresponding to the operation type is allowed to be executed, a first modification operation is received for the second configuration information in the node configuration interface; wherein, the first modification operation is used to change the allowed operation corresponding to the operation type to not allowed operation corresponding to the operation type. Based on the first modification operation, the target configuration information of the target task node is determined, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed; When the second configuration information includes configuration information indicating that the operation corresponding to the operation type is not allowed to be performed, a second modification operation for the second configuration information is received in the node configuration interface. In response to the second modification operation instruction, changing the operation corresponding to the operation type from not allowing execution to allowing execution of the operation type, the second modification operation is not effective.

2. The method according to claim 1, characterized in that, The step of obtaining the first configuration information in the process configuration interface includes: In the process configuration interface, a configuration operation for the first task process is received; wherein the configuration operation for the first task process is used to configure the operation type associated with each task node in the first task process. Based on the configuration operation for the first task process, the first configuration information is determined.

3. The method according to claim 2, characterized in that, Determining the first configuration information based on the configuration operation for the first task flow includes: Based on the configuration operation for the first task flow, first configuration information indicating at least one of the following is determined: whether to allow the execution of an operation corresponding to the operation type, the operation rules of the operation type, or the presentation mode of the operation control corresponding to the operation type.

4. The method according to claim 1, characterized in that, The method further includes: The node configuration interface displays a prompt message indicating that the second modification operation is not allowed.

5. The method according to claim 2, characterized in that, The second configuration information includes configuration information for operation rules indicating the operation type, wherein the operation rules for the operation type allow task nodes to configure separately for the target operation type; The step of receiving modification operations related to the second configuration information in the node configuration interface includes: In the node configuration interface, the operation rule configuration operation for the target operation type associated with the target task node is received.

6. The method according to claim 5, characterized in that, The target task node is an approval node, and the target operation type includes a return type; The step of receiving operation rule configuration operations for the target operation type associated with the target task node in the node configuration interface includes: In the node configuration interface, an operation rule configuration operation for the return type is received. The operation rule configuration operation is used to configure a return strategy. The return strategy includes at least one of the following: return to the initiator, or return to any preceding node of the approval node in the first task flow.

7. The method according to claim 1, characterized in that, The method further includes: In the node configuration interface, a jump control is presented, which is used to trigger the presentation of the process configuration interface.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: In response to the execution of the first task process instance to the target task node, the operation page of the target task node is presented according to the target configuration information; wherein, the first task process instance is a task process instance generated after the first task process is triggered.

9. The method according to claim 8, characterized in that, The target configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to the operation type. The operation page of the target task node displays a target operation control, which is used to trigger the operation corresponding to the allowed operation type.

10. A task flow configuration system, characterized in that, The system includes: The presentation module is used to present the first task flow and the flow configuration interface; The acquisition module is used to acquire first configuration information from the process configuration interface; wherein, the first configuration information is used to perform batch configuration for each task node in the first task process; The presentation module is further configured to respond to a configuration operation for a target task node in the first task flow, and to present second configuration information related to the target task node in the first configuration information in the node configuration interface for configuring the target task node. The determination module is used to receive modification operations related to the second configuration information in the node configuration interface, and determine the target configuration information of the target task node based on the modification operations; The determining module is used for: When the second configuration information includes configuration information indicating that the operation corresponding to the operation type is allowed to be executed, a first modification operation is received for the second configuration information in the node configuration interface; wherein, the first modification operation is used to change the allowed operation corresponding to the operation type to not allowed operation corresponding to the operation type. Based on the first modification operation, the target configuration information of the target task node is determined, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed; When the second configuration information includes configuration information indicating that the operation corresponding to the operation type is not allowed to be performed, a second modification operation for the second configuration information is received in the node configuration interface. In response to the second modification operation instruction, changing the operation corresponding to the operation type from not allowing execution to allowing execution of the operation type, the second modification operation is not effective.

11. An electronic device, characterized in that, The electronic device includes a processor and a memory; The processor is configured to execute instructions stored in the memory, causing the electronic device to perform the method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, Includes instructions that instruct an electronic device to perform the method as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes computer-readable instructions for implementing the method according to any one of claims 1 to 9.

Images