3.0.9614.474
Release notes
Release date:
Release version: 3.0.9614.474
Enhancements and New Features
Fallback Distributions with Dynamic Sender Party
Problem: It is cumbersome and time-consuming to setup similar distributions for a set of partners, since you can only set them up one-by-one.
Solution: Added support for fallback distributions with the option to use a dynamic sender party.
If a distribution only has one partner (sending or receiving) defined, the system will automatically fallback to this new distribution type.
This means that it is now possible to setup a single distribution specification for a set of partners in either sending or receiving end.
Expanded Tracking Field Types
Problem: Tracking Fields were limited to XML documents in the flow, which in many cases have not been sufficient for other document types as JSON or scenarios where any other document type is just passed through in the flow.
Solution: By enabling Context Properties and Link macros as Tracking Field Types, it is now possible to put tracking fields on other document types than XML.
Previously, the only supported type was XPath, which retrieves a value from the CDM document. Now, the tracking field functionality has been expanded with two new types:
Context Property
Allows a context property defined at the CDM stage to be used as a tracking field. This includes both native Link properties and custom properties.Macro
Allows a string containing Link macros to be defined as a tracking field. This can consist of a single macro or a combination of fixed text and one or more macros.
To keep tracking field behavior consistent, macros are resolved only at the CDM stage.
Enhanced the “Failed Document” email to be more human-readable and easier to understand
Example:
Conversion table changelog
Problem: It is not possible to see directly on a Conversion Table what, when and by who it has been changed, which is sometimes a challenge in tracing down errors.
Solution: Ability to view changelogs for individual Conversion Tables
Document number more visible in tracking search details
Problem: When a user marks several documents in the list view in LINK and chooses "Show documents", the user is presented for a number of cards reflecting the exact number of marked records.
These cards can be hard to recognize because they have a D-xxxxx number instead of an easy number to recognize by the user. Usually that would be the document number.
Solution: Document number is now included in the document tabs
Standard Reports
Problem: Out-of-the-box Link does not contain any reports, however some useful examples are mention in the user-guide. These examples have not been part of an out-of-the-box installation, but could potentially be useful for customers "as is" or as examples.
Solution: Standard reports have been introduced to Link, now offering five predefined reports. These reports are not user-modifiable and will be maintained and updated as part of ongoing product releases.
Support for more partner certificate types
Problem: Due to an increased focus on security, the limited support for SSH keys was becoming a challenge, especially in SFTP scenarios.
Solution: Link now supports several OpenSSH key types, including RSA, ECDSA, and ED25519. This gives customers greater flexibility when configuring secure connections and helps align with modern security requirements.
Breaking changes
This release includes some breaking changes:
The following methods have a renamed parameter.
Note: This only affects calls that use explicit parameter names like GetByDocumentConfigsIdIn(documentConfigsIdIn: 1, partnersIdIn: 2, includeTemplates: false)
Task<IEnumerable<DistributionEntity>> GetByDocumentConfigsIdIn(Int32 documentConfigsIdIn, Int32 partnersIdIn, Int32 partnersIdOut, Boolean includeTemplates)
Task<IEnumerable<DistributionEntity>> GetByDocumentTypesIdIn(Int32 documentTypesIdIn, Int32 partnersIdIn, Int32 partnersIdOut, Boolean includeTemplates)
Changed to:
Task<IEnumerable<DistributionEntity>> GetByDocumentConfigsIdIn(Int32 documentConfigsIdIn, Int32 partnersIdIn, Int32 partnersIdOut, Boolean includeFallback) <-- includeTemplates are changed to includeFallback
Task<IEnumerable<DistributionEntity>> GetByDocumentTypesIdIn(Int32 documentTypesIdIn, Int32 partnersIdIn, Int32 partnersIdOut, Boolean includeFallback)We always recommend testing any custom-built artifacts with new releases prior to performing an upgrade.