Spring '25 Product Updates

Update 19 Feb

Summary

We have released a further patch update for ProntoPlus and ProntoPayments (see table below), which resolves a newly identified issue where inactive and/or deprecated code references block the enablement of the ICU locale setting.

We are also aware of a Salesforce package called NPE4 which has not been updated with the latest API versions. If you have this package installed this may block attempts to enable the ICU locale setting.

Detail

Now that the Spring '25 update is active in production environments, we’d like to provide an important update on the ICU Local enablement process and related component changes.

We received confirmation from Salesforce CDN Admin that ACTIVE components are blocking the enablement of ICU Local, even if the Apex classes, triggers, and Visualforce pages are deprecated or unused. This is a critical issue for the upcoming update.

ACTIVE components with deprecated/unused items: These classes and triggers were not included in the initial release. One of our clients reported that ICU Locale cannot be enabled due to components with versions below 45 still being detected. Specifically, this involves two components from the Salesforce package (NPE4), and ProntoPlus.

ProntoPlus, ProntoPayment Components and NPE4 Package: Our further patch update covers ProntoPlus and ProntoPayment components (see table below), but you may still be blocked from enabling the ICU Locale if you have the NPE4 package installed. We have raised a case with Salesforce directly regarding the NPE4 package but we encourage you to do the same (if you are an AlphaSys customer you can request them to action the case on your behalf). This will help us address the issue proactively.

If you have any questions or need further clarification, please don’t hesitate to reach out.

Background

The Salesforce Spring ’25 release is being released in production orgs this month. We have discovered a feature relating to locale formats, which will require you to install a patch version for certain Posimente products. 

Salesforce are adopting an international standard for the way your org displays dates, times and currencies according to your locale. Part of this change is ensuring all API references in our product are compatible. Check out the Salesforce 6 Feb update for more information.

We are not aware of any data integrity issues relating to the change, therefore if you are using a product which is not compatible with the Salesforce locale changes, you may experience an error such as ‘Invalid Date and Time’.

We are releasing a patch version for the following products to address the change: