Task process management method, system and device, medium and program product

By obtaining and matching account type and task node information, displaying target task nodes that match the account, solving the problem of low task processing efficiency in complex task processes, achieving efficient task processing and user experience improvement.

CN119026889APending Publication Date: 2024-11-26BEIJING YOUZHUJU NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310594838.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-24
Publication Date
2024-11-26

Smart Images

  • Figure CN119026889A_ABST
    Figure CN119026889A_ABST
Patent Text Reader

Abstract

The invention provides a task process management method, system and device, a medium and a program product. According to the method, in response to a viewing operation for a task process, an account type of a trigger account triggering the viewing operation and node information of a plurality of task nodes in the task process are obtained, and the node information indicates an account type set having access authority to the task nodes; determining a target task node matched with the trigger account from a plurality of task nodes according to the account type of the trigger account and node information of the task nodes in the task process; and the target task node is displayed in the task process, so that the trigger account executes a trigger operation for the target task node, and task processing is carried out. In the method, different task nodes can support accounts of different account types to access the nodes, and a user only needs to pay attention to the task nodes related to the user in the face of a complex task process, so that the task processing efficiency can be improved, and the user experience can be improved.
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 management method, system, device, computer-readable storage medium, and computer program product. Background Art

[0002] With the rapid development of computer technology, office automation (OA) applications that combine computer technology with modern office have emerged. OA applications can automatically handle office affairs. For example, based on OA applications, task processes (also known as workflows) can be automatically advanced, thereby improving office efficiency.

[0003] Specifically, a task flow can be arranged with multiple task nodes and the execution order between multiple task nodes, so that the OA application can process the task nodes in sequence according to the execution order of the task nodes and automatically advance the task flow. Different task nodes can usually be processed by different task processors, who can view the execution status of the task flow and process the task nodes that need to be processed.

[0004] When a task processor views the task flow, multiple task nodes included in the task flow can be displayed to the task processor. However, for a task flow with a large number of task nodes, it is difficult for the task processor to clearly and intuitively obtain task node information related to itself, which reduces the efficiency of task processing. Summary of the invention

[0005] The present application provides a task flow management method. The method can display task nodes that match the account type, so that users only need to focus on the task nodes related to themselves, improve task processing efficiency, and enhance user experience. The present application also provides a system, device, computer-readable storage medium, and computer program product corresponding to the above method.

[0006] In a first aspect, the present application provides a task flow management method. The method comprises:

[0007] In response to a viewing operation on a task flow, obtaining an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task nodes;

[0008] According to the account type of the triggering account and the node information of multiple task nodes in the task flow, determining a target task node matching the triggering account from the multiple task nodes;

[0009] The target task node is displayed in the task process so that the trigger account executes a trigger operation on the target task node to perform task processing.

[0010] In some possible implementations, the node information further indicates an operation permission set corresponding to at least one account type in the account type set, the operation permission set includes at least one operation type, and the method further includes:

[0011] In response to a trigger operation on the target task node, determining, according to the node information, a set of operation permissions corresponding to the account type of the triggering account;

[0012] A task processing interface corresponding to the target task node is displayed, wherein the task processing interface provides at least one operation control corresponding to the target task node, wherein a target operation control in the at least one operation control is used to perform a target operation, and an operation type of the target operation is at least one operation type in an operation permission set corresponding to the account type of the triggering account.

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

[0014] In response to a trigger operation on a target operation control in the at least one operation control, an interface corresponding to the target operation control is called, the target operation is executed, and a task processing result of the target task node is obtained.

[0015] In some possible implementations, displaying the task processing interface corresponding to the target task node includes:

[0016] Displaying a task processing interface according to a first content identifier of the target task node, wherein the first content identifier is used to indicate information to be processed of the target task node, and the task processing interface includes the information to be processed;

[0017] The method further comprises:

[0018] In response to a trigger operation on a target operation control in the at least one operation control, calling an interface corresponding to the target operation control, executing the target operation, and obtaining a task processing result of the target task node;

[0019] The task processing interface is displayed according to the second content identifier of the target task node, where the second content identifier is used to indicate the task processing result of the target task node, and the task processing interface includes the task processing result of the target task node.

[0020] In some possible implementations, displaying the task processing interface according to the second content identifier of the target task node includes:

[0021] Determining a result display template of the target task node according to the second content identifier of the target task node;

[0022] The task processing result of the target task node is filled into the result display template, and the task processing result of the target task node is displayed on the task processing interface.

[0023] In some possible implementations, after obtaining the task processing result of the target task node, the method further includes:

[0024] In response to a reset operation on the target task node, a task processing result of the target task node is reset.

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

[0026] In response to a selection operation on a plurality of candidate task nodes in a task node resource pool, determining the plurality of task nodes;

[0027] The task flow is generated in response to an orchestration operation on the plurality of task nodes, wherein the orchestration operation is used to indicate a dependency relationship between the plurality of task nodes in the task flow.

[0028] In some possible implementations, generating the task flow in response to the orchestration operation on the plurality of task nodes includes:

[0029] In response to a connection operation for the plurality of task nodes, determining a dependent node set of at least one task node among the plurality of task nodes, the dependent node set including task nodes that the at least one task node depends on;

[0030] In response to configuration operations for the plurality of task nodes, determining a branch condition;

[0031] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.

[0032] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the method further includes:

[0033] Storing the task processing result of the first task node;

[0034] In response to a trigger operation on the second task node, a task processing interface corresponding to the second task node is displayed, and the task processing interface corresponding to the second task node includes the task processing result of the first task node.

[0035] In a second aspect, the present application provides a task process management system. The system comprises:

[0036] an acquisition unit, configured to acquire, in response to a viewing operation on a task flow, an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task nodes;

[0037] a determining unit, configured to determine a target task node matching the triggering account from the multiple task nodes according to the account type of the triggering account and the node information of the multiple task nodes in the task flow;

[0038] A display unit is used to display the target task node in the task process so that the trigger account executes a trigger operation on the target task node to perform task processing.

[0039] In some possible implementations, the node information further indicates an operation permission set corresponding to at least one account type in the account type set, the operation permission set includes at least one operation type, and the determining unit is specifically configured to:

[0040] In response to a trigger operation on the target task node, determining, according to the node information, a set of operation permissions corresponding to the account type of the triggering account;

[0041] The display unit is specifically used for:

[0042] A task processing interface corresponding to the target task node is displayed, wherein the task processing interface provides at least one operation control corresponding to the target task node, wherein a target operation control in the at least one operation control is used to perform a target operation, and an operation type of the target operation is at least one operation type in an operation permission set corresponding to the account type of the triggering account.

[0043] In some possible implementations, the system further includes:

[0044] The execution unit is used to respond to the trigger operation of the target operation control in the at least one operation control, call the interface corresponding to the target operation control, execute the target operation, and obtain the task processing result of the target task node.

[0045] In some possible implementations, the display unit is specifically used to:

[0046] Displaying a task processing interface according to a first content identifier of the target task node, wherein the first content identifier is used to indicate information to be processed of the target task node, and the task processing interface includes the information to be processed;

[0047] The execution unit is specifically used for:

[0048] In response to a trigger operation on a target operation control in the at least one operation control, calling an interface corresponding to the target operation control, executing the target operation, and obtaining a task processing result of the target task node;

[0049] The display unit is also used for:

[0050] The task processing interface is displayed according to the second content identifier of the target task node, where the second content identifier is used to indicate the task processing result of the target task node, and the task processing interface includes the task processing result of the target task node.

[0051] In some possible implementations, the system further includes:

[0052] The reset unit is used to reset the task processing result of the target task node in response to the reset operation on the target task node.

[0053] In some possible implementations, the system further includes:

[0054] An orchestration unit is used to determine the multiple task nodes in response to a selection operation on multiple candidate task nodes in a task node resource pool; and generate the task flow in response to an orchestration operation on the multiple task nodes, wherein the orchestration operation is used to indicate a dependency relationship between the multiple task nodes in the task flow.

[0055] In some possible implementations, the arrangement unit is specifically configured to:

[0056] In response to a connection operation for the plurality of task nodes, determining a dependent node set of at least one task node among the plurality of task nodes, the dependent node set including task nodes that the at least one task node depends on;

[0057] In response to configuration operations for the plurality of task nodes, determining a branch condition;

[0058] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.

[0059] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the system further includes:

[0060] A storage unit, used to store the task processing result of the first task node;

[0061] The display unit is specifically used for:

[0062] In response to a trigger operation on the second task node, a task processing interface corresponding to the second task node is displayed, and the task processing interface corresponding to the second task node includes the task processing result of the first task node.

[0063] In a third aspect, the present application provides an electronic device, the 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 the task flow management method in the first aspect or any implementation of the first aspect.

[0064] 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 task flow management method described in the first aspect or any one of the implementations of the first aspect.

[0065] 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 task flow management method described in the first aspect or any one of the implementations of the first aspect.

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

[0067] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0068] The embodiment of the present application provides a task flow management method. The method responds to a viewing operation on a task flow, obtains the account type of a triggering account that triggers the viewing operation and the node information of multiple task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task node, and then determines a target task node that matches the triggering account from multiple task nodes according to the account type of the triggering account and the node information of multiple task nodes in the task flow, and displays the target task node in the task flow, so that the triggering account executes a triggering operation on the target task node and performs task processing.

[0069] In this method, different account types have different access rights to task nodes. Through the account type and the node information of the task node, the target task node that matches the account type can be determined from the task process and displayed. Faced with a complex task process, users only need to focus on the task nodes related to themselves, which can improve task processing efficiency and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] 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.

[0071] Figure 1 An architecture diagram of a task process management system provided in an embodiment of the present application;

[0072] Figure 2 A flowchart of a task flow management method provided in an embodiment of the present application;

[0073] Figure 3 A schematic diagram of a task flow interface provided in an embodiment of the present application;

[0074] Figure 4 A schematic diagram of a process scheduling interface provided in an embodiment of the present application;

[0075] Figure 5 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 involved in the embodiments of the present application are introduced.

[0078] A task node is a module used to perform tasks, thereby realizing specific functions or providing specific capabilities. The tasks to be performed by a task node usually correspond to operations. In other words, a task node can complete the processing of a task by triggering an operation.

[0079] In different scenarios, the tasks to be performed by the task nodes and the operations corresponding to the tasks may be different. For example, in an e-commerce scenario, the task to be performed by a task node may be to create a promotional activity, and the task to be performed by another task node may be to approve the promotional activity. The operation corresponding to the task of creating the promotional activity may include a creation operation, and the operation corresponding to the task of approving the promotional activity may include approval and rejection. Furthermore, the operation corresponding to the task of approving the promotional activity may also include reallocation of approvers. For another example, in an attendance management scenario, the tasks to be performed by the task nodes may include an abnormal attendance record reminder task, an abnormal attendance record correction task, and an abnormal attendance record approval task. The operation corresponding to the abnormal attendance record reminder task includes detail viewing, the operation corresponding to the abnormal attendance record correction task includes correction and submission, and the operation corresponding to the abnormal attendance record approval includes approval and rejection.

[0080] A task process, also known as a workflow, refers to an execution sequence consisting of a series of task nodes. Among them, the dependency relationship between task nodes can represent the execution order of task nodes. Task nodes can be set with task processors. Considering that task nodes may be automatically processed or manually processed, the task processor can be set as a system or a task processor. The task processors of different task nodes can be different. For example, the task processor for creating a promotion task can be an operator, and the task processor for approving a promotion task can be a manager. It should be noted that the tasks to be performed by a task node can be processed by one or more task processors. When a task node is set with multiple task processors, and multiple task processors complete the task processing, it means that the task execution of the task node has been completed.

[0081] In order to achieve efficient and convenient generation of task flows, task flow orchestration tools (such as process orchestration engines) have emerged. Task flow orchestration tools support visual operations, and users (such as process orchestration personnel) can use visual operations, such as dragging and connecting operations on the process orchestration interface, to orchestrate task nodes, thereby generating task flows.

[0082] After the task flow is generated, other users (such as task processing personnel) can view the task flow through the task flow interface and perform task processing on the task nodes that need to be executed. Specifically, when the task processing personnel triggers the task flow viewing operation in the task flow interface, the task processing personnel can be shown multiple task nodes included in the task flow, and the execution order and execution status of the multiple task nodes can also be shown to the task processing personnel. The task processing personnel can enter the task processing interface by triggering the task node and perform task processing in the task processing interface.

[0083] However, for a task flow with a large number of task nodes, the task processor needs to find the task node related to itself from a large number of task nodes, and then process the task on the task node, which reduces the efficiency of task processing. If a corresponding task flow is developed for each task processor, the development cost will increase sharply.

[0084] In view of this, the present application provides a task flow management method. The method responds to a viewing operation for a task flow, obtains the account type (also referred to as a role in some cases) of a triggering account (user's account) that triggers the viewing operation and the node information of multiple task nodes in the task flow, wherein the node information indicates a set of account types with access rights to the task node (in some cases referred to as the role domain of the node), and then determines the target task node that matches the triggering account from multiple task nodes according to the account type of the triggering account and the node information of multiple task nodes in the task flow, and then displays the target task node in the task flow, so that the triggering account performs a triggering operation for the target task node and performs task processing.

[0085] In this method, different task nodes can support accounts of different account types to access the node. Through the account type and the node information of the task node, the target task node that matches the account type of the triggering account (for example, the task node whose role domain intersects with the role owned by the user) can be determined from the task process, and the target task node can be displayed. Faced with complex task processes, users only need to pay attention to the task nodes related to themselves, so that the task processing efficiency can be improved and the user experience can be improved. Moreover, this method does not need to develop corresponding task processes for each task processor, which greatly reduces the development cost.

[0086] Furthermore, each account type in the account type set can be configured with an operation permission set corresponding to the account type, and the operation permission set includes at least one operation type. By providing operation controls corresponding to the operation types included in the operation permission set in the task processing interface, accounts of different account types can perform different operations on task nodes, thereby reducing possible erroneous operations in task processing.

[0087] In addition, this method can build complex, multi-branch task processes to meet different business needs. Moreover, this method can complete task processing in one task processing interface, without the need for users to manually jump between different businesses, which greatly simplifies user operations, reduces the difficulty of user task processing, and improves user experience.

[0088] In order to make the technical solution of the present application clearer and easier to understand, the system architecture of the task flow management method provided in the embodiment of the present application is introduced below with reference to the accompanying drawings.

[0089] See also Figure 1The schematic diagram of the architecture of a task flow management system shown in the figure, the task flow management system 10 includes a scheduling subsystem 11, which can also be called a construction subsystem, responsible for the advancement of task flows and the scheduling of tasks. The scheduling subsystem 11 can advance the task flow or schedule tasks under event-driven. The event can be an event in a message queue or a hypertext transfer protocol (HTTP) callback event.

[0090] Furthermore, the task flow management system 10 may also include at least one execution engine 12, which is used to automatically execute tasks in the task node. In this way, the scheduling subsystem 11 can realize the hosting of the task node through at least one execution engine 12. For example, the scheduling subsystem 11 can determine the execution engine 12 corresponding to the type of the task node according to the type of the task node, and automatically process the tasks to be executed by the task node through the execution engine 12 to realize the automatic advancement of the task flow.

[0091] In some possible implementations, the task flow management system 10 may further include a task node resource pool 13, an orchestration subsystem 14, or a standard operating procedure (SOP) subsystem 15. The functions of the task node resource pool 13, the orchestration subsystem 14, and the SOP subsystem 15 are described below.

[0092] Task node resource pool 13, also known as atomic node market, is used to create atomic task nodes according to business data. Atomized task nodes refer to the smallest unit for generating task flow, and the task nodes can usually be reused. The creation process of task nodes can be: abstracting reusable tasks into application programming interfaces (application programming interfaces, APIs), saving the abstracted APIs and related data into objects (objects), and objects can be data structures including at least one of the following fields: node type (e.g., static nodes or dynamic nodes), operation names, operation identifiers (identifiers, IDs), operation parameters, uniform resource locators (uniform resource locators, URLs). Wherein, URLs can include at least one of page URLs or third-party URLs (links). The above objects can be stored in task node resource pool 13 as task nodes. Task node resource pool 13 is used to provide multiple configurable task nodes, each of which is used to implement specific functions or provide specific capabilities.

[0093] The orchestration subsystem 14, also called the orchestration center, is used to perform task flow orchestration according to the task nodes provided by the task node resource pool 13, thereby generating a task flow. The orchestration subsystem 14 can provide a visual orchestration interface, through which the user can select a task node in the task node resource pool 13, and perform orchestration operations such as connecting the selected task nodes, thereby realizing task flow orchestration and generating a task flow.

[0094] The SOP subsystem 14, also referred to as the SOP center, is used to store the process templates of the task flow. The SOP subsystem 14 can be a database, and the process templates of the task flow can be solidified and stored in the database. Further, the scheduling subsystem 11 is used to obtain the process templates of the task flow and instantiate them to execute the task flow. The scheduling subsystem 11 can generate process data, such as task processing results, during the execution of the task flow. Accordingly, the SOP subsystem 14 is also used to store the above-mentioned process data.

[0095] Next, the process of the scheduling subsystem 11 performing task flow advancement or task scheduling is described.

[0096] like Figure 1 As shown, the scheduling subsystem 11 includes an acquisition unit 112, a determination unit 114 and a display unit 116. The acquisition unit 112 is used to obtain the account type of the triggering account that triggers the viewing operation and the node information of multiple task nodes in the task process in response to a viewing operation on the task process, and the node information indicates a set of account types that have access rights to the task node. The determination unit 114 is used to determine a target task node that matches the triggering account from the multiple task nodes based on the account type of the triggering account and the node information of the multiple task nodes in the task process. The display unit 116 is used to display the target task node in the task process so that the triggering account executes the triggering operation on the target task node and performs task processing.

[0097] It should be noted that Figure 1 The subsystems or units in the subsystems are divided by function, and the above-mentioned systems or subunits can be implemented by software or by hardware. When the above-mentioned subsystems and units are implemented by software, the subsystems and units can be software functional modules, services, components or plug-ins. When the above-mentioned subsystems and units are implemented by hardware, the above-mentioned subsystems and units can be servers or terminals. In other words, the various subsystems of the task flow management system 10 or the units in the subsystems can be deployed in a distributed manner in a computing device cluster, or the task flow management system 10 can be implemented by a computing device cluster, for example, including a server and a terminal. Figure 1The system architecture shown is merely an exemplary architecture. In other possible implementations of the embodiment of the present application, the task process management system 10 may also be other architectures, and the present application does not impose any limitation on this.

[0098] The task flow management system 10 for executing the task flow management method is introduced above. Next, the task flow management method provided by the present application will be described in detail with reference to the accompanying drawings.

[0099] See also Figure 2 A flowchart of a task flow management method is shown, the method comprising:

[0100] S202: In response to a viewing operation on a task flow, obtaining an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow.

[0101] A task flow, or workflow, refers to an execution sequence consisting of a series of task nodes. A task node refers to a module used to perform tasks to achieve specific functions or provide specific capabilities. The dependencies between task nodes in a task flow can represent the execution order of the task nodes. Usually, a task flow represents a complex business that includes multiple operations. Multiple task nodes can represent multiple operations respectively. By executing the tasks to be performed by the task nodes according to the execution order of the task nodes, the processing of complex business can be realized. In this way, complex business can be decomposed into multiple simple operations to facilitate the processing of complex business.

[0102] Considering that the multiple task nodes included in the task flow can be executed by different users, the user can trigger the operation of viewing the task flow, thereby processing the task to be performed by the task node that the user needs to process. The triggering method of viewing the task flow can include multiple. In some possible implementations, the user can trigger the operation of viewing the task flow on the main page (for example, the task flow interface) of the task flow management system 10. In other possible implementations, the user can also trigger the operation of viewing the task flow through the prompt page when receiving the prompt information (for example, the to-do reminder message, the process processing reminder message) sent by the task flow management system 10.

[0103] In specific implementation, when a viewing operation on a task flow is detected, the account type of the triggering account that triggers the viewing operation and the node information of multiple task nodes in the task flow can be obtained in response to the viewing operation on the task flow. When obtaining the account type, the account identifier of the triggering account, including the account name or account number, can be first obtained, and then the account type of the triggering account can be obtained from the account information library according to the account identifier. When obtaining the node information, the multiple task nodes included in the task flow can be obtained according to the process identifier of the task flow, and the node information of the multiple task nodes can be obtained based on the node identifiers of the multiple task nodes included in the task flow.

[0104] The account type (also referred to as role) may include a category identifier obtained by classifying the account from at least one dimension. The account type may be different according to the classification dimension. For example, if the account is classified from the dimension of the type of work, the account type may include an operator account, a developer account, a tester account, etc. For another example, if the account is classified from the dimension of the work region, the account type may include a northeast region account, a northwest region account, a southwest region account, etc.

[0105] It should be noted that since accounts can be classified from different dimensions, an account may include multiple account types. For example, the account types of account A may include an operations staff account and a Northwest region account.

[0106] The node information of a task node may be information describing the task node. The node information of a task node indicates a set of account types that have access rights to the task node. In other words, the node information of a task node indicates the account types that can see the task node. In some examples, the node information of a task node may include the above-mentioned set of account types, also referred to as the role domain of the task node. Taking the creation of a promotion activity node as an example, the node information of the task node indicates the following set of account types: {operation staff account, management staff account}.

[0107] Considering that task nodes are usually stored in the task node resource pool in the form of objects, the properties of the corresponding objects can be read according to the task node identifier to obtain the node information of the task node. Among them, the node information can also include the node type. The node type can include a static task node or a dynamic task node. Different types of task nodes can use different execution engines for task processing.

[0108] S204: Determine a target task node that matches the triggering account from the multiple task nodes according to the account type of the triggering account and the node information of the multiple task nodes in the task flow.

[0109] In specific implementation, the target task node can be determined by comparing the account type of the triggering account and the account type set corresponding to the multiple task nodes. In some embodiments, the task node where the account type of the triggering account and the account type set corresponding to the multiple task nodes have an intersection can be determined as the target task node.

[0110] For example, the task process includes task node A, task node B, task node C and task node D. The account type set that has access rights to task node A is the operator account, the account type set that has access rights to task node B is the developer account, the account type set that has access rights to task node C is the operator account and the Northeast region account, the account type set that has access rights to task node D is the Northwest region account, the account type of trigger account A is the operator account and the Northeast region account, and the account type of trigger account B is the operator account and the Northwest region account. Therefore, the target task nodes that match trigger account A are task node A and task node C, and the target task nodes that match trigger account B are task node A, task node C and task node D.

[0111] In this way, for the same task process, the target task nodes matched by triggering accounts of different account types may be different, thereby implementing the screening of a large number of task nodes according to the account type to obtain the target task nodes related to the account type of the triggering account.

[0112] S206: Display the target task node in the task process so that the triggering account executes the triggering operation on the target task node to perform task processing.

[0113] In order to quickly obtain task nodes related to itself and process tasks in a timely manner, the target task nodes can be displayed, for example, in the task flow interface. In this way, for the same task flow, different target task nodes can be displayed to trigger accounts of different account types.

[0114] See also Figure 3 A schematic diagram of a task flow interface is shown, task flow interface 302 is a task flow interface for triggering account A, and task flow interface 304 is a task flow interface for triggering account B. The task flow includes task node A, task node B, task node C, and task node D. Triggering account A triggers a viewing operation for the task flow, and in response to the viewing operation, the account type of triggering account A and the node information of task nodes A to task nodes D are obtained, and according to the account type of triggering account A and the node information of task nodes A to task nodes D, it is determined that the target task nodes matching the triggering account A are task nodes A and task nodes C, so task nodes A and task nodes C are displayed in the task flow interface 302.

[0115] Similarly, triggering account B triggers a viewing operation on the task process. In response to the viewing operation, the account type of triggering account B and the node information of task node A to task node D are obtained, and based on the account type of triggering account B and the node information of task node A to task node D, it is determined that the target task nodes that match triggering account B are task node A, task node C, and task node D. Therefore, task node A, task node C, and task node D are displayed in the task process interface 304.

[0116] It can be seen that for trigger accounts of different account types, task nodes to which the account type of the trigger account has access rights can be displayed in the task flow interface, so that the task nodes in the task flow can be displayed in a targeted manner.

[0117] Based on the above description, the embodiment of the present application provides a task flow management method. In this method, different task nodes can support accounts of different account types to access the node. Through the account type and the node information of the task node, the target task node matching the account type can be determined from the task flow, and the target task node is displayed. In the face of complex task flows, users only need to pay attention to the task nodes related to themselves, so that the task processing efficiency can be improved and the user experience can be improved.

[0118] The above describes the process of displaying task nodes in the task flow. The following describes the task processing process in detail.

[0119] A target task node can be executed by multiple trigger accounts. Different trigger accounts can have different executable operations on the target task node. For example, some trigger accounts can perform viewing operations, while some trigger accounts can perform viewing operations and modification operations.

[0120] Based on this, in some possible implementations, the node information of the task node may also indicate an operation permission set corresponding to at least one account type in the account type set. The operation permission set includes at least one operation type. Specifically, the operation permission set may record at least one of the operation name, operation ID, or operation parameter of at least one operation type. In this way, by the account type of the triggering account, the executable operations of the target task node are restricted to avoid misoperation on the task node.

[0121] The steps of task processing may specifically include:

[0122] A2: In response to a trigger operation on the target task node, determine an operation permission set corresponding to the account type of the triggering account according to the node information.

[0123] A4: Display the task processing interface corresponding to the target task node.

[0124] Among them, the task processing interface can provide at least one operation control corresponding to the target task node, and the target operation control in the at least one operation control is used to execute the target operation. For example, when the target operation control is triggered, the target operation is executed, and the operation type of the target operation is at least one operation type in the operation permission set corresponding to the account type of the triggering account.

[0125] In this way, the user can execute the target operation by triggering at least one operation control in the task processing interface to process the target task node.

[0126] A6: In response to a trigger operation on a target operation control in at least one operation control, an interface corresponding to the target operation control is called to execute a target operation and obtain a task processing result of a target task node.

[0127] For different target task nodes, the interface type may be different. For example, the interface may be an application programming interface (API) interface or a remote procedure call (RPC) interface.

[0128] This will be explained below with reference to a specific example. For the target task node "Create a promotional campaign", the operation permission set corresponding to the account type of triggering account A includes operations for viewing existing promotional campaigns and creating new promotional campaigns. Therefore, the task processing interface of triggering account A may include operation controls for viewing existing promotional campaigns and operation controls for creating new promotional campaigns. In response to the triggering operation of triggering account A on one of the operation controls (for example, an operation control for creating a new promotional campaign), the interface corresponding to the operation control can be called to perform the target operation (for example, creating a new promotional campaign), thereby obtaining the task processing result (for example, a promotional campaign ID).

[0129] In some embodiments, in order to improve the efficiency of task processing, the task processing interface can be used to display information related to the task. At this time, the steps of task processing can specifically include:

[0130] B2: In response to the triggering operation on the target task node, determine the operation permission set corresponding to the account type of the triggering account according to the node information.

[0131] B4: According to the first content identifier of the target task node, the task processing interface corresponding to the target task node is displayed.

[0132] The first content identifier is used to indicate the pending information of the target task node. The task processing interface includes the pending information, which refers to the information that needs to be processed when executing the target task node. For example, taking the target task node "create a promotional activity" as an example, the pending information may include one or more of the name, start time, end time, and promotion form of the promotional activity.

[0133] By displaying the pending information on the task processing interface, users do not need to manually jump between different businesses. In this way, the pending information can be used to assist in triggering the account to process tasks, and tasks can be processed on one task processing interface, thereby improving task processing efficiency.

[0134] B6: In response to a trigger operation on a target operation control in at least one operation control, an interface corresponding to the target operation control is called to execute a target operation and obtain a task processing result of a target task node.

[0135] B8: Display the task processing interface according to the second content identifier of the target task node.

[0136] The second content identifier is used to indicate the task processing result of the target task node, and the task processing result includes the task processing result of the target task node. In some embodiments, the result display template of the target task node can be determined according to the second content identifier of the target task node, and then the task processing result is filled into the result display template, so that the task processing result of the target task node is displayed on the task processing interface.

[0137] After completing the task processing, the task processing results are directly displayed in the task processing interface, without jumping to other interfaces (such as the result viewing interface) to view the task processing results. The task processing and the viewing of the task processing results can be completed in one task processing interface, thereby improving the user's task processing experience.

[0138] It should be noted that, in the embodiment of the present application, the type of the first content identifier or the second content identifier is not limited. For example, the first content identifier or the second content identifier may be a uniform resource locator (URL).

[0139] Take the target task node "Create a promotion" as an example. According to the first content identifier of the target task node, the candidate promotion list page can be displayed in the task processing interface, and the triggering account can perform the operation of creating a new promotion in the candidate promotion list page to obtain the created promotion ID, and then display the promotion ID in the task processing interface according to the second content identifier of the target task node. In this way, through the content identifier of the target task node, task processing can be completed in one task processing interface without jumping to multiple different systems, which improves the convenience of task processing for users.

[0140] In addition, the embodiment of the present application can also realize the reset of the task node. Specifically, in response to the reset operation for the target task node, the task processing result of the target task node is reset. Figure 3 As shown, in response to the reset control operation next to the trigger target task node, the target task node processing result can be reset by releasing the storage space of the processing result. In this way, the task processing result of the target task node is cleared, and the triggering account can execute the target task node again to obtain the task processing result of the new target task node, thereby updating the task processing result.

[0141] In the process of executing the task flow, data sharing can also be achieved between task nodes. Specifically, the multiple task nodes may include a first task node and a second task node, and the task processing result of the first task node may be stored. In response to a trigger operation on the second task node, a task processing interface corresponding to the second task node is displayed, and the task processing interface includes the task processing result of the first task node.

[0142] By storing the task processing result of the first task node in the form of shared storage, other task nodes (such as the second task node) can obtain the task processing result of the first task node and use the task processing result of the first task node to perform task processing. In this way, the data flow between different task nodes is not limited to the dependency relationship of the task nodes, and nodes that do not have a dependency relationship or a direct dependency relationship can also use the task processing results of other task nodes to perform task processing, thereby realizing data sharing between multiple task nodes in the task flow.

[0143] The above describes the task processing process. Below, the task flow arrangement process in the embodiment of the present application will be described.

[0144] Scheduling a task flow refers to the process of arranging multiple task nodes into a task flow according to the dependency relationship of the task nodes. Specifically, in response to a selection operation for multiple candidate task nodes in a task node resource pool, multiple task nodes can be determined, and then in response to an arrangement operation for multiple task nodes, a task flow can be generated. Among them, the task node resource pool can store multiple candidate task nodes that can be arranged for the task flow, and the arrangement operation is used to indicate the dependency relationship of multiple task nodes in the task flow.

[0145] In some possible implementations, the task flow can be arranged through the process arrangement interface, thereby realizing visual process arrangement. Figure 4 The schematic diagram of a process orchestration interface shown in the figure, the process orchestration interface 40 may include a task node display area 402 and a task node orchestration area 404. In the task node display area 402, multiple candidate task nodes in the task node resource pool may be displayed in the form of task node icons, and a user (e.g., a process orchestration staff) may drag multiple candidate task node icons to the task node orchestration area 404 by dragging the candidate task node icons to select multiple task nodes included in the task process.

[0146] The process scheduler can perform schedule operations on multiple task nodes in the task node schedule area 404. In some embodiments, the dependency relationship of multiple task nodes can be represented by the direction of arrows, and task node A pointing to task node B can indicate that the dependent node of task node A is task node B.

[0147] Considering the increasing complexity of business scenarios, the dependency relationship between task nodes is also complicated. In an embodiment of the present application, the task flow of multiple branches (such as a tree) can be generated by determining the dependent node set and branch conditions of the task node. Specifically, in response to the connection operation for multiple task nodes, the dependent node set of at least one task node in the multiple task nodes is determined, and the dependent node set includes the task nodes that at least one task node depends on, in response to the configuration operation for multiple task nodes, the branch conditions are determined, so that the task flow can be generated according to the dependent node set and branch conditions of at least one task node.

[0148] By determining the dependent node set of the task node through the connection relationship between the task nodes, the dependent nodes of the task node can be determined, and then by configuring the branch conditions, the execution direction of the task process can be determined. In this way, a multi-branch, complex task process is generated to meet complex business scenarios and various user needs.

[0149] It should be noted that the above embodiments provided in this application can be implemented independently or in combination as required, and this application does not impose any restrictions on this.

[0150] Combination of the above Figures 1 to 4 The task flow management method 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.

[0151] See also Figure 1 The structure diagram of the task flow management system shown in the figure, the system 10 includes:

[0152] An acquisition unit 112 is used to acquire, in response to a viewing operation on a task flow, an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task nodes;

[0153] A determining unit 114, configured to determine a target task node matching the triggering account from the multiple task nodes according to the account type of the triggering account and the node information of the multiple task nodes in the task flow;

[0154] The display unit 116 is used to display the target task node in the task process so that the trigger account executes the trigger operation for the target task node to perform task processing.

[0155] In some possible implementations, the node information further indicates an operation permission set corresponding to at least one account type in the account type set, the operation permission set includes at least one operation type, and the determining unit 114 is specifically configured to:

[0156] In response to a trigger operation on the target task node, determining a permission set corresponding to the account type of the triggering account according to the node information;

[0157] The display unit 116 is specifically used for:

[0158] A task processing interface corresponding to the target task node is displayed, wherein the task processing interface provides at least one operation control corresponding to the target task node, wherein a target operation control in the at least one operation control is used to perform a target operation, and an operation type of the target operation is at least one operation type in an operation permission set corresponding to the account type of the triggering account.

[0159] In some possible implementations, the system 10 further includes:

[0160] The execution unit is used to respond to the trigger operation of the target operation control in the at least one operation control, call the interface corresponding to the target operation control, execute the target operation, and obtain the task processing result of the target task node.

[0161] In some possible implementations, the display unit 116 is specifically used to:

[0162] Displaying a task processing interface according to a first content identifier of the target task node, wherein the first content identifier is used to indicate information to be processed of the target task node, and the task processing interface includes the information to be processed;

[0163] The execution unit is specifically used for:

[0164] In response to a trigger operation on a target operation control in the at least one operation control, calling an interface corresponding to the target operation control, executing the target operation, and obtaining a task processing result of the target task node;

[0165] The display unit 116 is also used for:

[0166] The task processing interface is displayed according to the second content identifier of the target task node, where the second content identifier is used to indicate the task processing result of the target task node, and the task processing interface includes the task processing result of the target task node.

[0167] In some possible implementations, the system 10 further includes:

[0168] The reset unit is used to reset the task processing result of the target task node in response to the reset operation on the target task node.

[0169] In some possible implementations, the system 10 further includes:

[0170] An orchestration unit is used to determine the multiple task nodes in response to a selection operation on multiple candidate task nodes in a task node resource pool; and generate the task flow in response to an orchestration operation on the multiple task nodes, wherein the orchestration operation is used to indicate a dependency relationship between the multiple task nodes in the task flow.

[0171] In some possible implementations, the arrangement unit is specifically configured to:

[0172] In response to a connection operation for the plurality of task nodes, determining a dependent node set of at least one task node among the plurality of task nodes, the dependent node set including task nodes that the at least one task node depends on;

[0173] In response to configuration operations for the plurality of task nodes, determining a branch condition;

[0174] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.

[0175] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the system further includes:

[0176] A storage unit, used to store the task processing result of the first task node;

[0177] The display unit 116 is specifically used for:

[0178] In response to a trigger operation on the second task node, a task processing interface corresponding to the second task node is displayed, and the task processing interface corresponding to the second task node includes the task processing result of the first task node.

[0179] The task flow management system 10 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 management system 10 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes of each method in the illustrated embodiment are not described in detail here.

[0180] The present application also provides an electronic device. The electronic device is specifically used to implement Figure 1 The functions of the task flow management system 10 in the illustrated embodiment.

[0181] Figure 5 A schematic diagram of the structure of an electronic device 500 is provided. Figure 5 As shown, the electronic device 500 includes a bus 501, a processor 502, a communication interface 503 and a memory 504. The processor 502, the memory 504 and the communication interface 503 communicate with each other via the bus 501.

[0182] The bus 501 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 5 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.

[0183] The processor 502 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).

[0184] The communication interface 503 is used for communicating with the outside. For example, the communication interface 503 can be used for communicating with a terminal. The communication interface 503 is used to receive a viewing operation for a task flow triggered by a terminal so that the terminal displays a target task node.

[0185] The memory 504 may include a volatile memory, such as a random access memory (RAM). The memory 504 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).

[0186] The memory 504 stores executable codes, and the processor 502 executes the executable codes to perform the aforementioned task flow management method.

[0187] Specifically, in implementing Figure 1 In the case of the embodiment shown, and Figure 1 When each module or unit of the task flow management system 10 described in the embodiment is implemented by software, the execution Figure 1 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 504. The processor 502 executes the program code corresponding to each unit stored in the memory 504 to perform the aforementioned task flow management method.

[0188] 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 a 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 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 task flow management method applied to the task flow management system 10.

[0189] 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.

[0190] 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.

[0191] When the computer program product is executed by a computer, the computer executes any of the aforementioned task flow management methods. The computer program product may be a software installation package, and when any of the aforementioned task flow management methods is needed, the computer program product may be downloaded and executed on a computer.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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.

[0199] 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.

[0200] 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 task process management method, characterized in that: The method comprises: In response to a viewing operation on a task flow, obtaining an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task nodes; According to the account type of the triggering account and the node information of multiple task nodes in the task flow, determining a target task node matching the triggering account from the multiple task nodes; The target task node is displayed in the task process so that the trigger account executes a trigger operation on the target task node to perform task processing.

2. The method according to claim 1, characterized in that The node information further indicates an operation permission set corresponding to at least one account type in the account type set, the operation permission set including at least one operation type, and the method further includes: In response to a trigger operation on the target task node, determining, according to the node information, a set of operation permissions corresponding to the account type of the triggering account; A task processing interface corresponding to the target task node is displayed, wherein the task processing interface provides at least one operation control corresponding to the target task node, wherein a target operation control in the at least one operation control is used to perform a target operation, and an operation type of the target operation is at least one operation type in an operation permission set corresponding to the account type of the triggering account.

3. The method according to claim 2, characterized in that The method further comprises: In response to a trigger operation on a target operation control in the at least one operation control, an interface corresponding to the target operation control is called, the target operation is executed, and a task processing result of the target task node is obtained.

4. The method according to claim 2, characterized in that: The display of the task processing interface corresponding to the target task node includes: Displaying a task processing interface according to a first content identifier of the target task node, wherein the first content identifier is used to indicate information to be processed of the target task node, and the task processing interface includes the information to be processed; The method further comprises: In response to a trigger operation on a target operation control in the at least one operation control, calling an interface corresponding to the target operation control, executing the target operation, and obtaining a task processing result of the target task node; The task processing interface is displayed according to the second content identifier of the target task node, where the second content identifier is used to indicate the task processing result of the target task node, and the task processing interface includes the task processing result of the target task node.

5. The method according to claim 3 or 4, characterized in that: After obtaining the task processing result of the target task node, the method further includes: In response to a reset operation on the target task node, a task processing result of the target task node is reset.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: In response to a selection operation on a plurality of candidate task nodes in a task node resource pool, determining the plurality of task nodes; The task flow is generated in response to an orchestration operation on the plurality of task nodes, wherein the orchestration operation is used to indicate a dependency relationship between the plurality of task nodes in the task flow.

7. The method according to claim 6, characterized in that The generating the task flow in response to the orchestration operation on the plurality of task nodes comprises: In response to a connection operation for the plurality of task nodes, determining a dependent node set of at least one task node among the plurality of task nodes, the dependent node set including task nodes that the at least one task node depends on; In response to configuration operations for the plurality of task nodes, determining a branch condition; The task flow is generated according to the dependent node set of the at least one task node and the branch condition.

8. The method according to any one of claims 1 to 4, characterized in that: The plurality of task nodes include a first task node and a second task node, and the method further includes: Storing the task processing result of the first task node; In response to a trigger operation on the second task node, a task processing interface corresponding to the second task node is displayed, and the task processing interface corresponding to the second task node includes the task processing result of the first task node.

9. A task process management system, characterized in that: The system comprises: an acquisition unit, configured to acquire, in response to a viewing operation on a task flow, an account type of a triggering account that triggers the viewing operation and node information of a plurality of task nodes in the task flow, wherein the node information indicates a set of account types that have access rights to the task nodes; a determining unit, configured to determine a target task node matching the triggering account from the multiple task nodes according to the account type of the triggering account and the node information of the multiple task nodes in the task flow; A display unit is used to display the target task node in the task process so that the trigger account executes a trigger operation on the target task node to perform task processing.

10. An electronic device, characterized in that: The 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 8.

11. 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 8.

12. A computer program product, characterized in that When the computer program product is executed on an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 8.