Release Notes 1.5.0.1
Metadata
This release documentation version 1.0.
| Release | 1.5.0.1 |
|---|---|
| Release date | 2026-02-12 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.5.0.1+v1.5.0.1-c6484d4 |
| Log Server version | 1.5.0.1+v1.5.0.1-b9b48b4 |
| HostScreen Server version | 1.5.0.1+v1.5.0.1-de236152 |
| Web Terminal Hub version | 1.5.0.1+v1.5.0.1-ce17a4a |
| Web Terminal Client version | 1.5.0.1+v1.5.0.1-6e326f1 |
| Management Console | 1.5.0.1+v1.5.0.1-5406d83 |
| Log Viewer | 1.5.0.1+v1.5.0.1-f7e3b76 |
.NET Platform
| .NET Release | 8.0.24 |
|---|---|
| .NET Runtime | 8.0.24 |
| ASP.NET Core Runtime | 8.0.24 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| 139.b2ce7f0fdd0a95e0d041.js | 348.346fc49ec8486632cb8a.js |
| 175.bf278fa03ed199f33bfe.js | 352.6091dcdcc9cb22bcb4bb.js |
| 193.802bdfe141978c7ef570.js | 637.9018b0b2e4ed3cb78e63.js |
| 195.de7e9c1342aee967caac.js | 763.2863d87215bf444f10da.js |
| 264.72bbfb8aadd859e7772a.js | loader.d95c5a09841350654ce9.js |
| 312.5f79004d343b87edf0a1.js | main.e01746e761d96f2a3dcf.js |
Upgrade Recommendations
This update is recommended for organisations who use the 5250 protocol and require to pass device name/id to the host or use single character auto-enter fields.
Security Notes
This release does is not required to fix any known security issues.
.NET Security
.NET 8.0.24 is used this release of Jubilant that includes security updates. Maximum severity: High. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
None
High Importance Fix Notes
None
In this Release
Preview
The preview version of Automations (macros) first available in 1.3.1.3 continues to be improved, new in this release is the ability to import/export date to/from Excel. If you are interested in working with the preview, please contact support@flynet.email for more information.
New
A connection wizard has been added to the management console. This wizard will attempt to guide users through the process of creating a host connection. The wizard can attempt to automatically determine some properties of a connection including encryption, host protocol and terminal type.
Fixed
| ID | Protocols | Description |
|---|---|---|
| WTC.489 | ALL | Add a timestamp to client log messages |
| WTC.490 | ALL | Reinstate the refresh button |
| WTC.493 | ALL | Autoconnect query string does not recognize + as a space |
| WTC.498 | ALL | Browser print is horizontally compressed in portrait mode when stretch-to-fit is off |
| WTC.499 | ALL | Associated printer screen erroneously shows 'Awaiting Screen' |
| WTC.500 | ALL | Some virtual keyboard layouts are missing caps keyboards |
| WTC.501 | ALL | Settings with missing properties sometimes are not 'fixed' properly on import |
| WTC.504 | ALL | When custom logo is active Jubilant logo is sometimes displayed incorrectly |
| MCC.40 | ALL | Fix incorrect button state |
| WTA.94 | ALL | Make the mismatched screen error message configurable |
Known Issues
| ID | Protocols | Description |
|---|---|---|
| WTC.429 | ALL | On-screen keyboard on small screen devices |
| WTC.492 | ALL | Screen size calculations are slightly off |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 8.0.24 | All | See .Net Security Notes. |
Change Notes
WTC.489 Add a timestamp to client log messages
Client log messages now include a client timestamp to aid in issue diagnosis.
WTC.490 Reinstate the refresh button
The refresh button has been reinstated onto the tool bar to help to mitigate issues for customers with slow networks who are unable to use web sockets. The button is not visible by default. To enable the button edit config.json (in C:\Program Files\flynet\Jubilant\WebTerminal\web\settings by default) and add or edit the following setting:
"showMenuBarRefreshButton": true
If you are adding the setting, then do not forget that each line except the last must end in a comma.
Save the change and refresh the browser to pick up the change, the refresh button should now be available on the toolbar.
We recommend that you make a backup of config.json before making any changes.
WTC.493 Autoconnect query string does not recognize + as a space
A + symbol in an autoconnect URL was not being correctly interpreted as a space, this has been resolved in this release.
WTC.498 Browser print is horizontally compressed in portrait mode when stretch-to-fit is off
There was an issue where portrait browser prints were compressed horizontally if stretch-to-fit was off, this has been fixed in this release.
WTC.499 Associated printer screen erroneously shows 'Awaiting Screen'
The tab for an associated printer sometimes showed the 'Awaiting Screen' message in error, this has been resolved in this release.
WTC.500 Some virtual keyboard layouts are missing caps keyboards
Some virtual keyboard layouts were missing caps layouts, causing an error when the caps layout was accessed. This has been fixed in this release.
WTC.501 Settings with missing properties sometimes are not 'fixed' properly on import
Under certain circumstances client settings without saved values were not properly handled when the settings were loaded, this has been resolved in this release.
WTC.504 When custom logo is active Jubilant logo is sometimes displayed incorrectly
On certain mobile platforms the Jubilant logo was displayed incorrectly when a custom logo was in use. This has been resolved in this release.
MCC.40 Fix incorrect button state
Under certain conditions, buttons in the management console could fail to reflect the true state of the underlying data. This has been resolved in this release.
WTA.94 Make the mismatched screen error message configurable
It is now possible to turn off the warning message shown when a send action is sent to the hub for an out-of-date screen.
It is also possible to allow the sending of the AID key if there are no field changes.
Messaging
By default, the message will be shown. To disable the message:
- Open the management console
- Click on Global Settings in the Web Terminal section
- WITHOUT making any changes, click the Save button, this will save the latest version of the file which includes the new settings
- Open WebTerminalSettings.json in C:\ProgramData\Flynet\Jubilant\WebTerminal\web\hub in a suitable editor (e.g. VS Code).
- At the bottom of the file there is a new section titled SendAction, in that section set the value of SuppressClientMessage to true.
- Save the file.
- Run iisreset from an administrator command prompt. Note that this will disconnect any users currently connected via the Jubilant server.
If you have multiple Jubilant servers, you will need make this change on all servers.
We recommend that you make a backup of WebTerminalSettings.json before you make any changes.
Allow SendAction with Screen Mismatch if No Field Changes
The new SendAction section also contains a setting which allows send actions which do not alter any fields to be allowed through despite a screen mismatch. This setting is enabled by default. To disable this feature, set AllowMismatchedSendActionWithZeroFields to false.
Settings Example and Defaults
C:\ProgramData\Flynet\Jubilant\WebTerminal\web\hub\WebTerminalSettings.json.
"SendAction": {
"AllowMismatchedSendActionWithZeroFields": true,
"SuppressClientMessage": false
}
WTC.429 On-screen keyboard on small screen devices
On small screen devices the on-screen keyboard can be difficult to use. The work around is to define a new keyboard layout and select it via the settings.
WTC.492 Screen size calculations are slightly off
Under certain, rare, circumstances an issue with screen size calculations can cause the top line of the screen to be partly or wholly obscured. This usually occurs when the host changes the screen resolution. The work around is either to turn on stretch to fit in the settings menu or to resize the browser window, changing its width until the top line is visible.
Installation
Fresh Install
Please see the Jubilant Admin Manual for Fresh Install Instructions.
Upgrade
Note
Please note the specials steps below if upgrading from a 1.0.x build to a 1.1.x or later build.
If upgrading from Jubilant 1.0.x to 1.1.x extra steps must be carried out before and after the install steps below.
Upgrade is carried out using Jubilant scripts.
- Unzip the installer into a folder.
- Close any web browsers.
- Close any Services windows.
- Open PowerShell ISE as Administrator.
- In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
- Run the required script by pressing the green play / run script button on the toolbar.
- The upgrade of Jubilant is complete.
If this is an upgrade from Jubilant 1.0.x to 1.1.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.