Skip to main content

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.

New Feature​

  1. New Security Warning Within Health Check
    • With the variety of configuration options available in enosix Link, it is possible to configure it insecurely. Link now provides a warning section in the Health Check that informs you when an insecure connection is detected. While the specific details of what is insecure are not shown, please reach out and we will help you adjust your configuration to remove the risk.

New Features​

  • Metadata Dict Keys
    • The /metadata endpoint now retrieves and provides the SAP dictionary keys.
    • These keys are used to ensure the correct updates are changed when updating SAP records.
    • This new functionality allows the Link's APIs to support greater levels of SAP customization.

  • [Feature]: Improved error handling to enable providing better support.

  • [Feature]:Upgraded API versions to 63.0 to maintain compatibility with the latest Salesforce releases. Classes no longer trigger the API version warning in the Salesforce optimizer.

  • [Bug]: Corrected year handling format.

  • Resolved an issue where the date used to sync was formatted incorrectly and caused a one-year shift into the future for certain dates at the end of 2023 and 2024.

  • The affected dates are:

    • 2023-12-31
    • 2024-12-29
    • 2024-12-30
    • 2024-12-31

  • If your sync process runs daily and you're concerned that data was missed from those dates it will be necessary to do a Full Run with the Minimum Date From set to the day before the last date you have missing data from the list above.

    • See Data Source for more information on the Minimum Date From field.
    • See Run Sync for a guide on performing a Full Run.

  • [Feature]: Improved internal error handling.

Upgraded Apex API versions to 63.0 to maintain compatibility with the latest Salesforce releases and ensure continued functionality.

  • [Feature]: All operations support optional query parameters to support enosix SAP Framework CID functionality.
  • [Feature]: Update operation Dictkey lookup changed to static file from dynamic API call to improve update operation performance.
  • [Bugfix]: Command operation failure will be sent as an error message rather than empty output document.
  • [Bugfix]: Fixed parser exception when trying to close a bad SAP session.

  • [Feature]: Custom headers can now be configured to be included on every request to SAP. For more information, see our documentation: Server Configuration

  • [Bug Fix]: Sap-language will no longer be overwritten by the Accept-Language header