Feature
- PDF generation for Sales Documents now provides a clear, localizable message when the PDF is not yet ready, improving user experience and supporting translation.


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:
Regression Testing:
Products Tested:
Mobile App Compatibility:
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.
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.
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.
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.
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.
To align with industry standards, Salesforce is reducing maximum TLS server certificate lifespans in phases:
| Date | Maximum Lifespan |
|---|---|
| March 15, 2026 | 200 days |
| March 15, 2027 | 100 days |
| March 15, 2029 | 47 days |
This means certificates will be renewed more frequently. Some CA vendors have already begun issuing 200-day certificates.
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.
| Change | Effective Date | enosix Impact | Customer Action |
|---|---|---|---|
| Root Certificate → DigiCert Global Root G2 | Feb 5, 2026 | No disruption observed | Link & Connect: update to latest release if not on stable channel |
| Dual-use Certificate Ban (mTLS) | June 15, 2026 | No impact (enosix does not use mTLS) | None for enosix products |
| Certificate Lifespan → 200 days | March 15, 2026 | No impact for Named Credential integrations | Link & Connect: stay current on releases |
For any questions or support, please contact the enosix team.
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:
Regression Testing:
Products Tested:
Mobile App Compatibility:
SDK v1.7 + Apex Code Generator + Cloud-UI:
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 Summer ‘25 release. Below are the key details of the testing process and outcomes:
Regression Testing:
Products Tested:
Mobile App Compatibility:
SDK v1.7 + Apex Code Generator:
The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.
Upgraded Apex API versions to 63.0 to maintain compatibility with the latest Salesforce releases and ensure continued functionality.
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:
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)
Regression Testing:
Products Tested:
Mobile App Compatibility:
SDK v1.6 + Apex Code Generator:
The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.