Workflow construction method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, and provides a workflow construction method and device, equipment and a medium, and the method comprises the steps: constructing a plurality of universal components, and generating a component identifier of each universal component; constructing a workflow topological structure according to the graphical arrangement instruction of the universal component and the component identifier of the universal component; in the workflow topological structure, defining a component association rule among the plurality of universal components; and constructing a workflow according to the workflow topological structure and the component association rule. According to the method, the functions are packaged into the universal components, a user is allowed to build a workflow topological structure in a graphical arrangement mode, and the component association rules among the universal components are customized, so that the workflow can be quickly and flexibly built, the development efficiency is improved, the technical threshold is reduced, and the development flexibility and maintainability are enhanced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a workflow construction method, device, equipment and medium. BACKGROUND

[0002] At present, in some development scenarios, for example, the development of government and enterprise intelligent agents usually adopts a hard coding mode. In this mode, each link of the business interaction process, from the presentation of the front-end user interface elements to the logic jump of the back-end multi-round dialogue, needs to be implemented by the developers through writing specific program codes. This development method leads to high redundancy of the front-end code, and similar functions in different business scenarios cannot be effectively reused, and when the business process needs to be adjusted or updated, modification, testing and re-deployment must be carried out at the code level.

[0003] Therefore, the traditional hard coding development mode not only prolongs the development cycle and increases the maintenance cost, but also makes it difficult for business personnel without programming ability to directly participate in the design and iteration of the intelligent agent interaction process. SUMMARY

[0004] The present application provides a workflow construction method, device, equipment and medium to solve the technical problem that the hard coding development mode in the prior art not only prolongs the development cycle and increases the maintenance cost, but also makes it difficult for business personnel without programming ability to directly participate in the design and iteration of the intelligent agent interaction process.

[0005] The present application provides a workflow construction method, comprising the following steps: Constructing a plurality of general components and generating a component identifier of each of the general components; Constructing a workflow topology structure according to the graphical arrangement instructions of the general components and the component identifiers of the general components; Defining component association rules between a plurality of the general components in the workflow topology structure; Constructing a workflow according to the workflow topology structure and the component association rules.

[0006] According to the workflow construction method provided by the present application, the graphical arrangement instructions are obtained in the following way: Displaying a visual interface; the visual interface includes a component selection area and a canvas area; In response to a first operation event and a second operation event in the visual interface, generating the graphical arrangement instructions according to the first operation event and the second operation event; The first operation event is used to add one or more of the general components from the component selection area to the canvas area; the second operation event is used to adjust the position, configure the attributes, or establish a connection of the added general components in the canvas area.

[0007] According to a workflow construction method provided by the present invention, the step of constructing a workflow based on the workflow topology and the component association rules includes: Based on the workflow topology, determine the task node corresponding to each of the general components, and the execution order among the multiple task nodes; Based on the component association rules, determine the data transmission path between the general components associated with multiple task nodes; A workflow is constructed based on the execution order among the multiple task nodes and the data transfer path between the common components associated with the multiple task nodes.

[0008] According to a workflow construction method provided by the present invention, the step of constructing a workflow topology structure based on the graphical orchestration instructions of the general component and the component identifier of the general component includes: Determine at least one first target general component corresponding to the graphical orchestration instructions of the general component; Instantiate at least one of the first target general components as task nodes, and create a mapping relationship between the component identifier of the first target general component and the task node; Based on the task nodes and their corresponding execution order, a workflow topology is constructed.

[0009] According to a workflow construction method provided by the present invention, defining component association rules among the plurality of general components includes: Determine at least one set of general components from a plurality of general components; each set of general components includes a source component and at least one second target general component; For each set of general components, define the triggering conditions of the source component and the response action of each second target general component, and create at least one data transfer path between the second target general components.

[0010] According to a workflow construction method provided by the present invention, the component identifier of the general component is obtained in the following manner: Obtain the component type and component properties of each of the aforementioned general components; Based on the component type and the component attributes, a component identifier is generated for each of the general components.

[0011] According to a workflow construction method provided by the present invention, the plurality of general components include: button components, form components, text components, script components, or atomic capability components.

[0012] The present invention also provides a workflow construction apparatus, comprising: The first construction module is used to construct multiple general components and generate a component identifier for each of the general components; The second construction module is used to construct a workflow topology based on the graphical orchestration instructions of the general components and the component identifiers of the general components; The third building module is used to define component association rules between multiple general components in the workflow topology; The fourth construction module is used to construct the workflow based on the workflow topology and the component association rules.

[0013] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the program to implement the workflow construction method as described above.

[0014] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the workflow construction method as described above.

[0015] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the workflow construction method as described above.

[0016] The workflow construction method, apparatus, device, and medium provided by this invention encapsulate functions into standardized, universal components, allowing users to build workflow topologies through graphical arrangement (such as drag-and-drop) and customize component association rules between universal components, thereby enabling rapid and flexible workflow construction. Compared to traditional hard-coding development, the workflow construction method provided by this invention improves development efficiency, lowers the technical threshold, and enhances development flexibility and maintainability. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the workflow construction method provided by the present invention.

[0019] Figure 2 This is a schematic diagram of the workflow construction device provided by the present invention.

[0020] Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0022] The workflow construction method of this invention embodiment, such as Figure 1 As shown, it includes steps 110, 120, 130 and 140.

[0023] Step 110: Construct multiple general components and generate a component identifier for each of the general components.

[0024] It should be noted that the general components in this embodiment refer to the reusable and standardized functional modules that developers need to create.

[0025] In practical applications, general-purpose components can be front-end UI components, such as input boxes, buttons, and dropdown menus. They can also be back-end service components, such as data validation, API calls, and script execution.

[0026] In one example, several common components include: button components, form components, text components, script components, or atomic capability components, etc.

[0027] The workflow includes several components: a button component (action-triggered, triggered by user clicks or system activation to initiate subsequent components); a form component (structured data collection, gathering multi-field user input (such as personal information and business parameters) and formatting it for use by later components); a text component (delivering textual information, such as instructions, prompts, and results); a script component (executing pre-defined script logic during workflow execution to control dynamic front-end parameters or process data passed between components); and an atomic capability component (calling external backend application service interfaces based on input parameters and outputting the results to extend workflow functionality).

[0028] In practical applications, button components support custom object groups, form components support custom parameter types, text components support dynamic content output, script components can be used to edit simple front-end logic for controlling or passing dynamic parameters, and atomic capability components support calling custom back-end services to enrich the content presented by the components. By pre-building at least five types of general components, users can quickly build flexible and reusable business processes.

[0029] After the general components are built, each general component will be assigned a unique component identifier to avoid component confusion. For example, even if there are multiple similar components (such as two input boxes), they can be accurately distinguished by the component identifier.

[0030] Step 120: Construct a workflow topology based on the graphical orchestration instructions of the general components and the component identifiers of the general components.

[0031] Graphical orchestration instructions are typically generated based on the user's visual actions (such as dragging components or connecting components with arrows).

[0032] It should be understood that, in order to avoid confusion caused by multiple similar components, in this embodiment, based on the general components selected by the user in the graphical arrangement instructions of the general components and the corresponding user operations, the component identifiers of the general components are used to record which component identifiers are selected and the connection relationships between the component identifiers, thereby forming a workflow topology.

[0033] Step 130: In the workflow topology, define component association rules between multiple general components.

[0034] Component association rules are used to characterize how common components interact, how data flows, and under what conditions a process leads to which branch.

[0035] In one example, component association rules can include execution order rules to define the conditions for triggering components. For instance, regarding the connection between general component A and general component B in a workflow topology, it can be further defined that: when general component A receives a user submission, general component B immediately performs validation. As another example, regarding the connection between general component B and general component C in a workflow topology, it can be further defined that: when the validation result of general component B is successful, general component C is triggered to store the data in the user submission; if the validation result is unsuccessful, general component C is not triggered, and an error message is returned.

[0036] In one example, component association rules can also include data linkage rules to define how data is passed between components. For instance, regarding the connection between general component A and general component B in a workflow topology, it can be further defined that general component A passes user-inputted data as an input parameter to the parameter to be validated in general component B. As another example, regarding the connection between general component B and general component C in a workflow topology, it can be further defined that general component B passes validated general component B data to general component C as data to be stored.

[0037] Step 140: Construct the workflow based on the workflow topology and the component association rules.

[0038] This step integrates the workflow topology, which includes the user-selected general components and their connections, with the component association rules that define all interaction logic, ultimately generating a complete and executable workflow.

[0039] In practical applications, a workflow can be a configuration file, a piece of executable code, or an instance that can run in a workflow engine; there are no restrictions on this.

[0040] The workflow construction method in this embodiment encapsulates functionality into standardized, general-purpose components, allowing users to build workflow topologies through graphical orchestration (such as drag-and-drop) and customize component association rules between these general-purpose components. This enables the rapid and flexible construction of workflows. Compared to traditional hard-coding development, the workflow construction method provided by this invention improves development efficiency, lowers the technical threshold, and enhances development flexibility and maintainability.

[0041] It should be noted that each implementation method of this application can be freely combined, rearranged, or executed individually, and does not need to rely on or depend on a fixed execution order.

[0042] In some embodiments, the graphical arrangement instructions are obtained in the following manner: The display interface includes a component selection area and a canvas area. In response to a first operation event and a second operation event in the visual interface, the graphical arrangement instructions are generated based on the first operation event and the second operation event. The first operation event is used to add one or more of the general components from the component selection area to the canvas area; the second operation event is used to adjust the position, configure the attributes, or establish a connection of the added general components in the canvas area.

[0043] In this embodiment, the visual interface is mainly divided into two operation areas: the component selection area and the canvas area.

[0044] Specifically, the component selection area displays all pre-built common components, such as button components, form components, text components, script components, or atomic capability components, for users to choose from at any time. The canvas area is used for users to edit common components.

[0045] In this embodiment, the user's first operation event in the component selection area and the second operation event in the canvas area are captured in real time.

[0046] Here, the first operation event typically refers to a user dragging a generic component from the component selection area to the canvas area, or clicking on a generic component in the component selection area and then placing it at a specified location on the canvas area. For example, a user drags a generic component (such as a form component) from the component selection area to an empty space on the canvas area (such as the left side of the canvas) and then releases the mouse. The complete user operation from the start of dragging to the final release, as detected by the system, is the first operation event.

[0047] Here, the second action event typically refers to editing and connecting components on the canvas, including but not limited to: Position adjustment: Drag the component to change its layout on the canvas; Attribute configuration: Select a component (such as a button component) and modify its text, color, bound backend service, and other attributes in the pop-up configuration panel; Establish a connection: Drag a line from the connection point of one component to another component to define the flow of the process and the path for data transfer.

[0048] In this embodiment, the operation data of the first operation event is recorded in real time, such as the type and identifier of the component to be added, and the position coordinates of the component to be added in the canvas area. Additionally, the operation data of the second operation event is also recorded in real time, such as the identifier of the component to be adjusted, the original and new position coordinates of the component to be adjusted in the canvas area, the identifier of the component whose attributes are configured and the configured attribute values, and the source component ID, target component ID, and connection type to be established. Finally, based on the operation data of the first and second operation events, graphical arrangement instructions are generated.

[0049] The workflow construction method in this embodiment provides a visual interface for users to edit, captures the user's first and second operation events, and generates graphical arrangement instructions. This allows users to intuitively and conveniently select and arrange the components required for the workflow without coding, reducing the technical threshold for workflow construction and improving arrangement efficiency.

[0050] In some embodiments, constructing the workflow based on the workflow topology and the component association rules includes: Based on the workflow topology, determine the task node corresponding to each of the general components, and the execution order among the multiple task nodes; Based on the component association rules, determine the data transmission path between the general components associated with multiple task nodes; A workflow is constructed based on the execution order among the multiple task nodes and the data transfer path between the common components associated with the multiple task nodes.

[0051] In this embodiment, each general component in the workflow topology is mapped to a task node, which is a specific execution step in the workflow. Specifically, the lines and arrows connecting these task nodes are analyzed to determine their execution order. For example, an arrow pointing from task node A to task node B means that task node B is the next step after task node A.

[0052] Similarly, after determining the execution order, the component association rules are parsed to determine the data transfer path between task nodes, that is, which component's data needs to be passed to which component's parameter. For example, the value of the email field in the user input form component is passed to the recipient parameter of the email sending component.

[0053] Finally, the execution order and data transfer paths obtained above are combined to generate a final, complete, and executable workflow. This workflow instance contains all the necessary information, such as what each step is, their order, branching conditions, and what data needs to be transferred between each step.

[0054] For example, if the execution order is task node A, task node B, and task node C, and the data transmission path is task node A transmitting identity information to task node B, and task node B transmitting legitimate identity information to task node C, then integrating the above execution order and data transmission path, the following workflow is ultimately constructed: After startup, task node A is executed first, loading the form interface component for user input of identity information and transmitting the input parameters to task node B according to the data transmission path. After task node A completes execution, task node B is triggered according to the execution order. Task node B receives the identity information transmitted by task node A and verifies it. If the verification passes, it outputs valid user information and transmits the input parameters to task node C according to the data transmission path. After task node B completes execution, task node C is triggered according to the transmission order. Task node C receives the valid user information transmitted by task node B and stores the relevant data in the database according to the data transmission path, and the process ends.

[0055] The workflow construction method in this embodiment maps the workflow topology to task nodes and determines the execution order. At the same time, it extracts the data transmission path from the component association rules and finally integrates the two into a runnable workflow. This realizes the automated transformation of workflow from static design to dynamic execution, and improves the flexibility and execution efficiency of workflow construction.

[0056] In some embodiments, constructing the workflow topology based on the graphical orchestration instructions of the general component and the component identifier of the general component includes: Determine at least one first target general component corresponding to the graphical orchestration instructions of the general component; Instantiate at least one of the first target general components as task nodes, and create a mapping relationship between the component identifier of the first target general component and the task node; Based on the task nodes and their corresponding execution order, a workflow topology is constructed.

[0057] In this embodiment, the graphical orchestration instructions are a set of instructions generated by the user through a visual interface (such as adding form components, adding script components, connecting form and script components, etc.). Here, the general component targeted by the graphical orchestration instructions is determined, and this general component is designated as the first target general component.

[0058] Next, the general components are instantiated by assigning specific attributes to the current process, so that they can serve as task nodes in subsequent workflows. For example, a form component can be instantiated as a user information input node in the registration process, and configured with fields (name, mobile phone number), validation rules, and other information specific to the registration scenario, thus becoming a task node that only serves the current process.

[0059] Furthermore, a mapping relationship is established between the component identifier of the first target general component and the task node, so as to quickly locate the original general component, component function, and component attribute corresponding to this task node based on the component identifier. Through the mapping relationship, the task node can inherit the function and attribute of the general component without redefining it.

[0060] Finally, the connection relationships of components are extracted from the graphical orchestration instructions and transformed into the execution order of task nodes. The task nodes and their corresponding execution order are then integrated to form a workflow topology.

[0061] The workflow construction method in this embodiment selects target general components from graphical orchestration instructions and instantiates them as task nodes. At the same time, it establishes a mapping relationship between component identifiers and task nodes, determines the execution order of nodes based on the component connection relationship, and finally constructs a workflow topology structure. This effectively reduces the technical threshold for workflow construction and improves development efficiency.

[0062] In some embodiments, defining the component association rules among the plurality of general components includes: Determine at least one set of general components from a plurality of general components; each set of general components includes a source component and at least one second target general component; For each set of general components, define the triggering conditions of the source component and the response action of each second target general component, and create at least one data transfer path between the second target general components.

[0063] In this embodiment, logically related general components are first divided into groups, namely, general component sets. A general component set typically represents a complete trigger-response scenario. Each general component set includes general components with two roles: a source component and at least one second target general component. The source component acts as the trigger for the entire interaction, and the second target general component acts as the executor of the event triggered by the source component.

[0064] For example, a leave approval workflow includes the following task nodes: submitting a leave form (form component), department manager approval (approval component), HR archiving (atomic capability component 1), sending a notification to the employee (atomic capability component 2), and rejection with a reason (text component). Based on logical relationships, these components can be divided into three general component sets: Set 1 contains the form component as the source component and the approval component as the second target general component; Set 2 contains the approval component as the source component (approved), and atomic capability components 1 and 2 as the second target general components; Set 3 contains the approval component as the source component (approved but not approved), and the text component as the second target general component.

[0065] After determining the common component set, define the triggering conditions for the source components in each common component set, including but not limited to: User actions: such as clicking a button or submitting a form; Events occur: such as a timer reaching a specified time or a message being received from the message queue; Status change: such as the value of a data field changing to pending approval; Execution result: The result will be the same as the result of the previous component, either successful or unsuccessful.

[0066] Define the response action for each second target general component in each general component set. For example, load the approval interface, display the leave application form data to the approver, and wait for the approver to perform the approval operation.

[0067] After completing the above definitions, create a mapping relationship between the data input and data output of the second target general components. For example, source component A passes all the data it collects as input to target component B. Source component B passes its processed data to target components C and D respectively. Source component B passes text to target component E for display on the interface.

[0068] The workflow construction method in this embodiment improves the accuracy and executability of workflow logic definition by dividing general components into sets containing source components and second target general components, defining source component triggering conditions, second target general component response actions, and data transfer paths between components for each set.

[0069] In some embodiments, the component identifier of the general component is obtained in the following manner: Obtain the component type and component properties of each of the aforementioned general components; Based on the component type and the component attributes, a component identifier is generated for each of the general components.

[0070] Specifically, the component identifier for each general component is generated by combining the component type and component attributes. The component type defines the core functionality and category of the component, while the component attributes describe its specific parameters and configuration.

[0071] In this embodiment, in one example, the category prefix of the component identifier can be determined by the component type, and the attribute suffix of the component identifier can be determined by the component attribute. In this way, by combining type encoding and attribute feature encoding, the uniqueness of the final generated component identifier can be ensured, and the readability of the component identifier can also be achieved.

[0072] The workflow construction apparatus provided by the present invention is described below. The workflow construction apparatus described below and the workflow construction method described above can be referred to in correspondence.

[0073] The workflow construction apparatus of this invention, such as Figure 2 As shown, it includes the following modules: first building module 210, second building module 220, third building module 230 and fourth building module 240.

[0074] The first construction module 210 is used to construct multiple general components and generate a component identifier for each of the general components; The second construction module 220 is used to construct a workflow topology based on the graphical orchestration instructions of the general components and the component identifiers of the general components; The third construction module 230 is used to define component association rules between multiple general components in the workflow topology; The fourth construction module 240 is used to construct a workflow based on the workflow topology and the component association rules.

[0075] The workflow building apparatus in this embodiment encapsulates functions into standardized, universal components, allowing users to build workflow topologies through graphical arrangement (such as drag-and-drop) and customize component association rules between universal components, thereby enabling rapid and flexible workflow construction. Compared to traditional hard-coding development, the workflow building method provided by this invention improves development efficiency, lowers the technical threshold, and enhances development flexibility and maintainability.

[0076] Figure 3 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3 As shown, the electronic device may include: a processor 310, a communications interface 320, a memory 330, and a communication bus 340, wherein the processor 310, the communications interface 320, and the memory 330 communicate with each other via the communication bus 340. The processor 310 can call logical instructions in the memory 330 to execute a workflow construction method, which includes: Construct multiple general components and generate a component identifier for each of the general components; Based on the graphical orchestration instructions of the general components and the component identifiers of the general components, a workflow topology is constructed; In the workflow topology, component association rules are defined between multiple common components; The workflow is constructed based on the workflow topology and the component association rules.

[0077] Furthermore, the logical instructions in the aforementioned memory 330 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., each of which can store program code.

[0078] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program that can be stored on a non-transitory computer-readable storage medium, wherein when the computer program is executed by a processor, the computer is capable of executing the workflow construction method provided by each of the above methods, the method comprising: Construct multiple general components and generate a component identifier for each of the general components; Based on the graphical orchestration instructions of the general components and the component identifiers of the general components, a workflow topology is constructed; In the workflow topology, component association rules are defined between multiple common components; The workflow is constructed based on the workflow topology and the component association rules.

[0079] In another aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the workflow construction method provided by each of the above methods, the method comprising: Construct multiple general components and generate a component identifier for each of the general components; Based on the graphical orchestration instructions of the general components and the component identifiers of the general components, a workflow topology is constructed; In the workflow topology, component association rules are defined between multiple common components; The workflow is constructed based on the workflow topology and the component association rules.

[0080] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0081] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0082] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in each of the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of each embodiment of the present invention.

Claims

1. A workflow construction method characterized by, The method comprises the following steps: constructing a plurality of general components and generating component identifiers of each of the general components; constructing a workflow topology according to graphical arrangement instructions of the general components and the component identifiers of the general components; defining component association rules between the plurality of general components in the workflow topology; constructing a workflow according to the workflow topology and the component association rules.

2. The workflow construction method of claim 1, wherein, The graphical arrangement instructions are obtained in the following manner: displaying a visual interface; the visual interface comprises a component selection area and a canvas area; in response to a first operation event and a second operation event in the visual interface, generating the graphical arrangement instructions according to the first operation event and the second operation event; wherein the first operation event is used to add one or more of the general components in the component selection area to the canvas area; and the second operation event is used to adjust the position, configure the attribute or establish the connection of the added general components in the canvas area.

3. The workflow construction method of claim 1, wherein, The construction of the workflow according to the workflow topology and the component association rules comprises: determining task nodes corresponding to each of the general components and the execution order between a plurality of the task nodes according to the workflow topology; determining the data transmission path between the general components associated with a plurality of the task nodes according to the component association rules; constructing a workflow according to the execution order between a plurality of the task nodes and the data transmission path between the general components associated with a plurality of the task nodes.

4. The workflow construction method of claim 3, wherein, The construction of the workflow topology according to the graphical arrangement instructions of the general components and the component identifiers of the general components comprises: determining at least one first target general component corresponding to the graphical arrangement instructions of the general components; instantiating at least one of the first target general components as a task node and creating a mapping relationship between the component identifier of the first target general component and the task node; constructing a workflow topology according to the task node and the execution order corresponding to the task node.

5. The workflow construction method of claim 3, wherein, The definition of the component association rules between a plurality of the general components comprises: determining at least one general component set in a plurality of the general components; each of the general component set comprises a source component and at least one second target general component; for each of the general component set, defining the trigger condition of the source component and the response action of each of the second target general component, and creating a data transmission path between at least one of the second target general components.

6. The workflow construction method of claim 1, wherein, The component identifier of the general component is obtained in the following manner: obtaining the component type and the component attribute of each of the general components; generating the component identifier of each of the general components according to the component type and the component attribute.

7. The workflow construction method of claim 1, wherein, The plurality of general components comprises a button component, a form component, a text component, a script component or an atomic capability component.

8. A workflow construction apparatus characterized by comprising: The method comprises the following steps: a first construction module for constructing a plurality of general components and generating component identifiers of each of the general components; a second constructing module, configured to construct a workflow topology structure according to the graphical arrangement instruction of the general component and the component identifier of the general component; a third constructing module, configured to define component association rules between a plurality of the general components in the workflow topology structure; a fourth constructing module, configured to construct a workflow according to the workflow topology structure and the component association rules.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that, The processor implements the workflow construction method in any one of claims 1 to 7 when executing the computer program.

10. A non-transitory computer readable storage medium comprising a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that, The processor implements the workflow construction method in any one of claims 1 to 7 when executing the computer program.

Images