ES-361 – Upgraded jQuery library to address the following reported vulnerability: CVE-2015-9251.
ES-511 – Resolved RPA Script Playback UI issues.
ES-550 – Resolved issue where maximizing the RPA Toolbar would cause the change detection code to warn of unsaved changes.
ES-573 – Resolved display issues on the RPA Playback Summary Grid, in which the grid flashed and showed scrollbars when not needed in light theme, and failed to display in dark theme.
ES-574 – Resolved issue where the “play to step” action did not show a result in the RPA summary grid.
ES-578 – Resolved RPA Script Center display issues in the Internet Explorer 11 browser.
ES-492 – Added a “switch to page” RPA script command.
ES-502 – Added the ability to click to select a step on the RPA Script editor.
ES-116 – Addressed issue when changing Single Sign-on (SSO) rules where the proxy would queue up a new SignOnAttempt, but count both processes towards the redirect limit.
ES-408 – Addressed issue where password policy checks were performed on a user authenticated through custom auth, which typically required additional code in customAuth.js to avoid password policy checks from breaking the custom authenticated session from being established.
ES-414 – Resolved issue where the current edgeWeb data response needed to be reset when the existing Single Sign-on (SSO) session was re-established due to a timeout or other error.
ES-528 – Resolved issue where the drop-down visualization selector was not dismissing when the visualization is maximized.
ES-174 – Added access in the HTML Template Visualization to the container div via ‘$scope.containerElement’ and to the widgetId via ‘$scope.widgetID’. This can be used to limit jQuery DOM searching to within the Visualization, avoiding potential access to unwanted DOM nodes.
ES-512 – Added ability for a Server Action to prompt for record value but also show selected value from the table where the action is run from.
edgeCore uses H2 database in support of the SQL Transforms. SQL that uses Common Table Expression (CTE) ‘WITH’ clauses have been identified as causing two issues.
For additional information on this known issue, and remediation options, see SQL Transform.