Product: Kryon RPA
Product Version: 20.9.2
Components: Kryon Robot; Kryon Studio
Article Contributors: Richard Holt Jr
Buttons can be hard to work with when pages are formatted in obtuse ways. This article allows for a simpler approach to understanding and working with them.
Steps:
Working with buttons in a webpage is not always rudimentary. There are so many ways to create a button that the basic knowledge that something is a button can sometimes be illusive. “Buttons” can be created from button objects, links, div objects (divisions of a page), or even text. There are even more ways to create a button than these listed. To a user, a “button” is an item that when clicked causes a reaction. This usually triggers some underlying code in JavaScript or similar scripting language. For this reason, in this article assume that when we are talking about a clickable object, it will be described as a button for simplicity’s sake.
To illustrate this, this webpage with eleven different types of buttons was created. These buttons were clicked using Kryon in three different ways. Keep in mind, each step clicks a single button and can be used independent of any other steps, barring step 33 and 34 which deal with buttons inside iframe objects.
The eleven different types of buttons depicted in this webpage are located in a table format in the following manner:
| Description of Button Used |
| Button |
These buttons include:
- Button object
- Link object
- Button object that acts as a link
- Link object that acts as a button
- Div object that acts as a button (with button)
- Div object that acts as a button (without button)
- Button with no action
- Link with no action
- Disabled button
- Div object that acts as a button that clicks another button (the disabled button)
- Button object inside of an iframe
In the wizard, one can see that the visual objects have virtually no issue clicking on all the objects, but the issue is trying to find a unique enough object to reference. One can also see that the html objects, since these are not dynamically loaded, can click on the objects reliably. The one exception is the iframe button, but even it is clicked most of the time. And finally, the JavaScript is very reliable and fast. It also does not depend on the browser. The one caveat is that the iframe cannot be accessed directly from the main page via JavaScript as modern browsers have a block from accessing any iframe data from the main page for security reasons. This was overcome by simply finding the URL of the iframe page and loading that as a main page momentarily to click the button.
The wizard was created using RPA 20.9.2 but the methods used can be modified to any modern version of Kryon. The webpages must be hosted for Studio to understand how to interpret them. These tests were performed using https://app.netlify.com/drop to host the webpage.
Here are the files that I used:
StudioButtonTesting.zip
Working With Buttons.dwiz
https://drive.google.com/drive/folders/1EgtCSmIHC9TQ2Rqq5eHFIW4Ztf4g3ygx?usp=sharing