Task flow processing method and device, equipment, medium and product

Abstract

The invention provides a task flow processing method and device, equipment, a medium and a product, and is applied to a flow engine, the method comprises the steps that a flow configuration page is displayed, the flow configuration page is used for configuring a task flow, and the flow configuration page provides a view switching control; presenting the first task flow in the flow configuration page; wherein the first task process comprises a first process node of a non-artificial task type and a second process node of an artificial task type; and in response to a trigger operation for the view switching control, hiding a first process node in the first task process. According to the method, the process configuration personnel can efficiently and conveniently check the artificial task link in the task process, global understanding is formed for the process nodes related to the artificial task in the task process, and the process configuration efficiency is improved.

Description

Technical Field

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

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

[0003] However, a task flow usually includes a large number of flow nodes, and it is difficult for users to quickly and intuitively view the flow nodes of interest from the task flow. Summary of the invention

[0004] The present application provides a task flow processing method. The method can improve the configuration efficiency of the task flow. The present application also provides a device, an electronic device, a computer-readable storage medium, and a computer program product corresponding to the above method.

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

[0006] Display a process configuration page, which is used to configure the task process and provides a view switching control;

[0007] In the process configuration page, a first task process is presented; wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type;

[0008] In response to a triggering operation on the view switching control, the first process node in the first task process is hidden.

[0009] In some possible implementations, the first task process is used to execute a first business task, the first process node of the non-manual task type is used to indicate a logical operation process or a data processing process related to the first business task, and the second process node of the manual task type is used to indicate the interaction behavior with the user in the first business task.

[0010] In some possible implementations, the second process node of the manual task type includes at least one of the following: a process node for executing an approval operation, a process node for filling in information, and a process node for copying information.

[0011] In some possible implementations, in response to a trigger operation on the view switching control, the method further includes:

[0012] A trigger node, an end node, and a branch node indicating a flow structure of the first task flow are presented.

[0013] In some possible implementations, the first task process includes a main process and at least one sub-process, and in response to a trigger operation on the view switching control, hiding the first process node in the first task process includes:

[0014] In response to a trigger operation on the view switching control, determining the first process node in the main process and the at least one sub-process;

[0015] The first process node in the main process and the at least one sub-process is hidden.

[0016] In some possible implementations, the at least one sub-flow includes a first sub-flow and a second sub-flow that are in a nested relationship.

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

[0018] In the process configuration page, a second task process is presented; wherein the second task process includes a third process node of a non-manual task type;

[0019] The view switching control is presented in an untriggerable state.

[0020] In some possible implementations, the second process node that is not hidden in the first task process is in an uneditable state.

[0021] In a second aspect, the present application provides a task flow processing device, the device comprising:

[0022] A display module, used to display a process configuration page, wherein the process configuration page is used to configure the task process, and the process configuration page provides a view switching control;

[0023] A presentation module, used to present a first task process in the process configuration page; wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type;

[0024] The presentation module is further configured to hide the first process node in the first task process in response to a trigger operation on the view switching control.

[0025] In some possible implementations, the first task process is used to execute a first business task, the first process node of the non-manual task type is used to indicate a logical operation process or a data processing process related to the first business task, and the second process node of the manual task type is used to indicate the interaction behavior with the user in the first business task.

[0026] In some possible implementations, the second process node of the manual task type includes at least one of the following: a process node for executing an approval operation, a process node for filling in information, and a process node for copying information.

[0027] In some possible implementations, in response to a triggering operation on the view switching control, the presentation module is further configured to:

[0028] A trigger node, an end node, and a branch node indicating a flow structure of the first task flow are presented.

[0029] In some possible implementations, the first task process includes a main process and at least one sub-process, and the presentation module is specifically used to:

[0030] In response to a trigger operation on the view switching control, determining the first process node in the main process and the at least one sub-process;

[0031] The first process node in the main process and the at least one sub-process is hidden.

[0032] In some possible implementations, the at least one sub-flow includes a first sub-flow and a second sub-flow that are in a nested relationship.

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

[0034] In the process configuration page, a second task process is presented; wherein the second task process includes a third process node of a non-manual task type;

[0035] The view switching control is presented in an untriggerable state.

[0036] In some possible implementations, the second process node that is not hidden in the first task process is in an uneditable state.

[0037] In a third aspect, the present application provides an electronic device, the electronic device comprising a processor and a memory. The processor and the memory communicate with each other. The processor is used to execute instructions stored in the memory so that the electronic device executes the task flow processing method in the first aspect or any implementation of the first aspect.

[0038] 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 processing method described in the first aspect or any one of the implementations of the first aspect.

[0039] 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 processing method described in the first aspect or any one of the implementations of the first aspect.

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

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

[0042] The present application provides a task process processing method, which is applied to a process engine. The method first displays a process configuration page, wherein the process configuration page is used to configure the task process, and the process configuration page provides a view switching control. In the process configuration page, a first task process is presented, wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type, and in response to a trigger operation on the view switching control, the first process node in the first task process is hidden.

[0043] In this method, a view switching control is provided in the process configuration page. In the process of configuring the task process, the view switching control is triggered to switch from a view presenting all process nodes to a view presenting only process nodes of manual task types. By hiding the first process node of non-manual task type, the process configuration personnel can efficiently and conveniently view the manual task links in the task process, form a global understanding of the process nodes related to manual tasks in the task process, and improve the efficiency of process configuration. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] Figure 1 A flowchart of a task flow processing method provided in an embodiment of the present application;

[0046] FIG. 2A to FIG. 2F A schematic diagram of a process configuration page provided in an embodiment of the present application;

[0047] Figure 3 A schematic diagram of the structure of a task flow processing device provided in an embodiment of the present application;

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

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

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

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

[0052] The process engine is usually deployed in the application platform as a service (APaaS) platform as a service component. The aPaaS platform is a cloud service platform that simplifies the deployment and management of applications by providing scalable application infrastructure services. As part of the aPaaS platform, the process engine enables the aPaaS platform to support complex business process management and automation.

[0053] A task flow, also known as a workflow or a process template, can be understood as an execution sequence consisting of a series of process nodes. The dependencies between process nodes can represent the execution order of the process nodes. A process node can be understood as a module used to perform a specific task, thereby realizing a specific function or providing a specific capability.

[0054] Task processes are usually used to execute business tasks. For example, task processes can be used to execute business tasks such as onboarding approval, store inspections, and product demand status management. For business tasks with complex business logic, task processes may include a large number of process nodes, making it difficult for users (such as process schedulers) to quickly and intuitively view the process nodes of interest from the task process.

[0055] In view of this, the present application provides a task process processing method, which is applied to a process engine. The method first displays a process configuration page, wherein the process configuration page is used to configure the task process, and the process configuration page provides a view switching control. In the process configuration page, a first task process is presented, wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type, and in response to a trigger operation on the view switching control, the first process node in the first task process is hidden.

[0056] In this method, a view switching control is provided in the process configuration page. In the process of configuring the task process, the view switching control is triggered to switch from a view presenting all process nodes to a view presenting only process nodes of manual task types. By hiding the first process node of non-manual task type, the process configuration personnel can efficiently and conveniently view the manual task links in the task process, form a global understanding of the process nodes related to manual tasks in the task process, and improve the efficiency of process configuration.

[0057] To facilitate understanding of the technical solution provided by the embodiments of the present application, the following will be described in conjunction with the accompanying drawings. Figure 1 The flowchart of a task flow processing method shown is applied to a flow engine. The method specifically includes:

[0058] S101: Display the process configuration page.

[0059] The process configuration page, also known as the process configuration canvas, can be understood as a page provided by the process engine for configuring the task process. In other words, users (such as process schedulers) can schedule process nodes in the task process and the execution order between process nodes in the process configuration page. In addition, users can also configure node parameters for each process node in the process configuration page.

[0060] In an embodiment of the present application, the process configuration page provides a view switching control. The view switching control can be understood as a control for switching the process view presented in the process configuration page. That is, by triggering the view switching control, the process configuration page can present different process views including different process nodes for the same task process.

[0061] In this way, by providing view switching controls in the process configuration page, users (such as process schedulers) can switch views through quick and convenient operations to view different process views of the same task process, and present richer task process information to users during the process configuration process.

[0062] S102: On the process configuration page, presenting the first task process.

[0063] In the embodiment of the present application, the first task flow can be understood as the task flow currently being configured. Specifically, the first task flow can be a task flow with a process execution logic. In other words, the first task flow can be a task flow generated by arranging the execution order between the process nodes and the process nodes.

[0064] When the user has not triggered the view switching control, all process nodes of the first task process are presented in the process configuration page, which is the same as the traditional process configuration process.

[0065] In specific implementation, the first task process is presented in the process configuration page in the form of a topology diagram. In other words, all process nodes of the first task process constitute the nodes of the topology diagram, and the execution order between all process nodes of the first task process indicates the connection relationship between the nodes in the topology diagram.

[0066] In the embodiment of the present application, the first task flow includes a first flow node of a non-manual task type and a second flow node of a manual task type. That is to say, the first task flow includes two types of flow nodes: a non-manual task type and a manual task type. In the embodiment of the present application, the flow node of the non-manual task type in the first task flow is referred to as the first flow node, and the flow node of the manual task type in the first task flow is referred to as the second flow node.

[0067] Specifically, the first task process is used to execute the first business task, the first process node of the non-manual task type can be used to indicate the logical operation process or data processing process related to the first business task, and the second process node of the manual task type can be used to indicate the interactive behavior generated with the user in the first business task.

[0068] That is to say, the first process node of the non-manual task type can be understood as a data node and a logic node, and the second process node of the manual task type can be understood as a manual task node. During the execution of the first task flow, the first process node of the non-manual task type can usually be executed automatically without interacting with the user, and the second process node of the manual task type usually needs to interact with the user. For example, when the second process node of the manual task type is executed, a message corresponding to the second process node of the manual task type needs to be sent to the user.

[0069] A data node may indicate a data processing process, for example, a data node may include at least one of the following: a new record node, a record acquisition node, an update record node, a record deletion node, a storage submission node, and a node related to data communication with an external database. A logic node may indicate a logic operation process, for example, a logic node may include at least one of the following: a variable assignment node, a delay node, an error monitoring and processing node, a type conversion node, a data mapping node, a data assembly node, a formula node, and a function call node.

[0070] The second process node of the manual task type (i.e., the manual task node) may include at least one of the following: a process node for performing an approval operation, a process node for filling in information, and a process node for copying information. The process node for performing an approval operation may also be referred to as an approval node, the process node for filling in information may also be referred to as a filling task node, and the process node for copying information may also be referred to as a copy node.

[0071] For a process node for performing an approval operation (i.e., an approval node), when the process node is executed, the interaction with the user may be an action of sending a message of the approval task to the approver. For a process node for filling in information (i.e., a filling in task node), when the process node is executed, the interaction with the user may be an action of sending a message of the filling in task to the user. For a process node for copying information (i.e., a copy node), when the process node is executed, the interaction with the user may be an action of sending a copy message to the copy recipient.

[0072] It should be noted that in some process engines, the first process node of the non-manual task type is configured as a node parameter of the second process node of the manual task type. In other words, the user (for example, a process scheduler) can only add the second process node of the manual task type in the process configuration page, and when configuring the node for the second process node of the manual task type, configure the logical operation process or data processing process related to the business task. In this case, only the second process node of the manual task type will be presented in the process configuration page, and the first process node of the non-manual task type will not be presented.

[0073] In some other process engines, the first process node of the non-manual task type and the second process node of the manual task type are process nodes in a parallel relationship. In other words, the user (for example, a process scheduler) can add the first process node of the non-manual task type and the second process node of the manual task type in the process configuration page, and perform node configuration for the first process node of the non-manual task type and the second process node of the manual task type respectively. In this case, when the view switching control is not triggered, the first process node of the non-manual task type and the second process node of the manual task type (i.e., all process nodes) will be presented in the process configuration page.

[0074] Since the first process node of the non-manual task type will not be presented in the process engine that configures the first process node of the non-manual task type as the node parameter of the second process node of the manual task type, the task process processing method provided in the embodiment of the present application will not be applied to the process engine that configures the first process node of the non-manual task type as the node parameter of the second process node of the manual task type, but is applied to the process engine in which the first process node of the non-manual task type and the second process node of the manual task type are in a parallel relationship.

[0075] S103: In response to a triggering operation on a view switching control, hiding a first process node in a first task process.

[0076] The triggering operation for the view switching control may be understood as an operation for triggering view switching. For example, the triggering operation for the view switching control may be an operation of clicking the view switching control.

[0077] In the actual process configuration, since the second process node of the manual task type usually needs to interact with the user, in the process of configuring the process link, the process scheduler is more concerned with the process link composed of the second process node of the manual task type (also called the manual task link). For example, the second process node of the manual task type in the first task process can be related to approval. For example, the second process node of the manual task type in the first task process includes a process node for executing the approval operation, a process node for filling in the approval result, and a process node for copying the approval result. In this case, the process scheduler is more concerned with the manual task link in the first task process (also called the approval link here), such as how many times an application needs to be approved, who are the approvers, whether the multiple approvals are parallel or serial, whether the multiple approvals are co-signed or signed, etc.

[0078] When the view switching control is not provided, the entire first task process will be presented in the process configuration page, that is, all process nodes in the first task process (including the first process node of the non-manual task type and the second process node of the manual task type) are presented. The number of process nodes is large, and the relationship between the process nodes is relatively complex. It is difficult for process schedulers to intuitively and clearly understand the manual task link. In an embodiment of the present application, by providing a view switching control, the view presented in the process configuration page is switched to the manual task link, and the first process node of the non-manual task type is hidden, which helps process schedulers to efficiently and conveniently perform manual task links.

[0079] In some embodiments, considering the completeness of the manual task link, a trigger node, an end node, and a branch node indicating the process structure of the first task flow may also be presented.

[0080] Among them, the trigger node can be understood as a node that triggers the first task flow, that is, the trigger node is usually the starting node of the first task flow. In the embodiment of the present application, there is no restriction on the form of the trigger node. For example, the trigger node can be a general trigger (such as a button-based trigger, a record change-based trigger, a timer trigger, etc.), an application trigger (such as an application event-based trigger), a message queue trigger (such as a trigger when a specified queue message is received), etc.

[0081] The end node can be understood as a node for ending the first task flow, that is, the end node is usually the last node of the first task flow or each branch in the first task flow. The branch node for indicating the flow structure of the first task flow can be understood as a flow node that characterizes the execution logic of the first task flow. For example, the branch node for indicating the flow structure of the first task flow can be a conditional branch node, a parallel branch node, a list loop node, a conditional loop node, etc.

[0082] That is to say, although the trigger node, the end node and the branch node for indicating the process structure of the first task flow do not belong to the second process node of the manual task type, since the trigger node, the end node and the branch node for indicating the process structure of the first task flow can more completely reflect the overall link process of the manual task link, after triggering the view switching control, they can be presented together with the second process node of the manual task type.

[0083] Furthermore, the embodiment of the present application supports the presentation of manual task links in sub-processes. Specifically, the first task process includes a main process and at least one sub-process, and in response to a trigger operation on a view switching control, the first process node of the manual task type in the main process and at least one sub-process is determined, and the first process node in the main process and at least one sub-process is hidden.

[0084] That is to say, in the case where the first task process includes a sub-process and the sub-process includes a second process node of the manual task type, after triggering the view switching control, the first process node in the sub-process is also hidden, and the second process node in the sub-process is presented together with the second process node in the main process, presenting the complete manual task link of the first task process.

[0085] In some embodiments, at least one sub-process of the first task process includes a first sub-process and a second sub-process in a nested relationship. In this case, the second process nodes of the manual task type in the two sub-processes in the nested relationship can also be presented in the process configuration page. In this way, the process node relationship of the manual task link in the first task process is more completely presented.

[0086] In specific implementation, the number of nested layers supported for presentation can also be set. For example, a maximum of 5 layers of nested sub-processes are supported.

[0087] In addition, in some possible implementations, the second process node that is not hidden in the first task process is in an uneditable state. That is, when the user (for example, a process scheduler) triggers the view switching control, the view presented on the process configuration page is switched. After hiding the first process node in the first task process, the user can only view the second process node in the first task process on the process configuration page, but cannot edit the second process node, for example, cannot add a new process node, cannot delete a process node, cannot modify the node parameters of the process node, etc. If the user needs to edit the second process node in the first task process, it is necessary to return to the view presented in the process configuration page before the view switching (that is, the view presenting all the process nodes of the first task process) for editing. In this way, the view switching control only provides the view switching function, which is decoupled from other functions provided by the process engine to avoid mutual influence between different functions.

[0088] Furthermore, in response to the re-triggering operation on the view switching control, all process nodes of the first task process are re-presented in the process configuration page. That is, when the user (for example, a process scheduler) triggers the view switching control again, the view presented on the process configuration page will be changed back to the view presenting all process nodes.

[0089] In this method, a view switching control is provided in the process configuration page. In the process of configuring the task process, the view switching control is triggered to switch from a view presenting all process nodes to a view presenting only process nodes of manual task types. By hiding the first process node of non-manual task type, the process configuration personnel can efficiently and conveniently view the manual task links in the task process, form a global understanding of the process nodes related to manual tasks in the task process, and improve the efficiency of process configuration.

[0090] The foregoing describes the situation in which the first task flow includes a first flow node of a non-manual task type and a second flow node of a manual task type. In other embodiments, the task flow configured in the flow configuration page may not include a second flow node of a manual task type.

[0091] Specifically, in the process configuration page, a second task process is presented, wherein the second task process includes a third process node of a non-manual task type. In this case, a view switching control in an untriggerable state is presented.

[0092] That is to say, the second task flow only includes one type of flow node: a non-manual task type. In the embodiment of the present application, the flow node of the non-manual task type in the second task flow is referred to as a third flow node.

[0093] Regardless of whether the task flow in the process configuration page includes a process node of a manual task type, when the view switching control is not triggered, all the process nodes of the task flow are presented in the process configuration page. When the task flow in the process configuration page includes a process node of a manual task type (i.e., corresponding to the first task flow), the user (e.g., a process scheduler) can switch the view presented in the process configuration page to view the manual task link by triggering the view switching control. When the task flow in the process configuration page does not include a process node of a manual task type (i.e., corresponding to the second task flow), the view switching control is in an untriggerable state, and the user (e.g., a process scheduler) cannot trigger the view switching control and cannot switch the view presented in the process configuration page. In this way, misoperation and invalid operation during the process configuration process are avoided, and the efficiency of process configuration is improved.

[0094] Next, the task flow processing method provided by the embodiment of the present application is described in conjunction with the specific flow configuration process. FIG. 2A to FIG. 2F A schematic diagram of a process configuration page is shown in Figure 2A In the example, the process configuration page 20 presents a task process 21, wherein the task process 21 only includes process nodes of non-manual task types, and does not include process nodes of manual task types. That is, the task process 21 can be understood as the second task process in the embodiment of the present application.

[0095] exist Figure 2B In the process configuration page 20, a task process 22 is presented, wherein the task process 22 includes a process node of a non-manual task type and a process node of a manual task type (in Figure 2B Only the group leader approval node and the financial person in charge approval node are presented). That is to say, task flow 22 can be understood as the first task flow in the embodiment of the present application.

[0096] In the embodiment of the present application, the process configuration page provides a view switching control. Figure 2C As shown, the upper left area of ​​the process configuration page 20 presents a view switching control 23. Figure 2C In the example, the view switching control is in an untriggered state. At this time, the process configuration page 20 presents all process nodes of the task process 22.

[0097] The user (for example, a process scheduler) triggers the view switching control 23, such as Figure 2D As shown, in the upper left area of ​​the process configuration page 20, the view switching control 23 is in a triggered state. At this time, the process configuration page 20 hides the process nodes of non-manual task types in the task flow 22 and only presents the process nodes of the manual task type in the task flow 22. In addition, the process configuration page 20 also presents a trigger node (i.e. Figure 2D Fill in the form node in the form), the end node (i.e. Figure 2D The end node in the task flow 22 and the branch node for indicating the process structure of the task flow 22 (ie Figure 2D ) in the conditional branch node.

[0098] The present application embodiment supports the presentation of manual task links in sub-processes. Figure 2E As shown, in the upper left area of ​​the process configuration page 20, the view switching control 23 is in a triggered state, and the process configuration page 20 hides the process nodes of non-manual task types in the task process 24, and only presents the process nodes of manual task types in the task process 24. The task process 24 includes a sub-process, and in the process configuration page 20, the process nodes of non-manual task types in the sub-process are also hidden, and only the process nodes of manual task types in the sub-process are presented.

[0099] exist Figure 2F In the process configuration page 22, a task process 21 is presented, and the task process 21 only includes process nodes of non-manual task types, and does not include process nodes of manual task types. In this case, the view switching control is in an untriggerable state. In response to the triggering operation on the view switching control, a prompt information 25 is presented. The prompt information 25 can be used to prompt the user (for example, a process scheduler) that when the task process does not include a process node of a manual task type, the view switching control is in an untriggerable state.

[0100] Combination of the above Figure 1 2 and 3 provide a detailed introduction to the task flow processing method provided in the embodiment of the present application. The following will introduce the apparatus and device provided in the embodiment of the present application in conjunction with the accompanying drawings.

[0101] See also Figure 3 The structure diagram of the task flow processing device shown in FIG. 30 includes:

[0102] A display module 301 is used to display a process configuration page, where the process configuration page is used to configure a task process and provides a view switching control;

[0103] A presentation module 302, configured to present a first task process in the process configuration page; wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type;

[0104] The presentation module 302 is further configured to hide the first process node in the first task process in response to a trigger operation on the view switching control.

[0105] In some possible implementations, the first task process is used to execute a first business task, the first process node of the non-manual task type is used to indicate a logical operation process or a data processing process related to the first business task, and the second process node of the manual task type is used to indicate the interaction behavior with the user in the first business task.

[0106] In some possible implementations, the second process node of the manual task type includes at least one of the following: a process node for executing an approval operation, a process node for filling in information, and a process node for copying information.

[0107] In some possible implementations, in response to a triggering operation on the view switching control, the presenting module 302 is further configured to:

[0108] A trigger node, an end node, and a branch node indicating a flow structure of the first task flow are presented.

[0109] In some possible implementations, the first task process includes a main process and at least one sub-process, and the presentation module 302 is specifically used to:

[0110] In response to a trigger operation on the view switching control, determining the first process node in the main process and the at least one sub-process;

[0111] The first process node in the main process and the at least one sub-process is hidden.

[0112] In some possible implementations, the at least one sub-flow includes a first sub-flow and a second sub-flow that are in a nested relationship.

[0113] In some possible implementations, the presenting module 302 is further configured to:

[0114] In the process configuration page, a second task process is presented; wherein the second task process includes a third process node of a non-manual task type;

[0115] The view switching control is presented in an untriggerable state.

[0116] In some possible implementations, the second process node that is not hidden in the first task process is in an uneditable state.

[0117] The task flow processing device 30 according to the embodiment of the present application may correspond to executing 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 processing device 30 are respectively to implement Figure 1 For the sake of brevity, the corresponding processes of each method in the illustrated embodiment are not described in detail here.

[0118] The present application also provides an electronic device. The electronic device is specifically used to implement Figure 3 The functions of the task flow processing device 30 in the illustrated embodiment.

[0119] Figure 4 A schematic diagram of the structure of an electronic device 400 is provided. Figure 4 As shown, the electronic device 400 includes a bus 401, a processor 402, a communication interface 403 and a memory 404. The processor 402, the memory 404 and the communication interface 403 communicate with each other via the bus 401.

[0120] The bus 401 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 4 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.

[0121] The processor 402 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).

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

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

[0124] The memory 404 stores executable codes, and the processor 402 executes the executable codes to perform the aforementioned task flow processing method.

[0125] Specifically, in implementing Figure 3 In the case of the embodiment shown, and Figure 3 When each module or unit of the task flow processing device 30 described in the embodiment is implemented by software, the execution Figure 3 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 404. The processor 402 executes the program code corresponding to each unit stored in the memory 404 to perform the aforementioned task flow processing method.

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

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

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

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

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

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

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

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

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

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

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

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

[0138] 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 flow processing method, characterized in that: Applied to a process engine, the method comprises: Display a process configuration page, which is used to configure the task process and provides a view switching control; In the process configuration page, a first task process is presented; wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type; In response to a triggering operation on the view switching control, the first process node in the first task process is hidden.

2. The method according to claim 1, characterized in that The first task process is used to execute a first business task, the first process node of the non-manual task type is used to indicate a logical operation process or a data processing process related to the first business task, and the second process node of the manual task type is used to indicate the interaction behavior generated with the user in the first business task.

3. The method according to claim 1, characterized in that The second process node of the manual task type includes at least one of the following: a process node for executing an approval operation, a process node for filling in information, and a process node for copying information.

4. The method according to claim 1, characterized in that In response to a trigger operation on the view switching control, the method further includes: A trigger node, an end node, and a branch node indicating a flow structure of the first task flow are presented.

5. The method according to claim 1, characterized in that The first task flow includes a main flow and at least one sub-flow, and in response to the triggering operation on the view switching control, hiding the first flow node in the first task flow includes: In response to a trigger operation on the view switching control, determining the first process node in the main process and the at least one sub-process; The first process node in the main process and the at least one sub-process is hidden.

6. The method according to claim 5, characterized in that The at least one sub-process includes a first sub-process and a second sub-process in a nested relationship.

7. The method according to claim 1, characterized in that The method further comprises: In the process configuration page, a second task process is presented; wherein the second task process includes a third process node of a non-manual task type; The view switching control is presented in an untriggerable state.

8. The method according to any one of claims 1 to 7, characterized in that: The second process nodes that are not hidden in the first task process are in a non-editable state.

9. A task flow processing device, characterized in that: The device comprises: A display module, used to display a process configuration page, wherein the process configuration page is used to configure the task process, and the process configuration page provides a view switching control; A presentation module, used to present a first task process in the process configuration page; wherein the first task process includes a first process node of a non-manual task type and a second process node of a manual task type; The presentation module is further configured to hide the first process node in the first task process in response to a trigger operation on the view switching control.

10. An electronic device, characterized in that: The electronic device comprises a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the electronic device performs the method according to any one of claims 1 to 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 The computer program product comprises computer readable instructions for implementing the method according to any one of claims 1 to 8.

Images