New year, new update. With 2023’s arrival just around the corner, the new Salesforce Spring ‘23 Release Notes from the next update have already seen the light of day. It’s time to catch up and find out what’s new in Salesforce to start the year. Are you ready?
What is Salesforce Spring ’23 Release date?
The first organizations to upgrade will begin on January 13th, but until February 11th the upgrade won’t be available in all environments.
Featured news of Spring ‘23 release notes
More dynamic pages
- Dynamic Forms for Leads and Cases: Now this functionality is also available for those objects, in addition to those that previously had it: accounts, person accounts, contacts and opportunities.
- ‘View All’ for Dynamic Related Lists: Finally! Salesforce seems to have listened to us and added the option to view all the records that meet the criteria of a dynamic related list.
An old feature is now in Lightning
Now available in Lightning is the Sharing Hierarchy, which allows us to easily see who has access to a record and why. In addition, it includes users who have access to that locked log using Restriction Rules.
We now have here the change history for Activities
Field history tracking is a feature that is highly demanded by customers and useful in tracking how, by whom, and when a record has changed. We can now carry out this follow up in Activities (Events and Tasks). However, it should be noted that only a maximum of 6 fields can be tracked.
Reports and panels
- Custom Report Filters: We can now include individual dynamic filters which display custom results for each user. Therefore, you no longer need to create multiple reports for each user or use the “see as a specific user” feature, globally.
- Collections in Reports and Panels: It doesn’t matter if you use reports and/or dashboards in different folders. You can now group them in collections and easily access them from Home. In addition, you can manage the visibility of these collections with actions such as pin, hide, or share.
- More Panel Filters (Beta): The filters available for each dashboard will go from the 3, which we currently have, to 5.
- Bye-Bye Process Builder: It isn’t news that Process Builder will disappear. With this new update, the ‘Migrate to Flow’ tool now includes support for converting Process Builder into flows.
- Access external data on a Flow (Beta): Wow! Salesforce continues to go all in on no-code. Now we can query external data through actions that consume Web Services APIs using HTTP Callout.
- Interactive Components (Beta): LWCs that are included in a Screen Flow can communicate with each other without having to navigate to another page.
- Lookup Fields to create records: Hooray! You will no longer need to configure the Lookup Component, but simply select a field of type Lookup. In addition, new records can be created from that field, just as it works in layouts.
- Multi-select picklist improvements: The process of selecting multiple picklist values is simplified. These fields can now be used in the Checkbox Group and Multi-select Choice.
- Choice Lookup Component: No more having to scroll infinitely to find a particular value. This is simplified by a search engine that filters the values for picklists, static values, records, or even external data.
- Execution of screen flows from Slack (Beta): It’s that simple. If you have a Screen Flow without input parameters, you can run it from Slack through a button or shortcut.
What’s new with each cloud
- Collaborative Forecasts: From Salesforce Spring ‘23 on, new customized forecast pages can be created, adding components (both standard and custom) and defining the allocation of each layout according to the user. In addition, custom date fields may be used instead of the ‘Closed Date’.
- Territory Assignment History: Salesforce will make possible to track the allocation of users to territories. Therefore, it will be possible to create reports on who and when a salesperson worked on certain opportunities and analyze performance.
- Wizard para cargar Contactos and Leads: New functionality for Sales Cloud users, which will allow to import contacts and leads easily through a guided process.
- Opportunity Product Splits (Pilot): Salesforce has found that in certain businesses where opportunity and team management are complex, it makes sense to ‘split’ work at the product level rather than opportunity.
- Channel improvements: Especially in Facebook Messenger, where you leverage the structured content that allows you to send links, surveys, schedule meetings, etc. Also, functionalities are added in Voice, such as the recommendation of scripts and actions in real time.
- Einstein for Service: Einstein will now train the case classification model with new fields (not just Subject and Description) and introduce Einstein Conversation Mining (Beta) to build detailed reports.
- Routing: Omni-Channel supervisors will be able to view metrics and filter by skills more accurately in the Wallboard (pilot).
- Lightning Threading: Salesforce transitions to thread management to prevent duplicates and avoid size limits including only new content.
- Improve SEO: Using structured data that will improve page positioning.
- Component enhancements for LWR:
– Create cases directly from the Contact Support Form.
– Rules to control their visibility.
– The Actions bar (Beta) is included.
– Record Detail Component (Beta) to view and edit records.
- Performance improvements: Thanks to the use of Micro-batching.
- B2B and B2C improvements:
– Create B2B Stores with Lightning Web Runtime.
– Create Promotions and automations to apply them in-store.
– Show collections of related products from the page of a product.
– B2B and B2C Stores now accept multiple currencies and countries can be assigned.
– Developer Edition for B2C will be included.
- Improvements in Order Management:
– Create orders as if you were a customer with the Order on Behalf of UI.
– Manage the products of one or more shipments through the Store Fulfillment App.
Field Service Cloud
- Enhanced Scheduling and Optimization: Allows for scheduling appointments of more than one day and reallocating resources temporarily to another territory to meet demand.
- Asset Management: It will allow defining Attributes for each asset to manage repairs more efficiently.
- Mobility Enhancements: Cross-task navigation for iPad, component visualization and customization, and inventory filtering are improved to speed up the process of agents.
- Automotive Cloud: This new cloud is introduced for the Experience Cloud-based automotive industry.
- Consumer Goods: It will now include Analytics – Advanced Data Model app, which will increase insights on business efficiency.
Development (technical) news in Salesforce Spring ‘23
Secure Apex code with database operations in user mode (generally available)
The new Database and Search methods now support a parameter that allows you to run database and search operations in user mode rather than in system mode (default). To improve the Apex security context, you can specify user mode access for database operations. Field-level security (FLS) and user object permissions that you execute are respected in user mode and always apply sharing rules.
You can indicate the mode of operation using WITH USER_MODE or WITH SYSTEM_MODE in your SOQL query. This example specifies how to use them:
Dynamically passing link variables to a SOQL query
With the new Database.queryWithBinds, Database.getQueryLocatorWithBinds, and Database.countQueryWithBinds methods, variables in the query are resolved from a map directly with a key rather than from Apex code variables. As a result, variables do not need to be in scope when the query is run.
Use of the System.enqueueJob method to specify a delay in queue job scheduling
An optional new override adds queue jobs to the asynchronous run queue with a specified minimum delay (0 to 10 minutes). Using the System.enqueue (queueable, delay) method ignores any delay settings in the entire organization’s queue. Note: Delay is ignored during Apex testing.
Removing the Salesforce Platform API Version 21.0 to 30.0
Starting in Summer ’21, we are announcing the removal of API versions. Releases 21.0 to 30.0 of the Salesforce platform API will be removed in Summer ’23. They are now unused and no longer Salesforce compatible.
- 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0
- 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0
- v21.0, v22.0, v23.0, v24.0, v25.0, v26.0, v27.0, v28.0, v29.0, v30.0
Specify a default language for second generation and unlocked managed packets
When you create a new version of a package, you can set a default language for it. Setting a default language allows subscribers to customize the tags of components in the Translation Workbench, even if it doesn’t include translations in the package. If you create a package without specifying a language, the default language is the same that the Dev Hub user who created the package. Previously, this functionality only existed in first-generation managed packages.
Uses the — language when you create a new version of the package and includes the language code displayed in Supported Languages in the Salesforce Help. For example:
- sfdx force:package:version:create -p “Your Package Alias” –-language es
Manages and publishes changes with DevOps Center (GA)
Salesforce finally publishes its DevOps Center that allows changes and releases to be managed through a point-and-click interface or directly from the source control system (or a combination of both).
And all of this is a summary view of the great news that we will see in the first release of the year. However, if you still have any questions regarding Spring ‘23 release notes, do not hesitate to contact the S4G team.