Release notes
Release date:
Release version: 3.0.9799.2336
Improvements and enhancements
Improved XSD validation support for Custom APIs
Internal ID: LINKOB-I-683
Problem
Custom APIs generated from XSD schemas did not fully support pattern-based field restrictions. This made it difficult to enforce specific input requirements and prevent invalid data from being submitted through custom API endpoints.
Solution
Link now supports conversion of XSD simple types containing pattern-based restrictions into corresponding .NET types.
This enhancement provides the foundation for applying schema-defined pattern validation to Custom API requests, helping ensure that incoming data meets the expected structural requirements.
Faster loading of the outgoing transport locations list
Internal ID: LINKOB-614
Problem
The list of outgoing transport locations could load slowly in installations with many partners associated with transport locations.
Solution
Loading of the list has been optimized to reduce waiting times.
Improved performance of document tracking under heavy load
Internal ID: LINKOB-602
Problem
Under heavy load, certain document tracking queries could consume excessive database CPU resources in specific scenarios.
This could affect query performance and potentially impact other operations running concurrently.
Solution
A new database index has been introduced to optimize the affected document tracking queries.
This reduces processing overhead and improves query performance, particularly in environments with large transaction volumes.
The additional index may slightly increase upgrade duration for environments with large tracking databases.
Simplified folder configuration for Integrated FTP
Internal ID: LINKOB-I-473
Problem
The previous Integrated FTP configuration supported multiple candidate directories for outgoing file delivery. However, this approach did not adequately support real-world scenarios where trading partners use different folders for different document types. It also introduced unnecessary configuration complexity.
Solution
The Integrated FTP Send component now uses a single Target folder field instead of the previous Candidate directories list.
This simplifies configuration and makes the destination folder explicit. Existing configurations are automatically converted to the new format during the upgrade.
The change is technically incompatible with configurations containing multiple candidate directories. However, an analysis of existing production configurations found no outgoing Integrated FTP locations using more than one candidate directory.
Bug fixes
-
Fixed unintended time zone conversion when processing date-time values using XSLT date conversion functions (#2350).
-
Fixed missing error log content in Tracking Additional Files for Scheduler Task Handlers (#2436).
-
Fixed missing creation and modification information in the Partner Contacts column chooser (#2487).
-
Fixed an issue where cancelled messages could cause the Inbox/Outbox API to return an empty result despite pending messages (#2526).
-
Previously reported slow loading and editing of partners with large identification lists is no longer reproducible (#2551).
-
Clarified handling of password settings referenced through configuration macros; the reported scenario requires an alternative configuration approach (#2740).
-
Fixed misleading distributed transaction errors when processing control messages referencing unknown documents or interchanges (#2756).
-
Fixed EDIFACT comparison errors when excluding entire segments, such as UNH, in the Test Tool (#2765).
-
Fixed runtime errors when assembling or disassembling X12 documents (#2785).
-
Fixed Advanced HTTP Handler errors when using dynamically generated request types (#2803).
-
Fixed missing field validation information in Partner Onboarding forms (#2805).