New landing page for deployed link instance

See updating to the latest release for details on how to use the landing page. The new landing page can be disabled, and is outlined in the Link product documentation.

The new metrics health check has been added to monitor any potential issues in processing requests.

{
  "Metrics": {
    "status": "Healthy",
    "description": "",
    "data": {
      "requests-per-second": "0",
      "total-requests": "3502",
      "current-requests": "0",
      "failed-requests": "0"
    }
  }
}

• [Feature]: A new landing page providing information on the version and links to documentation
• [Feature]: Basic request metrics for monitoring performance of a Link deployment

Updates to support SAP SSO O-Auth. This latest version has been tested to work with our Salesforce SAP Auth Provider for named credentials allowing for password-less per-user access to SAP.

• [Bugfix]: Proxy of url encode form content added

• [Bugfix]: Remove duplicated tablerowstate attributes when manually specified
• [Bugfix]: Validated support for large document/async invocable functionality
• [Bugfix]: Resolved text serialization errors

An incremental update to improve the experience for long running requests.

To update already deployed applications to no longer have timeouts:

1. Create a new package
2. Deploy the new package to your existing application

• [Bugfix]: Removed HTTP timeout from deployed applications allowing SAP to handle timeouts

Announced on Dec 10th, 2021 the Zero Day Log4j vulnerability CVE-2021-44228, is affecting systems worldwide. enosix has reviewed its systems and has yet to detect any platforms, apps, or services that are affected by this vulnerability.

Salesforce is conducting its own analysis of its systems. Any Salesforce apps provided by enosix (Surface, Transact, Commerce, CPQ) are not using log4j and are not affected. Salesforce will provide updates to the Salesforce platform, if needed.

The enosix connect platform does not utilize java or the log4j libraries and is not affected. Your IT department should review any other apps you are running in the SAP BTP platform, see SAP Note 3130476

enosix Link does not utilize java or the log4j libraries and is not affected. SAP Note 3130868 details that none of the SAP Cloud Connector versions contain the affected log4j-core and are not affected.

enosix will continue to review our systems and provide assistance. We advise that all computer systems operators review their systems that may be affected and take the recommend steps to patch any affected software.

Address bugs and repair deployments since the Salesforce Commerce changes

• [Update]: Add support for Winter '22
• [Bugfix]: Fix price/unit on checkout screen
• [Bugfix]: Fix the cart total icon when item counts are updated

Salesforce Winter 22 Testing and Validation

Improved Support for S4 Hana including new component to support credit data (Credit Segments vs Credit Areas)

Improved doc flow support

Consistent custom fields:

• Will display when configured in Salesforce even if not found in SAP (label with no data)
• NEW support for custom fields for Delivery Item Details and Inquiry Item Details
• All data type formats are confirmed to work for custom fields (Date/Numeric/Alphanumeric/BlankValue/LabelOnly)

This release requires an upgrade of the Surface SAP Components

• [Feature]: Credit Segment control for S4 Hana implementations to replace Credit Area component on Salesforce account page.
• [Feature]: NEW Sales Doc Flow is now supported at both the header level (FLOW ONLY) and item detail level
• [Feature]: NEW "Edit Settings" link on enosix log page that brings user directly to the Custom Settings page for enosix Log Settings
• [Update]: Custom field display logic was centralized and made consistent across all components, configured fields display even if there is no returned data from SAP.
• [Bugfix]: Item partners were displaying on the sales document header partners section. Sales Document Partners now only show the header level partners.
• [Bugfix]: Demographic information for Contact Person, Vendor, and Personnel partner types is now populated correctly.

Patch release to address security defects

• [Update]: Addressed multiple security related opportunities

Patch to address customer submitted issues.

Notes:

1. To make use of the new Accept-Language feature in an existing app, a new package needs to be created with the same selected APIs and published to the existing app. Please find notes on packaging and publishing APIs in our packaging docs

Known Issues in this release:

1. Publishing a package may result in a System.NullReferenceException in CheckConnectivityServicesStep.cs or CheckAuthorizationStep.cs.
   1. To resolve this issue, navigate to your App Details page, click the Re-auth SCP button and follow the steps in the wizard. After the wizard completes, your package should publish successfully.

• [Feature]: Translation Language for returned descriptions can be requested using the Accept-Language header.
• [Update]: Search context RIO's without a leading structure are now supported.
• [Update]: Added additional configurable output logging for diagnosing response messages from SAP
• [Update]: Performance improvements in data serialization
• [Bugfix]: Service hub url parameter for manual deployments to docker are correctly using secure wss transport, fixing cannot connect issue.
• [Bugfix]: Port was being stripped off of the connection string in SAP connections, causing issues when connecting to SAP systems using a custom proxy server.
• [Bugfix]: Fixed a race condition in the console viewing documentation without a project.
• [Bugfix]: Fixed a docker access issue consuming a base image for new applications

Fix to address orphaned sessions in SAP