Release Notes 1.2.1.3
Metadata
This release documentation version 1.0.
| Release | 1.2.1.3 |
|---|---|
| Release date | 2024-11-07 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.2.1.3+1.2.1.3-b9ca1f9 |
| Log Server version | 1.2.1.3+1.2.1.3-9fd2c26 |
| HostScreen Server version | 1.2.1.3+1.2.1.3-b51bd070 |
| Web Terminal Hub version | 1.2.1.3+1.2.1.3-9a78c4a |
| Web Terminal Client version | 1.2.1.3+1.2.1.3-bff5a04 |
| Management Console | 1.2.1.3+1.2.1.3-e0f7049 |
| Log Viewer | 1.2.1.3+1.2.1.3-cc7f417 |
.NET Platform
| .NET Release | 8.0.10 |
|---|---|
| .NET Runtime | 8.0.10 |
| ASP.NET Core Runtime | 8.0.10 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| renderer.45cbef36a9281764da79.js | renderer.191ab12d65cee0117db4.js |
| renderer.1493df2d2054c22ebfdf.js | renderer.ae24acce9733b5a5256d.js |
| renderer.b1da4a98aeaf17000e3e.js | renderer.b7b6e9b6608bdd597d1a.js |
| renderer.cb7ab0a72ff46265163d.js | renderer.e8d6bb3353755ffa43ef.js |
| renderer.f5d3fc6faae7cd81a067.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.10 is used this release of Jubilant that includes security updates. Maximum severity: Important. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
This release contains no known critical or high severity Node vulnerabilities.
A single moderate severity issue is not surfaced in Jubilant. This package will be updated in the next release.
A single low severity issue is not surfaced in Jubilant. This package will be updated in the next release.
High Importance Fix Notes
This upgrade is recommended for a fix to null handling in wrapped fields and a fix for invalid space characters.
It is also recommended for organizations where 3270 IND$FILE is used.
In this Release
New
| ID | Protocols | Description |
|---|---|---|
| WTC.347 | All | Automatic host connection and setting LU / Device ID using URL query string. |
Fix
| ID | Protocols | Description |
|---|---|---|
| WTC.317 | 3270 | Fixed handling of IND$FILE append and new flags. |
| WTC.329 | All | Fixed logging before logging client was ready. |
| WTC.350 | All | Fixed incorrect null handling in wrapped entry fields. |
| WTC.351 | All | Fixed incorrect insertion of unsupported space character. |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 8.0.10 | All | See .Net Security Notes. |
Change Notes
WTC.347 - Automatic host connection and setting LU / Device ID using URL query string
A new feature allows immediate connection to a host definition ID and optionally an LU Name / Device ID passed in on the URL query string.
For example: https://server/fjterm/?AutoConnectionName=MainframeProd&AutoConnectionNow=&AutoLuName=EXMPLU1
AutoConnectionName must be set to the Definition Name (found in the Host Definition in FJManage).
AutoConnectionNow must be set for the connection to connect automatically. It can simply be present (as in the example above), or set to yes or true.
The AutoLuName is optional. If it is present, the connection will use the given value to set the LU Name (3270) or Device ID (5250).
WTC.317 - Fixed handling of IND$FILE append and new flags
3270 IND$FILE Append and New file flags are correctly applied during an upload.
The user interface has been updated so that it correctly only allows the user to select only one of Append, Replace or New.
WTC.329 - Fixed logging before logging client was ready
When a host session was first connected, if client logging was in debug mode, the first log message would fail. This was because the session log had not yet been established. This has been fixed in this release. Any log message is held until the session log is available.
WTC.350 - Fixed incorrect null handling in wrapped entry fields
In some edge cases, using [BACKSPACE] or some of field clearing action, in a field that wraps the screen, could result in nulls being embedded between non-null characters. This is not a valid value. The host could misinterpret what value was being sent. This has been fixed in this version.
WTC.351 - Fixed incorrect insertion of unsupported space character
In some edge cases, using [BACKSPACE] or some of field clearing action, could result in HTML   characters being evaluated into a non-compatible white space character. The host could misinterpret what value was being sent. 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.