We're pleased to announce the release of ECLI 2.2.0! 🎉
⚠️ If you use the P21 ECLI or LSAF integration, you must upgrade them before or during your P21E 5.0.0 upgrade.
We specifically ensured that ECLI 2.2.0 supports 4.1.x, 4.2.x, and 5.0.0 for this reason.
You will likely find it easier to upgrade your ECLI prior to your P21E 5.0.0 upgrade instead of coupling both upgrades to be done at the same time.
ECLI 2.2.0 supports new capabilities of P21E 4.2.0 and 5.0.0. ⚡️
Specifying the string encoding for Chinese-language files validated by the NMPA engine
Support for BIMO data packages
Support for uploading custom specs (only for customers with a custom spec adapter)
ECLI 2.2.0 is more accessible than previous versions. 💻
It is now officially supported by the two LTS JDK versions (8 and 11). It is known to work with most other JDK versions, but we only perform validated testing on 8 and 11.
ECLI is now supported on more operating systems. The ECLI uses embedded Aspera components for file transfer which have OS dependencies. These have been updated and tested in a larger variety of Windows, Linux and OSX versions.
Aspera transfers are now supported from within the LSAF and SAS environments. This often requires additional configuration and diagnostics, and clients interested in using this capability should contact our Support Team.
Reduced API key permissions required to perform an ECLI validation
ECLI 2.2.0 has improved documentation and diagnostics. 🗂
ECLI 2.2.0 has significant improvements to its logging and diagnostic facilities. P21 also offers dedicated Developer Support for users of ECLI.
Self-service is now possible for ECLI usage. The documentation includes a public download link for the necessary software components. Starting with Enterprise 5.0.0, users can generate their own personal API key for validation.
Clearer error reporting for Aspera connectivity issues
Learn more in the Configuration & Administration collection.
Please email questions or feedback to firstname.lastname@example.org.