To ensure a smooth transition, each critical update has an opt-in period, which ends on the auto-activation date that’s displayed on the Critical Updates page in Setup. During this period, you can manually activate and deactivate the update as often as you need to evaluate the impact on your org and modify affected customizations. After the opt-in period has passed, the update is activated. For more details, see Respond to Critical Updates.
New Critical Updates
These critical updates are new in Spring ’19.
- Turn On Lightning Experience (Critical Update)
- Salesforce will turn on Lightning Experience on a rolling basis starting in Winter ‘20 to empower users to move faster, do more, and be more productive. We encourage everyone to start preparing to transition to Lightning Experience soon so that your users can benefit from everything the new interface has to offer. The future of the Salesforce user experience and platform is Salesforce Lightning. Moving forward, all innovations will be in Lightning Experience. Take advantage of the lead time before Lightning Experience is turned on to understand how your org’s features and customizations perform in the new interface and to prepare your users via change management. Start now to ensure a better experience for everyone when Lightning Experience is turned on later. Better yet, take control and turn on Lightning Experience for your users before this update is auto-activated, on your terms.
- Open a Window into Productivity with Pop-Out Utilities (Critical Update)
- Pop utilities out of the utility bar and into their own separate windows. You can arrange popped-out utilities, even move them onto different monitors. You can interact with a popped-out utility alongside your main window, making multitasking a breeze. When you’re done using the utility, pop it back into your utility bar or close the window.
- Enable External Org-Wide Defaults in Orgs with Communities or Portals (Critical Update)
- This update enables the External Sharing Model and provides admins with a list of objects whose default external access settings must be reviewed. This update helps you secure your data by letting you set more restrictive levels of access for external users. Before Spring ‘19, org-wide defaults gave internal and external users the same default access to objects. After activating this update, external org-wide defaults are enabled in all orgs with communities or portals.
- Return Null Values in Process and Flow Formulas (Critical Update)
- This update enables process and flow formulas to return null values when the calculations involve a null record variable or null lookup relationship field.
- Enable Manual Account Sharing in Enterprise Territory Management (Critical Update)
- This update changes the TerritoryManual reason code in AccountShare records to Territory2AssociationManual and is required to let users share accounts manually with territory groups. After you activate the update in production, it can take up to two weeks before you see the changes.
- Convert Guided Action List Settings into Deployments in Setup (Critical Update)
- Migrate your existing Guided Action List settings into deployments that you manage in Setup. You can then reuse a Guided Action List configuration on different record pages and orgs. As of Spring ’19, you can no longer configure these settings in component properties. Instead, use deployments that you manage in Setup. To simplify the transition, perform a one-time migration of your existing settings into deployments.
- Enable Improved Caching of Org Schema
- This critical update enables improved caching of org schema details and resolves known issues with version-specific object and field handling.
Pre-Existing Critical Updates
These critical updates were announced in a previous release and are still available.
- Add a Namespace Prefix to pageReference.state Properties and Query Parameters
- As mentioned in the Spring ’19 release notes, this critical update addresses an issue with naming conflicts between package components. A namespace prefix distinguishes your package and its contents from other developers' packages. The namespace prefix prevents conflicts between components on the state or query parameter name. Query parameters and pageReference.state properties must have a namespace prefix. If they don’t, this critical update removes them from the org's URLs. This critical update is enabled for Summer ’19 on May 17, 2019.
- Open Hyperlinks in Formula Fields Correctly
- As mentioned in the Spring ’19 release notes, this critical update addresses an issue when opening hyperlinks in formula fields. If you have formula fields that contain a HYPERLINK function, Lightning Experience ignores the target value when attempting to open the link. This critical update ensures that the target value for hyperlinks is honored, whether it’s explicitly configured or set by default. This critical update is enabled in Summer ’19 on May 17, 2019.
Postponed Critical Updates
These critical updates were announced in a previous release and the auto-activation date was postponed.
- Postponed “Remove Instance Names from URLs for Visualforce, Community Builder, Site.com Studio, and Content Files” Critical Update
- This critical update, released in Spring ’18, was scheduled for auto-activation in Spring ’19, but has been postponed to Winter ’20.
- “Stop Automated Field Updates from Suppressing Email Notifications” Critical Update Postponed
- This critical update, released in Summer ‘17, was scheduled for auto-activation in Spring ‘19 but has been postponed to March 1, 2020 GMT.