What's New in 6.6

  • When upgrading to Login Enterprise v6.6 from a version older than 6.3, all existing API tokens will become invalid and must be manually recreated. You can do this in the Login Enterprise UI. For steps, see Adding a System Access Token

  • The new UI and Public API Launcher upgrade feature in v6.6 is only compatible with Windows-based Launchers already running v6.6 or higher. Launchers on older versions must be updated manually one final time

  • For other upgrade limitations and detailed steps on upgrading the Appliance from v5 to v6, see Upgrading the Appliance from v5 to v6

Features

Changes/Improvements

  • Improve Script Recorder logs by breaking complex XPath searches into smaller parts to better diagnose scenarios when elements are stuck

  • Unify and improve how Script Recorder starts applications so that application startup is more reliable and easier to track in recordings and results

  • Optimize the FindElementByInformation method in WinApp Recorder, making the element search and script execution faster

  • Remove the automatic start and stop commands from scripts generated by Run and Record, preventing you from accidentally pasting duplicate start/stop commands into existing scripts

  • Allow access to Action settings while a WinApp recording is paused, allowing you to inspect and test recorded steps during an ongoing recording

  • Add an option to keep applications open when stopping a WinApp recording, enabling you to stop recording without forcing the application to close and continue recording later from the same state

  • Change the name of typing actions in WinApp Recorder so the action title shows that text was typed without exposing the actual input in the results or comments

  • Make Web Recorder logging more consistent by logging every step in Playwright‑based scripts, in line with other script types

  • Functions for holding and releasing keys, e.g., holding Ctrl while clicking to open links in a new tab, are not supported in the Playwright scriptbase, so that these interactions can be reliably scripted

  • Allow Web Recorder to record and replay websites that use automation detection or blocking, allowing you to create scripts for more modern, security‑hardened web applications

  • Add key down and key up functions for Playwright‑based scripts, allowing you to script interactions that require holding keys, such as opening links in a new tab while holding Ctrl

  • Reduce the size of Script Editor and Engine components by trimming redundant Playwright binaries, significantly decreasing disk usage for these tools

  • Filter Load Test events in the Results page by multiple criteria, such as Description, Event title, Type, Account, Launcher, Application, and Target host, and configure which columns are shown

  • Filter Application Test events in the Results page using the same rich filter options that are available for Load Tests, including column configuration and test run selection in compare mode

  • Improve the All Events table performance with lazy loading. The table loads an initial set of rows and retrieves additional rows while scrolling, keeping the page responsive even with large numbers of events

  • Show the test run number and status alongside events in All Events and related views, making it easier to distinguish events from different runs of the same test

  • Choose the baseline test directly in the “Generate PDF” pop-up for Load and Application Tests, without having to go to the Compare page first to change the baseline

  • Change the scroll behavior in the Application Test Results page so horizontal scroll is contained within the results table instead of spanning the entire page, making controls on the right side easier to access

  • Chart tooltips are now slightly transparent, so they no longer block the chart lines/results when multiple items are shown

  • Exclude successful applications from the Application Test Results view and from generated PDF reports for both single and compare views

  • View the applications included in an application group directly from the Test Configuration page, without navigating away to see what the group contains

  • Improve the text and tooltip for the “Include successful applications” setting in Application Test Configuration, so it clearly explains that it controls screenshots while still including successful measurements in reports

  • Make the Export data option more visible in the old Continuous Test Results page by adding a dedicated Export data button next to the time span selector that always exports raw data for the selected period to CSV

  • Make the choice between creating single accounts and bulk accounts more visible by moving this option to the top of the Create Accounts page

Bug Fixes

  • Web Recorder captures Alt+H both as typed text and as a mouse hover, instead of treating it consistently as a hover action

  • Opening Application properties in Script Editor shows an empty dialog instead of pre‑filling it with the current properties.

  • Scripts that use Interop.UIAutomationClient do not compile correctly in Script Editor and reports missing namespace errors

  • Pasting text in Script Editor can cause the editor to reformat the entire script and move the cursor to the end of the file, disrupting the current editing position

  • When creating a provider with an existing name, the error message is generic and does not clearly indicate that the name is already in use

  • Sorting by Connector on the Test Configuration page does not work reliably, and results are inconsistently sorted when switching between ascending and descending order

  • Clicking Save multiple times while saving a Test configuration is in progress can result in a “400 Bad Request” error and an incorrectly saved configuration

  • Saving a Test configuration after a temporary network disconnect and reconnect may leave the UI in a state where a second save attempt without changes results in an error

  • Pressing Enter in the Name field of a Continuous Test automatically selects all schedule timeslots when using a daily or weekly schedule

  • Continuous Tests cannot reliably export multiple raw data sets via the Public API for the same Test over different time ranges without returning errors

  • The Continuous Test notifications dialog shows an empty email placeholder by default when entering recipient addresses manually, which can be confusing and misleading

  • The confirmation dialog for starting a Load Test does not correctly display large numbers, e.g., 4‑digit account counts, causing spacing and layout issues

  • Load Test compare charts do not always show the applications from the selected baseline test, and after changing the baseline, charts sometimes appear only for non‑baseline tests

  • The Events Type filter uses a dropdown without an inner scroll, causing long lists of event types to break the layout and overflow outside the dropdown in the UI

  • The EUX score column in Load Test Results does not consistently show warning icons when EUX is in a warning state, and the behavior is inconsistent with VSImax and the PDF report

  • If custom EUX folder paths were previously configured via the API, editing and saving the Test Configuration through the UI will reset these settings to the default

  • Old daily UserSessionMetrics partitions in the Postgres session metrics database are not cleaned up correctly, allowing partitions outside the retention window to continue to accumulate

  • Enabling or disabling accounts on the Accounts page scrolls the page back to the top, making it difficult to keep focus on the row where the change was made

  • Entering only spaces in the Username and Domain fields on the Create Account page is not treated as empty input, so front‑end validation does not correctly show that both fields are required

  • Account Group filters that use email addresses, e.g., *@gmail.com do not correctly filter the number of accounts and behave inconsistently with the preview

  • Attempting to upgrade an Appliance to a lower version does not clearly block or warn against the downgrade, increasing the risk of accidental downgrades and instability

  • Toggling the Selenium Drivers auto‑update sends an incorrect payload and may result in an unsupported media type error

  • Some user sessions fail intermittently with the error “The Launcher did not respond to a session request in a timely fashion,” and Launchers can become unresponsive when processing new user sessions

  • When a Windows 365 test is present in the environment, the “Create raw data export” dialog for Continuous Tests fails to load the list of available tests and remains stuck in a loading state

  • When attempting to update the Edge Web automation driver from the UI, the Update action does not complete successfully

  • Continuous test application execution failures occurring right at the start of a cycle (before any measurements are taken) are not counted in the App failures column in the Test Summary and Dashboard