Task process configuration method, system, device, medium and product

By combining process level and node level configuration, the problem of low efficiency in task process configuration is solved, the unified and personalized configuration of task nodes is realized, and configuration efficiency and applicability are improved.

CN119088444AActive Publication Date: 2024-12-06BEIJING ZITIAO NETWORK TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411237513.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-04
Publication Date
2024-12-06
Estimated Expiration
2044-09-04

AI Technical Summary

Technical Problem

In the prior art, in the task process configuration, users need to make cumbersome and separate configurations for each task node, resulting in low configuration efficiency and difficulty in taking into account convenience and personalized needs.

Method used

Provide a task process configuration method, which realizes unified configuration of task nodes through process-level configuration functions, and supports node-level configuration modification, combining process configuration interface and node configuration interface to realize batch configuration and personalized configuration.

Benefits of technology

It improves the configuration efficiency of task nodes in the task process, takes into account the unified configuration at the process level and personalized needs at the node level, meets diversified business needs, and improves the applicability of configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088444A_ABST
    Figure CN119088444A_ABST
Patent Text Reader

Abstract

The invention provides a task process configuration method, system and device, a medium and a product, the method is applied to a process engine, and the method comprises the following steps: presenting a first task process and a process configuration interface; obtaining first configuration information in the process configuration interface; wherein the first configuration information is used for performing batch configuration on each task node in the first task process; in response to a configuration operation for a target task node in the first task process, presenting second configuration information related to the target task node in the first configuration information in a node configuration interface configured for the target task node; and in the node configuration interface, receiving a modification operation related to the second configuration information, and determining target configuration information of the target task node according to the modification operation. In the method, the configuration efficiency is improved through a flow level configuration function, and personalized configuration for the task nodes is realized through a node level configuration function.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a task flow configuration method, system, electronic device, computer-readable storage medium, and computer program product. Background Art

[0002] With the continuous development of computer technology, process engines have emerged. Process engines usually refer to systems used to define, execute and manage task processes (also known as workflows). Users can arrange task nodes and the execution order between task nodes. In this way, the process engine can process task nodes in sequence according to the execution order of task nodes and advance the task process.

[0003] After arranging 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] The present application provides a method for configuring a task flow. The method is targeted at task flow configuration scenarios and can take into account both convenience and personalized needs. The present application also provides a system, electronic device, computer-readable storage medium, and computer program product corresponding to the above method.

[0005] In a first aspect, the present application provides a method for configuring a task flow, the method comprising:

[0006] Presenting the first task process and process configuration interface;

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

[0008] In response to a configuration operation on a target task node in the first task flow, presenting second configuration information related to the target task node in the first configuration information in a 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 according to the modification operation, the target configuration information of the target task node is determined.

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

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

[0012] First configuration information is determined according to the configuration operation for the first task flow.

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

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

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

[0016] In the node configuration interface, receiving a first modification operation for the second configuration information; wherein the first modification operation is used to modify the operation corresponding to the operation type to be not allowed to be executed;

[0017] According to the first modification operation, target configuration information of the target task node is determined, and the target configuration information indicates that an 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 execution of an operation corresponding to the operation type, and receiving, in the node configuration interface, a modification operation related to the second configuration information includes:

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

[0020] In response to the second modification operation indicating that not allowing the operation corresponding to the operation type to be executed is modified to allowing the operation corresponding to the operation type to be executed, the second modification operation is not taken into effect.

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

[0022] In the node configuration interface, prompt information is presented, where the prompt information is used to prompt that the second modification operation is not allowed to be performed.

[0023] In some possible implementations, the second configuration information includes configuration information indicating an operation rule of an operation type, where the operation rule of the operation type allows the task node to be configured respectively for the target operation type;

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

[0025] In the node configuration interface, an 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 receiving, in the node configuration interface, an operation rule configuration operation for the target operation type associated with the target task node comprises:

[0028] In the node configuration interface, an operation rule configuration operation for the return type is received, and the operation rule configuration operation is used to configure a return strategy, and 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 process.

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

[0030] In the node configuration interface, a jump control is presented, and the jump control 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 first task flow instance executing to the target task node, an operation page of the target task node is presented according to the target configuration information; wherein the first task flow instance is a task flow instance generated after the first task flow is triggered.

[0033] In some possible implementations, the target configuration information includes configuration information indicating whether to allow execution of an operation corresponding to an 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 operation type that is allowed to be executed.

[0034] In a second aspect, the present application provides a task flow configuration system, the system comprising:

[0035] A presentation module, used to present the first task process and the process configuration interface;

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

[0037] The presenting module is further configured to present, in response to a configuration operation on a target task node in the first task flow, second configuration information related to the target task node in the first configuration information in a node configuration interface for configuring the target task node;

[0038] A determination module is used to receive a modification operation related to the second configuration information in the node configuration interface, and determine the target configuration information of the target task node according to the modification operation.

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

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

[0041] First configuration information is determined according to the configuration operation for the first task flow.

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

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

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

[0045] In the node configuration interface, receiving a first modification operation for the second configuration information; wherein the first modification operation is used to modify the operation corresponding to the operation type to be not allowed to be executed;

[0046] According to the first modification operation, target configuration information of the target task node is determined, and the target configuration information indicates that an 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 execution of an operation corresponding to the operation type, and the determining module is specifically configured to:

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

[0049] In response to the second modification operation indicating that not allowing the operation corresponding to the operation type to be executed is modified to allowing the operation corresponding to the operation type to be executed, the second modification operation is not taken into effect.

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

[0051] In the node configuration interface, prompt information is presented, where the prompt information is used to prompt that the second modification operation is not allowed to be performed.

[0052] In some possible implementations, the second configuration information includes configuration information indicating an operation rule of an operation type, where the operation rule of the operation type allows the task node to be configured separately for the target operation type; and the determination module is specifically configured to:

[0053] In the node configuration interface, an 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, the target operation type includes a return type; and the determination module is specifically configured to:

[0055] In the node configuration interface, an operation rule configuration operation for the return type is received, and the operation rule configuration operation is used to configure a return strategy, and 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 process.

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

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

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

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

[0060] In some possible implementations, the target configuration information includes configuration information indicating whether to allow execution of an operation corresponding to an 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 operation type that is allowed to be executed.

[0061] In a third aspect, the present application provides an electronic device, the electronic device comprising 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 so that the electronic device executes a configuration method for a task flow in the first aspect or any implementation of the first aspect.

[0062] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, wherein the instructions instruct an electronic device to execute the method for configuring a task flow described in the first aspect or any one of the implementations of the first aspect.

[0063] In a fifth aspect, the present application provides a computer program product comprising instructions, which, when executed on an electronic device, enables the electronic device to execute the method for configuring the task flow described in the first aspect or any one of the implementations of the first aspect.

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

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

[0066] The present application provides a method for configuring a task flow, which is applied to a process engine. First, a first task flow and a process configuration interface are presented. In the process configuration interface, first configuration information is obtained, wherein the first configuration information is used to perform batch configuration on each task node in the first task flow. In response to a configuration operation on a target task node in the first task flow, in a 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, a modification operation related to the second configuration information is received, and according to the modification operation, a target configuration information of the target task node is determined.

[0067] In this method, the process engine provides process-level configuration functions and node-level configuration functions. After the user completes the process-level configuration, the task node automatically has the process-level configuration information. At the same time, the process engine also supports users to modify the configuration information of the task node. In this way, through the process-level configuration function, unified configuration of each task node in the task process is achieved to improve configuration efficiency. Through the node-level configuration function, personalized configuration of the task node is achieved, taking into account both convenience and personalized needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical method of the embodiments of the present application, the drawings required for use in the embodiments are briefly introduced below.

[0069] Figure 1 A flowchart of a method for configuring a task flow provided in an embodiment of the present application;

[0070] FIG. 2A to FIG. 2C A schematic diagram of a task flow configuration page provided in an embodiment of the present application;

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

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

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

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

[0075] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

[0078] A process engine, also known as a process orchestration engine or process orchestration tool, is usually used to define, execute, and manage task processes. A process engine usually supports visual operations. Users (such as process orchestrators) can orchestrate task nodes and generate task processes by dragging, connecting, and other operations on the process orchestration page.

[0079] A task process, 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 realizing specific functions or providing specific capabilities. Different types of task nodes are used to perform different types of tasks. For example, a fill-in task node can be used to perform a form-filling task, and an approval node can be used to perform an approval task.

[0081] When users (such as process planners) plan task flows, they can set task processors for task nodes. Considering that task nodes may be processed automatically or manually, task processors can be set to the system or task processors. For example, the task processor for filling in task nodes can be the initiator, and the task processor for approval nodes can be the direct leader, department head, etc.

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

[0083] A task node is usually associated with at least one operation type. The operation type associated with a task node can be understood as the operation that the task handler can perform on the task node in the task process instance. For example, for an approval node, the task handler can perform a pass operation or a reject operation, and the operation types associated with the approval node can include a pass type and a reject type.

[0084] After arranging the task flow, the user (e.g., the process arranger) can configure the task nodes. For example, the user can configure the operation type associated with each task node. Usually, the user needs to configure each task node in the node configuration interface of each task node. However, the above method requires the user to perform configuration operations on each task node, which is cumbersome and the configuration efficiency of the task flow is low.

[0085] In view of this, the present application provides a method for configuring a task process. The method is applied to a process engine, first presenting a first task process and a process configuration interface, obtaining first configuration information in the process configuration interface, wherein the first configuration information is used to perform batch configuration for each task node in the first task process, and in response to a configuration operation for a target task node in the first task process, presenting second configuration information related to the target task node in the first configuration information in a node configuration interface for configuring the target task node, and then, 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 according to the modification operation.

[0086] In this method, the process engine provides process-level configuration functions and node-level configuration functions. After the user completes the process-level configuration, the task node automatically has the process-level configuration information. At the same time, the process engine also supports users to modify the configuration information of the task node. In this way, through the process-level configuration function, unified configuration of each task node in the task process is achieved to improve configuration efficiency. Through the node-level configuration function, personalized configuration of the task node is achieved, taking into account both convenience and personalized needs.

[0087] To facilitate understanding of the technical solution provided by the embodiments of the present application, it will be described below with reference to the accompanying drawings.

[0088] See also Figure 1 The flowchart of a method for configuring a task flow provided by an embodiment of the present application is shown, and the method can be executed by a process engine. The method specifically includes:

[0089] S101: presenting a first task process and a process configuration interface.

[0090] In the embodiment of the present application, the first task flow may be a task flow with flow execution logic, that is, the first task flow may be a task flow generated by arranging task nodes and the execution order between the task nodes.

[0091] The process configuration interface can be understood as an interface provided by the process engine for performing relevant configurations for the first task process. In an embodiment of the present application, a user can configure the process level for the first task process through the process configuration interface. For example, a user can configure the task name, rule events, etc. for the first task process through the process configuration interface.

[0092] The embodiments of the present application do not limit the presentation method of the first task flow and the process configuration interface. In some embodiments, the first task flow and the process 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 process configuration interface is presented in the right half of the display area. In other embodiments, the first task flow and the process configuration interface can also be presented overlappingly, for example, the first task flow is presented in the display area, and the process configuration interface is presented in the display area as a floating box.

[0093] S102: In the process configuration interface, obtain first configuration information.

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

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

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

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

[0098] In an embodiment of the present application, the operation type associated with each task node in the first task flow may include the operation type 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, the operation types supported by task node B include operation type B1, operation type B2, and operation type B3, and 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] In conjunction with the specific example, the first task flow includes an approval node, a filling task node, and a copy node. The operation types associated with the approval node (i.e., the operation types supported by the approval node) are the consent type, the rejection type, the return type, the signature type, the transfer type, the copy type, the group chat initiation type, and the temporary storage type. The operation types associated with the filling task node (i.e., the operation types supported by the filling task node) are the transfer type, the copy type, the group chat initiation type, and the temporary storage type. The operation types associated with the copy node (i.e., the operation types supported by the copy node) are the group chat initiation type. At this time, the operation types associated with each task node of the first task flow are the consent type, the rejection type, the return type, the signature type, the transfer type, the copy type, the group chat initiation type, and the temporary storage type.

[0100] It should be noted that the embodiment of the present application does not limit the source of the operation type. In some embodiments, the operation type may be predefined in the process engine, and in other embodiments, the operation type may also be user-defined.

[0101] In some embodiments, the first configuration information may indicate different types of information. In specific implementations, according to the configuration operation for the first task flow, the first configuration information indicating at least one of the following is determined: whether to allow execution of an operation corresponding to the operation type, an operation rule of the operation type, or a presentation method of an operation control corresponding to the operation type.

[0102] In other words, the first configuration information may include information related to multiple configuration items of the operation type. Among them, whether the operation corresponding to the operation type is allowed to be executed can be understood as whether the task node opens the operation corresponding to the operation type. The operation rule of 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 control corresponding to the operation type can be understood as the rule for displaying the operation control corresponding to the operation type, such as presenting the name and presenting the icon.

[0103] Taking the example of the first configuration information indicating whether to allow the execution of an operation corresponding to an operation type, in an embodiment of the present application, the operation type associated with each task node in the first task process includes the operation type supported by each task node in the first task process. The user can configure whether to enable the operation corresponding to the operation type supported by each task node in the first task process.

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

[0105] Continuing with the above example, when configuration items related to operation types 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, and a column for configuring whether the operation corresponding to the operation type is allowed to be executed. The user can perform configuration operations for each operation type in the table to generate first configuration information.

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

[0107] In an embodiment of the present 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] Among them, the target task node can be any task node in the first task process, the configuration operation of the target task node in the first task process can be understood as an operation of performing node-level configuration on the target task node, and the node configuration interface can be understood as an interface provided by the process engine for performing relevant configuration on the target task node.

[0109] The embodiment of the present 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 information related to the target task node in the first configuration information, that is, the second configuration information is at least part of the information in the first configuration information. Specifically, when the first configuration information includes information related to multiple configuration items of an operation type, the second configuration information may include information of the operation type 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 process include operation type A1, operation type A2 and operation type B1, the first configuration information includes configuration information related to operation type A1, operation type A2 and operation type B1, and 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 in the first configuration information that is related to operation type A1 and operation type A2.

[0112] Similarly, the second configuration information may also be presented in the form of a table in the node configuration interface. Continuing with the above example, the table of the node configuration interface includes rows corresponding to operation type A1 and operation type A2, and the content presented in the table of the node configuration interface is the same as the configuration information related to operation type A1 and 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 to be executed, and the operation corresponding to operation type A2 is allowed to be executed, and the second configuration information also indicates that the operation corresponding to operation type A1 is not allowed to be executed, and the operation corresponding to operation type A2 is allowed to be executed.

[0113] Thus, in an embodiment of the present application, by providing a process-level configuration function, a unified configuration is performed for each task node in the first task process, and the first configuration information at the process level will be automatically assigned to the task node, thereby realizing batch configuration of each task node in the task process. When performing node-level configuration for the target task node, the first configuration information is used as the initial configuration information of the target task node, and the process-level configuration information related to the target node is presented.

[0114] S104: In the node configuration interface, a modification operation related to the second configuration information is received, and according to the modification operation, target configuration information of the target task node is determined.

[0115] Among them, the modification operation related to the second configuration information can be understood as an operation for modifying the second configuration information. In the embodiment of the present application, the process engine provides a node-level configuration function, and the user can modify the process-level configuration information related to the target node to achieve a more fine-grained, node-level configuration, and then complete the configuration of the target task node.

[0116] In this way, for task flow configurations that do not require individualization, users can use the process-level configuration function to achieve unified configuration for each task node in the task flow, thereby improving configuration efficiency. For task flow configurations that require individualization, users can perform process-level configurations and node-level configurations for task nodes that require individualization, thereby meeting diverse business needs and improving the applicability of task flow configurations.

[0117] In some embodiments, the second configuration information includes configuration information indicating whether the operation corresponding to the operation type is allowed to be executed. In the node configuration interface, a first modification operation for the second configuration information is received, and then, according to the first modification operation, the target configuration information of the target task node is determined. The first modification operation is used to modify the operation corresponding to the operation type to be allowed to be executed to the operation corresponding to the operation type, and the target configuration information indicates that the operation corresponding to the operation type is not allowed to be executed.

[0118] That is, when the execution of the operation corresponding to the operation type is allowed in the process-level configuration, the user can make modifications in the node-level configuration to configure the target task node to not allow the execution of the operation corresponding to the operation type. For example, the operation types associated with the target task node include operation type A1 and operation type A2, and 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 operations corresponding to operation type A1 and operation type A2 are allowed to be executed. The user can modify the second configuration information so that the target configuration information of the target task node indicates that the operations corresponding to operation type A1 and / or operation type A2 are not allowed to be executed.

[0119] In this way, when there are task nodes in the first task process that need to enable certain operation types, but the target task node does not need to enable these operation types, the second configuration information is modified through node-level configuration to turn off the operation type of the target task node to meet the personalized configuration requirements of the task node.

[0120] In some other embodiments, the second configuration information includes configuration information indicating whether to allow the operation corresponding to the operation type to be executed. In the node configuration interface, a second modification operation for the second configuration information is received, and in response to the second modification operation indication, the operation corresponding to the operation type not being allowed to be executed is modified to the operation corresponding to the operation type being allowed to be executed. The second operation is not effective.

[0121] That is, when the execution of the operation corresponding to the operation type is not allowed in the process-level configuration, the user cannot make modifications in the node-level configuration, and cannot configure the target task node to allow the execution of the operation corresponding to the operation type. For example, 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 the execution of the operation corresponding to operation type A1 and operation type A2 is not allowed, and the user cannot modify the second configuration information, and the target configuration information of the target task node still indicates that the execution of the operation corresponding to operation type A1 and operation type A2 is not allowed.

[0122] Furthermore, a prompt message may be presented in the node configuration interface. The prompt message is used to prompt that the second modification operation is not allowed. That is, when the user wants to modify the operation corresponding to the operation type that is not allowed to be executed to the operation corresponding to the operation type that is allowed to be executed in the node-level configuration, the user is informed by presenting a prompt message that the target configuration information of the target task node is the same as the second configuration information and cannot be modified.

[0123] In this way, the configuration priority at the process level is higher than the configuration at the node level. If certain operation types have been closed in the process level configuration, the operation types cannot be opened in each task node in the first task process, thereby realizing batch closing of operation types at the process level.

[0124] In other embodiments, the second configuration information includes configuration information indicating an operation rule of the operation type, and the operation rule of the operation type is to allow the task node to be configured separately for the target operation type. That is to say, in the embodiment of the present application, the process-level configuration can not only configure a specific implementation of an operation corresponding to the operation type for each task node in the first task process, but also support different task nodes to configure operation rules for the same operation type (i.e., the target operation type).

[0125] In specific implementation, in the node configuration interface, an operation rule configuration operation for a target operation type associated with a target task node is received. In other words, for target operation types that support separate configuration of operation rules for different task nodes, users can configure operation rules separately in the node configuration interface. In this way, for the same operation type, different operation rules can be configured in combination with the specific business requirements of the task node to meet personalized needs.

[0126] Specifically, the target task node may be an approval node, and the target operation type may include a return type. That is, the process-level configuration allows different task nodes to configure operation rules for return types respectively.

[0127] In this case, in the node configuration interface, an operation rule configuration operation for a return type is received, wherein the operation rule configuration operation is used to configure a return strategy, and 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.

[0128] In other words, in the embodiment of the present application, different approval nodes are allowed to be configured with different operation rules. For some approval nodes, the return policy can be configured to allow return to the initiator, and 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, the embodiment of the present application also supports jumping to the process level configuration when performing the node level configuration. Specifically, in the node configuration interface, a jump control is presented, and the jump control is used to trigger the presentation of the process configuration interface.

[0130] By providing a jump control in the node configuration interface, when the user is performing node-level configuration, the jump control can be triggered to quickly switch to the process configuration interface. In this way, the user can quickly change the process-level configuration information at any time.

[0131] In this method, the process engine provides process-level configuration functions and node-level configuration functions. After the user completes the process-level configuration, the task node automatically has the process-level configuration information. At the same time, the process engine also supports users to modify the configuration information of the task node. In this way, through the process-level configuration function, unified configuration of each task node in the task process is achieved to improve configuration efficiency. Through the node-level configuration function, personalized configuration of the task node is achieved, taking into account both convenience and personalized needs.

[0132] After configuring the first task flow through the process-level configuration and node-level configuration provided by the embodiment of the present application, in the process of running the first task flow, a page can be presented based on the target configuration information of the target task node. Specifically, in response to the first task flow instance executing to the target task node, the operation page of the target task node is presented according to the target configuration information. Among them, the first task flow instance is a task flow instance generated after the first task flow is triggered.

[0133] That is, when the first task process instance is executed 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 execution of an operation corresponding to an 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 operation type allowed to be executed.

[0135] That is, the operation types allowed to be executed by the target task node are configured through the process level configuration and the node level configuration. In the operation page of the target task node, the target operation control corresponding to the operation type allowed to be executed is presented.

[0136] For example, the target configuration information of the target task node indicates that the types of operations allowed to be executed include operation type A1 and operation type A2. In the operation page of the target task node, a target operation control for triggering the operation corresponding to operation type A1 and a target operation control for triggering the operation corresponding to operation type A2 are presented. In this way, the task processor of the target task node can trigger the corresponding operation through the target operation control in the operation page of the target task node.

[0137] Furthermore, the target configuration information may also indicate the presentation mode of the operation control corresponding to the operation type. At this time, in the operation page of the target task node, the presentation mode of the target operation control may match the target configuration information, for example, the target operation control is presented with the presentation name and presentation icon indicated by the target configuration information.

[0138] The previous article introduced the configuration method of the task flow provided by this application, and the following will explain it in conjunction with specific scenarios.

[0139] See also FIG. 2A to FIG. 2C The task flow configuration page shown in the figure is Figure 2A In the example, the task flow configuration page 20 includes a first task flow presentation area 21 and a flow configuration interface 22. The first task flow includes four task nodes, namely, "employee filling in a form", "direct supervisor approval", "financial supervisor approval", and "financial director approval". The flow configuration interface 22 is used to configure the flow level for the first task flow.

[0140] Specifically, the user can configure the task process name and the operation type associated with each task node in the first task process in the process configuration interface 22. The process configuration interface 22 presents 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 process include consent type, rejection type, transfer type, return type, group chat initiation type, form save type, initiator revocation type and initiator reminder type. The configuration items include whether the operation corresponding to the operation type is allowed 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 an example, in the first configuration information at the process level, it is indicated that the operation corresponding to the transfer type is not allowed to be executed, and it is indicated that the operation corresponding to the return type is allowed to be executed. The presentation method of the operation control corresponding to the return type is "the presentation name is rejected, and the presentation style is style D", and the operation rule of the return type is "allowing the task node to configure the operation rules for the return type separately."

[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, if the user triggers the configuration operation for the operation type at the process level, the message "Please allow editing after operation" is displayed to inform the user that subsequent configuration can only be performed after running and executing the operation type.

[0143] like Figure 2CAs shown, for the case where there are multiple options such as "button style", multiple options are presented to the user by presenting the first drop-down menu 222, and the user can select from the multiple 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 the configuration information through in-situ configuration to complete the process-level configuration.

[0145] In some other embodiments, a configuration interface for configuration items is provided for process-level configuration. Figure 3 The schematic diagram of the operation rule configuration interface is shown. In the operation rule configuration interface 30, the user can configure the operation rules for initiating a group chat. The user can enter the group name in the operation rule configuration interface 30 and select a robot for initiating a group chat. After the user completes the configuration, the configuration information in the operation rule configuration interface 30 is semantically filled back into the process configuration interface 22. For example, "Create a group using the default application" is presented in the process configuration interface 22.

[0146] See also 4A to 4D The diagram of the task flow configuration page is shown in Figure 4A As shown, the second configuration information of the target task node is presented in the form of a table in the node configuration interface 41 of the task flow configuration page 40. Among them, the operation types associated with the target task node include consent type, rejection type, transfer type, return type, initiation of group chat type and save form type, and the configuration items of the operation types associated with the target task node in the second configuration information and the first configuration information are the same.

[0147] like Figure 4B As shown, the second configuration information indicates that the operation corresponding to the transfer type is not allowed. At this time, if the user triggers the second modification operation for the second configuration information, that is, the operation corresponding to the operation type is changed from not allowed to be executed to allowed to be executed, a prompt message 401 will be presented to inform the user that the second modification operation is not allowed.

[0148] The prompt information 401 may include a jump control (ie, the text of "process configuration"), and the user may trigger the jump control to present the process configuration interface. Figure 4C As shown, after the jump control is triggered, the task process configuration page 40 presents the node configuration interface 42 and the process configuration interface 43 in parallel.

[0149] Specifically, if the second configuration information indicates that the operating rules of the return type allow different task nodes to be configured separately for the return type, the user can modify the operating rules of the return type configured for the target task node in the node configuration interface 42. By presenting the second drop-down menu 402, the user can select the operating rules of 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 of the return type is to return to the initiator, that is, different task nodes are not allowed to be configured separately for the return type, the user cannot configure the operation rule of the return type for the target task node in the node configuration interface. When the user triggers the modification operation of the operation rule of the return type, prompt information 403 is presented, informing the user that the operation rules need to be changed in the process-level configuration before the operation rules can be configured separately for the same operation type of different task nodes.

[0151] After completing the configuration of the first task flow, in response to the triggering operation of the first task flow, a first task flow instance is generated. Figure 5 As shown, in response to the first task process instance being executed to 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 operations corresponding to the consent type, the rejection type, the transfer type, the return type, and the initiation of a group chat type are allowed to be performed, in the operation page 50, target operation controls corresponding to the consent type, the rejection type, the transfer type, the return type, and the initiation of a group chat type are presented, so that the task processor of the target task node can trigger the corresponding operation through the target operation control.

[0152] Combination of the above Figures 1 to 5 The configuration method of the task flow provided in the embodiment of the present application is introduced in detail. The system and equipment provided in the embodiment of the present application will be introduced in conjunction with the accompanying drawings.

[0153] See also Figure 6 The structure diagram of the configuration system of the task flow shown is shown, and the system 60 includes:

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

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

[0156] The presenting module 601 is further configured to present, in response to a configuration operation on a target task node in the first task flow, second configuration information related to the target task node in the first configuration information in a node configuration interface for configuring the target task node;

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

[0158] In some possible implementations, the acquisition module 602 is specifically configured to:

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

[0160] First configuration information is determined according to the configuration operation for the first task flow.

[0161] In some possible implementations, the acquisition module 602 is specifically configured to:

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

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

[0164] In the node configuration interface, receiving a first modification operation for the second configuration information; wherein the first modification operation is used to modify the operation corresponding to the operation type to be not allowed to be executed;

[0165] According to the first modification operation, target configuration information of the target task node is determined, and the target configuration information indicates that an 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 execution of an operation corresponding to the operation type, and the determining module 603 is specifically configured to:

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

[0168] In response to the second modification operation indicating that not allowing the operation corresponding to the operation type to be executed is modified to allowing the operation corresponding to the operation type to be executed, the second modification operation is not taken into effect.

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

[0170] In the node configuration interface, prompt information is presented, where the prompt information is used to prompt that the second modification operation is not allowed to be performed.

[0171] In some possible implementations, the second configuration information includes configuration information indicating an operation rule of an operation type, where the operation rule of the operation type allows the task node to be configured respectively for the target operation type; the determination module 603 is specifically used to:

[0172] In the node configuration interface, an 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 determination module 603 is specifically used to:

[0174] In the node configuration interface, an operation rule configuration operation for the return type is received, and the operation rule configuration operation is used to configure a return strategy, and 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 process.

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

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

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

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

[0179] In some possible implementations, the target configuration information includes configuration information indicating whether to allow execution of an operation corresponding to an 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 operation type that is allowed to be executed.

[0180] The task flow configuration system 60 according to the embodiment of the present application may correspond to the method described in the embodiment of the present application, and the above and other operations and / or functions of each module / unit of the task flow configuration system 60 are respectively to implement Figure 1 For the sake of brevity, the corresponding processes of each method in the illustrated embodiment are not described in detail here.

[0181] The present application also provides an electronic device. The electronic device is specifically used to implement Figure 6 The function of the configuration system 60 of the task flow in the illustrated embodiment.

[0182] Figure 7 A schematic diagram of the structure of an electronic device 700 is provided. 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 bus 701 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0184] The processor 702 may be any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0185] The communication interface 703 is used for communicating with the outside. For example, the communication interface 703 can be used for communicating with a terminal.

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

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

[0188] Specifically, in implementing Figure 6 In the case of the embodiment shown, and Figure 6 When each module or unit of the configuration system 60 of the task flow described in the embodiment is implemented by software, the execution Figure 6 The software or program code required for the functions of each module / unit in the system may be partially or completely stored in the memory 704. The processor 702 executes the program code corresponding to each unit stored in the memory 704 to perform the configuration method of the aforementioned task flow.

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

[0190] The embodiment of the present application further provides a computer program product, which includes one or more computer instructions. When the computer instructions are loaded and executed on a computing device, the process or function described in the embodiment of the present application is generated in whole or in part.

[0191] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. 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, optical fiber, 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 executes any of the aforementioned methods for configuring the task flow. The computer program product may be a software installation package, and when any of the aforementioned methods for configuring the task flow is required, the computer program product may be downloaded and executed on the computer.

[0193] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to each embodiment of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0194] The units involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the unit / module does not, in some cases, constitute a limitation on the unit itself.

[0195] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

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

[0197] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0198] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0199] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0200] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a 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 implement or use the present application. Various modifications to these embodiments will be 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 the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to 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 comprises: Presenting the first task process and process configuration interface; In the process configuration interface, first configuration information is obtained; wherein the first configuration information is used to perform batch configuration on each task node in the first task process; In response to a configuration operation on a target task node in the first task flow, presenting second configuration information related to the target task node in the first configuration information in a 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 according to the modification operation, the target configuration information of the target task node is determined.

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

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

4. The method according to claim 2, characterized in that: The second configuration information includes configuration information indicating whether to allow execution of an operation corresponding to the operation type, and receiving a modification operation related to the second configuration information in the node configuration interface, and determining target configuration information of the target task node according to the modification operation, including: In the node configuration interface, receiving a first modification operation for the second configuration information; wherein the first modification operation is used to modify the operation corresponding to the operation type to be not allowed to be executed; According to the first modification operation, target configuration information of the target task node is determined, and the target configuration information indicates that an operation corresponding to the operation type is not allowed to be executed.

5. The method according to claim 2, characterized in that: The second configuration information includes configuration information indicating whether to allow execution of an operation corresponding to the operation type, and receiving, in the node configuration interface, a modification operation related to the second configuration information includes: In the node configuration interface, receiving a second modification operation for the second configuration information; In response to the second modification operation indicating that not allowing the operation corresponding to the operation type to be executed is modified to allowing the operation corresponding to the operation type to be executed, the second modification operation is not taken into effect.

6. The method according to claim 5, characterized in that The method further comprises: In the node configuration interface, prompt information is presented, where the prompt information is used to prompt that the second modification operation is not allowed to be performed.

7. The method according to claim 2, characterized in that: The second configuration information includes configuration information indicating an operation rule of an operation type, where the operation rule of the operation type allows the task node to be configured respectively for the target operation type; The step of receiving, in the node configuration interface, a modification operation related to the second configuration information includes: In the node configuration interface, an operation rule configuration operation for the target operation type associated with the target task node is received.

8. The method according to claim 7, characterized in that The target task node is an approval node, and the target operation type includes a return type; The receiving, in the node configuration interface, an operation rule configuration operation for the target operation type associated with the target task node comprises: In the node configuration interface, an operation rule configuration operation for the return type is received, and the operation rule configuration operation is used to configure a return strategy, and 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 process.

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

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: In response to the first task flow instance executing to the target task node, an operation page of the target task node is presented according to the target configuration information; wherein the first task flow instance is a task flow instance generated after the first task flow is triggered.

11. The method according to claim 10, characterized in that The target configuration information includes configuration information indicating whether to allow the execution of an operation corresponding to an operation type. The operation page of the target task node presents a target operation control, and the target operation control is used to trigger the operation corresponding to the operation type that is allowed to be executed.

12. A task flow configuration system, characterized in that: The system comprises: A presentation module, used to present the first task process and the process configuration interface; An acquisition module, used to acquire first configuration information in the process configuration interface; wherein the first configuration information is used to perform batch configuration on each task node in the first task process; The presenting module is further configured to present, in response to a configuration operation on a target task node in the first task flow, second configuration information related to the target task node in the first configuration information in a node configuration interface for configuring the target task node; A determination module is used to receive a modification operation related to the second configuration information in the node configuration interface, and determine the target configuration information of the target task node according to the modification operation.

13. An electronic device, characterized in that: The electronic device comprises a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the electronic device performs the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that: The method comprises instructions, wherein the instructions instruct an electronic device to execute the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The computer program product comprises computer readable instructions for implementing the method according to any one of claims 1 to 11.

Citation Information

Patent Citations

  • Method and device for generating and processing approval process

    CN114185583A

  • Flow processing method and system, computer equipment and storage medium

    CN114186817A

  • Business process attribute setting method and device, computer equipment and storage medium

    CN115756704A

  • Business process implementation method and device, electronic equipment and storage medium

    CN117933685A

  • Configuration of a hyper-converged infrastructure (HCI) cluster using centralized workflows

    US20210096878A1