Task flow management method, system and device, and medium and program product
By determining the target task nodes matching the account in the task process management system and displaying it, the problem of difficulty in obtaining information in complex task processes is solved, the task processing efficiency and user experience are improved, and the development cost is reduced.
Patent Information
- Application Number
- PCT/CN2024/090566
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-24
- Filing Date
- 2024-04-29
- Publication Date
- 2024-11-28
AI Technical Summary
In complex task processes, it is difficult for task processors to obtain task node information clearly and intuitively, resulting in reduced task processing efficiency. The existing technology requires the development of task processes for each task processor, resulting in a sharp development cost. Increase.
By obtaining the account type that triggers the viewing operation and the node information in the task process, determine the target task node that matches the account, and display the node in the task process, make the account perform related operations, provide operation controls to perform target operations, and improve tasks Processing efficiency.
Users only need to pay attention to task nodes related to themselves, improve task processing efficiency, reduce development costs, simplify user operations, improve user experience, and support complex and multi-branch task process orchestration.
Smart Images

Figure CN2024090566_28112024_PF_FP_ABST
Abstract
Description
Task process management methods, systems, equipment and media, and program products
[0001] This application claims priority to Chinese Patent Application No. 202310594838.7 filed on May 24, 2023, and the contents of the above-mentioned Chinese patent application disclosure are hereby incorporated by reference in their entirety as part of this application. Technical Field
[0002] The present disclosure relates to a task flow management method, system, device, computer-readable storage medium, and computer program product. Background Art
[0003] With the rapid development of computer technology, office automation (OA) applications have emerged, integrating computer technology with modern office processes. OA applications can automate office tasks. For example, OA applications can automatically advance task processes (also known as workflows), thereby improving office efficiency.
[0004] Specifically, a task flow can include multiple task nodes and the execution order between them. This allows the OA application to process the task nodes sequentially according to their execution order, automatically advancing the task flow. Different task nodes are typically handled by different task handlers, who can view the execution status of the task flow and process the task nodes that require processing.
[0005] 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 the task node information related to itself, which reduces the efficiency of task processing.
[0006] Summary of the Invention
[0007] This application provides a task process management method. This method displays task nodes that match their account types, allowing users to focus on only those relevant to them, improving task processing efficiency and user experience. This application also provides a system, device, computer-readable storage medium, and computer program product corresponding to the above method.
[0008] In a first aspect, the present application provides a task process management method. The method comprises:
[0009] 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;
[0010] Determining, according to the account type of the triggering account and node information of multiple task nodes in the task process, a target task node that matches the triggering account from the multiple task nodes;
[0011] The target task node is displayed in the task process, so that the triggering account executes a triggering operation on the target task node to perform task processing.
[0012] 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 including at least one operation type, and the method further includes:
[0013] In response to a trigger operation on the target task node, determining, based on the node information, a set of operation permissions corresponding to the account type of the triggering account;
[0014] The task processing interface corresponding to the target task node is displayed, and the task processing interface provides at least one operation control corresponding to the target task node. The target operation control in the at least one operation control is used to perform the target operation, 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.
[0015] In some possible implementations, the method further includes:
[0016] 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.
[0017] In some possible implementations, displaying the task processing interface corresponding to the target task node includes:
[0018] 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;
[0019] The method further comprises:
[0020] 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;
[0021] 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.
[0022] In some possible implementations, displaying the task processing interface according to the second content identifier of the target task node includes:
[0023] Determining a result display template for the target task node according to the second content identifier of the target task node;
[0024] 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.
[0025] In some possible implementations, after obtaining the task processing result of the target task node, the method further includes:
[0026] In response to the reset operation on the target task node, the task processing result of the target task node is reset.
[0027] In some possible implementations, the method further includes:
[0028] 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;
[0029] The task flow is generated in response to an orchestration operation on the plurality of task nodes, where the orchestration operation is used to indicate a dependency relationship among the plurality of task nodes in the task flow.
[0030] In some possible implementations, generating the task flow in response to the orchestration operation on the plurality of task nodes includes:
[0031] In response to a connection operation on 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;
[0032] determining a branch condition in response to configuration operations on the plurality of task nodes;
[0033] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.
[0034] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the method further includes:
[0035] Storing the task processing result of the first task node;
[0036] 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 a task processing result of the first task node.
[0037] In a second aspect, the present disclosure provides a task process management system. The system includes:
[0038] an acquiring unit, configured to, in response to a viewing operation on a task flow, acquire 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;
[0039] a determining unit, configured to determine, from the plurality of task nodes, a target task node that matches the triggering account based on the account type of the triggering account and node information of the plurality of task nodes in the task flow;
[0040] The display unit 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.
[0041] 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 including at least one operation type, and the determining unit is specifically configured to:
[0042] In response to a trigger operation on the target task node, determining, based on the node information, a set of operation permissions corresponding to the account type of the triggering account;
[0043] The display unit is specifically used for:
[0044] The task processing interface corresponding to the target task node is displayed, and the task processing interface provides at least one operation control corresponding to the target task node. The target operation control in the at least one operation control is used to perform the target operation, 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.
[0045] In some possible implementations, the system further includes:
[0046] 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.
[0047] In some possible implementations, the display unit is specifically configured to:
[0048] 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;
[0049] The execution unit is specifically used for:
[0050] 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;
[0051] The display unit is also used for:
[0052] 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.
[0053] In some possible implementations, the system further includes:
[0054] The reset unit is configured to reset the task processing result of the target task node in response to a reset operation on the target task node.
[0055] In some possible implementations, the system further includes:
[0056] An orchestration unit is configured 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 configured to indicate a dependency relationship between the multiple task nodes in the task flow.
[0057] In some possible implementations, the arrangement unit is specifically configured to:
[0058] In response to a connection operation on 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;
[0059] determining a branch condition in response to configuration operations on the plurality of task nodes;
[0060] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.
[0061] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the system further includes:
[0062] a storage unit, configured to store a task processing result of the first task node;
[0063] The display unit is specifically used for:
[0064] 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 a task processing result of the first task node.
[0065] In a third aspect, the present disclosure provides an electronic device comprising a processor and a memory. The processor and the memory communicate with each other. The processor is configured to execute instructions stored in the memory to cause the electronic device to perform the task flow management method according to the first aspect or any implementation of the first aspect.
[0066] In a fourth aspect, the present disclosure 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 process management method described in the first aspect or any implementation of the first aspect.
[0067] In a fifth aspect, the present disclosure 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.
[0068] Based on the implementations provided in the above aspects, the present disclosure can be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS
[0069] In order to more clearly illustrate the technical methods of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments.
[0070] FIG1 is an architecture diagram of a task process management system provided by an embodiment of the present disclosure;
[0071] FIG2 is a flowchart of a task process management method provided by an embodiment of the present disclosure;
[0072] FIG3 is a schematic diagram of a task flow interface provided by an embodiment of the present disclosure;
[0073] FIG4 is a schematic diagram of a process orchestration interface provided by an embodiment of the present disclosure; and
[0074] FIG5 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0075] The terms "first" and "second" in the embodiments of the present disclosure are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Therefore, the terms "first" and "second" may explicitly or implicitly include one or more of the features.
[0076] First, some technical terms involved in the embodiments of the present disclosure are introduced.
[0077] A task node is a module used to execute tasks, thereby achieving specific functions or providing specific capabilities. The tasks 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.
[0078] 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 one 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 operations corresponding to the creation of the promotional activity task may include the creation operation, and the operations corresponding to the approval of the promotional activity task may include approval and rejection. Furthermore, the operations corresponding to the approval of the promotional activity task may also include reassigning the approver. For another example, in an attendance management scenario, the tasks to be performed by the task nodes may include abnormal attendance record reminder tasks, abnormal attendance record correction tasks, and abnormal attendance record approval tasks. The operations corresponding to the abnormal attendance record reminder tasks include detail viewing, the operations corresponding to the abnormal attendance record correction tasks include correction and submission, and the operations corresponding to the abnormal attendance record approval tasks include approval and rejection.
[0079] 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 processed automatically or manually, the task processor can be set to the system or the 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 operations staff, and the task processor for approving a promotion task can be a management staff. It should be noted that the task 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 is completed.
[0080] To efficiently and conveniently generate task flows, task flow orchestration tools (e.g., process orchestration engines) have emerged. Task flow orchestration tools support visual operations, allowing users (e.g., process orchestrators) to orchestrate task nodes through visual operations such as dragging and dropping, and connecting within the process orchestration interface, thereby generating a task flow.
[0081] 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 the 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.
[0082] However, for task flows with a large number of task nodes, task handlers must search through the vast number of task nodes to find the task nodes relevant to them and then process them, which reduces task processing efficiency. If a separate task flow is developed for each task handler, development costs will increase dramatically.
[0083] In view of this, the present disclosure provides a task process management method. The method, in response to a viewing operation on a task process, obtains the account type (also sometimes referred to as the role) of a triggering account (a user's account) that triggers the viewing operation and the node information of multiple task nodes in the task process, wherein the node information indicates a set of account types that have access rights to the task node (also sometimes referred to as the role domain of the node). Then, based on the account type of the triggering account and the node information of multiple task nodes in the task process, a target task node that matches the triggering account is determined from the multiple task nodes, and then the target task node is displayed in the task process so that the triggering account executes the triggering operation on the target task node and performs task processing.
[0084] In this method, different task nodes can support accounts of different account types to access the node. Through the account type and node information of the task node, the target task node that matches the account type of the triggering account can be determined from the task process (for example, a task node whose role domain intersects with the role owned by the user) and the target task node is displayed. Faced with complex task processes, users only need to focus on the task nodes related to themselves, which can improve task processing efficiency and enhance user experience. Moreover, this method does not require the development of corresponding task processes for each task handler, significantly reducing development costs.
[0085] 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.
[0086] Furthermore, this method can construct complex, multi-branch task flows to meet diverse business needs. Furthermore, it can complete task processing within a single task processing interface, eliminating the need for users to manually navigate between different services. This significantly simplifies user operations, reduces the difficulty of task processing, and enhances the user experience.
[0087] In order to make the technical solution of the present disclosure clearer and easier to understand, the system architecture of the task process management method provided by the embodiment of the present disclosure is introduced below with reference to the accompanying drawings.
[0088] Referring to FIG1 , a schematic diagram of the architecture of a task flow management system is shown. Task flow management system 10 includes a scheduling subsystem 11, which can also be referred to as a construction subsystem and is responsible for advancing task flows and scheduling tasks. Scheduling subsystem 11 can advance task flows or schedule tasks under an event-driven approach. Events can be events in a message queue or Hypertext Transfer Protocol (HTTP) callback events.
[0089] Furthermore, the task flow management system 10 may also include at least one execution engine 12, which is used to automatically execute tasks in task nodes. Thus, the scheduling subsystem 11 can manage task nodes through at least one execution engine 12. For example, based on the type of task node, the scheduling subsystem 11 can determine the execution engine 12 corresponding to the type of task node, and automatically process the tasks to be executed by the task node through the execution engine 12, thereby automatically advancing the task flow.
[0090] 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.
[0091] The task node resource pool 13, also known as the atomic node market, is used to create atomic task nodes based on business data. The atomic task node refers to the smallest unit for generating a task process, and the task node can usually be reused. The creation process of the task node can be: abstracting the reusable task into an application programming interface (API), saving the abstracted API and related data into an object (object), and the object can be a data structure including at least one of the following fields: node type (for example, a static node or a dynamic node), operation name, operation identifier (ID), operation parameters, uniform resource locator (URL). Among them, the URL can include at least one of a page URL or a third-party URL (link). The above objects can be stored in the task node resource pool 13 as task nodes. The task node resource pool 13 is used to provide a plurality of programmable task nodes, each of which is used to implement a specific function or provide a specific capability.
[0092] Orchestration subsystem 14, also known as the orchestration center, is used to orchestrate task flows based on the task nodes provided by task node resource pool 13, thereby generating task flows. Orchestration subsystem 14 provides a visual orchestration interface through which users can select task nodes from task node resource pool 13 and perform orchestration operations such as connecting the selected task nodes, thereby orchestrating task flows and generating task flows.
[0093] The SOP subsystem 14, also known 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. Furthermore, 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.
[0094] Next, the process of the scheduling subsystem 11 performing task flow advancement or task scheduling will be described.
[0095] As shown in Figure 1, 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 the 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.
[0096] It should be noted that the subsystems in Figure 1 or the units in the subsystems are divided according to their functions, 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 process management system 10 or the units in the subsystems can be distributedly deployed in a computing device cluster, or the task process management system 10 can be implemented by a computing device cluster, for example, including servers and terminals. The system architecture shown in Figure 1 is only an exemplary architecture. In other possible implementations of the embodiments of the present disclosure, the task process management system 10 can also be other architectures, and the present disclosure does not limit this.
[0097] The above is an introduction to the task process management system 10 for executing the task process management method. Next, the task process management method provided by the present disclosure will be described in detail with reference to the accompanying drawings.
[0098] Referring to the flowchart of a task process management method shown in FIG2 , the method includes:
[0099] 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 multiple task nodes in the task flow.
[0100] A task flow, or workflow, is an execution sequence consisting of a series of task nodes. A task node is a module used to execute tasks to achieve specific functions or provide specific capabilities. The dependencies between task nodes in a task flow can represent the order in which the task nodes are executed. Typically, a task flow represents a complex business involving multiple operations, and multiple task nodes can each represent multiple operations. 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 achieved. In this way, complex business can be broken down into multiple simple operations, making it easier to handle complex business.
[0101] Considering that the multiple task nodes that task flow comprises can be performed by different users, the user can trigger the operation of viewing task flow, thereby the task to be performed by the task node that the user needs to process is processed.The triggering mode of viewing task flow can include multiple.In some possible implementations, the user can trigger the operation of viewing task flow on the main page (for example, task flow interface) of task flow management system 10.In other possible implementations, the user can also trigger the operation of viewing task flow by the prompting page when receiving the prompting information (for example, to-do list reminder message, process processing reminder message) that task flow management system 10 sends.
[0102] In a specific implementation, when a viewing operation on a task flow is detected, the account type of the triggering account that triggered 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 based on the account identifier. When obtaining the node information, the multiple task nodes included in the task flow can be obtained based on the process identifier of the task flow, and the node information of the multiple task nodes included in the task flow can be obtained based on the node identifiers of the multiple task nodes included in the task flow.
[0103] The account type (also known as role) can include a category identifier derived from classifying accounts based on at least one dimension. Account types can vary depending on the classification dimension. For example, if accounts are categorized based on job type, account types might include operations personnel accounts, developer accounts, and tester accounts. Another example is if accounts are categorized based on work region, account types might include Northeast region accounts, Northwest region accounts, and Southwest region accounts.
[0104] It should be noted that since accounts can be categorized from different dimensions, an account can include multiple account types. For example, the account types of account A can include an operations staff account and a Northwest region account.
[0105] The node information of a task node can be information describing the task node. The node information of a task node indicates the 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 can include the aforementioned set of account types, also known as the role domain of the task node. For example, for creating a promotion activity node, the node information of the task node indicates the following set of account types: {operation staff account, management staff account}.
[0106] Considering that task nodes are usually stored in the task node resource pool in the form of objects, the node information of the task node can be obtained by reading the properties of the corresponding object according to the task node identifier. Among them, the node information can also include the node type. The node type can include static task nodes or dynamic task nodes. Different types of task nodes can use different execution engines to perform task processing.
[0107] 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 process.
[0108] In a specific implementation, the target task node can be determined by comparing the account type of the triggering account with the set of account types corresponding to the multiple task nodes. In some embodiments, the target task node can be determined as the task node if the account type of the triggering account intersects with the set of account types corresponding to the multiple task nodes.
[0109] 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, and the account type set that has access rights to task node D is the Northwest region account. The account types of triggering account A are the operator account and the Northeast region account, and the account types of triggering account B are the operator account and the Northwest region account. Therefore, the target task nodes that match triggering account A are task node A and task node C, and the target task nodes that match triggering account B are task node A, task node C, and task node D.
[0110] In this way, for the same task process, the target task nodes matched by triggering accounts of different account types can be different, thereby enabling screening of a large number of task nodes according to account type to obtain target task nodes related to the account type of the triggering account.
[0111] 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.
[0112] To facilitate quick access to relevant task nodes and timely task processing, 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.
[0113] Referring to FIG3 , which illustrates a schematic diagram of a task flow interface, task flow interface 302 is the task flow interface for triggering account A, and task flow interface 304 is the task flow interface for triggering account B. The task flow includes task nodes A, B, C, and D. Triggering account A triggers a view operation for the task flow. In response to this view operation, the account type of triggering account A and the node information for task nodes A through D are obtained. Based on the account type of triggering account A and the node information for task nodes A through D, the target task nodes matching triggering account A are determined to be task nodes A and C. Therefore, task nodes A and C are displayed in task flow interface 302.
[0114] Similarly, triggering account B triggers a viewing operation for 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, the target task nodes that match triggering account B are determined to be 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.
[0115] It can be seen that for trigger accounts of different account types, task nodes with access permissions for the trigger account's account type can be displayed on the task process interface, thereby achieving targeted display of task nodes in the task process.
[0116] Based on the above description, the disclosed embodiments provide a task process management method. In this method, different task nodes can support accounts of different account types to access the node. Based on 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 complex task processes, users only need to focus on the task nodes related to them, which can improve task processing efficiency and enhance user experience.
[0117] The above describes the process of displaying task nodes in the task flow. The following describes the task processing process in detail.
[0118] 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 other trigger accounts can perform viewing operations and modification operations.
[0119] Based on this, in some possible implementations, the node information of a task node may also indicate a set of operation permissions corresponding to at least one account type in a set of account types. The set of operation permissions includes at least one operation type. Specifically, the set of operation permissions may record at least one of the operation name, operation ID, or operation parameters of the at least one operation type. In this way, the account type of the triggering account can be used to restrict the executable operations of the target task node, thereby preventing erroneous operations on the task node.
[0120] The steps of task processing may specifically include:
[0121] 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.
[0122] A4: Displays the task processing interface corresponding to the target task node.
[0123] 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.
[0124] 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.
[0125] A6: In response to a trigger operation on a target operation control in at least one operation control, call an interface corresponding to the target operation control, execute the target operation, and obtain a task processing result of the target task node.
[0126] 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.
[0127] 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 the operation of viewing existing promotional campaigns and the operation of creating new promotional campaigns. Therefore, the task processing interface of triggering account A can 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, the 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, the promotional campaign ID).
[0128] In some embodiments, in order to improve task processing efficiency, the task processing interface can be used to display task-related information. In this case, the task processing steps may specifically include:
[0129] 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.
[0130] B4: Displaying the task processing interface corresponding to the target task node according to the first content identifier of the target task node.
[0131] The first content identifier indicates pending information for the target task node. The task processing interface includes pending information, which refers to information that needs to be processed when executing the target task node. For example, taking the target task node "Create Promotion" as an example, the pending information may include one or more of the promotion's name, start time, end time, and promotion type.
[0132] By displaying pending information on the task processing interface, users do not need to manually jump between different businesses. In this way, the pending information is used to assist in triggering accounts to process tasks, and tasks are processed on one task processing interface, thereby improving task processing efficiency.
[0133] B6: In response to a trigger operation on a target operation control in at least one operation control, call an interface corresponding to the target operation control, execute the target operation, and obtain a task processing result of the target task node.
[0134] B8: Display the task processing interface according to the second content identifier of the target task node.
[0135] 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, a result display template of the target task node can be determined based on the second content identifier of the target task node, and the task processing result is then filled into the result display template. In this way, the task processing result of the target task node is displayed on the task processing interface.
[0136] After completing task processing, the task processing results are directly displayed in the task processing interface, without having to jump to other interfaces (such as the result viewing interface) to view the task processing results. Task processing and viewing of task processing results can be completed in one task processing interface, thereby improving the user's task processing experience.
[0137] It should be noted that, in the embodiment of the present disclosure, 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).
[0138] Let's take the target task node "Create a Promotion" as an example. Based on the first content identifier of the target task node, a candidate promotion list page can be displayed in the task processing interface. The triggering account can then create a new promotion in the candidate promotion list page, obtain the created promotion ID, and then display the promotion ID in the task processing interface based on 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 having to jump to multiple different systems, which improves the convenience of task processing for users.
[0139] In addition, the disclosed embodiment 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. As shown in Figure 3, in response to the operation of triggering the reset control next to the target task node, the reset of the target task node processing result can be realized 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 realizing the update of the task processing result.
[0140] During the execution of a task flow, data can be shared between task nodes. Specifically, the multiple task nodes may include a first task node and a second task node. The task processing results of the first task node may be stored. In response to a trigger operation on the second task node, the task processing interface corresponding to the second task node may be displayed, and the task processing interface may include the task processing results of the first task node.
[0141] By storing the task processing results 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 results of the first task node and use them to perform task processing. In this way, the data flow between different task nodes is not limited to the dependencies between task nodes. Nodes that do not have dependencies or direct dependencies 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.
[0142] The task processing process is described above. Now, the task flow arrangement process in the embodiment of the present disclosure will be described.
[0143] Orchestrating a task flow refers to the process of arranging multiple task nodes into a task flow based on the dependencies between the task nodes. Specifically, in response to a selection operation on multiple candidate task nodes in a task node resource pool, multiple task nodes can be determined, and then in response to an orchestration operation on the multiple task nodes, a task flow can be generated. The task node resource pool can store multiple candidate task nodes for task flow orchestration, and the orchestration operation is used to indicate the dependencies between the multiple task nodes in the task flow.
[0144] In some possible implementations, the task flow can be arranged through a process arrangement interface, thereby realizing visual process arrangement. Referring to the schematic diagram of a process arrangement interface shown in Figure 4, the process arrangement interface 40 can include a task node display area 402 and a task node arrangement area 404. In the task node display area 402, multiple candidate task nodes in the task node resource pool can be displayed in the form of task node icons. A user (for example, a process arrangement staff) can drag multiple candidate task node icons to the task node arrangement area 404 to realize the selection operation of multiple task nodes included in the task flow by dragging the candidate task node icons.
[0145] The process orchestrator can perform orchestration operations on multiple task nodes in the task node orchestration area 404. In some embodiments, the dependency relationship between multiple task nodes can be represented by the direction of arrows. Task node A pointing to task node B can indicate that the dependent node of task node A is task node B.
[0146] Taking into account the increasing complexity of business scenarios, the dependency relationships between task nodes are also complicated. In an embodiment of the present disclosure, a multi-branch (e.g., tree-like) task flow can be generated by determining a dependent node set and branch conditions of a task node. Specifically, in response to a connection operation for a plurality of task nodes, a dependent node set of at least one task node among the plurality of task nodes is determined, the dependent node set including the task nodes on which at least one task node depends, and in response to a configuration operation for a plurality of task nodes, a branch condition is determined, so that a task flow can be generated based on the dependent node set and branch conditions of at least one task node.
[0147] 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. 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 can be generated to meet complex business scenarios and various user needs.
[0148] It should be noted that the above embodiments provided in the present disclosure can be implemented independently or in combination as required, and the present disclosure does not limit this.
[0149] The above describes in detail the task process management method provided by the embodiment of the present disclosure in conjunction with Figures 1 to 4. The following describes the system and device provided by the embodiment of the present disclosure in conjunction with the accompanying drawings.
[0150] Referring to the structural diagram of the task process management system shown in FIG1 , the system 10 includes:
[0151] an acquiring unit 112 configured to, in response to a viewing operation on a task flow, acquire 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;
[0152] a determining unit 114 configured to determine, from the plurality of task nodes, a target task node that matches the triggering account based on the account type of the triggering account and node information of the plurality of task nodes in the task flow;
[0153] The display unit 116 is configured to display the target task node in the task process so that the triggering account executes a triggering operation on the target task node to perform task processing.
[0154] 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 including at least one operation type, and the determining unit 114 is specifically configured to:
[0155] In response to a trigger operation on the target task node, determining, based on the node information, a permission set corresponding to the account type of the triggering account;
[0156] The display unit 116 is specifically used for:
[0157] The task processing interface corresponding to the target task node is displayed, and the task processing interface provides at least one operation control corresponding to the target task node. The target operation control in the at least one operation control is used to perform the target operation, 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.
[0158] In some possible implementations, the system 10 further includes:
[0159] 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.
[0160] In some possible implementations, the display unit 116 is specifically configured to:
[0161] 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;
[0162] The execution unit is specifically used for:
[0163] 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;
[0164] The display unit 116 is further used for:
[0165] 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.
[0166] In some possible implementations, the system 10 further includes:
[0167] The reset unit is configured to reset the task processing result of the target task node in response to a reset operation on the target task node.
[0168] In some possible implementations, the system 10 further includes:
[0169] An orchestration unit is configured 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 configured to indicate a dependency relationship between the multiple task nodes in the task flow.
[0170] In some possible implementations, the arrangement unit is specifically configured to:
[0171] In response to a connection operation on 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;
[0172] determining a branch condition in response to configuration operations on the plurality of task nodes;
[0173] The task flow is generated according to the dependent node set of the at least one task node and the branch condition.
[0174] In some possible implementations, the multiple task nodes include a first task node and a second task node, and the system further includes:
[0175] a storage unit, configured to store a task processing result of the first task node;
[0176] The display unit 116 is specifically used for:
[0177] 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 a task processing result of the first task node.
[0178] According to the embodiment of the present disclosure, the task process management system 10 can correspond to executing the method described in the embodiment of the present disclosure, and the above-mentioned and other operations and / or functions of each module / unit of the task process management system 10 are respectively for realizing the corresponding processes of each method in the embodiment shown in Figure 2. For the sake of brevity, they will not be repeated here.
[0179] The present disclosure also provides an electronic device for realizing the functions of the task flow management system 10 in the embodiment shown in FIG1 .
[0180] FIG5 is a schematic diagram of the structure of an electronic device 500. As shown in FIG5, 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.
[0181] Bus 501 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified as address buses, data buses, control buses, etc. For ease of illustration, FIG5 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.
[0182] 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).
[0183] The communication interface 503 is used for external communication. For example, the communication interface 503 can be used for communication with a terminal. The communication interface 503 is used to receive a viewing operation for a task flow triggered by the terminal so that the terminal can display the target task node.
[0184] The memory 504 may include volatile memory, such as random access memory (RAM), or non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).
[0185] The memory 504 stores executable codes, and the processor 502 executes the executable codes to perform the aforementioned task flow management method.
[0186] Specifically, when implementing the embodiment shown in FIG1 , and when each module or unit of the task flow management system 10 described in the embodiment of FIG1 is implemented by software, the software or program code required to execute the functions of each module / unit in FIG1 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.
[0187] The present disclosure 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 that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the task process management method applied to the task process management system 10.
[0188] The present disclosure also provides a computer program product comprising one or more computer instructions that, when loaded and executed on a computing device, fully or partially generate the process or function described in the present disclosure.
[0189] 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.
[0190] 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 the computer.
[0191] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to the various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two 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 box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0192] The units involved in the embodiments described in this disclosure may be implemented in software or hardware, wherein the name of a unit / module does not, in some cases, limit the unit itself.
[0193] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and 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 chip (SOCs), complex programmable logic devices (CPLDs), and the like.
[0194] In the context of the embodiments of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0195] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the common and similar parts between the various embodiments. For the systems or devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method description.
[0196] It should be understood that in the present disclosure, "at least one (item)" refers to one or more, and "plurality" refers to 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 previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items 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.
[0197] It should also be noted that, in this document, relational terms such as first and second, etc., are used only 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 "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.
[0198] The steps of the methods or algorithms 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), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0199] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present disclosure. Various modifications to these embodiments will be readily apparent to one 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 disclosure. Therefore, the present disclosure is not limited to the embodiments shown herein, but is intended to be construed in the widest manner consistent with the principles and novel features disclosed herein.
Claims
1. A task process management method, comprising: 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 task flow management method according to claim 1, wherein: 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 task process management 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; The 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, the target operation control in the at least one operation control is used to perform the target operation, 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.
3. The task flow management method according to claim 2, further comprising: 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 task flow management method according to claim 2, wherein: The display of the task processing interface corresponding to the target task node includes: Displaying a task processing interface according to the first content identifier of the target task node, wherein the first content identifier is used to indicate the to-be-processed information of the target task node, and the task processing interface includes the to-be-processed information; The task flow management method further includes: In response to a trigger operation on a target operation control in the at least one operation control, calling the The interface corresponding to the target operation control executes the target operation to obtain the 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, wherein 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 task flow management method according to claim 3 or 4, wherein: After obtaining the task processing result of the target task node, the task flow management 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 task flow management method according to any one of claims 1 to 5, further comprising: 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 task flow management method according to claim 6, wherein: 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 task flow management method according to any one of claims 1 to 5, wherein: The multiple 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, comprising: An acquisition unit is configured to, in response to a viewing operation on a task flow, acquire a trigger for the viewing operation. The account type of the triggering account of the operation and the node information of multiple task nodes in the task process, wherein the node information indicates a set of account types that have access rights to the task node; 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; The display unit is configured 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.
10. An electronic device comprising a processor and a memory; wherein: The processor is used to execute instructions stored in the memory, so that the electronic device executes the task flow management method as described in any one of claims 1 to 8.
11. A computer-readable storage medium comprising instructions, wherein: The instruction instructs the electronic device to execute the task flow management method as described in any one of claims 1 to 8. 12 . A computer program product, when the computer program product is executed on an electronic device, enables the electronic device to execute the task flow management method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Workflow processing method and system
CN106897857A
Method and system for processing work flow
CN106897858A
Flow processing method and system, computer equipment and storage medium
CN114186817A
Authority management method and device, equipment and medium
CN114978601A
Electronic messaging integration to graph-based workflow platform
WO2019165371A1
