Skip to main content

15 posts tagged with "salesforce"

View All Tags

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

Testing Highlights​

  • Regression Testing:

    • Tests 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.1:

    • Confirmed compatibility with Sales app.
    • Verified Lightning components function in the Salesforce Mobile app.

  3. SDK v1.7 + Cloud-UI:

    • 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 Spring ‘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 has announced several certificate-related changes in 2026 that may generate questions from customers. enosix has reviewed these changes and assessed the impact across our product line. No customer-facing disruptions have been observed to date, and our architecture minimizes exposure to these changes. Below is a summary of each change and how it relates to enosix products.

1. Root Certificate Transition to DigiCert Global Root G2 (Effective February 5, 2026)​

Salesforce has transitioned to issuing certificates chained from the DigiCert Global Root G2. Any certificate issued by Salesforce after February 5, 2026 will be chained to this new root in most environments. Salesforce recommends that organizations adopt the Mozilla Root Certificate Set to future-proof their trust stores.

Impact on enosix Products​

  • Salesforce Apps (Surface, Transact, Commerce, SDK, Sync): enosix integrations with SAP are built on Named Credentials and Callouts, not direct API client connections. Salesforce manages the outbound TLS trust chain for Named Credential callouts, so no customer action is required for these products. Self-signed certificates and CA-signed certificates that you upload to your org are not in scope for this change.

  • enosix Link: The enosix Link appliance has been patched to include the latest root certificate updates, including DigiCert Global Root G2. Customers should review the Link release announcements and ensure they are running the latest version. Customers not using the stable (automatic update) channel should update to the latest release to ensure continued compatibility.

  • enosix Connect: The enosix Connect appliance has been patched to support the latest root certificate updates. Customers should review the Connect release announcements and ensure they are running the latest version. Customers not using the stable (automatic update) channel should update to the latest release to ensure continued compatibility.

2. Deprecation of Dual-use Certificates (Effective June 15, 2026)​

Effective June 15, 2026, Chrome will mandate a strict separation between server and client authentication certificates ("dual-use" ban). This impacts customers using mutual TLS (mTLS) with Salesforce, requiring that client certificates are not sourced from the same public roots used for website trust.

Impact on enosix Products​

enosix products do not use mTLS for connectivity between Salesforce and SAP. This change has no impact on enosix integrations. Customers who have implemented custom mTLS configurations outside of enosix products should review the Salesforce-supported CAs for Client Auth EKUs and audit their mTLS usage independently.

3. Certificate Lifespan Reductions (Starting March 15, 2026)​

To align with industry standards, Salesforce is reducing maximum TLS server certificate lifespans in phases:

DateMaximum Lifespan
March 15, 2026200 days
March 15, 2027100 days
March 15, 202947 days

This means certificates will be renewed more frequently. Some CA vendors have already begun issuing 200-day certificates.

Impact on enosix Products​

  • Salesforce Apps (Surface, Transact, Commerce, SDK, Sync): Certificate renewal is managed entirely by Salesforce for Named Credential connections. No customer action is required.

  • enosix Link & Connect: Appliance updates include support for more frequent certificate rotations. Customers should stay current on the latest releases to ensure their appliances handle renewed certificates seamlessly. Customers not using the stable (automatic update) channel should regularly check for and apply the latest updates.

Summary​

ChangeEffective Dateenosix ImpactCustomer Action
Root Certificate → DigiCert Global Root G2Feb 5, 2026No disruption observedLink & Connect: update to latest release if not on stable channel
Dual-use Certificate Ban (mTLS)June 15, 2026No impact (enosix does not use mTLS)None for enosix products
Certificate Lifespan → 200 daysMarch 15, 2026No impact for Named Credential integrationsLink & Connect: stay current on releases

Additional Resources​

For any questions or support, please contact the enosix team.

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