UI-flow
UI-flow is primarily used for automating UI processes.
In many cases, UI-flow might not be necessary. However, if the software you want to automate doesn’t provide an API, or if you are unfamiliar with APIs, you can add a UI-flow to your workflow to achieve results. Creating a UI-flow involves using our builder plugin, which records your actions to reproduce them during automation.
Usage
UI-flow can automate UI processes by recording user interactions and replicating them. This allows for automation in scenarios where APIs are not available.
Settings
Tips & Tricks
Add Steps
In a UI-flow, most nodes are steps. Each step corresponds to an action (e.g., click, input, or pressing a shortcut). Multiple actions can be combined into a single UI-flow.
In most cases, you can record these steps using the builder plugin, but you can also manually add steps by clicking the plus sign. However, steps added manually in the editor do not have the key attributes (target object and the action to be performed) and require this information to make the step complete. (Refer to matching rules and action rules for detailed setup methods).
It is recommended to use the builder plugin to record steps initially and then modify them as needed.
Application Launcher
Another type of node in a UI-flow is the Application Launcher. This node is used to open a new application window, determining where the subsequent steps will be executed.
There are a few configuration options:
- In UI-flows that run independently, an Application Launcher should be included at the beginning to open the corresponding page.
- If the target page is always a fixed address(eg. google.com), just enter the corresponding address is enough.
- If the target page varies(eg. a.jira.com and b.jira.com), set it with prompt labels. The agent will ask the user for the information of those labels before attempting to execute the flow.
- When a UI-flow is part of a workflow and doesn’t need to open a new window, such as two UI-flows executing consecutively in one window, the Application Launcher in the second UI-flow should be deleted to avoid opening a new window during execution.