10 posts tagged with "salesforce"

• [Feature]: Enhanced the Developer API of enosix Surface to support multiple SAP systems.

Documents will now display in order by create date and document number to show the most recently created document first by default.

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.

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.

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.

• [Feature]: Sales Document Line Item Custom Fields
• [Feature]: Partner List now has Custom Fields
• [Update]: Updated connection test to report installed SAP Components
• [Bugfix]: Flexi-Page Tabs - Modal Tabs have been reworked to be more reliable, fixing the issue where they were sometimes blank, or not in the correct order.
• [Bugfix]: Delivery Detail - Shipping Condition code and create date fixed
• [Bugfix]: Fixed permission issue for standard user profile when viewing New PDF component
• [Bugfix]: Doc Flow - Originating Item field fixed and Create Date display to local time fixed
• [Bugfix]: Invoice Sales unit was displaying internal instead of external SAP format
• [Bugfix]: Credit Partners were displaying incorrect address data

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

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

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.

See this page in the enosix documentation for older release notes.