Method and apparatus for editing workflow, and device, storage medium and program product

Abstract

A method and apparatus for editing a workflow, and a device, a storage medium and a program product. The method comprises: presenting an editing interface of a workflow, wherein the editing interface is used for editing a node graph corresponding to the workflow; in response to receiving a preset operation performed on a target node in the node graph, presenting a configuration window associated with the target node, wherein the configuration window comprises a plurality of configuration pages used for configuring the target node, and information that different configuration pages support configuration for is independent of each other; and acquiring update configuration information of the target node via the configuration window, so as to update the workflow. Therefore, the efficiency of workflow editing can be improved, and the efficiency of maintaining and updating a workflow can be improved.

Description

Method, apparatus, device, storage medium and program product for editing workflow Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, computer-readable storage media, and computer program products for providing an editing workflow. Background Art

[0002] Visual editing of workflows is a method of designing and organizing workflows through a graphical interface, which allows users to create, edit, and modify workflows in an intuitive way. How to edit workflows is a key issue.

[0003] Summary of the Invention

[0004] In a first aspect of the present disclosure, a method for editing a workflow is provided. The method comprises: presenting a workflow editing interface for editing a node graph corresponding to the workflow; in response to receiving a preset operation on a target node in the node graph, presenting a configuration window associated with the target node, the configuration window including multiple configuration pages for configuring the target node, wherein the configuration information supported by different configuration pages is independent of each other; and obtaining updated configuration information of the target node via the configuration window to update the workflow.

[0005] In a second aspect of the present disclosure, a device for editing a workflow is provided. The device includes: a first presentation module configured to present an editing interface for the workflow, the editing interface being used to edit a node graph corresponding to the workflow; a second presentation module configured to, in response to receiving a preset operation on a target node in the node graph, present a configuration window associated with the target node, the configuration window including multiple configuration pages for configuring the target node, wherein the configuration information supported by different configuration pages is independent of each other; and an update module configured to obtain updated configuration information of the target node via the configuration window to update the workflow.

[0006] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0007] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0008] In a fifth aspect of the present disclosure, a computer program product is provided, which includes computer-executable instructions, and when the computer-executable instructions are executed by a processor, the method of the first aspect is implemented.

[0009] It should be understood that the content described in this summary section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

[0012] 2A and 2B show schematic diagrams of interfaces according to some embodiments of the present disclosure;

[0013] FIG3 shows a flowchart of an interaction process according to some embodiments of the present disclosure;

[0014] FIG4 shows a schematic structural block diagram of an apparatus for interaction according to certain embodiments of the present disclosure;

[0015] FIG5 shows a block diagram of an electronic device capable of implementing various embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0017] It should be noted that the titles of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and any type of embodiment may be included under any section / subsection. Furthermore, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or in different sections / subsections.

[0018] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0019] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects shall comply with the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user is aware of and confirms them. Accordingly, when implementing the various embodiments of the present disclosure, the types, scope of use, and usage scenarios of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method may vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0020] If this specification and the solutions in the examples involve the processing of personal information, such processing will be done only with a legitimate basis (such as with the consent of the subject of personal information or as necessary for the performance of a contract) and only within the prescribed or agreed scope. A user's refusal to process personal information other than that required for basic functions will not affect the user's use of basic functions.

[0021] As described above, electronic devices can generally edit workflows based on user operations of creating, adding, and editing nodes in a graphical interface. Furthermore, users (eg, developers) can use some process libraries to assist in implementing process nodes.

[0022] For example, some process libraries can provide users with editable components, allowing them to write components (such as React components, a type of code component in a database used to build user interfaces). Electronic devices can implement the business logic of a complete workflow based on the component coupling, association, and other component relationships set by users during the component writing process.

[0023] This workflow editing method has low workflow development efficiency due to the complexity of the code, and subsequent workflow maintenance is difficult and the workflow update efficiency is low.

[0024] For example, some process libraries provide users with callable nodes based on the logic of nodes at the graph editing level (such as node position, node quantity, etc.). Electronic devices can also implement the business logic of the complete workflow based on the nodes called by the user and the node relationships set by the user.

[0025] However, this workflow editing method also has many problems. For example, the execution logic of the node itself is unknown, which makes the maintenance of the node itself, the editing of node relationships between nodes, and the linkage between nodes and other external applications extremely complicated.

[0026] In some more complex process editing scenarios, nodes also have characteristics such as rich node information, many node types, complex logic, and rich linkages between nodes.

[0027] Therefore, traditional technologies still face great challenges in the maintainability, scalability, and stability of workflow application projects.

[0028] In light of this, embodiments of the present disclosure propose a workflow editing solution. This solution presents a workflow editing interface for editing the node graph corresponding to the workflow. Furthermore, in response to receiving a preset operation on a target node in the node graph, a configuration window associated with the target node is presented. The configuration window includes multiple configuration pages for configuring the target node, where the configuration information supported by different configuration pages is independent of each other. Furthermore, updated configuration information for the target node can be obtained through the configuration window to update the workflow.

[0029] Based on this approach, the embodiments of the present disclosure can provide multiple configuration pages for configuring target nodes. The configuration information supported by different configuration pages is independent of each other, that is, the configuration capabilities of different configuration pages are independent. Therefore, the codes of the business logics represented by different configuration information will not pollute each other, reducing the complexity of the code and improving the maintainability of the code. Furthermore, in the subsequent maintenance and expansion process, since the business logics represented by different configuration information are independent of each other, the adjustment of one or more configuration information will not affect other business logics, and the addition or deletion of one or more configuration information will not affect other business logics, thereby improving the maintainability, scalability and stability of the workflow. Therefore, the embodiments of the present disclosure can improve the efficiency of workflow editing and improve the efficiency of workflow maintenance and updating.

[0030] Sample Environment

[0031] FIG1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. As shown in FIG1 , the example environment 100 may include an electronic device 110 .

[0032] In the example environment 100, an application 120 is installed in an electronic device 110. A user 140 can interact with the application 120 via the electronic device 110 and / or its attached devices. The application 120 can be an integrated development environment application or any other suitable application.

[0033] In the environment 100 of FIG. 1 , if the application 120 is active, the application 120 may provide a presentation interface 150 to the user 140 .

[0034] In some embodiments, the electronic device 110 communicates with the server 130 to provide services for the application 120. The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as "wearable" circuitry, etc.).

[0035] The server 130 may be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks, and big data and artificial intelligence platforms. The server 130 may include, for example, a computing system / server such as a mainframe, an edge computing node, a computing device in a cloud environment, etc. The server 130 may provide background services for the application 120 that supports content presentation in the electronic device 110.

[0036] A communication connection may be established between the server 130 and the electronic device 110. The communication connection may be established via a wired or wireless method. The communication connection may include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus connection, a Wi-Fi connection, etc., and the embodiments of the present disclosure are not limited in this respect. In the embodiments of the present disclosure, the server 130 and the electronic device 110 may implement signaling interaction via the communication connection between them.

[0037] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure.

[0038] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0039] Example Interaction

[0040] An example interaction process according to an embodiment of the present disclosure will be described below with reference to Figures 2A and 2B. Figures 2A and 2B show example interfaces 200A and 200B according to some embodiments of the present disclosure, which may be provided by the electronic device 110 shown in Figure 1, for example.

[0041] An example interaction process according to an embodiment of the present disclosure will be described below with reference to Figures 2A and 2B. Figures 2A and 2B show example interfaces 200A and 200B according to some embodiments of the present disclosure, which may be provided by the electronic device 110 shown in Figure 1, for example.

[0042] As shown in Figure 2A, the electronic device 110 can, for example, present an interface 200A (workflow editing interface), which can present predefined workflows aaa, workflow bbb, workflow ccc, workflow ddd, workflow eee, and workflow fff. In response to receiving an editing operation for any predefined workflow, a node graph of the workflow can be presented, such as workflow aaa and workflow bbb. In the workflow editing interface, a list of node graphs for switching between multiple workflows can be presented to quickly switch between the node graphs of the workflows. Taking the presentation of the node graph 210 of workflow bbb as an example, the editing interface 200A can be used to edit the node graph 210 of workflow bbb. The node graph 210 can include node windows corresponding to multiple nodes, such as node window 211, node window 212, node window 213, and the like.

[0043] In node graph 210, two associated nodes can be connected using a target method, while two unassociated nodes can be left unconnected. The target method can be based on a predetermined line element or any other appropriate connection method. Line elements can be straight lines, broken lines, curves, etc., which are not described in detail here.

[0044] In some embodiments, the two nodes in an associated relationship can be in a sequential call relationship. Taking Figure 2A as an example, the relationship between node window 212 and node window 213 is a sequential call relationship, and during the execution of the workflow, the node corresponding to node window 212 can be called first, and then the node corresponding to node window 213 can be called. In other embodiments, the two node windows in an associated relationship can also represent the relationship between a parent node and a child node, that is, the two associated nodes can be in a hierarchical relationship, where the parent node is the upper level corresponding to the child node.

[0045] In some embodiments, in response to receiving a preset operation on a target node in the node map 210 , the electronic device 110 may present a configuration window associated with the target node, the configuration window.

[0046] As some examples, the target node may be any appropriate node, such as a process node, etc.

[0047] In some embodiments, electronic device 110 may present a node management interface corresponding to a target node in response to receiving a preset operation. Furthermore, the node management interface may include a canvas component and a configuration window, and the canvas component may display a node window for the target node. Using FIG. 2A as an example, the canvas component may display node windows 211, 212, and 213 for the target node.

[0048] In some embodiments, the configuration window includes multiple configuration pages for configuring the target node. The multiple configuration pages can support different business logic, and the number of multiple configuration pages can be set as needed. A list of multiple configuration pages can be presented in the configuration window to quickly switch between configuration pages. Preset operations include but are not limited to control triggering operations, sliding button triggering operations, text box input instructions, etc.

[0049] In some embodiments, the plurality of configuration pages may include one or more of a first configuration page, a second configuration page, a third configuration page, a fourth configuration page, and a fifth configuration page.

[0050] As some examples, the first configuration page is used to configure the form information corresponding to the target node, including adding and deleting form information, presenting a form information interface, and the like.

[0051] The second configuration page is used to configure the input information of the target node, including the input data protocol (used to indicate the type of input data, the data type of input data, the form presentation form, etc.), modify the input data protocol, the form rendering information of the form information updated due to the modification of the input data protocol, etc.

[0052] The third configuration page is used to configure the output information of the target node, including the output data protocol (used to indicate the type of output data, the data type of output data, etc.), modify the output data protocol, the form rendering information updated due to the modification of the output data protocol, synchronize modification information with other applications or platforms or systems, etc.

[0053] The fourth configuration page is used to configure the error handling logic of the target node, including capturing error information during the operation of the target node, storing error information, presenting error information in the node graph of the target node, etc.

[0054] The fifth configuration page is used to configure the metadata of the target node. The metadata includes the node type, node name, node identification information, node description information, etc. of the target node. The fifth configuration page can modify the metadata of the target node, present the modification process of the metadata of the target node in the node diagram of the target node, etc.

[0055] For example, the configuration page may be as shown in Table 1 below. Table 1 includes configuration information supported by different configuration pages and configuration information descriptions corresponding to each configuration information.

[0056] Table 1

[0057] Taking FIG. 2A as an example, the configuration window 220 in the interface 200A includes multiple configuration pages, namely, configuration page 221 (script), configuration page 222 (input), configuration page 223 (output), and configuration page 224 (information) as shown in FIG. 2A .

[0058] In some embodiments, the plurality of configuration pages correspond to a plurality of plug-ins of the target node, and the plurality of plug-ins are mutually orthogonal, that is, independent of each other. In addition, any of the plurality of plug-ins can be plugged in or out (added or deleted).

[0059] In some embodiments, the electronic device 110 may receive a first request to delete a first plug-in from among a plurality of plug-ins. Further, the electronic device 110 may disable a first service logic corresponding to the first plug-in on the target node based on the first request.

[0060] As some examples, the first plug-in may be any one or more of a plurality of plug-ins. The first request may be generated in response to receiving a trigger operation of a user to delete a control for the first plug-in, or may be obtained by receiving a first request for the first plug-in automatically generated by the electronic device 110, and so on.

[0061] In some embodiments, the electronic device 110 may disable the first service logic of the target node based on the first request. Further, the electronic device 110 may delete the configuration page corresponding to the first plug-in from multiple configuration pages of the target node.

[0062] In some embodiments, the electronic device 110 may receive a second request to add one or more second plug-ins. Based on the second request, the electronic device 110 may add a second service logic corresponding to the second plug-in to the target node.

[0063] As some examples, the second plug-in can be one or more of a plurality of plug-ins, or can be determined by user-defined addition. The second request can be generated in response to receiving a user trigger operation to add a control for the second plug-in, or can be obtained by receiving a second request for the second plug-in automatically generated by the electronic device 110, etc.

[0064] In some embodiments, the electronic device 110 adds the second service logic to the target node based on the second request. Further, the electronic device may add a configuration page corresponding to the second plug-in to multiple configuration pages of the target node.

[0065] In some embodiments, the user operates one or more configuration items in multiple configuration pages of the target node to update the configuration information in the multiple configuration pages. Based on the updated configuration information of the target node, the electronic device 110 updates the node window corresponding to the target node in the node map to indicate at least part of the updated configuration information.

[0066] Taking FIG2B as an example, for node window 212, the interface 200B may present a second configuration page (Inputs) associated with the node corresponding to the node window 212, and the second configuration page (Inputs) presents editable configuration items, such as "keywords", "types", "required", "operations", etc. as shown in FIG2B. When a user triggers an update operation for a configuration item in the second configuration page, the electronic device 110 may update one or more configuration items under the "keywords", "types", "required", and "operations" options in the second configuration page (Inputs).

[0067] As some examples, a user can enter text in a text box to perform operations on keywords and types, such as adding, deleting, and modifying keywords. Alternatively, a user can trigger a selection operation on a "required" configuration, selecting "required" or "optional." Based on the user's trigger selection operation, electronic device 110 updates the form item permissions for the corresponding keyword to required or optional input. Alternatively, electronic device 110 can update other configuration items based on the updated configuration information, and so on.

[0068] It should be noted that the configuration window of the node corresponding to the node window 212 presented in the interface 200B may be triggered to display after the node window 212 is added to the node graph 210 of the interface 200. Of course, the configuration window of the node corresponding to the node window 212 may also be triggered to display under other triggering conditions. For example, after the node window 212 is added, the electronic device 110 may trigger the display of the node configuration window corresponding to the node window 212 in response to the selection of a predetermined trigger button.

[0069] Based on this approach, on one hand, embodiments of the present disclosure can provide multiple independent plug-ins. Furthermore, embodiments of the present disclosure support independent management of multiple plug-ins, such as upgrading one or more of the multiple plug-ins, adding one or more plug-ins, or deleting one or more of the multiple plug-ins. Furthermore, embodiments of the present disclosure support any combination of different plug-ins, thereby increasing the flexibility of plug-in usage.

[0070] On the other hand, the embodiments of the present disclosure provide corresponding configuration pages for multiple independent plug-ins, thereby achieving independence between the business logics corresponding to the multiple plug-ins during the workflow configuration process.

[0071] Therefore, the embodiments of the present disclosure can reduce the probability of errors in workflow execution, improve the update efficiency of workflows and the stability of updated workflows, and multiple plug-ins are independent of each other, so that the business of each plug-in is clear and the flexibility of editing each plug-in is improved.

[0072] Example Process

[0073] FIG3 shows a flow chart of a personal information page interaction process 300 according to some embodiments of the present disclosure. The process 300 may be implemented at the electronic device 110. The process 300 is described below with reference to FIG1.

[0074] In block 310 , the electronic device 110 presents a workflow editing interface, where the editing interface is used to edit a node graph corresponding to the workflow.

[0075] In box 320, in response to receiving a preset operation on a target node in the node graph, the electronic device 110 presents a configuration window associated with the target node, where the configuration window includes multiple configuration pages for configuring the target node, where the configuration information supported by different configuration pages is independent of each other.

[0076] In block 330 , the electronic device obtains updated configuration information of the target node via the configuration window to update the workflow.

[0077] In some embodiments, the multiple configuration pages include multiple items of the following: a first configuration page, used to configure the form information corresponding to the target node, a second configuration page, used to configure the input information of the target node, a third configuration page, used to configure the output information of the target node, a fourth configuration page, used to configure the error handling logic of the target node, and a fifth configuration page, used to configure the metadata of the target node.

[0078] In some embodiments, the plurality of configuration pages corresponds to a plurality of plug-ins for the target node.

[0079] In some embodiments, the process 300 further includes: receiving a first request to delete a first plug-in among the plurality of plug-ins; and disabling a first service logic corresponding to the first plug-in on the target node based on the first request.

[0080] In some embodiments, process 300 further includes: receiving a second request to add a second plug-in; and adding second business logic corresponding to the second plug-in to the target node based on the second request.

[0081] In some embodiments, process 300 further includes: updating a node window corresponding to the target node in the node graph based on the updated configuration information of the target node to indicate at least a portion of the updated configuration information.

[0082] In some embodiments, in response to receiving a preset operation on a target node in a node graph, presenting a configuration window associated with the target node includes: in response to receiving the preset operation, presenting a node management interface corresponding to the target node, the node management interface including a canvas component and a configuration window, the canvas component displays the node window of the target node.

[0083] Example devices and equipment

[0084] Embodiments of the present disclosure also provide corresponding apparatuses for implementing the above-described methods or processes. FIG4 shows a schematic structural block diagram of an apparatus 400 for editing a workflow according to certain embodiments of the present disclosure. Apparatus 400 may be implemented as or included in electronic device 110 as discussed above. The various modules / components in apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0085] As shown in Figure 4, the device 400 includes a first presentation module 410, which is configured to present an editing interface of the workflow, and the editing interface is used to edit the node graph corresponding to the workflow; a second presentation module 420, which is configured to present a configuration window associated with the target node in response to receiving a preset operation on the target node in the node graph, and the configuration window includes multiple configuration pages for configuring the target node, wherein the configuration information supported by different configuration pages is independent of each other; and an update module 430, which is configured to obtain updated configuration information of the target node via the configuration window to update the workflow.

[0086] In some embodiments, the multiple configuration pages include multiple items of the following: a first configuration page, used to configure the form information corresponding to the target node, a second configuration page, used to configure the input information of the target node, a third configuration page, used to configure the output information of the target node, a fourth configuration page, used to configure the error handling logic of the target node, and a fifth configuration page, used to configure the metadata of the target node.

[0087] In some embodiments, the plurality of configuration pages corresponds to a plurality of plug-ins for the target node.

[0088] In some embodiments, the apparatus 400 further includes a plug-in deletion module configured to: receive a first request to delete a first plug-in among multiple plug-ins; and disable a first business logic corresponding to the first plug-in on the target node based on the first request.

[0089] In some embodiments, the apparatus 400 further includes a plug-in adding module configured to: receive a second request for adding a second plug-in; and add a second business logic corresponding to the second plug-in to the target node based on the second request.

[0090] In some embodiments, the apparatus 400 further includes a configuration update module configured to: based on the updated configuration information of the target node, update a node window corresponding to the target node in the node graph to indicate at least part of the updated configuration information.

[0091] In some embodiments, the second presentation module 420 is further configured to: in response to receiving a preset operation, present a node management interface corresponding to the target node, the node management interface including a canvas component and a configuration window, and the canvas component displays the node window of the target node.

[0092] The units included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 400 can be implemented at least in part by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can 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.

[0093] FIG5 shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 500 shown in FIG5 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 500 shown in FIG5 can be used to implement the electronic device 110 shown in FIG1 .

[0094] As shown in FIG5 , electronic device 500 is a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processors or processing units 510, memory 520, storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processing unit 510 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 500.

[0095] The electronic device 500 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 can be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data (e.g., training data for training) and can be accessed within the electronic device 500.

[0096] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 5 , a disk drive for reading from or writing to a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0097] The communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0098] Input device 550 may be one or more input devices, such as a mouse, keyboard, or trackball. Output device 560 may be one or more output devices, such as a display, a speaker, or a printer. Electronic device 500 may also communicate with one or more external devices (not shown) via communication unit 540 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with electronic device 500, or with any device that allows electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0099] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0100] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0101] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0102] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0103] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes 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 flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0104] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for editing a workflow, comprising: Presenting an editing interface of the workflow, the editing interface being used to edit a node graph corresponding to the workflow; In response to receiving a preset operation on a target node in the node graph, presenting a configuration window associated with the target node, the configuration window including a plurality of configuration pages for configuring the target node, where the information supported for configuration by different configuration pages is independent of each other; and Obtaining updated configuration information of the target node via the configuration window to update the workflow.

2. The method according to claim 1, wherein the plurality of configuration pages include multiple ones of the following: A first configuration page for configuring form information corresponding to the target node, A second configuration page for configuring input information of the target node, A third configuration page for configuring output information of the target node, A fourth configuration page for configuring error handling logic of the target node, A fifth configuration page for configuring metadata of the target node.

3. The method according to claim 1, wherein the plurality of configuration pages correspond to a plurality of plugins of the target node.

4. The method according to claim 3, further comprising: Receiving a first request to delete a first plugin among the plurality of plugins; And Based on the first request, disabling a first business logic corresponding to the first plugin of the target node.

5. The method according to claim 3, further comprising: Receiving a second request to add a second plugin; And Based on the second request, adding a second business logic corresponding to the second plugin to the target node.

6. The method according to claim 1, further comprising: Based on the updated configuration information of the target node, updating a node window corresponding to the target node in the node graph to indicate at least part of the updated configuration information.

7. The method according to claim 1, wherein presenting a configuration window associated with the target node in response to receiving a preset operation on the target node in the node graph includes: In response to receiving the preset operation, presenting a node management interface corresponding to the target node, the node management interface including a canvas component and the configuration window, and the canvas component displaying a node window of the target node.

8. An apparatus for editing a workflow, comprising: A first presenting module configured to present an editing interface of the workflow, the editing interface being used to edit a node graph corresponding to the workflow; A second presenting module configured to present a configuration window associated with the target node in response to receiving a preset operation on the target node in the node graph, the configuration window including a plurality of configuration pages for configuring the target node, where the information supported for configuration by different configuration pages is independent of each other; And An updating module configured to obtain updated configuration information of the target node via the configuration window to update the workflow.

9. An electronic device, comprising: At least one processing unit; And And At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having stored thereon a computer program, the computer program, when executed by a processor, implementing the method according to any one of claims 1 to 7.

11. A computer program product, the computer program product being tangibly stored in a computer storage medium and including computer-executable instructions, the computer-executable instructions, when executed by a device, causing the device to perform the method according to any one of claims 1 to 7.

Images