Patch release to address security defects
- [Update]: Addressed multiple security related opportunities
Patch release to address security defects
More fields added and customizations based on customer requests.
There was an error in SAP. Please contact your administrator
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).
Patch release to address display of sales document header fields
Fixes for sales document item custom fields
More custom fields just where they are needed: Sales Doc Item and Partner components can now be customized.
Many bug fixes from customer submissions and the enosix QA team.
This release requires an update to your RIOS in SAP in order to work properly. Please enter a ticket in the support portal to request an update, and our team will work with you to install it.
We have begun using the major release number (ex. 2 in this case) to indicate changes in RIOs needed to support the new Surface functionality.
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.
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.
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.
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.
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
The "...__c" SObject is not currently mapped in the SAP Customer Information Setting Custom Metadata Type.
When upgrading from versions <= 1.9.5 to v1.10.1 the page layouts become invalid because of an issue with the way field presets are stored on the record pages. To overcome this situation, you must click on the affected app pages that use custom field presets. You should record all existing values before you upgrade, since existing values in the app editor will be lost. After the upgrade, you can manually reconfigure your app pages with your recorded values.
When upgrading from v1.7.x v1.8.x, you’ll need to modify any customized “SAP Sales Document Details” flows that use the Sales Doc Flow component by following the instructions located here: "Fixing “SAP Sales Document Details” flows cloned from v1.7.x or v1.8.x".
When upgrading from v1.6 or below, please follow the instructions located here: Upgrading to Latest Version of Surface.
See this page in the enosix documentation for older release notes.