Release Notes

v.3.4

Issue

The user was unable to automate actions on a specific website using WebAutomation activities.

Root Cause

Although the feature successfully identified the element, the browser blocked the programmatic action due to a Content Security Policy (CSP) error.

Fix Details

We have resolved the issue by updating the runtime script to handle the JavaScript execution in compliance with CSP restrictions.

v.3.2

Issue

The user is unable to click on a specific element on the webpage.

Root cause

We found that the issue was with the general.css file, which was used to highlight elements. After adding the CSS file, it attempts to search for headers on the web page. Since there are no headers on the current web page, it was throwing a null error.

Fix details

We added the general.css file for overall styling, but the exact name of the CSS file could vary (e.g., main.css, style.css, or base.css). Therefore, we added validations to the style.css file for those extensions and released revised version.

Expected behavior

Since we added the validations to the style.css file, even though the headers are not present on the webpage, the web automation (clicking on a specific element) will work.