Skip to main content
Skip table of contents

What's New in 6.4

  • When upgrading to Login Enterprise v6.4 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.

  • 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

  • Add custom text to your Load Test PDF reports

  • The names of the timers in Application scripts can now be set to up to 64 characters (instead of 32 characters)

  • The Continuous Test event table now shows the total number of events for your selected time frame and filters

  • The Applications table in the UI now includes an Application Type column to distinguish Windows Applications from Web Applications (Selenium and Playwright)

  • Search for the Test name in the pop-up when adding Tests to a Role

  • Search for the Test name in the pop-up when adding Test runs to a Role

  • Search for the Application Name in the pop-up when adding Applications to a Role

  • Search for the Application Group name in the pop-up when adding Application Groups to a Role

  • Search for User and Group names in the Access Control section of the UI

  • Search for the Role name in the Access Control section of the UI

  • NVIDIA nVector agent and the NVIDIA nVector Desktop Prepare workload are now included by default

  • All product documentation links now point to the new restructured documentation platform

Bug Fixes

  • When stopping a Continuous Test with a Custom Connector, the active sessions trigger an incorrect and unnecessary event, "The engine stopped responding after a session was created"

  • The API method to upload a script doesn't work from Swagger

  • Adding waits and pressing Enter removes the previous action. This applies to both the Test configuration and Application Group configuration pages

  • Saving an empty value in a Load Test run comment field displays "null" in the field

  • Tests with an RDP Connector cannot be copied when using an external database

  • Upgrading to Login Enterprise 6.3 sometimes fails in DatabaseBootstrapper with a database deadlock

  • Assigning the Built-in admin role to a user or group removes all permissions from the built-in admin account

  • The database migrator for Login Enterprise 6.3 is not compatible with SQL Server 2016

  • Public API token stops working after a month, with the error “The HTTP status code of the response was not expected (401)”

  • The search fields in the UI don't work for values containing “20”, “2”, or “0”

  • Events with titles over 128 characters created via the CreateEvent function or Public API are not saved to the database and are lost

  • Pausing the engine results in an unhandled exception in the Login Enterprise service, and the pause/resume engine event is not triggered

  • Screenshots of Application Test events are missing in the UI

  • The pop-up for edit SLA report > SLA Agreement > Threshold is out of view

  • When editing an Application, the Save button remains inactive after changing the browser profile path

  • The Test selection table in Continuous Test results > Export data > Select data for exporting contains incorrect text

  • If a user belongs to multiple LDAP groups, the system doesn’t apply their permissions, and the user has no assigned access.

  • Enabling email notifications for Application Tests without specifying a recipient email address causes the EventNotificationsWorker to crash

  • Recording elements in WinApps that contain slashes or brackets in the XPath can sometimes cause errors when the recorded script is played back

  • The default sort order on the Load Test and Application Test results pages is ascending, not descending

  • The default sort order for Load Test events is ascending, not descending

  • When the “Show password” option is disabled, the eye icon is initially hidden, but it reappears after an incorrect login attempt. This allows users to reveal the password even though the feature is configured to be disabled

  • You can’t add a new LDAP user if the user has previously logged in as part of an LDAP group. An error message appears: “User name already exists”

  • In the Application Test Action pop-up, if many actions are present, they overlap the Close button and cannot be scrolled

  • Using the Change allowed URLs option in the appliance menu does not apply newly added or modified URLs

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.