Prerequisites now includes RabbitMQ 3.10.8 and 3.11.18 for Service Framework.

We've upgraded Service Framework's queuing system, RabbitMQ, to give us access to enhanced features and support.

Note: If you're running Service Framework with a central and child installations, after upgrading the central installation, you'll need to restart the Vista Service at all child installations to keep the synchronisation running.

Minor fixes and stability improvements.

RabbitMQ, the queuing system used by Service Framework, can now be upgraded in Central-Child mode without the child server having to be restarted afterwards.

Now when upgrading Service Framework, any deprecated Alert Manager, Configuration Distributor, Configuration Handlers and Content Delivery queue processor configurations are removed to improve performance.

Loyalty Manager now loads when an Organisation Code is entered in Service Framework Manager.

We've fixed an issue which prevented the Service Framework installer from completing successfully when upgrading a machine running instances of a service.

We've improved Service Framework logging (Vista.Service.ApiRouter.log) so that it now shows a logging level of WARN for 400 error codes and includes an external/remote IP address, for the client making the request.

If a new SSL certificate is configured (in the file Service.Configuration.Instance.json) for IPv6 for a Service Framework website, Service Framework now correctly uses it.

We've improved the way installers handle locked files. When the option Keep trying to update locked files is selected, the installer will now always retry locked files, including DBVERSION.ini.

Text now appears correctly in your configured language in the Group Sales Manager user interface.

When a URI path can't be found, the alert message no longer discloses internal server information.

When a URI path can't be found, we now make sure the log file contains the entire URI that was requested.

We've removed a low-risk security vulnerability associated with .NET 5 and .NET Core text encoding in our Service Framework package.

We've fixed an issue which could cause an error message when running the Setup Client Installer.

We've updated the Vista installer to allow you to choose how the installer behaves when attempting to overwrite a locked file. If you select the Keep trying to update locked files option, the installer will make multiple attempts to overwrite the file before reporting an error.

Note: This option is also available when using the installer in unattended mode.

Service Host now attempts to restart unhealthy services for a period of time before marking them Faulted.

The Service Framework installer no longer closes unexpectedly when installing to a machine with many active TCP connections on port 4443.

Caching issues no longer prevent users users who have signed out and cleared their browser cache from signing in again. Previously, this issue could occur when Service Framework was running on Windows Server 2019.

You can now successfully install Service Framework with RabbitMQ 3.11.

The following fields now appear correctly in Service Framework Manager's pages after installing:

• Service Provider
• Show errors on Screen
• Test Mode Cabinets
• Pre Load reporting Engine
• Logging Level
• Use Cinema Default Seat Allocation
• Log Activity

Active SSL certificates no longer appear as expired in Service Framework Manager.

Installation no longer fails at the INSTALLING Service Framework Services step when upgrading Vista applications using Service Framework Services.

The Service Framework web server now starts and the login page, dashboard, and other pages all appear as expected, even when a Service Framework component package was missing the Application.zip file.

Region-specific numeric formatting configuration no longer occasionally causes an error similar to "Failed to update Directory Service data.

Now when upgrading Service Framework, any deprecated Alert Manager, Configuration Distributor, Configuration Handlers and Content Delivery queue processor configurations are removed to improve performance.

Loyalty Manager now loads when an Organisation Code is entered in Service Framework Manager.

Service Framework no longer continues trying to establish a connection with a service that has been stopped.

When a URI path can't be found, the alert message no longer discloses internal server information.

The Service Framework landing page and web applications now load correctly without users needing to refresh the page.

Some active SSL certificates no longer incorrectly appear as expired in Service Framework Manager.

We've fixed an issue in the Service Framework landing page, where users would see a blank screen and need to refresh the page to load information.