Improved error tracking capabilities to provide more insightful crash analysis.
Fixed issue with deployments failing to start on BTP cloud.
Improved error tracking capabilities to provide more insightful crash analysis.
Fixed issue with deployments failing to start on BTP cloud.
Adding ability to protect API access with API Key, configured in BTP Cloud Foundry
WHAT'S NEW:
Updated Connect with minor bug fixes and console infrastructure.
(No action is needed for our Connect customers to continue using their deployed connect apps.)
For any questions, reach us at 👉 https://go.enosix.com/support
📣 Connect 1.3.10 is here! Below are some important changes made to this release that focuses on customer requests and improvements to the user experience. 📣
1️⃣ Refresh All APIs
When an update to multiple RIOs are made in SAP, clicking this 1 button will refresh the metadata for all the currently selected APIs in the project. This will allow pulling all of the latest changes into a project with a couple clicks instead of the need for manually re-adding all RIOs that have been updated.
2️⃣ Enhanced Error Reporting
When errors occur while deploying or running the application, more meaningful messages are presented to enable a user to take action. The screenshot above shows an example when the destination service in SAP BTP becomes unbound from the deployed application.
3️⃣ User Experience Improvements
Multiple enhancements have been made to improve the user experience, such as:
When publishing an existing package, the most recent packages are listed first.
The Bundles feature has been removed to make it quicker to access your custom RIOs. The RIO selection screen now supports adding all available RIOs, as well as removing all selected RIOs.
When selecting APIs, the name of the RIO will match what it is named in SAP.
4️⃣ Support for Customizing ID
Adding APIs now supports searching for a RIO with a Customizing ID(CID), and still filtering down based on the name. When multiple APIs are added for the same RIO, each with a different CID, they will be accessible on different routes in the deployed application.
Refresh All APIs
buttonPublish Package
modalMax Depth Exceeded
exception in a deployed applicationAn incremental update to improve the experience for long running requests.
To update already deployed applications to no longer have 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.
Patch to address customer submitted issues.
Notes:
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 docsKnown Issues in this release:
Accept-Language
header.Fix to address orphaned sessions in SAP
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).