• [Bugfix]: API end points no longer shut off 30 days post-deployment

This release consists of primarily bugfixes, but also introduces a new session handling approach.

Known Bugs:

• Deleting an app does not always remove it from SAP Cloud. Workaround: Remove manually from inside the SAP Cloud Cockpit.
• Occasionally, after an app deployment or package publishing, the app status does not go back to active properly. Workaround: refresh the browser.
• If you are running in 'Passthrough' authentication mode, in Swagger portal, when you use the "Authenticate" button at the top of the page, there are two logins presented. You should use the top one. Workaround (to avoid remembering which one you want): using the lock icon on any of the API calls will present a single box that will work (for all APIs on that connection).

• [Feature]: New session handling approach using distinct API calls vs. the session parameter on individual API calls
• [Update]: Changed email provider for password resets
• [Bugfix]: Dialog box when publishing a package no longer says "done" prematurely
• [Bugfix]: Authentication now properly turns off when changed in the app authentication tab
• [Bugfix]: Package docker naming convention updated to simplify manual deployment
• [Bugfix]: Improved handling of SAP connection errors
• [Bugfix]: Parameters in EnosixDocument search RIO now work properly
• [Bugfix]: Docker images now last more than 30 days

Incremental update to expand Tax integration and pricing.

• [Feature]: Original price displayed on custom product detail component
• [Feature]: Allow for configuring multiple jurisdiction cart tax integration from SAP.
• [Update]: Added busy indicator when calculating price and availability from SAP on product detail page.
• [Update]: 1.3.2 - Support for Spring '21
• [Bugfix]: PO Number from checkout saved to order even if blank
• [Bugfix]: Cart pricing error on first checkout after login
• [Bugfix]: Doc flow on order summary component is now populated correctly
• [Bugfix]: Missing total value on item detail on order summary

This is a small patch to fix an issue preventing the activation of pass-through authentication on an app.

The most significant update is the ability to generate PDF documents. Users can now access SAP Document generation from Salesforce for Quotes, Orders, Invoices, and other output sales documents.

This release we have a number of customer-requested enhancements to the Customer Credit Information and Customer Partners components.

Also - several customer-reported bug fixes. We are listening: you report 'em and we fix 'em. Keep submitting feature and bug requests to our Support Portal.

• [Feature]: The Customer Credit Info component now supports display of data from from multiple credit areas for the Account
• [Feature]: Customer Partners component now allows for controlling sorting at design time and runtime
• [Feature]: New Generate PDF Document component for Sales Order, Quotes and Invoices from the document details in Flow and Flexi Pages.
• [Update]: Http Trace calls to SAP now record the outbound headers
• [Update]: Improved error messages
• [Bugfix]: Sold To account number is now correct on Invoice Detail header
• [Bugfix]: Customer Sales Areas component Shipping Condition Code field now displays the value as well as description when Display Values option is enabled
• [Bugfix]: Advanced Order Search component Sold To now allows entry of customer number, the To Search Date visibility control attribute now works properly, and the Created To field now properly hides when not selected
• [Bugfix]: Sales Document Lists only display a single spinner while loading (we know it was bugging you)
• [Bugfix]: Setting customized Sales Doc, Invoice, or Delivery Flexi Page as override now works properly

Add functionality for syncing product and account data. Completes the entry tier. Bug fixes, additional functionality important for demos - in particular syncing bill to/ship to and pricing/ATP on product detail page.

• [Feature]: Bill to and ship to sync from SAP and are properly captured on order when selected
• [Feature]: Real-time pricing, ATP, and tiered pricing on product detail page.
• [Feature]: Confirm item availability on cart before creating order.
• [Feature]: Improved branding of store configuration control.
• [Update]: Resolved security review issues for app store
• [Update]: Moved line item component to use new line item RIO.

Link now supports multiple connections per app instance. A single deployed application in SAP Cloud Foundry can now define multiple routes to different virtual hosts. This reduces the number of deployed applications needed for development and test environments, and Cloud Foundry memory allocation requirements.

Link latest and stable have been updated to this release 2.2.22

Please see the link documentation for install instructions.

• [Feature]: Link version is now returned in health check endpoint /health, and included as a response header enosix-link-v. This will assist in ensuring the most up to date version of Link is deployed, Additionally the enosix-link-v header is captured in your Salesforce Surface logs viewable in the Salesforce enosix app for debugging.
• [Update]: Version naming change, previous versions were prefixed with the year and the release number, ex: 2020.1.12, going forward link versions will follow a Major.Minor.Patch version scheme. with this release 2.2 the successor of 2020.1.12. The existing labels for enosix/link:stable will be updated with this release.
• [Bugfix]: Fixed issue with configuring multiple connections within a single instance. Note: this was mainly used in development and QA connections.

Note that with this release we have moved to a more traditional semver numbering scheme for release versions. The prior release was 2020.17.1.

Check out the enosix connect documentation portal

• [Feature]: Lots of documentation updates
• [Feature]: Changes to RIO bundles
• [Feature]: SAP Cloud Platform credentials can now be renewed when they expire
• [Feature]: SAP session functionality - you can now perform multiple API calls within a single session on the server; EXISTING TENANTS MUST BE REDEPLOYED TO TAKE ADVANTAGE
• [Update]: Various console stability improvements
• [Update]: Various improvements to the manual deployment process
• [Bugfix]: You are no longer able to attempt to use an SAP Cloud Connector on apps not deployed in SAP Cloud Platform
• [Bugfix]: Memory quota for apps in SAP Cloud Platform is no longer reset on redeployment
• [Bugfix]: You can now create apps with the same name as apps that were previously deleted

The Salesforce Winter 21 release includes a breaking change​

The Restrict Access to AuraEnabled Apex Methods for authenticated users was a critical update included in the Winter 21 release that essentially require that a user be explicitly granted access to the Apex code that a front-end lightning component calls. Without making a security change to Salesforce the lightning components in salesforce apps (including enosix apps) can behave in strange ways including not displaying or looking like they are frozen.

Does it impact my organization?​

While this update affects all apps - not just enosix. But within your enosix apps, Surface v1.10 and later include the updated permission sets and are thus unaffected. All customers running an earlier version of Surface or any enosix product other than Surface are likely to see problems.

How do I fix it?​

The easiest way to correct the issue is to create a Salesforce permission set per app and add all of the Apex classes for that app to the permission set. The permission set can then be granted to each affected user who needs access to that app.

Below is an example for our Surface app, and this same workaround will work for other enosix apps, as well as apps from other salesforce partners and any custom developed app you may have in your org.

1. Create a Permission set​

• Setup > Quick Find, Enter 'Permission Sets'
• In the Permission Sets screen click on the New button it is in the list header.
• In the Label field enter a descriptive name - something like 'enosix Surface Winter 21 Security Patch'. (The best practice is to create a permission set per app to reduce access to apex code but in a pinch one permission set can be used for all your apps.)
• Click Save.

2. Add Apex Classes to the permission set​

• In the Permission Set screen click on the Apex Class Access Link. (Under Apps Section, fifth down from the top)
• In the Apex Class Access Table click the Edit button in the table header.
• There will be two list boxes, in the right one labeled Available Apex Classes, select the classes prefixed for the app your are correcting. For enosix Surface select all classes that start with ensxapp. (NOTE: for other enosix apps select ensxsdk, ensxafs, ensxb2b and any classes that start with the prefixes CTRL_, UTIL_, SBO_, or RFC_) . Other salesforce apps will have their own guidance on what prefixes or grouping to select.
• With the list entries selected click on the Add Button with the Arrow pointing to the Right >, the selected entries will be moved to the Enabled Apex Classes list box. It may take a couple of scans of the list to find all of the apex classes, and the add button can be used multiple times.
• Click on the Save Button.

3. Assign the permission set to users​

• Click on the Manage Assignment Button in the toolbar it is to the right of the Find Settings search box.
• In the Assigned Users screen click add assignments and in the list of users select the users who need access to the app by checking the box in the Action column.
• Click the Assign Button.
• The user permissions for the app should now be corrected for Winter 21.

This patch release is to fix a single issue (see Bugfix below). Organizations not experiencing this issue do not need to upgrade.

Updated Install links are available here: Surface Salesforce Package Installation

• [Bugfix]: Account number mapping (SAP Customer information Settings) using a field on custom SObjects (rather than the Account object) is now working. This fixes message: The "...__c" SObject is not currently mapped in the SAP Customer Information Setting Custom Metadata Type.