Release notes
Release date:
Release version: 3.0.9741.18968
Enhancements and New Features
Connection configuration in Partner Onboarding
Internal ID: LINKOB-I-55
Problem
Setting up a new partner required connection details to be coordinated outside the onboarding flow, making it harder to configure how documents should be exchanged.
Solution
Partner Onboarding now supports connection configuration for SFTP, FTP and AS2. Connections can be configured for sending, receiving or bidirectional document exchange. For FTP and SFTP, the connection can be hosted by either the partner or customer, including the option to use Link Integrated FTP. AS2 onboarding collects the relevant identifiers, certificates and endpoint addresses from the appropriate parties.
|
|
|---|
Large files no longer block the Outbox
Internal ID: LINKOB-I-488
Problem
A file that exceeded the supported size could block the Outbox API, preventing other queued documents from being retrieved until the problematic entry was manually removed.
Solution
Outbox payloads exceeding 125 MB are now excluded from retrieval and marked as failed in LINK, allowing processing to continue for other messages instead of blocking the Outbox.
Status events now reflect the result of error rules
Internal ID: LINKOB-S-13
Problem
Status events could be triggered before error rules had finished processing. If an error rule subsequently changed a document’s status—for example to Ignored—the earlier event could represent the wrong status.
Solution
Error rules are now resolved before status events are triggered, so events take status changes made by error rules into account.
Faster loading of large conversion tables
Internal ID (Solution): LINKOB-534
Problem
Large conversion tables could take disproportionately long to load in the LINK UI.
Solution
UI performance when loading conversion tables containing large amounts of data has been improved.
Breaking changes
SFTP library upgraded
The SSH.NET library used by our SFTP client has been upgraded from version 2024.2.0 to 2026.0.0.
This upgrade includes some behavioral and compatibility changes that may affect existing SFTP integrations:
-
Legacy DSA (
ssh-dss) support has been removed. Connections to SSH/SFTP servers that rely exclusively on DSA host keys or DSA authentication keys may no longer succeed. Such servers should be configured to use a currently supported key algorithm, such as RSA, ECDSA, or Ed25519. -
Some SFTP write operations now truncate existing remote files before writing. This prevents trailing content from a previous, larger file from remaining after it is overwritten.
Custom artifacts using our SFTP client abstraction do not need to make changes because of SSH.NET API changes.
Custom artifacts that directly reference the bundled SSH.NET library instead of using our SFTP abstraction may be affected by API removals, signature changes, and deprecations introduced in newer SSH.NET versions.
We always recommend testing any custom-built artifacts with new releases prior to performing an upgrade.