Skip to main content

13 posts tagged with "salesforce"

View All Tags

Salesforce Winter '26 Compatibility Testing​

The enosix team has completed extensive testing to ensure compatibility of the latest enosix apps with the Salesforce Winter ‘26 release. Below are the key details of the testing process and outcomes:

Testing Highlights​

  • Regression Testing:

    • A total of 140 regression scenarios were executed to validate functionality and compatibility.

  • Products Tested:

  • Mobile App Compatibility:

    • The Surface app was tested in the latest version of the Salesforce Mobile app.

Testing Scope and Outcomes​

  1. Sync for Salesforce v1.3.4:

    • Validated real-time data synchronization between Salesforce and SAP.
    • Ensured consistent performance across core use cases, including object synchronization and data accuracy.

  2. Surface v2.8:

    • Confirmed compatibility with Sales, Service and Console apps.
    • Verified Lightning components function in the Salesforce Mobile app.
    • Validated Lightning components work in experience sites.

  3. SDK v1.7 + Apex Code Generator + Cloud-UI:

    • Verified code generation capabilities and deployment to Salesforce Winter ‘26 orgs.
    • Verified ability to configure a material/product and update price on quote line item using Cloud-UI in CPQ.

Results​

  • Compatibility Confirmed: All tested products are fully compatible with Salesforce Winter ‘26.
  • No Critical Issues Identified: Testing revealed no blockers or critical issues.

The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.

Salesforce Summer '25 Compatibility Testing​

The enosix team has completed extensive testing to ensure compatibility of the latest enosix apps with the Salesforce Summer ‘25 release. Below are the key details of the testing process and outcomes:

Testing Highlights​

  • Regression Testing:

    • A total of 136 regression scenarios were executed to validate functionality and compatibility.

  • Products Tested:

  • Mobile App Compatibility:

    • The Surface app was tested in the latest version of the Salesforce Mobile app.

Testing Scope and Outcomes​

  1. Sync for Salesforce v1.3.4:

    • Validated real-time data synchronization between Salesforce and SAP.
    • Ensured consistent performance across core use cases, including object synchronization and data accuracy.

  2. Surface v2.8:

    • Confirmed compatibility with Sales, Service and Console apps.
    • Verified Lightning components function in the Salesforce Mobile app.
    • Validated Lightning components work in experience sites.

  3. SDK v1.7 + Apex Code Generator:

    • Tested SDK integrations for Transact, including CPQ & Sales Doc.
    • Verified code generation capabilities and deployment to Salesforce Summer ‘25 orgs.

Results​

  • Compatibility Confirmed: All tested products are fully compatible with Salesforce Summer ‘25.
  • No Critical Issues Identified: Testing revealed no blockers or critical issues.

The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.

The enosix team has completed extensive testing to ensure compatibility of the latest enosix apps with the Salesforce Spring ‘25 release. Below are the key details of the testing process and outcomes:

ICU Locale Formats​

You may have received an email or noticed in the Salesforce release notes about the upcoming enforcement of ICU locale formats, which standardize the representation of dates, times, currencies, and numbers across the platform. We want to assure you that this change does not affect enosix components. Our team has thoroughly tested these components with the new formats activated in a Spring Preview org, and they function as expected. Generally, this update does not apply to enosix components.

The email notification you received was triggered by legacy, deprecated surface Visualforce components within your org that utilize API versions below 45. Salesforce requires a minimum API version of 45.0 for all Apex Classes, Apex Triggers, and Visualforce Pages to auto enable ICU locale formats. Consequently, your sandbox org was not enabled on the ICU locale formats due to these outdated API versions.

You can still activate the ICU locale formats with components that use API versions below 45.0.

We are actively addressing these older API version dependencies and plan to update them in the next major release of Surface. This will ensure compatibility with the the latest salesforce releases and prevent future notifications.

For more information on the ICU locale formats and the upcoming changes, please refer to Salesforce's official documentation: Enable ICU Locale Formats (Release Update)

Testing Highlights​

  • Regression Testing:

    • A total of 123 regression scenarios were executed to validate functionality and compatibility.

  • Products Tested:

  • Mobile App Compatibility:

    • The Surface app was tested in the latest version of the Salesforce Mobile app.

Testing Scope and Outcomes​

  1. Sync for Salesforce v1.3.2:

    • Validated real-time data synchronization between Salesforce and SAP.
    • Ensured consistent performance across core use cases, including object synchronization and data accuracy.

  2. Surface v2.7:

    • Confirmed compatibility with Sales, Service and Console apps.
    • Verified Lightning components function in the Salesforce Mobile app.
    • Validated Lightning components work in experience sites.

  3. SDK v1.6 + Apex Code Generator:

    • Tested SDK integrations for Transact, including CPQ & Sales Doc.
    • Verified code generation capabilities and deployment to Salesforce Spring ‘25 orgs.

Results​

  • Compatibility Confirmed: All tested products are fully compatible with Salesforce Spring ‘25.
  • No Critical Issues Identified: Testing revealed no blockers or critical issues.
  • Optimized Performance: Minor adjustments have been made to enhance performance and user experience.

The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.

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

warning

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.

note

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.

SalesDocList-Component

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

CreditData-Component

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