Salesforce Release Impacts

Spring '22 Release

International Components for Unicode (ICU) Locale Formats

What is changing?

Beginning with the Winter '20 release, Salesforce added a new international locale standard to supplement and eventually replace the previously used Java Development Kit locales.

With the Spring '22 Salesforce release, all orgs will be required to use the International Components for Unicode (ICU) locales.

Orgs created after the Winter '20 release had ICU locales enabled by default when the org was created. However, the option may have been disabled.

Orgs created prior to the Winter '20 release did not have this option, and Salesforce has not required orgs to enable it. This changes with the Spring '22 release when the use of ICU locales is required.

What do locales affect?

Locale settings effect the formats used for elements such as dates, times, numbers, and currencies.

Salesforce has a help document that shows the differences between the current Oracle JDK locales and the new ICU locales.

For US English, the differences include:

  • Datetime formats add a comma between the year and the time

  • Negative currencies switch from using parentheses to a negative sign at the beginning of the amount

    Screenshot of en-us differences
Refer to the document linked above for the differences in formats for other locales, which may have additional impacts beyond dates and currencies.

What is LiquidFrameworks doing to prepare for this required change?

We have tested the impact of enabling the ICU locales to the FieldFX suite of products. Our testing did not uncover any conflicts with FieldFX packages.

What do I need to do to prepare for this required change?

Salesforce has a document that summarizes the steps to take to switch from using the JDK locales to enabling ICU locales instead. Familiarize yourself with the steps that are required and be ready to complete testing on custom code and other apps you may have installed.

Winter '22 Release

My Domain Activation Required

  • Beginning with the Winter '22 release, Salesforce requires that all orgs activate a My Domain.

  • My Domain impacts the URLs that display when navigating FieldFX Back Office.

  • Switching to a custom My Domain reduces potential impacts when Salesforce switches an org to a different Salesforce instance.

  • My Domains have no impact on the operation of FieldFX or any of its modules, but all orgs without a My Domain defined should follow Salesforce’s procedures for activating a My Domain, including thoroughly testing any custom code and integrations in a Sandbox before activating in Production.

  • Be aware of My Domain considerations detailed by Salesforce.

The following orgs already have My Domain enabled:

  • Orgs running FieldFX Lightning

  • Orgs using single sign-on

  • Production orgs created on or after the Winter '21 release

Visualforce Remoting Changes

  • Salesforce is enforcing tighter security for the ways Visualforce pages use Apex controllers.

  • LiquidFrameworks has completed testing with the setting enabled and found no impacts.

  • For details and testing instructions, see the Salesforce help article on the updated requirements.

Summer '21 Release

The Summer '21 Release begins rolling to Sandboxes on April 4, 2021. See Salesforce’s Trust Status page to determine when your org(s) update to Summer '21.

Apex Property Restrictions

Restriction of Apex Controller Methods for Aura Components in Managed Packages

  • Beginning with the Summer '21 release, Salesforce is enforcing an update first introduced in the Summer '17 release.

  • The update enforces a rule on Apex methods that requires methods calling Aura components outside of the package namespace to have a global access modifier. Previously, Aura components outside of a namespace could access non-global methods.

  • See the Salesforce notice.

Access Modifiers on Apex Properties in Lightning Component Markup

  • With this release, Lightning Components are bound by the same access restrictions as other Apex properties.

    For example, a Lightning Component’s markup can no longer access Apex properties marked with an access of private or protected.

  • See the Salesforce notice.

Impacts to FieldFX

  • LiquidFrameworks has tested the impacts of these newly enforced restrictions.

    Aura components and Lightning Components have passed our tests.

Security Announcement - March 31, 2021

Vulnerability in 3rd Party AppExchange App

Summary

  • During a routine security review, Salesforce identified a vulnerability in a Salesforce AppExchange package called Lightning Sharing.

  • The package could allow users access to the org’s sharing permissions.

  • As a result of the vulnerability, Salesforce has removed the package from the AppExchange.

  • The package is no longer required, as a similar functionality was added for all orgs in the Spring '21 Salesforce release.

Recommended Action

  • Orgs with the Lightning Sharing package installed should remove the package and use Salesforce’s sharing settings instead.