Updated link version with improved documentation

https://docs.link.enosix.io/

• [Feature]: Use Checkly to monitor outages, add end to end monitoring and alerting to your link instances following our guide.
• [Update]: Updated runtime to dotnet core 3.1, this fixes many CVE's and memory issues

Bug fixes and performance improvements. Beta test version of asynchronous call support.

• [Feature]: Id and number are added to return messages to identify record relations.
• [Feature]: Model generator supports class prefix
• [Feature]: New setting to use improved xml serialization
• [Update]: Async RIO processing (Beta)
• [Bugfix]: Missing apex classes added to permission sets
• [Bugfix]: Updated model generation templates for Salesforce Critical Update Type.newInstance in API 48+

The documentation for enosix Link has a new home: https://docs.enosix.io (or https://docs.enosix.io/link to go directly to the Link documentation).

The documentation for enosix Connect has a new home: https://docs.enosix.io (or https://docs.enosix.io/connect to go directly to the Connect documentation).

The documentation for enosix Surface has a new home: https://docs.enosix.io (or https://docs.enosix.io/surface to go directly to the Surface documentation).

• [Bugfix]: Connecting to any SAP client ID (by service account or SAP Cloud Connector) now works as expected

Patch release to address display of sales document header fields

This release addresses security issues for the 2.2 release

• [Update]: PSA: Your SAP cloud connector certificate will expire every year. Please ensure to update the certificate prior to expiration by following the instructions here EXTERNAL LINK: SAP Cloud Connectivity issues due to Expired Certificate

Fixes for sales document item custom fields

• [Bugfix]: Sales document item custom fields now display SAP values without any client side formatting.

This bugfix release resolves issues with handling structures in RFC's and corrects parsing of different SAP date types.

• [Update]: Added support for structure parameter types in RFC API's
• [Bugfix]: Fixed parsing of different date component types returned in RIO's and RFC's