Verj.io V5.11.1 released

[Steve]

Verj.io V5.11.1 is now available and can be downloaded using the links below.

Downloads:
Verj.io Studio Links:
Windows 64 bit: https://downloads.verj.io/verjio/v5.11. ... _win64.exe
Linux 64 bit: https://downloads.verj.io/verjio/v5.11. ... x64.tar.gz
Mac: https://downloads.verj.io/verjio/v5.11. ... _1_mac.dmg

On-premise Server Links
Windows 64 bit: https://downloads.verj.io/verjio/v5.11. ... _win64.exe
Linux 64 bit: https://downloads.verj.io/verjio/v5.11. ... x64.tar.gz


Changes introduced in Version 5.11.1:

This is a re-release to resolve the problem that the debugger does not start when the debug icon is clicked.

Bug Fix:

1. FPL Highlight command causes a JavaScript CORS access error that crashes the form when using external Style Sheets.
   
   
2. The debugger does not start in the studio when the blue debug icon is clicked.

Changes introduced in Version 5.11.0:

1. Gateway Tunnels. Configured in the Verj.io Gateway, Gateway Tunnels allow remote Verj.io Applications running on trusted Verj.io On-Premises environments and Verj.io Service Plans access to databases and services that would otherwise be inaccessible outside of the Gateway’s private network.
   
   Gateway Tunnels work with any TCP/IP application or service that can be accessed by specifying a hostname and port number, including: Databases, Email, LDAP, HTTP(s), REST, SOAP and FTP services.
   
   For example, this makes it possible to securely access an on-premise database running within your private network from a Verj.io instance running within the Verj.io cloud. This makes it much easier to migrate an on-premise Verj.io instance to the cloud.
   
   
2. Upgrade to tomcat 9.0.63 that fixes:
   
   CVE-2022-29885 – Tomcat documentation fix for the EncryptInterceptor that incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was incorrect and has been resolved in this release.
   
   

Release notes and installation instructions:
See the V5.11.1 Readme