Skip to content

6.14.1

14 Sep 2026


Failures to open a solution are now logged

Section titled “Failures to open a solution are now logged”

When a solution could not be opened, the underlying error was discarded, leaving nothing behind to explain why. The exception is now written to the log so the cause of a failed solution load can be identified.


Fewer warnings in log files during package resolution

Section titled “Fewer warnings in log files during package resolution”

Resolving packages produced spurious warnings in the log files. Local package folders are now resolved directly and the temporary folder is no longer used, which removes these warnings.


Fixed false validation errors caused by failed value conversion

Section titled “Fixed false validation errors caused by failed value conversion”

Values that could not be converted to their target type were reported as validation errors even when they were valid. One known manifestation of the bug was where setting a binary-typed property of Cryptography function to a valid Base-64 string would show a validation error such as Cannot convert [Key] value [ABEi...] to type [Twenty57.Linx.Plugins.Cryptography.Shared.Common.Binary]


Some plugin updates failed due to broken type resolution

Section titled “Some plugin updates failed due to broken type resolution”

Plugin type resolvers failed on type names that omitted the assembly version number in the case of generic types. This caused some plugin updates to fail. Generic plugin types now resolve correctly.


Fixed the Solution Updates window not scrolling with the mouse wheel

Section titled “Fixed the Solution Updates window not scrolling with the mouse wheel”

The Solution Updates window ignored the mouse wheel, leaving the scrollbar as the only way to move through a long list of updates. The window now scrolls with the mouse wheel.


Fixed the Deploy window listing outdated deployment servers

Section titled “Fixed the Deploy window listing outdated deployment servers”

The Deploy window used the deployment servers read when the Designer started, so any server added or changed afterwards only appeared after a restart. The deployment server configuration is now reloaded each time the Deploy window is opened.


Linx Server: Fixed success metrics not shown

Section titled “Linx Server: Fixed success metrics not shown”

Clicking the green section of a metrics bar representing both success and error outcomes of a process or event did not show the successes. The success metrics are now shown when the green (success) section of a bar is clicked.


Linx Server: Fixed process errors being displayed without line breaks

Section titled “Linx Server: Fixed process errors being displayed without line breaks”

Multi-line error messages from a process were shown as a single line of text, making them difficult to read. Line breaks in process error messages are now preserved.