Table of Contents

Release Notes 1.3.2.3

Metadata

This release documentation version 1.0.

Release 1.3.2.3
Release date 2025-07-03
Release type Full release
Future Main branch release
Server version 1.3.2.3+v1.3.2.3-3de119e
Log Server version 1.3.2.3+v1.3.2.3-390c603
HostScreen Server version 1.3.2.3+v1.3.2.3-0b7d2fe0
Web Terminal Hub version 1.3.2.3+v1.3.2.3-a14fcf7
Web Terminal Client version 1.3.2.3+v1.3.2.3-80a96649
Management Console 1.3.2.3+v1.3.2.3-352abea
Log Viewer 1.3.2.3+v1.3.2.3-770ed32

.NET Platform

.NET Release 8.0.17
.NET Runtime 8.0.17
ASP.NET Core Runtime 8.0.17
Notable changes Link

Web Terminal Client Renderer File Names (checksum)

Location: Program Files\Flynet\Jubilant\WebTerminal\web
139.5a82c733beb6f79cdd57.js 352.fa952e83559d5e15215b.js
175.69c2a23145b45ea8e802.js 612.34b1303a8324ce622e14.js
193.404910a1cbc7962b8665.js 637.9604552952207d7cbe9b.js
195.f0190d2d30eeb2ce52ab.js loader.d95c5a09841350654ce9.js
312.3cf31581d5b39e50d08b.js main.26fc52333cf645bcc181.js
348.08572cbbb1d757612e2a.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.17 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

Preview

The preview version of Automations (macros) first available in 1.3.1.3 continues to be improved. If you are interested in working with the preview, please contact support@flynet.email for more information.

New

ID Protocols Description
WTC.308 All Add pinch to zoom
WTC.420 All Add a toggle for more specific numpad functionality
WTC.425 All Add on-screen, clickable hot-spots

Fixed

ID Protocols Description
WTC.417 ALL Fixed key mappings on num pad keys not working as intended
WTC.418 5250 Fixed issues with 'pop-up' screens
WTC.422 5250 Fixed the input type digits only is missing
WTC.423 ALL Fixed issues with key press routines cause automation tools to fail
WTC.424 5250 Fixed issues with right adjust blank/zero fill
SB.43 5250 Fixed issue where start of field attributes could be overwritten

Known Issues

ID Protocols Description
WTC.429 ALL On-screen keyboard on small screen devices
WTC.437 ALL Re-mapping numeric keys
WTC.438 ALL Deleting a double-width character via delete or backspace
WTC.439 ALL Toolbar visibility on first load
WTC.440 ALL Virtual keyboard key highlighting

Security

ID Protocols Description
.Net 8.0.17 All See .Net Security Notes.

Change Notes

WTC.308 - Add pinch to zoom

The Jubilant client now supports pinch to zoom on touch devices.

Two-Finger Pinch to Zoom: Pinch in or out with two fingers on touch devices to smoothly toggle zoom (can be turned on or off).

Two-Finger Swipe to Pan: When zoomed in, swipe with two fingers to navigate around the screen.

Follow-Cursor Option: Enable or disable “Follow Cursor” mode so the view re-centers on your touch point as you zoom.

Both zooming and follow-cursor behaviors are controlled via settings in the client configuration.

WTC.420 - Add a toggle for more specific numpad functionality

A new toggle 'Ignore numeric lock' has been added to the keyboard mapper. If this toggle is on the the user may choose between two modes: 'Always Functions' and 'Always Numeric'. In 'Always Functions' mode, the numeric keys on the numpad (0-9) will always send their function (Page Up etc) irrespective of the numlock state. In 'Always Numeric' mode, the numeric keys on the numpad (0-9) will always send their number irrespective of the numlock state.

WTC.425 - Add on-screen, clickable hot-spots

The Jubilant client now supports user definable, clickable hot-spots for the PF keys. Text such as 'F12=Next' can be detected and made clickable in the client. Clicking on such a hot-spot results in the relevant PF key being sent to the host.

Hot-spot Web Terminal Settings

Default hot-spot settings for users can be found in settings.json file, typically found in C:\Program Files\Flynet\Jubilant\WebTerminal\web\settings.

These are also the defaults if the settings are not present in the file.

{
  "AidKeyHotspotsEnabled": true,
  "ActionHotspotRegex": "\\b({{labels}})\\bs*(=|:|-)(?![=:|-])",
  "ActionHotSpotColor": "black",
  "ActionHotSpotBGColor": "#ECE9D8",
  "ActionHotSpotRowStart": 20
}
AidKeyHotspotsEnabled

This must be set as true or false. True turns on hot-spot functionality, false turns it off.

ActionHotspotRegex

This regular expression is used to detect the text on the screen that must trigger an action. See the hotspots.json file to see how to map on-screen text to a host action key.

{{labels}} is a special substitution token for the labels found in the hotspots.json file.

ActionHotSpotColor

An HTML style valid colour value for hotspot text.

ActionHotSpotBGColor

An HTML style valid colour value for hotspot background.

ActionHotSpotRowStart

The row from which must be scanned onwards from for hotspot text.

hotspots.json

The settings for controlling what text is detected on the screen and what action must be sent to the host when triggered can be found in the hotspots.json file, typically found in C:\Program Files\Flynet\Jubilant\WebTerminal\web\settings.

Extract from an example file:

[
  {
    "Label": "PF1",
    "Action": "PF1"
  },
  {
    "Label": "PF2",
    "Action": "PF2"
  },
  {
    "Label": "F1",
    "Action": "PF1"
  },
  {
    "Label": "CLEAR",
    "Action": "CLEAR"
  }
]
Label

The label is the text to search for on the screen, using the configured regular expression.

Action

The action that must be sent when clicking on the found label.

WTC.417 - Fixed key mappings on num pad keys not working as intended

There was an issue where some numpad keys could not be re-mapped as intended. This has been fixed in this release.

WTC.418 - Fixed issues with 'pop-up' screens

5250 An issue where the fields 'behind' a 'pop-up' screen were still active has been resolved in this version.

WTC.422 - Fixed the input type digits only is missing

5250 The input type digits only was missing. This has been fixed in this version.

WTC.423 - Fixed issues with key press routines cause automation tools to fail

Issues with the client key press routines could cause external automation tools to fail. These issues have been fixed in this version.

WTC.424 - Fixed issues with right adjust blank/zero fill

5250 There were several issues with the functionality of right adjust blank/zero fill such that the field exit keys did not trigger it. These have been resolved in this release. Note: in common with most other emulators tabbing out of a field WILL NOT trigger the field exit behaviour.

SB.43 Fixed issue where start of field attributes could be overwritten

5250 Under certain conditions the attributes at the start of a field could be overwritten. This has been fixed in this version.

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.437 Re-mapping numeric keys

Re-mapping the numeric keys (only) does not take immediate effect. The work around is to refresh the browser.

WTC.438 Deleting a double-width character via delete or backspace

Deleting a double-width character via delete or backspace can cause the field to break.

WTC.439 Toolbar visibility on first load

On the first load of a host into a new tab, the toolbar may not appear. The work around is to refresh the browser.

WTC.440 Virtual keyboard key highlighting

The virtual keyboard does not show any highlighting to indicate that a key has been pressed.

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.

  1. Unzip the installer into a folder.
  2. Close any web browsers.
  3. Close any Services windows.
  4. Open PowerShell ISE as Administrator.
  5. In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
  6. Run the required script by pressing the green play / run script button on the toolbar.
  7. 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.