CN116468388A

CN116468388A - Flow mixing arrangement system

Info

Publication number: CN116468388A
Application number: CN202310329609.2A
Authority: CN
Inventors: 葛丁佳
Original assignee: Shanghai Jingkun Computer Technology Co ltd
Current assignee: Shanghai Jingkun Computer Technology Co ltd
Priority date: 2023-03-30
Filing date: 2023-03-30
Publication date: 2023-07-21

Abstract

The embodiment of the disclosure provides a flow mixing arrangement system. Mixing and arranging at least part of nodes in the node providing module based on setting operation through the workflow generating module to form a workflow; the setting operation includes at least one of a drag, a pull, and a drag operation; the workflow execution module executes the workflow to obtain an execution result; the execution result comprises an execution state and an execution progress; and the display module displays the execution result. According to the embodiment, at least part of nodes in the node providing module can be mixed and arranged through the workflow generating module based on the setting operation to form a workflow, so that arrangement of an automatic flow under a plurality of business scenes can be realized.

Description

Flow mixing arrangement system

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a flow mixing arrangement system.

Background

With the gradual development of enterprise project business, business processes are gradually accumulated, the informationized construction of enterprises lacks planning, and various application systems are blindly built and purchased only with consideration of the requirements before the enterprises. However, the company operation needs cooperation of all departments, and the workflow involves different application systems of a plurality of departments, at this time, the application systems have no unified technology and data standard, the data cannot be mutually and automatically transferred, and the association sharing of the data is lacking, so that information island is caused, and the high-efficiency operation of the enterprise is seriously affected.

Disclosure of Invention

The embodiment of the disclosure provides a process mixing arrangement system which can realize arrangement of automatic processes under a plurality of business scenes.

In a first aspect, embodiments of the present disclosure provide a process mixing orchestration system, the system comprising: the system comprises a node providing module, a workflow generating module, a workflow executing module and a display module; the node providing module is used for providing at least one of a condition control node, an automation node, a resource node, a development operation and maintenance node and a notification report node; the workflow generation module is used for carrying out mixed arrangement on at least part of nodes in the node providing module based on setting operation to form a workflow; the setting operation includes at least one of a drag, a pull, and a drag operation; the workflow execution module is used for executing the workflow and obtaining an execution result; the execution result comprises an execution state and an execution progress; the display module is used for displaying the execution result.

According to the technical scheme disclosed by the embodiment, at least part of nodes in the node providing module are mixed and arranged through the workflow generating module based on setting operation to form a workflow; the setting operation includes at least one of a drag, a pull, and a drag operation; the workflow execution module executes the workflow to obtain an execution result; the execution result comprises an execution state and an execution progress; and the display module displays the execution result. According to the embodiment, at least part of nodes in the node providing module can be mixed and arranged through the workflow generating module based on the setting operation to form a workflow, so that arrangement of an automatic flow under a plurality of business scenes can be realized.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a schematic diagram of a flow mixing orchestration system according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram of another flow mixing arrangement system according to an embodiment of the invention.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but 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 illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the system embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, system embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

It will be appreciated that the data (including but not limited to the data itself, the acquisition or use of the data) involved in the present technical solution should comply with the corresponding legal regulations and the requirements of the relevant regulations.

Fig. 1 is a schematic architecture diagram of a process mixing orchestration system according to an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a process orchestration situation, as shown in fig. 1, and the system includes: the system comprises: the system comprises a node providing module, a workflow generating module, a workflow executing module and a display module; the workflow generation module is used for carrying out mixed arrangement on at least part of nodes in the node providing module based on setting operation to form a workflow; the setting operation includes at least one of a drag, a pull, and a drag operation; the workflow execution module is used for executing the workflow and obtaining an execution result; the execution result comprises an execution state and an execution progress; the display module is used for displaying the execution result.

The node providing module is used for providing at least one of a condition control node, an automation node, a resource node, a development operation and maintenance node and a notification report node.

Optionally, the condition control node includes a control component and a condition component; the condition component comprises an aggregation judgment rule and a one-by-one judgment rule; the aggregation judgment rule comprises judging based on the maximum value, the minimum value or the average value of a plurality of output values and a set target value if the prepositive node of the current node outputs the plurality of output values; the one-by-one judging rule comprises at least one condition group; the set of conditions includes at least one or condition and/or at least one and condition; the condition component is used for judging the input value of the condition component according to the aggregation judgment rule or the one-by-one judgment rule to obtain a judgment result; the workflow generating module is further used for connecting a plurality of nodes according to the condition control node to form a multi-branch workflow; the workflow execution module is further used for executing the multi-branch workflow according to the judging result; the control component is used for configuring the branch completion meeting item; the branch completion satisfaction item includes at least one branch execution completion in the multi-branch workflow; the workflow execution module is further configured to execute the post node of the multi-branch workflow based on the control component after the branch execution is completed.

The input value may be understood as an input parameter, and the input value may be an output parameter (i.e., an output value) of the front node, or may be a custom variable.

It should be noted that, with respect to the relationship between a component and a node, a component may be understood as a node. Specifically, the workflow generation module may consider a component to be a node when it orchestrates the components to form a workflow.

The condition control nodes comprise condition nodes and control nodes.

In this embodiment, the workflow generating module is further configured to connect a plurality of nodes according to the condition node to form a multi-branch workflow. Specifically, a plurality of nodes can be accessed after the conditional node to form a multi-branch workflow. The workflow execution module is further configured to execute the multi-branch workflow according to the determination result. Taking a one-by-one judgment rule as an example, each condition group can be accessed to one or more branch nodes, if a certain condition group judgment is passed, executing all the branch nodes accessed by the condition group, and if the certain condition group judgment is not passed, not executing all the branch nodes accessed by the condition group. If the judging result of each condition group does not pass, all branch nodes accessed by each condition group are not executed.

Wherein a multi-branch workflow may be understood as a part of the workflow. In this embodiment, the condition component is configured to, when a user composes a workflow (i.e. a workflow) and there is a requirement for multiple branches, access the condition component, i.e. the condition node, after the front node, and control the workflow to branch through a condition component custom configuration judgment item. And accessing the multi-branch node after the conditional node. Wherein a pre-node may be understood as a node preceding the current node. The types of the condition component supporting judgment rules include an aggregate judgment rule and a one-by-one judgment rule. The aggregation judgment rule comprises that if the front node of the current node outputs a plurality of output values, judgment is carried out based on the maximum value, the minimum value or the average value of the plurality of output values and a set target value. Wherein the current node may be understood as a conditional node. The one-by-one judging rule comprises at least one condition group; the set of conditions includes at least one or condition and/or at least one and condition. For the judging rules one by one, the parameter outputting, the custom variable and the parameter outputting variable of the front node can be judged. For the current node's entry, it can be understood as the exit of the leading node. Both in and out parameters can be understood as parameters. One condition group may have a plurality of branches, and a plurality of condition groups may also have a plurality of branches, which is not limited in this embodiment. For example, a determination is made for the value of A, B, assuming that a is 999 and b is 666, the condition determination rule is rule-by-rule: the first condition set is set as A not being empty, the second condition set is set as A being empty or B being equal to 666, and branches of two condition sets which are connected into the first condition set and the second condition set at the rear are all executed in a circulating mode if condition judgment is executed. The condition component is used for judging the input value of the condition component according to the aggregation judgment rule or the one-by-one judgment rule to obtain a judgment result; the workflow generating module is further used for connecting a plurality of nodes according to the condition control node to form a multi-branch workflow; the workflow execution module is further configured to execute the multi-branch workflow according to the determination result.

In this embodiment, the control component is configured to configure a branch completion satisfaction item; the branch completion satisfaction item includes at least one branch execution completion in the multi-branch workflow. The branch completion satisfaction item may be all branch execution completion, or may be custom which branch execution is completed, that is, may be part of branch execution completion. The workflow execution module is further configured to execute the post node of the multi-branch workflow based on the control component after the completion of the branch execution in the branch completion satisfaction item.

For example, when the workflow has multiple branch flows, the control component may be accessed after the multiple branches to form a control node, and if the current control node branch completion satisfaction item is set to be that all branch execution is completed, all branch flows that need to be connected with the control node are executed and then the post node or post flow of the control node is executed. If the branch completion satisfying item is set as a partial branch execution completion, the user can select a branch node connected with the control node, configure the completion and incompletion states of the branch node in a self-defined manner, and execute the control node post-flow after the branch flow execution accords with the branch completion satisfying item.

Optionally, the automation node includes an API component and a script component; the API component is used for acquiring service data of the third party system; the script component is used for processing the business data based on the script language.

Wherein the automation nodes comprise API nodes and script nodes.

In this embodiment, the API component supports APIs of the hypertext transfer protocol (HyperTextTransferProtocol, HTTP) and the hypertext transfer security protocol (HypertextTransferProtocolSecure, HTTPS), so that a user may obtain service data of a service system interface or service data of a third party system by arranging the API component, map nodes back and forth to open the service data by setting some parameters of the API response result, control the workflow more flexibly, and perform complex processing on the service data, thereby opening the information island phenomenon. Meanwhile, the API component supports polling operation, and a user can set different polling types according to requirements, wherein the polling types comprise: the polling time, the incremental polling and the polling times are used for selecting a field needing to be polled, and an expected value is set, and when the API response does not meet the expected requirement, the flow mixing arrangement system automatically calls an API component according to the setting.

Optionally, the system further includes an API management module, where the API management module is configured to generate a component and store the component in the node providing module.

In this embodiment, the flow mixing orchestration system further includes an API management module, where components generated using the API are exposed in an API component list. The user can customize the components generated by the drag API and make the layout of the workflow.

In this embodiment, the API management module may provide an API management function, support types of APIs such as WebService for HTTP and Web services, and the API entry mode supports two types of manual addition and import, so that a user may import types of data such as a Postman interface test tool and a Swagger framework in a one-key manner. And monitoring the API according to the set time by configuring the API monitoring, and if the API is abnormal, sending the API to corresponding staff in a mail mode. And by capturing the data of calling the API, integrating and visually displaying API monitoring data, wherein the monitoring data comprises various API monitoring indexes such as the number of times of calling the API, the calling amount, the monitoring frequency and the like. In addition, the components generated by the API may be saved to a node provisioning module (i.e., an application component library) of the workflow to be provided to the user for use in orchestrating the workflow. When the API is saved to the component, the user can select to set part of request parameters of the current API into form parameters in a self-defined way, and take part of response parameters of the API response result as output parameters for the subsequent nodes to use.

In this embodiment, the scripting language may be a programming language such as Python, bat, shell and Powershell, and the scripting component may support the customized setting of the parameter output and parameter input of the script, so as to integrate the service data of other nodes in the workflow and provide the service data for other nodes to use. And writing a service script in the script component, wherein the service script is used for processing service data and operation and maintenance operations in a service scene. When the business function is complex, a plurality of script components are arranged through various strategies such as conditions, judgment, branching and the like to form a workflow, so that the function of automatically operating the business scene is achieved.

Optionally, the resource node includes a public cloud component and a private cloud component; the public cloud component is used for creating cloud resources based on the first set resource information and the first set credential information; the private cloud component is used for creating virtual machine resources based on the second setting credential information, the second setting resource information and the virtual machine template information.

The resource nodes comprise public cloud nodes and private cloud nodes.

In this embodiment, the first setting resource information may be resource information configured by the user, such as example type and resource configuration information. The first set credential information may be a credential configured by a public cloud component that may be used to automatically create cloud resources based on the first set resource information and the first set credential information.

In this embodiment, the second setting credential information may be credential information configured by a user, and the second setting resource information may be resource information configured by the user. The private cloud can acquire the data center which can be accessed by the current account through the second set credential information, so that a host or a cluster can be selected in a self-defined mode, a virtual machine template and second set resource information can be acquired, and virtual machine resources can be automatically created.

Optionally, the development operation node includes a code management component, a code construction component, an article management component, a host deployment component, a mirror construction and management component, and a quality management component; the code management component is used for configuring a code warehouse source address so as to pull codes; the code construction component is used for compiling and packaging the pulled codes based on a set construction mode to obtain a packaged file; the product management component is used for uploading the packaged file to a setting warehouse; the host deployment component is used for deploying the packaged file into a set host; the mirror image construction and management component is used for packaging the pulled codes into a mirror image package file by calling a setting plug-in, sending the mirror image package file to a mirror image warehouse and distributing the mirror image package file to the setting host; the quality management component is used for integrating a setting tool, scanning the pulled codes based on the setting tool and executing test operation based on the setting tool and a setting file.

The development operation and maintenance nodes comprise a code management node, a code construction node, a product management node, a host deployment node, a mirror image construction and management node and a quality management node.

In this embodiment, the development operation and maintenance component uses an automated integration tool based on the development operation and maintenance devops concept to complete the operations of pulling, compiling, constructing, deploying to a host and automated testing of an application from a code, and meanwhile, can access a script component according to requirements for operation and maintenance operations before and after application deployment.

Specifically, the source address of the code warehouse and the project branches to be constructed can be configured in the management component so as to pull the code. Through the code construction component, a corresponding setting construction mode (such as a construction tool Maven, gradle, ANT, NPM) is selected, the pulled code is compiled based on the setting construction mode, and the code is packaged after the compiling, so that a packaged file is obtained. After compiling and packaging are completed, the packaged packaging text can be uploaded to a setting warehouse, which can be a Nexus warehouse, through a product management component according to requirements. And finally, distributing the packaged file to a setting directory of the setting host through the host deployment component.

In this embodiment, the setting plug-in, such as a Docker plug-in, may also be called by the mirror image building and managing component, where the pulled code is packaged into a mirror image package file, the mirror image package file is sent to a mirror image repository, and the mirror image package file is distributed to a setting directory of the setting host.

Specifically, the quality management component integrates a setting tool, such as a Jmeter test tool and a Sonar code quality management tool, and scans the pulled code based on the Sonar code quality management tool. And acquiring a setting file uploaded by a user, such as a Jmeter file, performing corresponding test operations, such as interface test, performance test operation and the like, based on the Jmeter test tool and the setting file, and outputting a test report.

Optionally, the notification reporting node includes a notification component and a reporting component; the notification component is used for configuring notification information and notification modes; the reporting component is configured to generate an execution report based on the execution result.

The notification reporting node comprises a notification node and a reporting node.

In this embodiment, the notification method may be a plurality of notification methods such as mail or office software. The notification information may include notification information and contact information of the notification target object. For example, if the notification mode is mail, the contact mode of the notification target object is the mail address of the recipient, and the notification information may be service data generated in the process of executing the workflow or information such as an execution result. By configuring the notification component in the workflow, the requirement that a user needs to notify related personnel (target objects) when the specified operation is completed can be met, the notification mail and the message support the parameter outputting of the mapping front node, and the service data or the execution result generated in the process of executing the workflow are intuitively displayed to the related personnel (target objects) in a notification mode.

In this embodiment, by configuring the report component, a PDF file report may be generated by editing based on service data or an execution result generated in the workflow, and downloading of the file report may be achieved by clicking a link of the PDF file report.

In this embodiment, for the workflow generating module, at least part of the components (i.e., at least part of the nodes) of the node providing module (i.e., the application component library) may be arranged in series through a setting operation to form a workflow. The workflow supports serial, parallel, conditional, branching, failed retry, etc. functions. The automatic circulation of each node can be realized through the workflow execution module, so that the inefficiency and the error of the manual processing workflow are solved, and the working efficiency is improved. Meanwhile, the execution result is directly displayed in real time through the display module, the execution state of the workflow is tracked in real time, and the automation of the business process is realized.

In this embodiment, the workflow execution module executes the workflow, and may obtain an execution result of each node, where the execution result may be represented by a log. The execution status and execution progress of the workflow can be represented by the execution result. The presentation module presents the log (execution result) by reading the log.

In this embodiment, the display module may further provide visual workflow construction, and full-interface visual dragging, pulling, and dragging to implement user-defined arrangement of the workflow, and provide a viewing function supporting a flow view viewing function and a real-time log generated by the workflow operation, so as to monitor and track the execution condition of the workflow in real time, thereby implementing real-time monitoring and tracking of the execution state and execution progress of the workflow.

In this embodiment, the workflow generating module further provides workflow collaboration capability, so that the current user can collaborate the created workflow to other user groups and/or other users, thereby facilitating organization and co-establishment and sharing of internal flows of a team.

In this embodiment, the variable corresponding to the workflow may meet the requirement that the user needs to transfer parameters between the flow nodes. In the workflow execution process, the execution of a certain node depends on the output of a previous node, and can be realized by using the output parameter quantity of the workflow and the configuration of the mapping front node parameter in the flow node. Meanwhile, the system disclosed by the embodiment can be used for configuring the input parameters during dynamic execution, and the input parameters can be realized through the custom variables of the workflow.

In this embodiment, the public service may be modularized by the flow mixing arrangement system, so that free mixing arrangement of multiple types of nodes may be supported, and a workflow may be arranged by adding new flow nodes and custom mixing arrangement nodes. The workflow can be expanded and arranged in an integrated external service mode, so that different flows corresponding to different service scenes can be built. The operations of flow, judgment, polling, failure retry and the like of the flow are handed over to the workflow generation module to be responsible, so that a user can focus on core business logic combing of a business scene, multiplexing and sharing of the business flow are supported, and the efficiency of the business scene and maintainability of the scene flow can be improved.

Optionally, the system further includes a plan module, where the plan module is configured to drag the plurality of workflows into a setting canvas if the number of workflows is multiple, and schedule an execution order of the plurality of workflows, so that the workflow execution module executes the plurality of workflows according to the execution order.

In this embodiment, if there are multiple workflows, different workflows may be dragged into the canvas, and the execution order corresponding to each workflow is arranged, and the multiple workflows are executed according to the execution order.

Optionally, the workflow execution module is further configured to continue executing the workflow at an interrupt if the workflow is interrupted.

In this embodiment, the workflow execution module may provide a failed retry function during the execution of the workflow. Specifically, when the workflow fails to execute in the running process, the workflow is interrupted, after the workflow is interrupted, the display module records the task node state in the workflow executing process, and meanwhile, the workflow executing module can retry to continue to execute tasks from the position where the task flow fails to interrupt, so that the whole workflow is not required to be executed again, and the waste of time and resources is reduced.

Fig. 2 is a schematic diagram of another flow mixing layout system according to an embodiment of the present invention. Optionally, the system further comprises a time setting module; the time setting module is used for setting the execution period or the execution time of the workflow; the workflow execution module is further configured to execute the workflow based on the execution cycle or the execution time.

In this embodiment, the workflow generating module may be bound to a time setting module, where the time setting module is configured to set an execution period or execution time of the workflow, where the execution period may be a multi-period type such as quarter, month, week, day, hour, minute, second, and the like. The execution time is understood to be a specific time point, for example, 14 minutes at day 29 of 2023, 3.

In this embodiment, the execution period or the execution time of the workflow may be set by the time setting module according to the requirement, and the workflow generating module may be bound, and the workflow executing module may execute the workflow according to the set execution period or execution time after reading the workflow.

Optionally, the workflow generating module is further configured to generate a workflow application program interface API, so that a third party system calls the API to execute the workflow.

In this embodiment, after the workflow is arranged, the workflow generating module may automatically generate a workflow application program interface API for external calling, so as to facilitate third party system integration to call the workflow. The user may view the request parameters at the workflow API interface and also support the downloading of the workflow API document.

As shown in fig. 2, optionally, the system further includes a security management module, where the security management module is configured to set a security rule and/or a fusing mechanism of the workflow; the workflow execution module is further configured to execute the workflow based on the security rules and/or fusing mechanism; the security rule comprises a host address for configuring and calling a workflow and a time period for the host to call the workflow; the fusing mechanism comprises that if the failure times of the workflow execution module for executing the workflow is larger than or equal to the set failure times in the set time, the workflow execution module prohibits the workflow from being invoked in the set freezing time.

In this embodiment, the security policy may be configured by the security management module, and the security management module is bound to the workflow generation module to provide the security policy management capability of the workflow, and by adding the security policy, the security of the workflow is uniformly managed and controlled. The security policy includes security rules and/or a fusing mechanism. The security rule may be to set the address of the host that called the workflow in the white list and the period of time that the host called the workflow. The fusing mechanism may include disabling the workflow execution module from invoking the workflow during a set freeze time if the number of failures of the workflow execution module to execute the workflow is greater than or equal to a set number of failures during the set time. For example: the set time was set to 5 minutes, the number of failures was 10, and the freezing period was 30 minutes. That is, if the a workflow is called for execution 10 times within 5 minutes, the a workflow will be frozen for 30 minutes and execution cannot be called for. And the display module can visually check the execution condition of the workflow bound by the security management module, wherein the execution condition can comprise the number of the workflows, the execution times of the workflows, the fusing times (namely the freezing times), the fusing records, the execution condition of the workflows and the error rate, so as to monitor the execution condition of the workflows and perform flow analysis based on the execution condition.

According to the flow mixing arrangement system disclosed by the embodiment of the invention, the workflow generation module is used for mixing and arranging all components in a dragging mode to form a workflow based on the graphical flow designer, so that the definition of various complex business scene flows can be rapidly realized. And executing the workflow through the workflow execution module to finish the operation of the corresponding business scene.

In the technical scheme disclosed by the embodiment, a low-code development environment is provided by a flow mixing arrangement system, and all components are intelligently integrated to form a workflow. Meanwhile, the user can self-define and drag the building workflow. Through the process mixing arrangement system, a user can quickly build a series of work processes, open the existing service systems, and integrate the service data and processes scattered in each service system. The execution states of all workflows are tracked and checked in real time through the display module, so that problems are found in time and optimization improvement is promoted. The flow mixing arrangement system can form an automatic flow by carrying out global mixing arrangement on various digitization capacities in a way of packaging components and dragging across technical stacks, so that more business requirements are met, and the automatic flow arrangement of each digitization scene is realized.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or system logic acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. A process mixing orchestration system, the system comprising: the system comprises a node providing module, a workflow generating module, a workflow executing module and a display module;

the node providing module is used for providing at least one of a condition control node, an automation node, a resource node, a development operation and maintenance node and a notification report node;

the workflow generation module is used for carrying out mixed arrangement on at least part of nodes in the node providing module based on setting operation to form a workflow; the setting operation includes at least one of a drag, a pull, and a drag operation;

the workflow execution module is used for executing the workflow and obtaining an execution result; the execution result comprises an execution state and an execution progress;

the display module is used for displaying the execution result.

2. The system of claim 1, further comprising a time setting module; the time setting module is used for setting the execution period or the execution time of the workflow; the workflow execution module is further configured to execute the workflow based on the execution cycle or the execution time.

3. The system of claim 1, wherein the workflow generation module is further configured to generate a workflow application program interface API for a third party system to call to the API to execute the workflow.

4. The system according to claim 1, further comprising a security management module for setting security rules and/or fusing mechanisms of the workflow; the workflow execution module is further configured to execute the workflow based on the security rules and/or fusing mechanism; the security rule comprises a host address for configuring and calling a workflow and a time period for the host to call the workflow; the fusing mechanism comprises that if the failure times of the workflow execution module for executing the workflow is larger than or equal to the set failure times in the set time, the workflow execution module prohibits the workflow from being invoked in the set freezing time.

5. The system of claim 1, wherein the workflow execution module is further configured to continue executing the workflow at an interrupt if the workflow interrupts execution.

6. The system of claim 1, wherein the condition control node comprises a control component and a condition component; the condition component comprises an aggregation judgment rule and a one-by-one judgment rule; the aggregation judgment rule comprises judging based on the maximum value, the minimum value or the average value of a plurality of output values and a set target value if the prepositive node of the current node outputs the plurality of output values; the one-by-one judging rule comprises at least one condition group; the set of conditions includes at least one or condition and/or at least one and condition;

the condition component is used for judging the input value of the condition component according to the aggregation judgment rule or the one-by-one judgment rule to obtain a judgment result; the workflow generating module is further used for connecting a plurality of nodes according to the condition control node to form a multi-branch workflow; the workflow execution module is further used for executing the multi-branch workflow according to the judging result;

the control component is used for configuring the branch completion meeting item; the branch completion satisfaction item includes at least one branch execution completion in the multi-branch workflow;

the workflow execution module is further configured to execute the post node of the multi-branch workflow based on the control component after the branch execution is completed.

7. The system of claim 1, wherein the automation node comprises an API component and a script component; the API component is used for acquiring service data of the third party system;

the script component is used for processing the business data based on the script language.

8. The system of claim 1, wherein the resource nodes comprise public cloud components and private cloud components; the public cloud component is used for creating cloud resources based on the first set resource information and the first set credential information; the private cloud component is used for creating virtual machine resources based on the second setting credential information, the second setting resource information and the virtual machine template information.

9. The system of claim 1, wherein the development and maintenance node comprises a code management component, a code construction component, an article management component, a host deployment component, a mirror construction and management component, and a quality management component; the code management component is used for configuring a code warehouse source address so as to pull codes; the code construction component is used for compiling and packaging the pulled codes based on a set construction mode to obtain a packaged file; the product management component is used for uploading the packaged file to a setting warehouse; the host deployment component is used for deploying the packaged file into a set host; the mirror image construction and management component is used for packaging the pulled codes into a mirror image package file by calling a setting plug-in, sending the mirror image package file to a mirror image warehouse and distributing the mirror image package file to the setting host; the quality management component is used for integrating a setting tool, scanning the pulled codes based on the setting tool and executing test operation based on the setting tool and a setting file.

10. The system of claim 1, wherein the notification reporting node comprises a notification component and a reporting component; the notification component is used for configuring notification information and notification modes; the reporting component is configured to generate an execution report based on the execution result.

11. The system of claim 1, further comprising a plan module for dragging a plurality of workflows into a setting canvas if the workflows are plural, and arranging an execution order of the plurality of workflows so that a workflow execution module executes the plurality of workflows in the execution order.

12. The system of claim 1, further comprising an API management module for generating components and saving to the node providing module.