Workflow creation method and apparatus, device and storage medium

Abstract

Embodiments of the present disclosure relate to a workflow creation method and apparatus, a device, and a storage medium. The method provided herein comprises: presenting a canvas component for editing a node graph of a workflow; via the canvas component, receiving an editing operation associated with the node graph, the editing operation being used for configuring at least one action associated with the workflow, and the at least one action being used for managing a trigger associated with the workflow; and, on the basis of the editing operation, creating the workflow.

Description

Methods, apparatus, devices, and storage media for creating workflows

[0001] This application claims priority to Chinese Patent Application No. 202411826129.8, filed on December 11, 2024, entitled “Method, Apparatus, Device and Storage Medium for Creating Workflows”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The exemplary embodiments disclosed herein relate generally to the field of computers, and more particularly to methods, apparatus, devices, and computer-readable storage media for creating workflows. Background Technology

[0003] With the development of computer technology, people can create and publish various types of applications through various platforms. In the application development process, workflow creation and management is an important task. For example, users can edit nodes in a workflow to indicate the processing flow of a request. Summary of the Invention

[0004] In a first aspect of this disclosure, a method for creating a workflow is provided. The method includes: presenting a canvas component of a node graph for editing the workflow; receiving, via the canvas component, an editing operation associated with the node graph, the editing operation configuring at least one action associated with the workflow, the at least one action managing triggers associated with the workflow; and creating the workflow based on the editing operation.

[0005] In a second aspect of this disclosure, an apparatus for creating a workflow is provided. The apparatus includes: a presentation module configured to present a canvas component of a node graph for editing the workflow; a receiving module configured to receive, via the canvas component, editing operations associated with the node graph, the editing operations being used to configure at least one action associated with the workflow, the at least one action being used to manage triggers associated with the workflow; and a creation module configured to create a workflow based on the editing operations.

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

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.

[0008] In a fifth aspect of this disclosure, a computer program product is provided. This computer program product is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method according to the first aspect.

[0009] It should be understood that the content described in this content section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

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

[0012] Figures 2A to 2E illustrate example interfaces according to some embodiments of the present disclosure;

[0013] Figure 3 illustrates a flowchart of an example process for creating a workflow according to some embodiments of the present disclosure;

[0014] Figure 4 shows a schematic structural block diagram of an example apparatus for creating a workflow according to some embodiments of the present disclosure; and

[0015] Figure 5 shows a block diagram of an electronic device capable of implementing several embodiments of the present disclosure. Detailed Implementation

[0016] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

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

[0018] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based 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 also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0019] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these aspects comply with applicable laws, regulations, and relevant provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing the embodiments of this disclosure, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with relevant laws and regulations through appropriate means. The specific methods of notification and / or authorization may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0020] In this specification and the embodiments, any processing of personal information will be carried out only under the premise of legality (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information other than that necessary for basic functions will not affect the user's use of basic functions.

[0021] Some platforms also support users configuring various types of applications based on generative models, such as agents or bots. However, existing workflows have limited support for triggers, which significantly restricts the use cases for workflows.

[0022] Embodiments of this disclosure propose a scheme for creating a workflow. The scheme includes: presenting a canvas component for editing a node graph of the workflow; receiving, via the canvas component, editing operations associated with the node graph, the editing operations configuring at least one action associated with the workflow, the at least one action managing triggers associated with the workflow; and creating the workflow based on the editing operations.

[0023] In this way, embodiments of the present disclosure can support the management of workflow triggers through a canvas component, thereby improving the flexibility and efficiency of trigger management.

[0024] The following section provides a detailed description of various example implementations of this scheme, with reference to the accompanying drawings.

[0025] Example Environment

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

[0027] In this example environment 100, electronic device 110 can run an application 120 that supports user interface interaction. Application 120 can be any suitable type of application for user interface interaction, examples of which may include, but are not limited to, development applications or other suitable applications. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0028] In environment 100 of Figure 1, if application 120 is active, electronic device 110 can present interface 150 through application 120 to support the creation of workflows.

[0029] In some embodiments, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, VR / AR devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0030] Server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support virtual scenarios in electronic devices 110.

[0031] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections; the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, server 130 and electronic device 110 can achieve signaling interaction through the communication connection between them.

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

[0033] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0034] Example Interaction

[0035] The following description, in conjunction with Figures 2A to 2E, illustrates example interactions for creating workflows according to some embodiments of the present disclosure. Figures 2A to 2E show example interfaces 200A to 200E according to some embodiments of the present disclosure. Interfaces 200A to 200E may, for example, be provided by the electronic device 110 shown in Figure 1.

[0036] As shown in Figure 2A, interface 200A can correspond to the workflow editing interface. As an example, editing interface 200A may include a canvas component for editing the node connection diagram corresponding to the workflow.

[0037] In some embodiments, the interface 200A may also be associated with the application to be created. As an example, the application may be associated with one or more workflows, and the interface 200A may correspond to the editing interface of the workflow associated with the application.

[0038] As shown in Figure 2A, in interface 200A, electronic device 110 can support various types of node editing operations by users, such as adding nodes to the canvas component, deleting nodes, connecting nodes, and modifying node attributes.

[0039] As will be detailed below, the electronic device 110 can allow users to configure actions associated with the workflow through a canvas component. Such actions can be used to manage one or more triggers associated with the workflow.

[0040] As shown in Figure 2A, the canvas component may include node 202. The electronic device 110 can receive the selection of node 202 and can present a configuration window 206 for the corresponding trigger configuration information. As an example, node 202 may be a preset node in the workflow, such as the start node.

[0041] In some embodiments, the electronic device 110 may support configuring the creation action of the trigger in the configuration window 206 of the start node 202. As an example, as shown in FIG2A, the electronic device 110 may provide an enable button for enabling the trigger in the configuration window 206.

[0042] Furthermore, configuration window 206 may include settings for configuring triggering conditions associated with the trigger to be created. In some embodiments, the trigger may be associated with two types of conditions: time conditions and event conditions. Time conditions may, for example, indicate the trigger's triggering time, while event conditions may indicate the triggering event.

[0043] For example, a time condition could be "every day at 10 a.m.". Such a time condition could indicate a periodic time or a fixed time.

[0044] Referring to Figure 2A as an example, the electronic device 110 can provide a control 208 for configuring time conditions in the configuration window 206. As an example, the electronic device 110 can determine the time zone and specific trigger time included in the trigger conditions via the control 208. For instance, the user can select a "selection-based" mode and choose a specific trigger time from a drop-down list.

[0045] In some embodiments, the electronic device 110 may also support the generation of expressions related to trigger time, such as cronjob expressions. As an example, the electronic device 110 may select the "smart generation" mode via control 208 and may accordingly present the generation window 200B as shown in FIG2B.

[0046] In Figure 2B, electronic device 110 can acquire natural language text input by the user via control 212. The natural language text may describe, for example, a desired trigger time, such as "1 AM every day". Furthermore, electronic device 110 can receive a trigger on the "Generate" button and can use a language model to process the natural language text to generate an expression corresponding to the trigger time. For example, the generated expression could be "0 1 * **".

[0047] As an example, electronic device 110 can receive a selection of control 214 and fill the expression into control 208 to complete the configuration of the trigger time.

[0048] In some embodiments, configuration window 206 may also support configuring event conditions associated with the created trigger. As an example, event conditions may include detecting an event in the application. In some scenarios, such an application may include a workflow-based application or other suitable applications.

[0049] In some embodiments, configuration window 206 may, for example, support configuring a trigger as an event trigger and may provide controls for configuring event conditions. In some examples, electronic device 110 may configure event conditions as a first application event within a target application associated with the workflow via controls.

[0050] As an example, the target application may include an application created via the editing interface 200A. Accordingly, such a first application event may include, for example, detecting a button click event, a content input event, etc., in the graphical interface corresponding to the application.

[0051] As another example, the target application may also include at least one configured application. This at least one application may be added based on user authorization. For example, such an application may include a third-party application different from the target application.

[0052] In some embodiments, upon obtaining application authorization, the electronic device 110 may present a set of application programming interface (APIs) associated with the application. Further, the electronic device 110 may receive a selection of at least one API from the set and may configure event conditions accordingly, including application events corresponding to the selected at least one API.

[0053] As an example, such an API could be a set of open APIs provided by a media application. For instance, a user could choose a content publishing API and configure event conditions to occur when the current user publishes new content within the media application.

[0054] Additionally, as shown in Figure 2A, the electronic device 110 may also provide a control 210 in the configuration window 206 to configure the input parameters of the workflow corresponding to the trigger.

[0055] In this way, embodiments of the present disclosure can support binding preset nodes in the workflow to triggers, so that the preset node will be automatically triggered to execute when the triggering condition of the trigger is met.

[0056] In some scenarios, such triggers may also be called system triggers, and the preset node may include, for example, the start node of the workflow. Additionally, when the start node 202 is configured to be associated with a trigger creation action, the electronic device 110 may, for example, display an indicator element 204 in the node 202 to indicate that the start node 202 is bound to a trigger.

[0057] In some embodiments, the electronic device 110 may also provide one or more trigger processing nodes in the canvas component to support users in adding corresponding trigger processing nodes to the workflow and configuring corresponding trigger management actions.

[0058] In some instances, the electronic device 110 may support adding trigger setting nodes to the canvas component. Figure 2C illustrates an exemplary trigger setting node 220 and its corresponding configuration window 222.

[0059] In some embodiments, the trigger setting node 220 can be used, for example, to create a new trigger or modify an existing trigger. As an example, the configuration window 222 includes a control 216 for entering the name of the trigger to be created or set.

[0060] As an example, if the input name is a new name, trigger setting node 220 can be used to perform a trigger creation action. As another example, if the input name is an existing name, trigger setting node 220 can be used to perform a trigger modification action.

[0061] In some scenarios, the electronic device 110 can also separate the functions of trigger creation and trigger editing. For example, the electronic device 110 can support adding trigger creation nodes and trigger editing nodes to the canvas component.

[0062] Similar to the configuration window 206 described above, the electronic device 110 can provide a control 218 to configure the trigger conditions. As discussed above, such trigger conditions may include time conditions or event conditions. For the specific configuration process of the trigger conditions, please refer to the description of control 208 above; this disclosure will not repeat it further here.

[0063] In addition, unlike configuration window 206, configuration window 222 may also provide control 224 to support binding created or set triggers to specified workflows. As an example, users can select the target workflow to bind by clicking the "+" button. Such workflows may include the currently edited workflow, workflows associated with the application to be created, or other workflows that the user has authorized access to.

[0064] When a trigger is bound to a target workflow (e.g., workflow X), the bound target workflow (e.g., workflow X) can be automatically satisfied if the trigger's triggering condition is met.

[0065] In some scenarios, triggers created via setting node 220 can also be called user triggers. Since the system triggers mentioned above are naturally bound to their corresponding workflows, it is not supported to bind system triggers to other workflows.

[0066] Furthermore, as shown in Figure 2C, the configuration window 222 can also indicate the output parameters 226 of the trigger setting node 220, such as the identifier of the created or edited trigger.

[0067] In some embodiments, the electronic device 110 may also support adding trigger deletion nodes to the canvas component for deleting specified triggers. For example, the input parameters corresponding to such a trigger deletion node may include the identifier of the trigger to be deleted, and its output parameters may include whether the trigger was successfully deleted.

[0068] In some embodiments, the electronic device 110 may also support adding trigger lookup nodes (also known as trigger read nodes) to the canvas component. Figure 2D illustrates an exemplary trigger query node 228 and the corresponding configuration window 230.

[0069] As shown in Figure 2D, the configuration window 230 can provide controls 232 to configure the query conditions for the trigger. As an example, such query conditions may include the trigger's identifier or the user identifier that created the trigger.

[0070] Additionally, the configuration window 230 can also display the output parameters 234 of the trigger lookup node 228. As an example, the trigger lookup node 228 can be configured to output a list of triggers that match the query criteria, which may include, for example, the identifier, name, creation time, trigger criteria, user identifier, workflow input parameters, etc. of each trigger.

[0071] In this way, embodiments of the present disclosure can enable users to manage triggers associated with workflows more flexibly by adding nodes to the workflow, thereby improving the management efficiency of trigger associations.

[0072] In some embodiments, the trigger configuration information obtained above may include specific values ​​directly entered by the user through controls. In other embodiments, the trigger configuration information may also indicate the association between at least one parameter associated with the trigger to be managed and at least one variable in the workflow.

[0073] For example, users can configure trigger conditions by applying specific variables in the workflow. For instance, the trigger's trigger time can correspond to a specific time variable in the workflow. In this way, embodiments of this disclosure can further improve the efficiency of dynamically managing triggers during workflow execution.

[0074] In some embodiments, at least one of the supported variables can be associated with a processing request received by the workflow. For example, if a user enters "Study English at 10 AM every morning" through an interactive interface associated with the workflow, the workflow can, for instance, read the variable "10 AM" from the processing request. Furthermore, based on the association configured by the user, this variable can trigger the creation of a trigger with the trigger condition "10 AM".

[0075] In this way, embodiments of this disclosure can further support the dynamic management of triggers based on user requests.

[0076] In some embodiments, as shown in FIG2E, the electronic device 110 may also present a trigger viewing interface 200E associated with the workflow. As shown, the electronic device 110 may present descriptive information of at least one trigger (e.g., trigger 236 and trigger 238) associated with the workflow in the trigger viewing interface 20E.

[0077] As an example, such descriptive information may include, but is not limited to: the trigger's identifier, name, creation time, triggering conditions (e.g., trigger time), user identifier, workflow input parameters, etc.

[0078] Additionally, the electronic device 110 may also provide one or more controls in the trigger viewing interface 200E. For example, the electronic device 110 may receive a selection of the delete control for trigger 236, thereby deleting trigger 236 from the workflow. As another example, the electronic device 110 may also receive a selection of the run control for trigger 238, and may run a second trigger 238. As an example, trigger 238 may be enabled and may trigger the execution of the corresponding processing flow in the bound workflow.

[0079] In this way, embodiments of the present disclosure can support the management of workflow triggers through a canvas component, thereby improving the flexibility and efficiency of trigger management.

[0080] Example process

[0081] Figure 3 shows a flowchart of a workflow creation process 300 according to some embodiments of the present disclosure. Process 300 can be implemented at electronic device 110. Process 300 will now be described with reference to Figure 1.

[0082] As shown in Figure 3, in box 310, the electronic device 110 presents a canvas component for editing a node graph of the workflow.

[0083] In box 320, electronic device 110 receives, via canvas component, an editing operation associated with a node graph, the editing operation being used to configure at least one action associated with a workflow, the at least one action being used to manage triggers associated with the workflow.

[0084] In box 330, electronic device 110 creates a workflow based on editing operations.

[0085] In some embodiments, at least one action includes at least one of the following: a create action for creating a new trigger associated with the workflow; a delete action for deleting an existing trigger associated with the workflow; a modify action for modifying the properties of an existing trigger associated with the workflow; and a search action for searching for at least one trigger associated with the workflow.

[0086] In some embodiments, receiving an editing operation associated with a node graph includes: presenting a configuration window associated with a target node in the node graph; and obtaining trigger configuration information associated with the target node via the configuration window.

[0087] In some embodiments, receiving an edit operation associated with a node graph further includes: adding a trigger processing node to the node graph as a target node, wherein the trigger processing node includes at least one of the following: a trigger setting node for creating and / or modifying triggers; a trigger deleting node; and a trigger finding node.

[0088] In some embodiments, trigger configuration information indicates triggering conditions associated with the trigger to be managed, including time conditions associated with trigger time and / or event conditions associated with trigger event.

[0089] In some embodiments, obtaining trigger configuration information associated with a target node via a configuration window includes: obtaining natural language text about the target trigger time via a first control in the configuration window; and generating an expression indicating the target trigger time based on the natural language text using a language model.

[0090] In some embodiments, the event conditions include: a first application event within the target application associated with the workflow; and / or a second application event associated with at least one configured application, the at least one application being different from the target application.

[0091] In some embodiments, obtaining trigger configuration information associated with a target node via a configuration window includes: presenting a set of application programming interface (API) objects associated with the application; and configuring event conditions, including application events corresponding to the selected API, in response to the selection of at least one API from the set of APIs.

[0092] In some embodiments, trigger configuration information indicates the target workflow bound to the trigger to be managed, such that the target workflow is triggered to execute in response to the trigger's triggering condition being met.

[0093] In some embodiments, trigger configuration information indicates the association between at least one parameter associated with the trigger to be managed and at least one variable in the workflow.

[0094] In some embodiments, at least one variable is associated with a processing request received by the workflow.

[0095] In some embodiments, receiving an edit operation associated with a node graph further includes receiving a selection of a preset node in the node graph as a target node, the preset node including the start node of the workflow.

[0096] In some embodiments, process 300 further includes: in response to at least one node in the node graph being associated with a trigger creation action, presenting an indicator element associated with at least one node.

[0097] In some embodiments, process 300 further includes: presenting a trigger viewing interface associated with the workflow; and presenting descriptive information of at least one trigger associated with the workflow in the trigger viewing interface.

[0098] In some embodiments, process 300 further includes: deleting the first trigger in response to a first operation on the first trigger of at least one trigger; or running the second trigger in response to a second operation on the second trigger of at least one trigger.

[0099] Example devices and equipment

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

[0101] As shown in Figure 4, the device 400 includes a presentation module 410 configured to present a canvas component for editing a node graph of a workflow; a receiving module 420 configured to receive, via the canvas component, an editing operation associated with the node graph, the editing operation being used to configure at least one action associated with the workflow, the at least one action being used to manage triggers associated with the workflow; and a creation module 430 configured to create a workflow based on the editing operation.

[0102] In some embodiments, at least one action includes at least one of the following: a create action for creating a new trigger associated with the workflow; a delete action for deleting an existing trigger associated with the workflow; a modify action for modifying the properties of an existing trigger associated with the workflow; and a search action for searching for at least one trigger associated with the workflow.

[0103] In some embodiments, the receiving module 420 is further configured to present a configuration window associated with a target node in the node graph; and to obtain trigger configuration information associated with the target node via the configuration window.

[0104] In some embodiments, the receiving module 420 is further configured to add a trigger processing node to the node graph as a target node, wherein the trigger processing node includes at least one of the following: a trigger setting node for creating and / or modifying triggers; a trigger deletion node; and a trigger lookup node.

[0105] In some embodiments, trigger configuration information indicates triggering conditions associated with the trigger to be managed, including time conditions associated with trigger time and / or event conditions associated with trigger event.

[0106] In some embodiments, the receiving module 420 is further configured to acquire natural language text about the target trigger time via a first control in a configuration window; and to generate an expression indicating the association with the target trigger time based on the natural language text using a language model.

[0107] In some embodiments, the event conditions include: a first application event within the target application associated with the workflow; and / or a second application event associated with at least one configured application, the at least one application being different from the target application.

[0108] In some embodiments, the receiving module 420 is further configured to present a set of application programming interface (API) objects associated with the application; and in response to the selection of at least one API from the set of APIs, configure event conditions, the event conditions including application events corresponding to the selected at least one API.

[0109] In some embodiments, trigger configuration information indicates the target workflow bound to the trigger to be managed, such that the target workflow is triggered to execute in response to the trigger's triggering condition being met.

[0110] In some embodiments, trigger configuration information indicates the association between at least one parameter associated with the trigger to be managed and at least one variable in the workflow.

[0111] In some embodiments, at least one variable is associated with a processing request received by the workflow.

[0112] In some embodiments, the receiving module 420 is further configured to receive a selection of a preset node in the node graph as a target node, the preset node including the start node of the workflow.

[0113] In some embodiments, the apparatus 400 further includes an element rendering module configured to render an indicator element associated with at least one node in a node graph in response to a trigger creation action.

[0114] In some embodiments, the apparatus 400 further includes an information presentation module configured to present a trigger viewing interface associated with the workflow; and to present descriptive information of at least one trigger associated with the workflow in the trigger viewing interface.

[0115] In some embodiments, the apparatus 400 further includes a processing module configured to delete the first trigger in response to a first operation on the first trigger of at least one trigger; or to run the second trigger in response to a second operation on the second trigger of at least one trigger.

[0116] Figure 5 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 Figure 5 is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 500 shown in Figure 5 can be used to implement the electronic device 110 of Figure 1.

[0117] As shown in Figure 5, electronic device 500 is in the form of a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processors 510 or processing units, memory 520, storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processor 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 500.

[0118] Electronic device 500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 500.

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

[0120] Communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of components of electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, electronic device 500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0121] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

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

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

[0124] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

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

[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0127] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they 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 chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for creating a workflow, including A canvas component that presents a node graph for editing workflows; The canvas component receives an editing operation associated with the node graph, the editing operation being used to configure at least one action associated with the workflow, the at least one action being used to manage triggers associated with the workflow; as well as Based on the editing operation, the workflow is created.

2. The method of claim 1, wherein the at least one action comprises at least one of the following: Create an action to create a new trigger associated with the workflow; The delete action is used to delete an existing trigger associated with the workflow; Modify actions used to modify the properties of existing triggers associated with the workflow; A lookup action is used to locate at least one trigger associated with the workflow.

3. The method of claim 1 or 2, wherein receiving the edit operation associated with the node graph comprises: A configuration window associated with the target node in the node graph is displayed; as well as The trigger configuration information associated with the target node can be obtained through the configuration window.

4. The method of claim 3, wherein receiving the edit operation associated with the node graph further comprises: Add a trigger processing node to the node graph as the target node. The trigger processing node includes at least one of the following: a trigger setting node for creating and / or modifying triggers; a trigger deletion node; and a trigger lookup node.

5. The method of claim 3 or 4, wherein the trigger configuration information indicates triggering conditions associated with the trigger to be managed, the triggering conditions including time conditions associated with triggering time and / or event conditions associated with triggering event.

6. The method of claim 5, wherein obtaining trigger configuration information associated with the target node via a configuration window includes: Natural language text about the target trigger time is obtained via the first control in the configuration window; as well as An expression associated with the target trigger time is generated based on the natural language text using a language model.

7. The method according to claim 5 or 6, wherein the event condition includes: The first application event within the target application associated with the workflow; and / or A second application event associated with at least one configured application, which is different from the target application.

8. The method of claim 7, wherein obtaining trigger configuration information associated with the target node via a configuration window includes: Presents a set of application programming interface (API) interfaces associated with the application; as well as In response to the selection of at least one API from the set of APIs, the event conditions are configured, the event conditions including an application event corresponding to the selected at least one API.

9. The method according to any one of claims 3 to 8, wherein the trigger configuration information indicates a target workflow bound to a trigger to be managed, such that the target workflow is triggered to execute in response to the trigger condition of the trigger being met.

10. The method according to any one of claims 3 to 9, wherein the trigger configuration information indicates the association between at least one parameter associated with the trigger to be managed and at least one variable in the workflow.

11. The method of claim 10, wherein the at least one variable is associated with a processing request received by the workflow.

12. The method according to any one of claims 3 to 11, wherein receiving the edit operation associated with the node graph further comprises: The selection of a preset node in the node graph is received as the target node, the preset node including the start node of the workflow.

13. The method according to any one of claims 1 to 12, further comprising: In response to at least one node in the node graph being associated with a trigger creation action, an indicator element associated with the at least one node is presented.

14. The method according to any one of claims 1 to 13, further comprising: Presents a view interface for triggers associated with the workflow; as well as The trigger viewing interface displays descriptive information about at least one trigger associated with the workflow.

15. The method of claim 14, further comprising: In response to a first operation on a first trigger of the at least one trigger, the first trigger is deleted; or In response to a second operation on the second trigger of the at least one trigger, the second trigger is operated.

16. An apparatus for creating a workflow, comprising: The presentation module is configured to present a canvas component that displays a node graph for editing workflows; A receiving module is configured to receive, via the canvas component, an editing operation associated with the node graph, the editing operation being used to configure at least one action associated with the workflow, the at least one action being used to manage triggers associated with the workflow; as well as The module is configured to create the workflow based on the edit operation.

17. An electronic device comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 15 when executed by the at least one processor.

18. A computer-readable storage medium having stored thereon computer-executable instructions that can be executed by a processor to implement the method according to any one of claims 1 to 15.

19. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 15.

Images