Release Notes 1.2.1.8
Metadata
This release documentation version 1.0.
Release | 1.2.1.8 |
---|---|
Release date | 2025-03-25 |
Release type | Full release |
Future | Main branch release |
Server version | 1.2.1.8+1.2.1.8-f0947f4 |
Log Server version | 1.2.1.8+1.2.1.8-8557559 |
HostScreen Server version | 1.2.1.8+1.2.1.8-bc11972b |
Web Terminal Hub version | 1.2.1.8+1.2.1.8-1ceb525 |
Web Terminal Client version | 1.2.1.8+1.2.1.8-5491c946 |
Management Console | 1.2.1.8+1.2.1.8-3815c7a |
Log Viewer | 1.2.1.8+1.2.1.8-f342794 |
.NET Platform
.NET Release | 8.0.14 |
---|---|
.NET Runtime | 8.0.14 |
ASP.NET Core Runtime | 8.0.14 |
Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
renderer.0aea6416792cc18c74b2.js | renderer.c229a19ae565fcc45446.js |
renderer.1f5b74f81d987a0397d1.js | renderer.cb7ab0a72ff46265163d.js |
renderer.883e6c89ee53e0c4838a.js | renderer.dce5f1ad2f954a7153a2.js |
renderer.b3ef7ae0337f4237ba22.js | renderer.ebd7091c0e4dc64ac6d5.js |
renderer.bd046df9c944c8139f74.js |
Upgrade Recommendations
This release does is not required to fix any known security issues.
This update is recommended for most users because of a Jubilant feature fix.
Security Notes
This release does is not required to fix any known security issues.
.NET Security
.NET 8.0.14 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
This upgrade is recommended for all users due to fixes to both 3270 and 5250 protocols.
In this Release
New
ID | Protocols | Description |
---|---|---|
WTC.364 | All | Configurable timeouts for hub disconnection and reconnection messages |
WTC.368 | All | Screen keep awake |
WTC.378 | All | Option to automatically show virtual keyboard on connection to a host |
WTC.380 | 5250 | Signed numeric support |
WTC.391 | All | Cursor positioning in entry fields after touch on touch devices |
Fixed
ID | Protocols | Description |
---|---|---|
HSS.69 | 5250 | Fixed Roll keys do not send data |
HSS.77 | All | Fixed Telnet messages can cause excessive CPU usage |
HSS.89 | 5250 | Fixed WriteErrorCode not handled correctly |
MCC.38 | All | Fixed incorrect keep alive timeout labels |
MCC.39 | All | Fixed keep alive timeout values are not saved |
WTC.354 | All | Fixed incorrect CSS applied when printing on an iPad |
WTC.355 | All | Fixed incorrect functioning of type-ahead keyboard buffer |
WTC.356 | 3270 | Fixed incorrect substitution of nulls by spaces |
WTC.369 | All | Fixed pasting text back into multi-line input |
WTC.373 | All | Fixed IME when nothing is entered |
WTC.376 | All | Fixed messages partially or entirely off screen on an iPad |
WTC.393 | All | Fixed copy and paste of first row of entire screen |
WTC.399 | All | Fixed reset of colour settings |
Security
ID | Protocols | Description |
---|---|---|
.Net 8.0.14 | All | See .Net Security Notes. |
Change Notes
WTC.364 - Configurable timeouts for hub disconnection and reconnection messages
A new feature allows for configuration of the wait times between the various messages that the client displays during disconnection and reconnection.
This feature can be enabled in the settings json file found by default at .../Flynet/Jubilant/WebTerminal/web/settings/settings.json.
The setting MessageAutoReconnectHubInSeconds can be set to a number in seconds. This setting specifies the time in seconds between when the client disconnects from the hub, and when the client shows the user a 'Lost Hub Connection' warning message.
The setting MessageLockedAutoReconnectHubInSeconds can be set to a number in seconds. This setting specifies the time in seconds between when client disconnects from the hub while the keyboard is locked (eg. after an action has been sent to the hub and the client is waiting for a response back), and when the client shows the user a 'Lost Hub Connection' warning message.
The setting MessageHiddenTimeInSeconds can be set to a number in seconds. This setting specifies the time in seconds between when client disconnects from the hub while the client is hidden (eg. the user has tabbed away from the client to another browser tab, or switched to another app on a mobile device), and when the client shows the user a 'Lost Hub Connection' warning message. This time includes any time the client was hidden for, if the client was hidden for longer than the time in seconds specified by this setting, the 'Lost Hub Connection' will be shown immediately, unless the MessageHiddenVisibleDelayInSeconds setting has been set.
The setting MessageHiddenVisibleDelayInSeconds can be set to a number in seconds. This setting specifies the time in seconds between when a client that is hidden and disconnected from the hub becomes visible again, and when the client shows the user a 'Lost Hub Connection' warning message.
The setting MessageUserReconnectHubInSeconds can be set to a number in seconds. This setting specifies the time in seconds between when a 'Lost Hub Connection' message is shown to a user, and when a 'Disconnected From Hub' message is shown to the user. Automatic connection attempts will be continued by the client until the 'Disconnected From Hub' message is shown to the user.
WTC.368 - Screen keep awake
A new feature allows a configurable option to allow screen keep awake when viewing a connected terminal session.
The screen keep awake feature prevents screens from going to sleep on both mobile devices and desktop devices.
This feature can be enabled in the settings json file found by default at .../Flynet/Jubilant/WebTerminal/web/settings/settings.json.
The setting ScreenKeepAwakeEnable can be set to 'Off', 'MobileDevices' or 'All'. When 'Off', the screen keep awake feature will be disabled. When 'MobileDevices', the screen keep awake feature will be enabled on mobile devices only, and be disabled on non-mobile devices. When 'All', the screen keep awake feature will be enabled on all devices.
The setting ScreenKeepAwakeDefault can be set to either True or False. This setting specifies what the default screen keep awake setting will be when a user has not altered the setting themselves.
The setting ScreenKeepAwakeUserToggle can be set to either True or False. This setting specifies if users are allowed to change the screen keep awake setting from the default.
If ScreenKeepAwakeEnable is enabled on the device the user is using, a new setting (Keep Screen Awake) will be available in the General Settings menu, opened via the cog icon on the Jubilant menu bar. If ScreenKeepAwakeUserToggle is set to False, this setting will be disabled. Otherwise, the user is able to use this setting to change their Screen Keep Awake preference.
WTC.378 - Option to automatically show virtual keyboard on connection to a host
A new option is available on mobile devices to allow the user to choose to have the virtual keyboard automatically shown on connection to a host.
This feature can be enabled in the settings on mobile devices via the Auto Show Virtual Keyboard setting.
WTC.380 - Signed numeric support
5250 The client now supports signed numeric fields along with FieldExit, FieldExitPositive and FieldExitMinus mappable keys.
WTC.391 - Cursor positioning in entry fields after touch on touch devices
A new feature adds a configurable option that allows control of what happens on touch devices when an entry field is tapped.
This feature can be enabled in the settings via the Touch Cursor at Text End setting.
When enabled the following rules apply on touch devices to a touch on an entry field:
If the cursor is already in the entry field then the cursor is placed where the touch occurred.
Otherwise, if the field is blank then the cursor is placed at the start of the field.
Otherwise, if the touch is at the end of the field and the last character is not blank then the cursor is placed at the end of the field.
Otherwise the cursor is placed immediately after the last non-blank character in the field
HSS.69 - Fixed Roll keys do not send data
5250 The Roll keys (RollUp, RollDown, RollLeft, RollRight) did not send modified field data to the host. This has been fixed in this version.
HSS.77 - Fixed Telnet messages can cause excessive CPU usage
Telnet messages sent by the host could cause the HSS to use excessive CPU. This has been fixed in this version.
HSS.89 - Fixed WriteErrorCode not handled correctly
5250 The command WriteErrorCode was not handled correctly causing incorrect characters to be displayed. This has been fixed in this version.
MCC.38 - Fixed incorrect keep alive timeout labels
The labels for the TCP and Telnet keep alive timeout indicated that the timeout was in minutes not seconds. This has been fixed in this version.
MCC.39 - Fixed keep alive timeout values are not saved
The values for the TCP and Telnet keep alives were not saved correctly. This has been fixed in this version.
WTC.354 - Fixed incorrect CSS applied when printing on an iPad
When printing on an iPad, incorrect CSS was applied. This has been fixed in this version.
WTC.355 - Fixed incorrect functioning of type-ahead keyboard buffer
Under some circumstances the keyboard buffer would fail to allow users to type-ahead. This has been fixed in this version.
WTC.356 - Fixed incorrect substitution of nulls by spaces
3270 In some situations the client would incorrectly substitute spaces for nulls. This has been fixed in this version.
WTC.369 - Fixed pasting text back into multi-line input
Under some rare conditions pasting previously copied text into a multi-line input would fail. This has been fixed in this version.
WTC.373 - Fixed IME when nothing is entered
If Enter was pressed to exit an empty IME then the UI could end up containing incorrect text. This has been fixed in this version.
WTC.376 - Fixed messages partially or entirely off screen on an iPad
For some settings of MessagePosition messages would be partially or entirely off the screen on an iPad. This has been fixed in this version.
WTC.393 - Fixed copy and paste of first row of entire screen
Under some conditions copying and pasting an entire page would result in the first row pasting incorrectly. This has been fixed in this version.
WTC.399 - Fixed reset of colour settings
Selecting Reset Colour Settings on the Settings panel did not reset the colour settings. This has been fixed in this version.
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.