Workflow editing method and apparatus, and device and storage medium

Abstract

The embodiments of the present disclosure relate to a workflow editing method and apparatus, and a device and a storage medium. The method provided in the present disclosure comprises: presenting an editing interface for a workflow, wherein the editing interface presents a node graph corresponding to the workflow, which node graph comprises a target node; acquiring configuration information associated with a target form item of the target node, wherein the configuration information indicates a group of target plugins enabled by the target form item; and on the basis of the group of enabled target plugins, providing the target form item in a node window of the target node, so as to configure the target node. In this way, the embodiments of the present disclosure can improve the workflow editing efficiency, and can also improve the flexibility of workflow editing.

Description

Method, device, equipment and storage medium for editing workflow Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to a method, apparatus, device, and computer-readable storage medium for editing a workflow. Background Art

[0002] Visual editing of workflow 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 an editing interface for the workflow, the editing interface presenting a node graph corresponding to the workflow, the node graph including a target node; obtaining configuration information associated with a target form item of the target node, the configuration information indicating a set of target plug-ins enabled for the target form item; and providing a target form item in a node window of the target node based on the set of enabled target plug-ins to configure the target node.

[0005] In a second aspect of the present disclosure, a device for editing a workflow is provided. The device includes: a presentation module configured to present an editing interface for the workflow, the editing interface presenting a node graph corresponding to the workflow, the node graph including a target node; an acquisition module configured to acquire configuration information associated with a target form item of the target node, the configuration information indicating a set of target plug-ins enabled by the target form item; and a provision module configured to provide the target form item in a node window of the target node based on the set of enabled target plug-ins, thereby configuring the target node.

[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, which, when executed by a processor, implement the method according to the first aspect of the present disclosure.

[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 according to the present disclosure may be implemented;

[0012] FIG2 illustrates a flowchart of an example editing workflow process according to some embodiments of the present disclosure;

[0013] FIG3A shows a schematic diagram of an example preset plug-in according to some embodiments of the present disclosure;

[0014] FIG3B shows a schematic diagram of an example interface according to some embodiments of the present disclosure;

[0015] FIG4 shows a schematic structural block diagram of an example editing workflow apparatus according to some embodiments of the present disclosure; and

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

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

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

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

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

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

[0022] According to traditional solutions, when users configure form items of target nodes in a workflow, they need to repeatedly develop functions corresponding to the form items, which affects the user experience.

[0023] Embodiments of the present disclosure provide a solution for editing a workflow. According to the solution, a workflow editing interface can be presented, the editing interface presenting a node graph corresponding to the workflow, the node graph including a target node; configuration information associated with a target form item of the target node is obtained, the configuration information indicating a set of target plug-ins enabled by the target form item; and based on the set of enabled target plug-ins, a target form item is provided in a node window of the target node to configure the target node.

[0024] In this way, the embodiments of the present disclosure can implement the functions corresponding to the target form items based on a group of target plug-ins, thereby improving the configuration efficiency of the form items and enhancing the flexibility of workflow editing.

[0025] Various example implementations of this solution are described in detail below in conjunction with the accompanying drawings.

[0026] Sample Environment

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

[0028] In this example environment 100, electronic device 110 may run an application 120 that supports interface interaction. Application 120 may be any suitable type of application for interface interaction, including, but not limited to, workflow editing applications or other suitable applications. Workflows are used to define and automate a series of steps or tasks in a business process. User 140 may interact with application 120 via electronic device 110 and / or its attached devices.

[0029] In the environment 100 of FIG1 , if the application 120 is active, the electronic device 110 may present an interface 150 for supporting interface interaction through the application 120. The interface 150 may be a workflow editing interface for editing configuration information associated with a target form item of a target node corresponding to the workflow.

[0030] 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.).

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

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

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

[0034] Example Process

[0035] 2 shows a flow chart of an example editing workflow process 200 according to some embodiments of the present disclosure. The process 200 may be implemented at the electronic device 110. The process 200 is described below with reference to FIG1.

[0036] In block 210 , the electronic device 110 presents an editing interface of the workflow, where the editing interface presents a node graph corresponding to the workflow, where the node graph includes a target node.

[0037] 3A as an example, the electronic device 110 may present an interface 300A (workflow editing interface), which may present a node graph 310 corresponding to the workflow. The node graph 310 may include multiple nodes, such as node 311, node 312, and node 313.

[0038] In node graph 310, two associated nodes can be connected by a straight line, broken line, curved line, or the like, while two unassociated nodes may not be connected. Furthermore, in some embodiments, two associated nodes may be in a sequential call relationship. Taking FIG3A as an example, the relationship between node 312 and node 313 is a sequential call relationship, and during the execution of the workflow, node 312 may be called first, followed by node 313.

[0039] In some embodiments, taking node 312 as a target node, target node 312 may include multiple form items, such as form item 315-1, form item 315-2, and form item 315-3, each of which may have a corresponding function. In some embodiments, such functions may be implemented based on configuration information for the form items.

[0040] In this disclosure, a "form item" refers to a single input field or component used in a node editing window to configure corresponding parameters of a node.

[0041] For ease of understanding, the following describes how to implement the corresponding functions of the form items.

[0042] 2 , in block 220 , the electronic device 110 obtains configuration information associated with the target form item of the target node, where the configuration information indicates a set of target plug-ins enabled by the target form item.

[0043] In some embodiments, taking form item 315-2 as the target form item, electronic device 110 can configure target form item 315-1 based on user operations to implement the function corresponding to target form item 315-1. For example, electronic device 110 can configure target form item 315-1 in response to the user enabling a set of target plug-ins for target form item 315-1.

[0044] An example code representation of the configuration information is shown below.

[0045] During engine initialization, the plugin manager can parse the user's configuration information and add the user-defined plugins d and e to the plugin collection. Furthermore, based on the configuration information, the plugin manager can determine that the plugins required for this form item are plugins a, b, c, and e. Accordingly, the plugin manager can retrieve these plugins from the plugin collection and initialize them accordingly.

[0046] In some embodiments, as shown in FIG3B , such a set of target plug-ins may include multiple preset plug-ins, such multiple preset plug-ins may include a first preset plug-in 320 to a seventh preset plug-in 326. In addition, such a set of target plug-ins may also include other appropriate plug-ins. This disclosure is not intended to limit the number and type of plug-ins.

[0047] As an example, the preset plug-ins supported by the integrated development environment may include the various plug-ins listed in Table 1. These plug-ins may be associated with different capabilities of the node, and the capabilities corresponding to different preset plug-ins are independent of each other. In other words, the capabilities corresponding to a plug-in do not depend on other plug-ins.

[0048] Table 1 Preset plug-ins and descriptions

[0049] In some embodiments, the first preset plug-in 320 can be used to present the interface element corresponding to the drawn form item. As an example, the first preset plug-in 320 can be responsible for displaying the interface of the form item, and the user can input data corresponding to the form item based on the interface.

[0050] In some embodiments, the second preset plug-in 321 can be used to present the description information of the form item. As an example, the second preset plug-in 321 can display the title and description information of the form item, for example, such description information can indicate what type of data can be entered into the form item.

[0051] In some embodiments, the third preset plug-in 322 can be used to maintain the display logic or hiding logic of the form item. As an example, the third preset plug-in 322 can be used to indicate whether the corresponding form item is displayed under specific circumstances. For example, in response to determining that the value in the previous form item associated with the electronic device 110 is greater than a threshold, the form item is hidden.

[0052] In some embodiments, the fourth preset plug-in 323 can be used to configure the default value displayed by the form item. As an example, the default number of retries for loading a web page on a certain website is 2. If the loading is not completed after 2 times, an error may be prompted for the web page.

[0053] In some embodiments, the fifth preset plug-in 324 can be used to maintain the validation logic of the form item. As an example, the fifth preset plug-in 324 can verify whether the type or format of the data input by the user in the form item is correct.

[0054] In some embodiments, the sixth preset plug-in 325 can be used to maintain the data change logic of the form item. As an example, the electronic device 110 can update the associated data based on the sixth preset plug-in 325 in response to determining the user's modification operation on a certain data.

[0055] In some embodiments, the seventh preset plug-in 326 can be used to maintain the highlight logic of the form item. As an example, the seventh preset plug-in 326 can highlight the form item so that it can be located.

[0056] In some embodiments, the user may select any combination of the seven preset plug-ins described above based on specific business needs to configure the target form item 315 - 1 , thereby realizing the function corresponding to the target form item 315 - 1 .

[0057] Furthermore, in some embodiments, such multiple preset plug-ins can be associated with different capabilities of the target node, and the capabilities corresponding to different preset plug-ins are independent of each other, that is, the electronic device 110 can plug and unplug the preset plug-ins at any time based on the user's configuration operation, so that the target form item 315-1 can have the corresponding function.

[0058] For example, the target form item 315-1 may enable the first preset plug-in 320 and the seventh preset plug-in 326 based on user configuration, so that the target form item 315-1 can have the functions of inputting data and highlighting. Furthermore, the user may disable the seventh preset plug-in 326 so that the target form item 315-1 does not have the highlighting function, but the user can still input data.

[0059] In this way, the disclosed embodiments can orthogonally divide form item functionality to form multiple plug-ins with independent functions. Furthermore, users can directly configure the corresponding plug-ins based on the required functions of the form items, eliminating the need for users to repeatedly develop the corresponding functions for the form items, thereby improving the configuration efficiency of the form items.

[0060] In some embodiments, such a set of target plug-ins may also include additional plug-ins 327 or 328 imported by the user. Such additional plug-ins may be plug-ins customized based on user needs, for example, indicating that a form item is required or not required, etc.

[0061] In some embodiments, the first preset plug-in 320 to the seventh preset plug-in 326 may be node built-in plug-ins, and the attachment plug-in imported by the user may be a workflow editing extension plug-in or a business extension plug-in.

[0062] In some embodiments, the additional plug-in 327 or 328 imported by the user needs to meet a preset plug-in interface constraint. Such a plug-in interface constraint may indicate a plurality of interfaces that the additional plug-in 327 or 328 needs to provide.

[0063] Table 2 Plugin interface constraints

[0064] With reference to the example of Table 2, in some embodiments, such multiple interfaces may include a first interface, and such a first interface may be used to provide an identification of the corresponding plug-in. As an example, such identification information may be, for example, address information, data information, etc. In some embodiments, such multiple interfaces may include a second interface, and such a second interface may be used to be called when the plug-in engine parses configuration information, so that each capability plug-in can be configured by the user. In some embodiments, such multiple interfaces may include a third interface, and such a third interface may be used to be called when registering the corresponding plug-in with the plug-in engine. In some embodiments, such multiple interfaces may include a fourth interface, and such a fourth interface may be used to initialize the corresponding plug-in.

[0065] In this way, users can implement custom form item function plug-ins based on the above interface constraints.

[0066] Furthermore, in some embodiments, the electronic device 110 may also provide context information associated with the corresponding node and / or corresponding form to the target interface in response to a target interface among the multiple interfaces being triggered. As an example, such context information may include information such as a node instance, form item configuration, form engine instance, etc. In this way, the plug-in can implement more abundant functions.

[0067] In some embodiments, the plug-in manager (or preset plug-in set) may have preset plug-ins (e.g., plug-in a, plug-in b, and plug-in c) by default. Furthermore, the user may configure a custom plug-in, and the plug-in manager may parse the user's custom configuration plug-in and add the custom plug-in (e.g., plug-in d and plug-in e) to the preset plug-in set. Furthermore, when the user configures the target form item, a custom plug-in set (or a group of target plug-ins) may be selected. As an example, form item 1 enables plug-in a, plug-in b, and plug-in d, and form item 2 enables plug-in a, plug-in c, and plug-in e. The electronic device 110 may obtain the corresponding plug-in from the preset plug-in set and initialize it to configure the form item.

[0068] 2 , in block 230 , the electronic device 110 provides a target form item in the node window of the target node based on the enabled set of target plug-ins to configure the target node.

[0069] In some embodiments, the electronic device 110 may configure the target form item in the target node based on a set of target plug-ins enabled by the user (which may include a user's custom plug-in).

[0070] Accordingly, electronic device 110 can provide the corresponding interactive capabilities of the form item based on a set of target plug-ins enabled by the form item. For example, electronic device 110 can manage or set the default values ​​provided by the form item based on the Default plug-in. As another example, electronic device 110 can configure the highlighting logic of the form item using the Highlight plug-in, for example, by highlighting the form item to alert the user when an input error occurs in the form item.

[0071] In this way, the disclosed embodiments can orthogonally divide form item functions to form multiple plug-ins with independent functions. In addition, users can also customize plug-ins. Furthermore, users can directly configure the corresponding plug-in based on the required functions of the form item, thereby improving the configuration efficiency of the form item.

[0072] Example devices and equipment

[0073] 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 example editing workflow apparatus 400 according to certain embodiments of the present disclosure. Apparatus 400 may be implemented as or included in electronic device 110. Each module / component in apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0074] As shown in Figure 4, the device 400 includes a presentation module 410, which is configured to present an editing interface of the workflow, the editing interface presents a node graph corresponding to the workflow, and the node graph includes a target node; an acquisition module 420, which is configured to obtain configuration information associated with a target form item of the target node, the configuration information indicating a set of target plug-ins enabled by the target form item; and a providing module 430, which is configured to provide a target form item in a node window of the target node based on the enabled set of target plug-ins to configure the target node.

[0075] In some embodiments, a set of target plug-ins includes at least one plug-in from a plurality of preset plug-ins, wherein the plurality of preset plug-ins are associated with different capabilities of the target node, and the capabilities corresponding to different preset plug-ins are independent of each other.

[0076] In some embodiments, the multiple preset plug-ins include at least one of the following: a first preset plug-in, used to present the interface element corresponding to the drawn form item; a second preset plug-in, used to present the description information of the form item; a third preset plug-in, used to maintain the display logic or hiding logic of the form item; a fourth preset plug-in, used to configure the default value displayed by the form item; a fifth preset plug-in, used to maintain the validation logic of the form item; a sixth preset plug-in, used to maintain the data change logic of the form item; and a seventh preset plug-in, used to maintain the highlight logic of the form item.

[0077] In some embodiments, the set of target plug-ins further includes additional plug-ins imported by a user, wherein the additional plug-ins satisfy preset plug-in interface constraints.

[0078] In some embodiments, the plug-in interface constraint indicates multiple interfaces that the additional plug-in needs to provide, and the multiple interfaces include multiple items of the following: a first interface, used to provide an identification of the corresponding plug-in; a second interface, used to be called when the plug-in engine parses configuration information; a third interface, used to be called when registering the corresponding plug-in to the plug-in engine; and a fourth interface, used to initialize the corresponding plug-in.

[0079] In some embodiments, the apparatus 400 further includes a processing module configured to provide context information associated with a corresponding node and / or a corresponding form to the target interface in response to a target interface among the multiple interfaces being triggered to be called.

[0080] The modules 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 modules in the device 400 can be implemented at least in part by one or more hardware logic components. As an 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), system on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0081] 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 of FIG1 .

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

[0083] 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., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), 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 and can be accessed within the electronic device 500.

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

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

[0086] 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).

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

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

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

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

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

[0092] While various implementations of the present disclosure have been described above, the above descriptions are intended to be illustrative, non-exhaustive, and non-limiting 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 a workflow editing interface, wherein the editing interface presents a node graph corresponding to the workflow, wherein the node graph includes a target node; Acquire configuration information associated with a target form item of the target node, the configuration information indicating a group of target plug-ins enabled by the target form item; as well as Based on the set of enabled target plug-ins, the target form item is provided in the node window of the target node to configure the target node.

2. The method according to claim 1, wherein the set of target plug-ins includes at least one plug-in from a plurality of preset plug-ins, wherein the plurality of preset plug-ins are associated with different capabilities of the target node, and the capabilities corresponding to different preset plug-ins are independent of each other.

3. The method according to claim 2, wherein the plurality of preset plug-ins include at least one of the following: The first preset plug-in is used to render the interface element corresponding to the drawn form item; The second preset plug-in is used to present the description information of the form item; The third preset plug-in is used to maintain the display logic or hiding logic of the form items; The fourth preset plug-in is used to configure the default values ​​displayed by the form items; The fifth preset plug-in is used to maintain the validation logic of form items; The sixth preset plug-in is used to maintain the data change logic of the form items; The seventh preset plug-in is used to maintain the highlight logic of form items. 4 . The method according to claim 1 , wherein the set of target plug-ins further comprises additional plug-ins imported by a user, wherein the additional plug-ins satisfy preset plug-in interface constraints.

5. The method according to claim 4, wherein the plug-in interface constraint indicates a plurality of interfaces that the additional plug-in needs to provide, and the plurality of interfaces include multiple of the following: The first interface is used to provide the identification of the corresponding plug-in; The second interface is used to be called when the plug-in engine parses the configuration information; The third interface is used to call when registering the corresponding plug-in with the plug-in engine; The fourth interface is used to initialize the corresponding plug-in.

6. The method according to claim 5, further comprising: In response to a target interface among the multiple interfaces being triggered to be called, context information associated with a corresponding node and / or a corresponding form is provided to the target interface.

7. A device for editing a workflow, comprising: A presentation module is configured to present an editing interface of a workflow, wherein the editing interface presents a node graph corresponding to the workflow, wherein the node graph includes a target node; an acquisition module configured to acquire configuration information associated with a target form item of the target node, wherein the configuration information indicates a group of target plug-ins enabled by the target form item; as well as A providing module is configured to provide the target form item in the node window of the target node based on the set of enabled target plug-ins, so as to configure the target node.

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

9. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 6.

10. A computer program product comprising computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 6.

Images