Disclosure of Invention
The invention aims to provide a flow project building method based on an RPA editor, which aims to solve the problems that the existing flow project building method provided by the background technology is not suitable for beginners, has high learning cost and is not beneficial to efficient flow editing.
In order to achieve the purpose, the invention provides the following technical scheme: a flow project building method based on an RPA editor comprises the following steps:
the method comprises the following steps: creating an automation project based on the RPA editor;
wherein, a flow item, a component item or an element item can be created by the RPA editor;
step two: editing the automation project through the components;
step three: debugging the project flow;
step four: and completing project construction through testing.
Preferably, the creating of the flow item in the first step includes the following steps:
step 1: opening an RPA editor, creating a new flow project, and inputting a project name;
step 2: searching an 'open browser' component through an RPA editor component panel, and dragging the component into an editing area to be connected to a starting node;
and step 3: selecting a browser type and inputting a website in an attribute panel of the component;
and 4, step 4: opening a browser webpage, and intelligently recording through an RPA editor based on a recorder;
and 5: performing entry searching through a browser, selecting a search result text through a recorder, and storing and exiting;
step 6: creating a variable list through an RPA editor, and creating a character string type variable for storing and acquiring structural information;
and 7: inputting a judgment condition and linking a character string type variable through an RPA editor;
and 8: inputting the then part of entries which accord with the judgment conditions and else part of entries which do not accord with the judgment conditions;
and step 9: the creation and execution is completed.
Preferably, the creating of the component item in the first step includes the following steps:
step 11: establishing a component project at the starting page of the RPA editor, and inputting a project name;
step 12: creating two character string type input variables as input attributes of the published components through an RPA editor parameter list;
step 13: newly building a project from the RPA editor component panel, and connecting an input variable to a starting node;
step 14: inputting a reading path in the item input variable, and inputting a reading area through an RPA editor component panel;
step 15: newly building a project from the panel of the RPA editor component, and connecting another input variable to the previous project node;
step 16: inputting a writing path in the item input variable, and inputting a writing area through an RPA editor component panel;
and step 17: and finishing creation and operation and exporting use.
Preferably, the creating of the element item in the first step includes the following steps:
step 21: newly building an element project on an RPA editor start page, and inputting a project name;
step 22: opening the element item, and publishing the created element item to an element market;
step 23: establishing a flow project at the starting page of the RPA editor, and installing an element project to be published;
step 24: and specifying the element item through the element selector in the flow item for running use.
Preferably, the RPA editor is capable of opening, referencing, editing, debugging and the like on a flow item, a component item or an element item.
Preferably, when the RPA editor edits the project in the second step, the project editing type includes a sequence, a flowchart, a script, an exception handling flow, a termination handling flow, and a parallel handling flow;
meanwhile, the project editing also comprises the selection of variables, parameters and recording.
Preferably, when debugging the project in the third step, after debugging is started, the whole process is executed to the first breakpoint and is suspended, and continuation can be selected to continue execution to the next breakpoint or suspend debugging;
when the debugging process is in the process of debugging, the debugging process can be selected to be paused at any time, and meanwhile, the debugging can be selected to be stopped.
Preferably, in the debugging process, single-step execution, step-by-step execution flow, one component debugging at a time or single-step skipping can be selected to directly debug the next component.
Preferably, during the debugging process, an endpoint is inserted through the RPA editor, and during the debugging process, when a breakpoint is encountered, the debugging will be automatically suspended.
Compared with the prior art, the invention has the beneficial effects that: the flow project building method based on the RPA editor can be used for visual editing, is low in learning cost, can be suitable for beginners to use, and is beneficial to improving the editing and building efficiency;
the method is convenient for editing and building the flow project, can carry out operation test, is convenient for carrying out endpoint test, can set a debugging process, can carry out simple and direct processing, and ensures the building efficiency of the flow project.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a technical scheme that: a flow project building method based on an RPA editor comprises the following steps:
the method comprises the following steps: creating an automation project based on the RPA editor;
wherein, a flow item, a component item or an element item can be created by the RPA editor;
step two: editing the automation project through the components;
step three: debugging the project flow;
step four: and completing project construction through testing.
In a specific application scenario, creating a flow item includes the following steps:
step 1: opening an RPA editor, creating a new flow project, and inputting a project name (taking MyFirstProject as an example);
step 2: searching an 'open browser' component through an RPA editor component panel, and dragging the component into an editing area to be connected to a starting node;
and step 3: in the attribute panel of the component, selecting a browser type and inputting a website, selecting the browser to use: IE, and web address can be selected: "https:// www.baidu.com";
and 4, step 4: opening a browser webpage, and intelligently recording through an RPA editor based on a recorder, wherein UIA3 is selected by a recorder desktop recording technology, and the support of the UIA3 is better for WPF and Windows Store Apps; (ii) a
And 5: performing entry searching through a browser, selecting a search result text through a recorder, and storing and exiting;
if weather is input, searching is carried out, and weather conditions are obtained and stored;
step 6: creating a variable list through an RPA editor, and creating a character string type variable for storing and acquiring structural information;
creating a String-type variable-weather for storing the retrieved weather text
And 7: inputting a judgment condition and linking a character string type variable through an RPA editor;
dragging in a "condition (If)" component from the component panel connects to the "get text" component, in the property panel of which the following is entered: judging conditions: contacts ("rain")
And step 8: inputting the then part of entries which accord with the judgment conditions and else part of entries which do not accord with the judgment conditions;
drag-in a confirmation box component to the Then part of the condition and enter the following in the property panel of the component: title: "tomorrow weather alert", description: 'rain in open weather, remember to bring umbrella'
Drag another confirmation box into the Else part of the condition and enter the following in the property panel of the component: title: "tomorrow weather alert", description: "go out and walk away in the daytime without rain".
And step 9: the creation is completed and the operation is executed.
In a specific application scenario, creating a component item includes the steps of:
step 11: creating a component project on an RPA editor start page, and inputting a project name (taking Excel data migration as an example);
step 12: creating two character string type input variables as input attributes of the published components through an RPA editor parameter list;
including, the read path: the path where the Excel file to be read is located and the write path are as follows: a path where an Excel file to be written is located;
step 13: newly building a project from the RPA editor component panel, and connecting an input variable to a starting node;
step 14: inputting a reading path in the item input variable, and inputting a reading area through an RPA editor component panel;
step 15: newly building a project from the panel of the RPA editor component, and connecting another input variable to the previous project node;
step 16: inputting a writing path in the item input variable, and inputting a writing area through an RPA editor component panel;
and step 17: and finishing creation and operation and exporting use.
In a specific application scenario, creating an element item includes the steps of:
step 21: newly building an element project on an RPA editor start page, and inputting a project name;
step 22: opening the element item, and publishing the created element item to an element market;
step 23: establishing a flow project at the starting page of the RPA editor, and installing an element project to be published;
and step 24: and specifying the element item through the element selector in the flow item for running use.
Preferably, the RPA editor is capable of opening, referencing, editing, debugging and the like on a flow item, a component item or an element item.
In a specific application scenario, when an RPA editor is used for editing a project, the project editing type comprises a sequence, a flow chart, a script, an exception handling flow, a termination processing flow and a parallel processing flow;
where the sequence is the smallest item type. They are suitable for linear processes, can seamlessly transition from one component to another, and can act as a single component block;
the flow chart can be used in a variety of situations, from large projects to small projects, where it can be reused;
unlike a sequence, the most important aspect of the flow chart is that it is applicable to more complex business logic. Automation items can be integrated simply and quickly in a more diverse manner using a plurality of different logical operators;
the script is a code file for storing different languages;
when the flow has errors in the running process, the exception handling flow helps to capture error information and process the error information;
when the execution of the main business flow is stopped, the termination processing flow is automatically operated, and the termination processing flow is usually used for state resetting, notification sending and the like;
the parallel processing flow is used for creating a flow which runs on the same robot in parallel with a certain foreground flow. For this reason, the parallel processing flow must not contain components that require user interaction;
meanwhile, the project editing also comprises the selection of variables, parameters and recording.
Furthermore, when debugging the project in the third step, after debugging is started, the whole process is executed to the first breakpoint and is suspended, and continuation can be selected to continue execution to the next breakpoint or suspend debugging;
when the debugging process is in the debugging process, the debugging process can be selected to be paused at any time, and meanwhile, the debugging can be selected to be stopped.
Furthermore, in the debugging process, single step execution, step-by-step execution flow, one component debugging at a time or single step skipping can be selected to directly debug the next component, in the debugging process, an endpoint is inserted through an RPA editor, and when a breakpoint is met in the debugging process, the debugging can be automatically suspended
Although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that various changes in the embodiments and/or modifications of the invention can be made, and equivalents and modifications of some features of the invention can be made without departing from the spirit and scope of the invention.