Upgraded Apex API versions to 63.0.
23 posts tagged with "surface"
View All TagsSurface 2.7.1
- [Bug Fix]: Resolved an issue with Document Search Custom Configuration where selecting an sObject Id for a Mapped Field would result in an error when performing a search. This fix will allow sObject Id fields to be used in a document search.
Salesforce Spring 25 Release
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:
- Sync for Salesforce v1.3.2
- Surface v2.7
- SDK v1.6, including the Apex code generator
-
Mobile App Compatibility:
- The Surface app was tested in the latest version of the Salesforce Mobile app.
Testing Scope and Outcomes
-
- Validated real-time data synchronization between Salesforce and SAP.
- Ensured consistent performance across core use cases, including object synchronization and data accuracy.
-
- Confirmed compatibility with Sales, Service and Console apps.
- Verified Lightning components function in the Salesforce Mobile app.
- Validated Lightning components work in experience sites.
-
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.
Surface 2.7
- [Feature]: Enhanced the Developer API of enosix Surface to support multiple SAP systems.
Surface 2.6
Documents will now display in order by create date and document number to show the most recently created document first by default.
Surface 2.5.1
- [Bugfix]: Fixed Bill of Lading data not displaying in the Delivery Search component
Improved Named Credentials
WHAT'S NEW: With the Winter '23 release, the improved Named Credentials schema works through External Credentials. The External Credentials are the root between connection to a system, permission to access, and the individual user token/password. Basic Authorization isn't supported in this release.
UPDATE: You can still use and create Legacy named credentials as before. Select the New Legacy button (click the arrow next to the New button).
NOTE: The Named Credentials and new External Credentials have no impact on our enosix solutions as the Basic Authorization is NOT supported in this release.
To access Surface Product Documentation: Post Installation Steps> Named Credentials
https://docs.enosix.io/surface...
Surface 2.5
- [Bugfix]: Fixed UI defects in the Customer Details component
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