- [Bugfix]: Fixed UI defects in the Customer Details component
enosix B2B Commerce
Store Configuration Component Initializes Default Values
The Initialize button appears when a new configuration option is introduced; clicking on this button will set the default values for any unset settings.
Provides the enosix Product Detail Template component to demonstrate integration with enosix Product Detail API
Use the enosix Product Detail Template as reference to return real-time data from SAP for your Product Detail page.
Confirmed checkout with Salesforce B2B Synchronous Checkout
enosix B2B integration has been tested inside the new Salesforce B2B Synchronous Checkout flow to provide the same checkout process; however, it is faster without the delayed message.
Updated the enosix B2B Commerce Package
The “enosix B2B Commerce” is a single package installed. The Standard and Professional packages will not be required or installed.
👉 The following features were improved:
1️⃣ Cart Bubble
The cart bubble includes the total count of items currently in your cart and is updated regardless of where you add products to your cart.
2️⃣ Complete Order
You can now see the “Total” amount for a completed order after the order has been completed and processed in the application on the Item Details Page.
3️⃣ Date Available
The Product Availability data is provided by the enosix Product Detail API.
- [Feature]: Store Configuration Component Initializes Default values
- [Feature]: Provides the enosix Product Detail Template component to demonstrate integrating with enosix Product Detail API
- [Update]: Confirmed checkout with Salesforce B2B synchronous checkout
- [Update]: Updated the enosix B2B Commerce package
- [Bugfix]: Cart Bubble is updated when products are added to cart
- [Bugfix]: Total is populated when viewing completed order
- [Bugfix]: Data Available is being displayed for product details
Manufacturing Cloud Application 1.2
📣 enosix Manufacturing Cloud - Prebuilt SAP Integration 📣
Add Support for Category Level Sales Agreement
As a user of Manufacturing Cloud, you will now be able to define your Sales Agreements at the category level where the Product is the primary category and still retrieve all your actuals from SAP.
The Update Actuals from SAP button
The enosix SAP Actuals Calculation table displays the Update Actuals from SAP button below the grid.
Please note: this component is not supported on mobile.
Display material results upon completion
A user can now select multiple products and the maximum number of schedule periods allowed by Salesforce for a Sales Agreement and still be able to update actuals.
- [Feature]: Add Support for Category Level Sales Agreement
- [Feature]: Fixed the Update Actuals from SAP button
- [Feature]: Display material results upon completion
Salesforce SDK 1.6.0
- [Feature]: Return Messages now expose ExtendedText1, ExtendedText2, ExtendedText3, and ExtendedText4
Connect 1.3.10
📣 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.
- [Feature]: Add support for adding RIOs with a customizing ID
- [Feature]: Added a
Refresh All APIs
button - [Update]: UX updates to the
Publish Package
modal - [Update]: Improved error reporting and provided clearer error messaging to user
- [Update]: Remove the Bundles API
- [Update]: RIO names will match SAP when selecting APIs
- [Bugfix]: Resolved a
Max Depth Exceeded
exception in a deployed application
Hot Fix: SURFACE 2.4.3
- [Bugfix]: Optimizations to increase performance and speed of Surface components
Hot Fix: SURFACE 2.4.2
Before: A user could click the Search button on the Advanced Order Search and not wait for the Sold To value to be populated, which caused the component to search other accounts.
Now: ✨ The Search button is disabled until the Sold To value is populated. ✨
- [Bugfix]: The search button on the Advanced Order Search will remain disabled until all default values are populated
Link 3.1
📣 We have added new low-code features for administering your Link instances in 3.1. 📣
1️⃣ When a cookie with a static value is desired on all requests to SAP, this can now be injected in Link through configuration. Cookies and their values can be configured per route so the client does not need to attach the cookie manually. For more details, see the documentation.
2️⃣ A new start-time metric will be visible from the /health endpoint the Link instance. This information can be used to manually derive other metrics for your Link instances' health.
- [Feature]: Cookie values can be injected into requests to SAP through configuration
- [Feature]: Start-Time metric is exposed on the
/health
endpoint
What's New: 'enosix Sync for Salesforce' Solution
Hello All!
📣 enosix is announcing our new solution, enosix Sync for Salesforce 📣
enosix Sync for Salesforce provides a Salesforce native app with the ability to replicate data from SAP to Salesforce.
1️⃣ Data is copied (replicated) from SAP to a Salesforce sObject on a daily or hourly schedule
2️⃣ Synced data can be used in Salesforce Reports, Formula fields since it is copied to Salesforce
Note: Depending on your batch schedule, data may be out of date. For real-time data use our Surface App.
FEATURES:
-
Admin friendly interface for configuring synchronization jobs from SAP to Salesforce
-
Source date from the library of enosix Sync Rapid Integration Objects
-
Target any native or custom Salesforce sObjects
-
Built-in data transformation with field to field mapping
-
Built in job scheduling
-
Built in logging and error reporting
-
Syncs can be run in development mode for testing without data updates
-
enosix SAP adapter support for:
- Efficient initial and delta syncing based on last execution date
- Support for specifying the language used for localized description fields
👉 The enosix Sync app provides the Valence syncing framework and enosix adapter for SAP.
- [Feature]: Added support for
sap-language
parameter to source localized data from SAP - [Feature]: Added support for
sap-client
parameter to source data from the non-default data client in SAP - [Feature]: Add support for
CID
to enable specifying which enosix SAP framework calls are invoked - [Feature]: Add support for scoped paging and batch/page size limits to allow Valence to properly plan the number of scopes needed to efficiently process data
- [Feature]: Add support for specifying a
System.Callable
for logging HTTP callout information for debugging purposes. - [Feature]: Add support for specifying
Last Queried Date
andInitial Load
fields to enable enosix SAP framework optimizations to occur for full and partial syncs.
SURFACE 2.4.1
📣 We are working hard to improve SURFACE. Below are some important changes made to this release that focuses on customer requests. 📣
Note if you are also using the enosix Transact App, this step must be completed prior to updating the Surface package in Salesforce.
1️⃣ Advanced Order Search Sold To Default
Added the ability to set the Sold To field on the Advanced Sales Document Search Component using a variable in the Flow. This will allow for using the component and sourcing it from other Salesforce Objects with the ability to restrict entry into this field.
2️⃣ **Added Contract Start and End Dates to the Sales Document Search
**
Added contract Start and End dates to the Sales Document Search component to display dates in the search results. These fields are not on by default, but you can turn them on. Using this feature requires updating the latest SFCI package 2.4+.
👉 Here is the link to the updated documentation page for the release compatibility: https://docs.enosix.io/surface...
3️⃣ Performance Reporting
Performance Details
Average Page Performance
There are two new reports added to the enosix Framework page; Performance Details which shows the average execution times, and Average Page Performance displays the breakdown of pages.
4️⃣ SAP Print Output Preview Button
The Sales Doc List component will now have a Preview button that allows users to view the SAP Print Output on a new page. (If the document doesn’t open, manage your settings for Pop-ups blocked.)
📣 Note: The Preview button is not supported in Mobile, and is hidden.
🐞 Credit Limit Used shown as percentage unit
The Credit Limit Used column, listed under the Credit Areas component, is displayed in percentage (%).
- [Feature]: Advanced Order Search Sold To Default
- [Feature]: Added Contract Start and End Dates to the Sales Document Search
- [Feature]: Performance Reporting
- [Feature]: SAP Print Output Preview Button
- [Bugfix]: Credit Limit Used shown as percentage unit