Important Notice
Like Salesforce CRM in other global regions, Salesforce on Alibaba Cloud follows same 3 times per year major release schedule. Our product goal is to keep Salesforce on Alibaba Cloud be identical to rest of the world when compliance permits, this document is a description of the current point in time and will evolve in the future.
Salesforce on Alibaba Cloud CRM Summer'25 Release Notes
This is a review of the features for the Summer'25 Release of Salesforce on Alibaba Cloud, in comparison to the public release notes for the versions outside of China.
For Salesforce Overall, General Enhancements are partially applicable to Salesforce on Alibaba Cloud, but Einstein Search, Salesforce Data Pipelines, Salesforce Archive, Trust Site Enhancements and all Einstein related updates are not applicable to Salesforce on Alibaba Cloud.
Summer'25 Product Update
In the Summer'25 release:
1). Prompt Builder (dependent on CXG LLM Gateway) is officially released.
2). CN Pro Edition (CN PE) is officially released.
3). Loyalty Management is in limited preview by invitation only (the features are currently being tested and do not have production support).
Key Products for Summer'25
CRM Product | Prompt Builder |
Pro Edition - PE - CN | |
Pro Edition - Web Services API - CN | |
Identity for Employees - CN | |
Survey Response Pack (1,000) - CN | |
CXG Product | CXG LLM Gateway |
Release Notes Overview
Feature | Product Family | Enabled for Users | Enabled for admins / developers | Requires admin setup | Description | Alibaba Specific Notes |
Yes |
|
| Lightning Experience is available on multiple editions and recommends using the Salesforce mobile app on mobile devices. Specific browsers and devices are supported, and there are limitations and considerations for third-party browser extensions and JavaScript libraries. |
| ||
|
| Yes | To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of page headers and modal windows when viewed at high magnification. This is the beginning of our effort to comply with WCAG 2.2 Resize and Reflow guidelines. Expect accessibility enhancements to other UI elements in future release updates. |
| ||
Yes |
|
| Ensure that Setup pages in Lightning Experience load content correctly when browsers block third-party cookies. If your users have general access to the internet, no action is required. If your company controls users' or servers' access to the internet through firewalls or allowlists, your IT department must add *.salesforce-setup.com to the company's list of allowed domains. Salesforce Setup pages are now hosted on that domain. | The domain should be *.setup.sfcrmproducts.cn in Salesforce on Alibaba Cloud. | ||
Benefit from Better Lightning Console Performance with Deferred Inactive Workspace Page Loading | Yes |
|
| Lightning Console now defers the loading of inactive workspace pages by default, which minimizes extra page loads and improves performance. An inactive workspace page doesn't load until the user navigates to that page. Regardless of whether the "Defer loading inactive console workspace pages" setting is enabled or disabled, content in pinned regions is always considered active and loads immediately. Previously, if a workspace page opened via a navigation rule, then the page immediately began loading even if the user remained on a different workspace page. | ||
Give Salesforce Platform License Users Access to the Lightning Console App |
|
| Yes | With access to the Lightning Console app, Salesforce Platform and Salesforce Platform Login license users can view multiple records and their related records on the same screen. |
| |
|
| Yes | Empower your greeters by creating better customer experiences by customizing components in lobby management. Greeters can now efficiently check in customers on waitlists by launching and using custom flows. Customize the actions available to greeters on service appointment cards and waitlist participant cards so they can use custom flow actions. Greeters can choose to hide or show waitlist topics with no participants. |
| ||
|
| Yes | This request body has changes. |
| ||
Update Object Permissions for All Custom Permission Sets or Profiles in One Step |
| Yes |
| Save time and clicks by editing object access simultaneously in all custom permission sets and profiles. There's no need to go to individual permission set or profile pages. In Object Manager, go to a specific object's access summary to review, add, or remove object permissions. |
| |
| Yes |
| Instead of going to many Setup pages, you can now update the user, object, field, and custom permissions in a permission set directly from the summary view. Previously, you were able to make only minimal permissions edits in the summary. |
| ||
Manage Included Permission Sets in the Permission Set Group Summary |
| Yes |
| Edit which permission sets are included in a permission set group without leaving the summary view. Previously, this information was read only, so this update makes it easier to take action while reviewing the permission set group. |
| |
| Yes |
| Easily see the tabs that a user can access or the tabs included in a permission set or permission set group. Using the summary views is faster than searching through multiple Setup pages, which was previously required to get this information. |
| ||
View and Manage a User's Permission Sets, Groups, and Queues More Easily |
| Yes |
| If you want to know what permission sets, groups, and queues a user is assigned to, you're in luck. With enhancements to the user access summary, you can add or remove a user from one or more permission sets, groups, or queues. You can also search, sort, and refresh the lists in each summary section. |
| |
| Yes |
| Now you can augment Agentforce workflows with external data. When you create a prompt template, select an external object and then access that object's fields just as you would with a custom or standard object. A common use case is when you have order and fulfillment data stored in an external system and you want to create a Salesforce agent that looks up the status of an order. | While Agentforce is not available in Salesforce on Alibaba Cloud, importing external data into Prompt Builder prompts. | ||
| Yes |
| Access data outside of your Salesforce org without worrying about limits. We removed the limits for new rows and callouts for these adapters: OData 2.0, OData 4.0, OData 4.01, Custom, GraphQL, Amazon DynamoDB, and the SQL adapters for Amazon Athena and Snowflake. This change is available for orgs hosted on Hyperforce. |
| ||
Enable Secure Roles Behavior and Update Sharing Group References in Production (Release Update) |
|
| Yes | To prevent unintended access by external site users if you enable digital experiences, Salesforce now secures access to records. The default sharing group that's available for roles and subordinates before you enable digital experiences is now displayed as Roles and Internal Subordinates instead of as Roles and Subordinates. To prepare for this change, update code and customizations that reference the old group name. Although Salesforce dynamically converts outdated references during a transition period, you must update all code and customizations to prevent errors. This update is available starting in Summer'25. |
| |
Enable Secure Roles Behavior and Update Sharing Group References in Sandboxes (Release Update) |
|
| Yes | To prevent unintended access by external site users if you enable digital experiences, Salesforce now secures access to records in non-preview sandbox orgs. The default sharing group that's available for roles and subordinates before you enable digital experiences is now displayed as Roles and Internal Subordinates instead of as Roles and Subordinates. To prepare for this change, update code and customizations that reference the old group name. This update was first available in Spring'25 and is enforced in Summer'25. |
| |
| Yes |
| To improve performance for large-scale transactions, Salesforce is changing how some sharing recalculations work behind the scenes. When group membership or role updates occur, related sharing rules are automatically recalculated. Previously, both of these operations always ran synchronously. Now, after group membership or role updates occur, related owner-based sharing rules can be recalculated asynchronously when that approach results in better performance. You can monitor these stages in the Setup Audit Trail. |
| ||
| Yes |
| With this update, the International Components for Unicode (ICU) locale formats replace Oracle's Java Development Kit (JDK) locale formats in Salesforce. Locales control the format for dates, times, currencies, addresses, names, numeric values, and the start day of the week. ICU sets the international standard for these formats. The ICU locale formats provide a consistent experience across the platform and improve integration with ICU-compliant applications across the globe. This update was first made available in Winter'20 and will be enabled in Summer'25 on orgs that haven't already switched to ICU locale formats and whose Apex Classes, Apex Triggers, and Visualforce Pages are using API version 45 or higher. |
| ||
| Yes |
| To start the conversion process for unrecoverable state and country/territory picklist mappings, clear your picklist mappings. This ensures accurate and consistent data as you transition from text-based state and country fields to picklists. Clearing data mappings is only intended for use when individually editing your picklist mapping isn't possible. |
| ||
| Yes |
| To improve accuracy and your users' experience, we updated the translations for some standard object, tab, and field names for these languages: Arabic, Bulgarian, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Portuguese (European), Romanian, Russian, Slovak, Slovenian, Spanish, Spanish (Mexico), Swedish, Thai, Turkish, and Ukrainian. |
| ||
Get the Desktop Dynamic Related List Experience on Mobile (Beta) |
|
| Yes | Give your users the same great experience of Dynamic Related Lists on desktop and mobile. Previously, the Dynamic Related List - Single component rendered only on record pages on desktop, and you configured a Single Related List component to render on mobile devices. Now, you configure one component for both experiences. |
| |
Yes |
|
| When you set up a related-list quick filter for the Record Type field, you now select the Value options from a multi-select picklist of available record types. Previously, you typed the Value options into a free-form text field, which sometimes returned incorrect filtering results. |
| ||
Enhance Accessibility with the Improved List Views Dropdown Menu | Yes |
|
| To improve accessibility and provide a more consistent user experience, the list views dropdown menu for all objects now uses Lightning Web Components (LWC). Overall, how your users work in list views hasn't changed, but the updated dropdown menu has some differences. Previously, the updated list views dropdown menu was available only for list views rendered with LWC and not for list views rendered with Aura. |
| |
Troubleshoot a Deployment That Contains a Custom Field Type Conversion |
| Yes |
| You can get an error when you use the metadata deploy() method or run a package upgrade and either of these deployments contains the conversion of a custom field from one data type to another. The error occurs if a deployment changes the data type of one or more custom fields and the objects that contain the affected custom fields contain a large amount of data. The limit is 85 million custom field type conversions. |
| |
| Yes |
| When you attempt to delete a custom object, if another standard object, custom object, or a Data Cloud data model object (DMO) contains a lookup field that references that custom object, you'll now see a more detailed page. This page includes a table that lists the objects that have relationships and now shows you the object API name and the field API name. The object API name is hyperlinked so you can go directly to the object and remove the relationship. If the object that contains the relationship field is a Data Cloud DMO, you can follow the provided help link to complete the process of removing the relationship. |
| ||
| Yes |
| The truncation of some record page text, especially noticeable at high browser zoom levels, has been removed to improve accessibility. This change applies to most field types in the Highlights Panel and Dynamic Highlights Panel, and to the section header text in the Record Detail component and in Dynamic Forms field sections. Base component level truncation remains unaffected. |
| ||
Select, Cut, and Paste Components More Easily When Using a Keyboard |
| Yes |
| In the Lightning App Builder, you can now use the Enter key to activate the component insertion icons before and after a component when cutting and pasting components with a keyboard. You can also use the Enter key to select a highlighted component on the canvas and navigate to its properties or delete it. Previously, although you could highlight the icons by tabbing through the canvas, you couldn't activate them to insert a component. |
| |
| Yes |
| The components available for a change set vary by edition. |
| ||
| Yes |
| Update the API version for your components to use new features and improvements. Versioning your Lightning web components ensures that your existing components aren't affected when Salesforce ships new features, bug fixes, and performance improvements that change existing behavior. Versioning also helps Salesforce deprecate legacy features. |
| ||
Resolve Errors Related to Accessing Referenced Lightning Components |
| Yes |
| Salesforce performs strict access checks when Aura components and Lightning web components (LWC) import or reference other components or modules. If you receive a No {COMPONENT or MODULE} named {component or module name} found error, check your imports before deploying to an org. If you're an ISV partner, confirm that the Lightning components and modules in your managed packages are exposed to subscribers. |
| |
Preview a Single Lightning Web Component Using Local Dev (Beta) |
|
| Yes | You can now configure Local Dev to run a real-time preview of a single Lightning web component. Previously, you had to publish a component to an org before you could preview it using Local Dev. |
| |
| Yes |
| We've expanded the documentation for Lightning base components. The documentation now provides more guidance in their usage. It also describes the advantages of using them to customize your Lightning apps and components. Our documentation now uses the name "Lightning base components" instead of "base Lightning components" for consistent terminology. |
| ||
Internal DOM Structure Is Changing for Lightning Base Components |
| Yes |
| Salesforce is preparing the base components for native shadow DOM to enhance performance and comply with Web Components standards. These updates change the internal DOM structure. Make sure that your tests don't rely on the previous internal structure of these components. |
| |
Migrate Lightning Web Components Projects to ESLint v9 Before Spring'26 | Yes |
|
| To help you write more consistent and modern JavaScript for your components, Lightning Web Components now supports ESLint v9. This version introduces improved performance, enhanced rules management, and improved plugin management. We recommend that you upgrade to v9 before Spring'26 because we're planning to end support for ESLint v8 in Winter'26. |
| |
| Yes |
| Improve your LWC development experience using the type definitions for Lightning base components. TypeScript for LWC is in developer preview and has several limitations. |
| ||
| Yes |
| Lightning Web Security includes new security protections with additional distortions for web APIs. ESLint rules matching the distortions are also available. |
| ||
Yes |
|
| Get more out of SLDS component blueprints and utilities with recent enhancements and bug fixes. |
| ||
Update Your Lightning Components to SLDS 2 with SLDS Linter (Beta) | Yes |
|
| Validate your code against Salesforce Lightning Design System 2 (SLDS 2 beta) rules with SLDS Linter (beta). Scan your code with SLDS Linter, then automatically fix your code and apply those suggestions in bulk across your repository. |
| |
Yes |
|
| Use SLDS Validator to improve your Salesforce Lightning Design System (SLDS) code. Scan your code, validate it against a set of SLDS guidelines, and use SLDS Validator suggestions and its auto-fix capability to update your code. |
| ||
| Yes |
| Write more concise code by using the new parseAsTemplate() method in the FormulaBuilder class. The parseAsTemplate() method evaluates a dynamic formula in template mode. In template mode, you can create formula expressions where values are interpolated into a string by using the merge field syntax {!Object_Name.Field_Name}. Compared to traditional string concatenation, this syntax makes your code cleaner and more readable. |
| ||
Specify an Org-Wide Enablement of Debug Logs During Metadata Deployment |
|
| Yes | Generating debug logs during a metadata deployment can cause longer test execution and is disabled by default. However, admins can choose to enable debug logs during metadata deployment via this setting, in conjunction with an active debug log trace flag. Enabling the debug log in the DebuggingHeader overrides this setting. |
| |
Enhance Invocable Apex Configuration Designs with New Action Extension Metadata (Developer Preview) |
| Yes |
| Use the InvocableActionExtension (Developer Preview) metadata type to specify how to present your action's inputs. You can set the order of inputs and provide descriptions and labels, as well as add extended attributes for Apex actions and types, ultimately improving the user experience within low-code tools like Flow Builder. The overall development experience has improved by giving you more control over the configuration experience without having to code a custom property editor (CPE). |
| |
Use Your Org's My Domain Login URL in API Calls (Release Update) |
|
| Yes | To prevent disruption after infrastructure updates that change your instance name, make sure that API traffic to your org uses the org's My Domain login URL. This update is available starting in Summer'25. |
| |
Salesforce Platform API Versions 21.0 Through 30.0 Retirement (Release Update) |
|
| Yes | The retirement of versions 21.0 through 30.0 of the Salesforce Platform API was first scheduled for Summer'23. The retirement is now postponed to Summer'25. These API versions are not supported and won’t be available starting in Summer'25. Applications consuming them are then disrupted. Requests fail with an error message indicating that the endpoint is deactivated. Upgrade all applications that use a legacy API version to a current version before this breaking change occurs. |
| |
Get Notified About Composite API Requests with EventLogFile Event Types |
| Yes |
| Query the EventLogFile object for the CompositeApi and CompositeApiSubrequest event types to get details about composite API and composite graph API requests and subrequests. |
| |
Other Improvements to Generating an OpenAPI Document for sObjects REST API (Beta) |
|
| Yes | With the latest version of the OpenAPI specification, you can query for all available resources and use a wildcard character in URIs. |
| |
| Yes |
| When retrieving metadata types, use the new rootTypesWithDependencies parameter on the RetrieveRequest object to request metadata types and their dependencies. |
| ||
Know When the Synchronous Compile on Deploy Setting Is Enabled in Sandboxes |
| Yes |
| The Deployment Status page in sandboxes now displays a banner when the Perform Synchronous Compile on Deploy setting for Apex is enabled. |
| |
Yes |
|
| The Metadata Coverage Report has been redesigned and moved to a new location. The old Metadata Coverage Report will be removed in the Summer'25 release. | Metadata coverage will be the same, but some listed features may not exist on Alibaba Cloud. For example, "Agentforce for Developers Settings" has metadata API coverage, but is not available for Salesforce on Alibaba Cloud. | ||
|
| Yes | You can now enable developers working in your org to deploy and retrieve pilot metadata types. Pilot metadata types are only guaranteed to work with the current API version and can be changed or removed in future releases. |
| ||
View Package Metadata Usage for Unlocked and Second-Generation Managed Packages |
| Yes |
| Determine whether the package you're building is approaching the metadata file size limit, or the maximum number of metadata files for a package. To view these details, use the Salesforce CLI sf package version report command. |
| |
| Yes |
| The Run Logs tab in Data Mask is now the Jobs tab. From a list view in the Jobs tab, you can click the Data Mask name to view specific information about each mask, such as configured objects, current job progress, and any errors thrown by the current job. |
| ||
Automate the Running of Data Mask Processes with Job Scheduler (Beta) |
| Yes |
| Configure how frequently you run Data Mask, daily, weekly, or monthly, to mask all new data in your sandbox. |
| |
| Yes |
| We've optimized the record loading and transformation so Data Mask jobs complete faster. When it completes a job, Data Mask now bypasses automation rather than deactivating or reactivating when a job is complete. Data Mask deletes field-history tracking instead of turning it off for the masking process. Serial mode is removed as jobs automatically retry records when row-locked. | Einstein mask generation is not available. | ||
| Yes |
| Stay up to date with recent Salesforce CLI enhancements so that you can learn about better ways to work with your Salesforce DX projects. | Salesforce CLI setup requires a different configuration for Salesforce on Alibaba Cloud. Please refer to the setup instructions in the Salesforce on Alibaba Cloud Architecture Guide. | ||
| Yes |
| The Salesforce Extension pack includes tools for developing on the Salesforce platform in the lightweight, extensible VS Code editor. These tools provide features for working with development orgs (scratch orgs, sandboxes, and DE orgs), Apex, Lightning web components, Aura components, and Visualforce. | |||
|
| Yes | The system property sun.nio.cs.map for Japanese character mapping from Shift_JIS to Windows-31J is no longer available. | |||
| Yes |
| With Change Data Capture, you can now receive notifications of record changes for more objects. |
| ||
| Yes |
| You can now view your Apex platform event trigger's configuration in Setup by checking the new Batch Size and User columns. Having this information available in the UI makes it easier to monitor your trigger's configuration and fine-tune it. Previously, the batch size and user information were available only via Tooling API or Metadata API in PlatformEventSubscriberConfig. |
| ||
The Timeout of Outbound Messages Is Reduced to 20 Seconds from 60 Seconds |
| Yes |
| With the lower timeout value, the system makes better use of resources and can process more messages. Also, the lower timeout value prevents long-running messages from delaying the processing of other messages in the queue. |
| |
| Yes |
| We renamed the "Oldest failures in queue" heading to "Oldest messages in queue" on the Outbound Messages page in Setup. The renamed heading helps you identify the queued messages. The queue contains messages that didn't fail but haven't been delivered yet, in addition to messages that failed delivery. |
| ||
Streaming API Clients Can Receive Disconnect Messages from Salesforce App Servers |
| Yes |
| In Streaming API version 64.0 and later, clients can sometimes be disconnected and must reconnect to the Streaming API endpoint. The disconnects, which happen more frequently when using a Hyperforce instance, are due to infrastructure auto-scaling. To keep the subscription active, add a listener for the /meta/disconnect channel and reconnect after receiving a disconnect message. |
| |
Yes |
|
| Simplify your users' daily tasks by integrating generative-AI powered by prompt templates into their workflow. | Access External Data in Prompt Builder is applicable. Furthermore, Optimize Prompt Development with Step-by-Step Visuals in Prompt Builder is applicable. | ||
| Yes |
| A new session timeout notification for LWR and enhanced LWR sites notifies authenticated users 5 minutes before their session is due to end. The notification gives users time to save their work and avoid being logged out unexpectedly. If they click Cancel, they're redirected to the login page when the session ends. |
| ||
Aura Record Field Information Icons in Experience Builder Sites Have Changed |
| Yes |
| To improve accessibility, the information icon on Aura record field components now defaults to a gray color, regardless of the site's theme. When site visitors hover over the icon, its color changes to the site's Action Color. This change aligns the icon's behavior with that of the Lightning record field experience. Previously, the information icon on Aura record fields appeared in the site's Detail Text Color on both display and hover. On mobile devices, information icon text now opens in a tooltip, matching desktop behavior. |
| |
Use the File Upload Enhanced Lightning Web Component with Aura and LWR Sites (Beta) |
| Yes |
| To upload files to Aura and Lightning Web Runtime (LWR) sites, and Lightning Experience, use the new File Upload Enhanced (Beta) flow screen component. To require users to upload a file, set the Required field to true. Previously, there was no File Upload component available for LWR sites. |
| |
|
| Yes | Upgrade existing LWR sites to enhanced LWR sites to take advantage of the latest features, including partial deployment, enhanced CMS workspaces and channels, expression-based visibility, and more. This update was first available in Spring'25. |
| ||
Help Your Site Visitors View Records More Easily with the New Record List Component |
| Yes |
| The Record List component for LWR sites helps your site visitors view, search, and sort their accounts, cases, and other data. With properties for component customization and styling, you can make sure that your visitors have a smooth and responsive experience across desktop, tablet, and mobile devices. |
| |
Enable a Modernized Record Experience in Aura Sites (Release Update) |
| Yes |
| Upgrade the Create Record Form, Record Banner, and Record Detail components to run on Lightning Web Component technology, which improves accessibility and performance. In Summer'25, the upgrade is enforced for all orgs. We strongly recommend that you test all customized record components before the update. |
| |
| Yes |
| To enhance security, email verification is now mandatory for users creating new sites. Email verification makes sure that new sites are associated only with a verified senderʼs email address. The email address of the sender must also be verified to send welcome emails to new members of a site. | CDN changes do not apply to Salesforce on Alibaba Cloud. | ||
|
| Yes | To simplify the process of building a registration handler for single sign-on (SSO) into your Experience Cloud site, use Flow Builder instead of Apex. Customize the new Authentication Provider User Registration flow template to create and update users who log in to your site via a third-party identity provider. | |||
|
| Yes | With this beta feature, you can now use Dynamic Related Lists on mobile. Previously, the Dynamic Related List - Single component rendered only on record pages on desktop, and you configured a Single Related List component to render on mobile devices. |
| ||
Set Up Mobile Features and Notifications By Using the External Client App Framework (Beta) |
| Yes |
| With three new plugins, you can now use an external client app to configure mobile features. The mobile app plugin for external client apps turns on mobile-specific features, such as screen lock upon a custom timeout value. The push notification plugin enables a mobile app's push notifications for an Android or iOS device. With the new notifications plugin, you can configure your mobile app to receive custom notifications. | Push notifications are not available on Salesforce on Alibaba Cloud. | |
Customize Seller-Focused Mobile Experience (Generally Available) |
| Yes |
| Add native pages for custom objects and customize the layout of record home pages in Seller-Focused Mobile Experience. Mobile Builder for Seller-Focused Experience is now generally available. |
| |
Yes |
|
| Comply with your company's security standards when you now limit who can export and publish from Quota Planning to territory-based forecast types in Pipeline Forecasting. |
| ||
|
| Yes | Work with large volumes of data without losing context when you freeze specific columns and headings with Quota Planning. Now when sales operations work on quota plans, Territory and Owner columns and table headings remain in a fixed position. |
| ||
Build a Modern Partner Portal with the Updated Partner Central 2.0 Template |
|
| Yes | Elevate your partner portal experience with the new Partner Central 2.0 template. This refreshed UI, built on the Aura framework, allows Partner Experience Builders to create sleek and intuitive portals using Lightning Web Components (LWCs) layered on Aura. This update enhances navigation and usability, providing partners with updated sales, enablement, and analytics pages. Best of all, it doesn't require a full migration. |
| |
| Yes |
| Now you can get related records in a single query in Flow Builder, making it easier to manage related records. Previously, you managed related records by adding separate Get Records elements. With the Get Records element, you can select related object relationships, which can help you reflect complex business logic. Related records in the Get Records element are available in screen flows, autolaunched flows, and template-triggered prompt flows. |
| ||
| Yes |
| When searching for and selecting resources in Flow Builder, you can choose to expand your search to include results from an expanded set of resources, like fields from records and related actions, components, and outputs. This feature was previously released in Winter'25, but was later removed. We're reintroducing this feature after addressing customer feedback. |
| ||
| Yes |
| Use resources and fields of the Time data type to process data where only the time of day matters and not the associated date. You can specify the time of the day down to the exact millisecond. The Time data type is available across flow elements, formula builder, expression builder, subflows, and resources such as variables and constants. It's also available in input and output to and from invocable actions. The time data type isn't supported in the offline flows available on the Salesforce Mobile app. |
| ||
| Yes |
| After selecting a picklist value, to make your selection clearer and easier to understand, the selection is rendered as a pill with an easy-to-read label. Previously, picklist selections were shown with API names, which could vary significantly from the provided labels. For example, a picklist option labeled "True" could appear as the value "1" after selecting it. |
| ||
Select an Entire Resource More Efficiently When Browsing Through a Resource |
| Yes |
| The new Entire Resource menu item on the resource selection menu streamlines how to select the entire resource that you're currently browsing. Previously, to select the entire resource, you had to select the resource from the resource menu, and then click out of the menu without selecting a specific field. |
| |
| Yes |
| With the new Has Error operator, you can configure negative assertions in a flow test. Intentionally test flow paths where things don't go according to plan, ensuring that your flows handle errors gracefully. Previously, you configured only positive assertions that tested for successful outcomes, which left gaps in your testing. The Has Error operator is available in flow tests for record-triggered and data cloud-triggered flows. Select the Has Error operator to configure negative assertions for Create Records, Update Records, Delete Records, and Action elements. |
| ||
Zoom Through the Flow Builder Canvas with Touch Gestures and Keyboard Shortcuts |
| Yes |
| You can now zoom in and out of the Flow Builder canvas using pinch-to-zoom gestures. |
| |
Select Resources Efficiently for More Elements When Adding Fields and Values | Yes |
|
| With this update, Flow Builder makes it easier to select resources for Start element triggers for schedule-triggered flows and for Update Records, Get Records, and Delete Records elements for all flow types. We now group the fields and values of manually selected objects with clearer labels to help you identify and select resources more easily. |
| |
Easily Discover and Add an Asynchronous Path in Record-Triggered Flows | Yes |
|
| When creating a Record-Triggered flow, you must add an asynchronous path when the flow involves external systems. The Add Asynchronous Path toggle is now more prominently displayed on the Start node, ensuring you don't overlook this crucial step for successful integrations. Additionally, if you attempt to add an action to the immediate path with a callout without enabling the Add Asynchronous Path toggle, a warning appears to ensure your flow can proceed correctly. |
| |
Build on Your Successes by Saving an Existing Flow as a Template | Yes |
|
| Whether you have a flow that performs well or took you a long time to finalize, it's now easier to save a flow as a template for future use. On the flow properties window, you now have the option to Save as Template, which will add the flow to the templates available when creating a new flow. |
| |
Manage Elements Faster in Auto-Layout Mode for All Flow Types | Yes |
|
| Improved element cards in the Flow Builder canvas make it easier to create and edit flows. The element cards offer a larger selection area, one-click access to the configuration panel, quick access to common element actions, and an improved canvas experience with less visual noise. These element cards are now available for all flow types in auto-layout mode. |
| |
Keep Users on One Flow Screen with Automatically Triggered Screen Actions (Generally Available) |
| Yes |
| Make your flow screens dynamic by running flows in the background automatically. With screen actions you can use additional flow logic without the user leaving the screen. When a user enters a value into a screen component, they see the results of that logic, and updates to the screen in real time. Screen actions help you build screen flows with fewer screens and provide an improved user experience. By default, automatically triggered screen actions run any time their input values are updated, and any time the screen loads, except when a user gets to a screen by clicking the Previous button on the next screen. |
| |
Get Better Usability with the File Upload Enhanced Flow Screen Component (Beta) |
| Yes |
| The new File Upload Enhanced (beta) flow screen component is similar to the existing File Upload screen component but has some enhancements. Now your users can upload files in screen flows in both Aura and Lightning Web Runtime (LWR) sites and in Lightning Experience. Also, you can require users to upload documents before moving on in the flow. |
| |
Get More Control Over Component and Field Layout in Screen Flows | Yes |
|
| Customize the width of screen components and record fields, whether they're in section columns or not. Additionally, tweak the vertical alignment of components and fields to optimize the way that they’re positioned relative to each other. |
| |
See How Your Screen Looks in Real Time on Different Screen Sizes | Yes |
|
| Check how your screen appears on large, medium, or small devices with the Preview Size feature. Identify and fix any layout issues during design time so that your screens always look great, no matter the device. |
| |
Help Users Make Selections Faster by Adding Icons to Choice Resources | Yes |
|
| Reduce the cognitive load on your users by adding icons to each of their choices in choice resources. Icons convey information at a glance, reducing the amount of text users must read and process. Choice resources with icons can only be used in Choice Lookup and Visual Picker components. Additionally, these choice resources must be of the text data type. |
| |
Display Choices in Tiles with the Visual Picker Component in Screen Flows | Yes |
|
| You can make choices in screen flows more visually engaging with the Visual Picker Component. Combining icons and text, the Visual Picker component helps users quickly select what they need without scrolling through long lists or dropdown menus. |
| |
| Yes |
| Build screen flows to help your users create draft autolaunched flow approval processes. Get input from a user and then call the new Create Flow Approval Process action to draft an autolaunched flow approval process with up to 20 levels of approvals. The draft can also contain final actions and a recall path. After creation, configure the flow approval process elements in Flow Builder. |
| ||
Use a Dynamic Action to Call a Flow Approval Process from a Flow |
| Yes |
| Use a flow to gather information about an approval submission before starting the associated flow approval process. Build an autolaunched flow to collect relevant data. Then add an Action element that calls the appropriate active, autolaunched flow approval process from your flow. To make the flow available to users after you test and activate the flow, add a custom button to the page layout for the affected object. |
| |
Yes |
|
| Configure your Send Email action with clearly organized input sections for recipients, senders, and email content. Switch between versions of the Send Email Action to control the visibility and organization of email content configuration parameters. Create your email content directly in the Send Email action without creating a text template resource first. Select an existing template by name instead of bringing the email template ID into the flow. Enhance your Flow Builder email actions with the new CC and BCC Recipient Address Collection fields. Choose a sender type, enter a sender email address, select an email template, attach files, and choose a specific record more easily. Log your email only if you provide a recipient or a related record ID. Add threading tokens to Body and Subject only if you provide a related record ID. Attaching files to emails in Flow Builder is easier now that you can provide a text collection variable in the Attachment ID Collection field in the Send Email action. |
| ||
| Yes |
| The debugging experience for flows now includes element-level summaries to help you understand more quickly what happened at each point in a flow. For example, for an Update Records element, the Debug Details pane shows at a glance how many elements were updated after the element was executed. Previously, element-level summaries were available only when debugging marketing flows. |
| ||
| Yes |
| Debug support is now available for data graph-triggered flows. |
| ||
| Yes |
| If your flow includes a send email or send SMS action, you can send a test message as part of your debug run. When setting up your debug run, specify the email addresses or phone numbers that you want to use to test your message. When you start the debug run, we'll attempt to send the message to the specified recipients. | SMS Sends are unavailable on Salesforce on Alibaba Cloud. | ||
| Yes |
| We made some improvements to the debug experience to make your debug results easier to navigate and understand. In the debug panel, each element run appears in a separate card, with easily skimmable information. Element cards load dynamically as you scroll for improved performance. To optimize your view of the debug results, you can now resize the width of the debug panel to see more of the debug results, or more of the Flow Builder canvas. The debug panel also now includes search functionality, so that you can quickly find and highlight what you're looking for. For the Create Records, Get Records, Update Records, Delete Records, Collection Filter, and Collection Sort elements, complex data types are now rendered in a code block using JSON formatting with syntax highlighting, making the information easier to digest. You can also copy the entire debug log with a click. |
| ||
| Yes |
| Get new flow updates with these versioned changes. |
| ||
| Yes |
| Integrate flow tests into your regression testing, unit testing, and continuous integration and continuous delivery (CI/CD) process. Use Salesforce CLI to run flow tests seamlessly in more channels, enhancing your testing capabilities. For example, before rolling out changes to your org, you can add flow tests in your CI/CD process to make sure that the changes don't break existing flows or Apex code. Previously, you ran a set of tests manually for each flow in Flow Builder, which was time-consuming and prone to oversight. |
| ||
Debug Flows More Easily by Viewing Output Resources in Flow Builder | Yes |
|
| The configuration panel in Flow Builder has a new View Output Resources section that displays output parameters and resources, such as output names and labels, data types, and descriptions. Use this section to help you debug flows and make sure that they're using the correct outputs, leading to more accurate and user-friendly flow designs. You can also sort output parameters and manually assign variables if needed. |
| |
| Yes |
| Flow Builder now supports multiple input controls, providing a flexible and user-friendly way to specify input values with ongoing enhancements to support more input types. You can switch between different input modes, this includes the resource picker you're familiar with and new modes that you can select from a picklist. |
| ||
Add Extended Metadata Annotations for Invocable Actions (Developer Preview) |
| Yes |
| Use the InvocableActionExt (Developer Preview) metadata type to specify how to present inputs and outputs, such as setting the order of inputs or providing descriptions and labels. With this change, action developers can add extended attributes for Apex actions and types, enhancing the user experience in low-code tools like Flow Builder. This change also improves the overall development experience by making it easier to configure complex actions. |
| |
|
| Yes | In order to allow access to certain standard classes that are available to be used as invocable action parameters, we're enforcing a change for built-in Apex actions that also enforces the visibility of the no-argument constructor on any class. This release update was first available in Summer'24 and was scheduled to be enforced in Winter'26, but we postponed the enforcement date to Summer'26. This release update was previously named Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs (Release Update). |
| ||
|
| Yes | This update was first made available in Winter'24 and was scheduled to be enforced in Winter'25, but we postponed the enforcement to Winter'26. With this update enabled, Salesforce restricts a user's ability to run a flow. A user must be granted the correct profile or permission set to run the flow. When enabled, this release update deprecates the FlowSites org permission, which gave all users in the org access to run any flow. With this update, flows run more securely because only users who are granted correct profiles or permission sets can run flows. Salesforce postponed the enforcement to allow additional time for admins to test and prepare for the change. There is no impact to admins who already enabled the update. |
| ||
| Yes |
| Create an autolaunched flow approval process from within the Approvals app. The wizard makes it easy to set up a draft process with up to 3 levels of approvals, final actions, and a recall path. For more flexibility, you also have the option to build an autolaunched flow approval process from scratch by using Flow Builder. |
| ||
| Yes |
| Want to get information about an approval submission before it's submitted for review? Call the new dynamic Request an Approval action from any flow that supports asynchronous paths. After the flow gets the information you need, add an Action element that calls the appropriate active autolaunched flow approval process. |
| ||
| Yes |
| You can now add a recall path to a flow approval process. A recall path contains a stage with background steps that run when someone recalls their approval submission. When the submission is recalled, the stage that was running and its related steps are canceled, and open approval work items are also canceled. The stage in the recall path then runs. When the stage in the recall path is completed, the approval submission is then recalled. |
| ||
Complete Approval Work Items in the Work Guide as a Delegate | Yes |
|
| When the Flow Orchestration Work Guide is added to an object's record page layout, it lists all open approval work items assigned to the approver viewing the record page. Now delegates can also see and complete open approval work items in the Work Guide. |
| |
| Yes |
| When an in-progress approval submission has an issue or is no longer needed, you can now cancel it. If an approval submission is associated with a flow approval process that has a configured recall path, canceling the approval submission doesn't perform any actions from the recall path. |
| ||
| Yes |
| Learn about improvements to Flow Approval Processes. |
| ||
| Yes |
| Define what happens when an orchestration encounters an error by using fault paths. To add error handling, configure a fault path for each stage in your orchestration. Then add elements to each fault path that executes if the attached stage or a step within the attached stage have an error. The elements on a fault path are run only when an error occurs in the attached stage. The ability to use fault paths in an orchestration means that you can reduce the risk of your orchestration ending in an error. |
| ||
| Yes |
| Learn about improvements to Flow Orchestration. |
| ||
|
| Yes | Prevent disruption for your customers and end users when the temporary redirection of legacy (non-enhanced) Salesforce host names ends. With this release update, legacy host name redirections end in production and demo orgs. Those redirections already ended in all other orgs in Winter'25. This update was first available in Spring'25 and is enforced in Spring'26. | Domains work differently for Salesforce on Alibaba Cloud. Please refer to Salesforce on Alibaba Cloud CRM feature differences (Summer'25 Release) for details. | ||
|
| Yes | To prevent disruption after infrastructure updates that change your instance name, replace instanced URLs in API traffic with your org's My Domain login URL. | |||
Enhance Your Mobile App With Three New Plugins for External Client Apps (Beta) |
| Yes |
| You can now configure mobile features and notifications by using the External Client App framework. With the new mobile app plugin for external client apps, you can set up mobile-specific features, such as screen lock upon a custom timeout value. With the new push notification plugin, you can turn on a mobile app's push notifications for an Android or iOS device. With the new notifications plugin, you can configure your mobile app to receive custom notifications. | Salesforce on Alibaba Cloud for Android is not yet available. Push notifications not supported. | |
|
| Yes | Set up single sign-on (SSO) with clicks instead of code. When you use the authentication provider framework for SSO into Salesforce, build your registration handler with Flow Builder instead of with Apex. Get a head start on your flow design with a new template. The template shows you how to create and update users who log in to your org or Experience Cloud site via a third-party identity provider. It includes two new invocable actions that help you get user information from the identity provider and create complete user records. It also gives you an easy way to manage user access without the mixed DML errors that you get in Apex. With flow, control user access by adding and removing permission sets at runtime in a single assignment. |
| ||
| Yes |
| To simplify the process of creating and updating users for single sign-on (SSO) configurations that use the authentication provider framework, we made it easier to access information that’s returned by the identity provider. If the identity provider returns a user info response or an ID token, we now automatically expose this information in the Apex Auth.UserData object. With the user info response and ID token automatically exposed, it's easier to set up your registration handler to access complex claims for advanced use cases. |
| ||
Migrate to a Multiple-Configuration SAML Framework (Release Update) |
| Yes |
| If you see this release update, your Salesforce instance uses our original single-configuration SAML framework, which supports single sign-on (SSO) with only one external identity provider. With this release update, we're removing support for the single-configuration SAML framework and supporting only the multiple-configuration SAML framework. To preserve your existing configuration, follow the steps to apply this update. Otherwise, your SSO configuration stops working when this update is enforced for production instances in Spring'26. |
| |
| Yes |
| Salesforce is upgrading its SAML framework as part of regular ongoing maintenance. This maintenance update improves the Salesforce security posture and, as a result, improves your security posture. This update can impact integrations that use SAML, including single sign-on (SSO) and single logout. This update was first announced in Winter'25 and is enforced in Summer'25. To avoid potential service interruptions, test your SAML integrations as soon as Summer'25 sandboxes become available. |
| ||
Triple Data Encryption Standard (Triple DES) for SAML Single Sign-On Stops Working in Winter'26 |
| Yes |
| In Winter'26, SAML single sign-on (SSO) configurations that use the Triple Data Encryption Standard (Triple DES) algorithm stop working. This change applies to all SSO configurations that use the Triple DES algorithm, whether you use Salesforce as an identity provider or as a service provider. To improve security, use the Advanced Encryption Standard (AES) algorithms, AES 128 or AES 256, instead. |
| |
Control JWT-Based Access Token Enablement as an App Developer |
| Yes |
| For external client apps and connected apps, we removed the ability for subscribers to control whether JSON Web Token (JWT)-based access tokens are enabled in the app policies. If a developer enables JWT-based access tokens in the app settings, all installed versions of the app automatically issue JWT-based access tokens. |
| |
See Which Sessions Are Associated with JWT-Based Access Tokens |
| Yes |
| To track and manage sessions more precisely, you can now determine which sessions are associated with JSON Web Token (JWT)-based access tokens. On the Session Management page in Setup, create a view that includes the new Associated with JWT field. |
| |
Login Type Is Changed for a Session Associated With Lightning Experience Logins |
| Yes |
| For consistency, we changed the login type for one of the sessions that's established when a user logs in. Previously, the login type for this session was Unknown. Now, the login type for this session is Application. |
| |
Take Advantage of Accessibility Improvements for Login Error Messages | Yes |
|
| To improve accessibility, we updated two error messages that are displayed on the Salesforce login page. Each message now starts with an "Error" prefix as a visual indicator. |
| |
| Yes |
| To encourage users to use caution when they approve access for an external client app or connected app, we added a warning message to the OAuth app approval page. |
| ||
| Yes |
| Find the New Connected App button on the External Client App Settings page. This functionality is controlled by the Allow creation of connected apps preference, which is disabled by default for new orgs. Now that external client apps support OAuth, SAML, and many of the same use cases as connected apps, we recommend that you use external client apps whenever possible. External client apps are now created in App Manager. |
| ||
|
| Yes | The New External Client App button is now available in Setup on App Manager. With SAML available in addition to OAuth, external client apps are more useful than ever. These features make external client apps the clear choice for connecting external applications with all of your Salesforce data. Connected apps can now be created in External Client App Settings. |
| ||
Integrate Service Providers as External Client Apps with SAML 2.0 |
|
| Yes | Use the SAML settings for external client apps to integrate a service provider with your Salesforce org. Set up SAML single sign-on when the service provider or identity provider initiates the flow. |
| |
Built-In Authenticators and WebAuthn Security Keys Are Allowed by Default in New Orgs |
| Yes |
| To give users access to phishing-proof identity verification methods, the settings to allow verification with WebAuthn-based methods are enabled by default in new orgs. Users can register built-in authenticators such as Touch ID or Windows Hello and physical security keys such as U2F keys. They can use these methods to complete identity verification challenges such as multi-factor authentication (MFA). |
| |
Explore Information About Suspicious Login Activity with the Login Anomaly Event |
|
| Yes | Investigate when there is an unusual login attempt, such as a login at an atypical time of day or uncommon end-point with the new Login Anomaly event from the Threat Detection app. |
| |
|
| Yes | Access and investigate crucial threat detection event information by default. Threat Detection data storage is now automatically enabled for all threat detection events, giving you immediate access to critical data. |
| ||
|
| Yes | Trigger automated actions and create cases with ease by using Platform-Event triggered flows powered by select Real Time Events. |
| ||
|
| Yes | Generate real-time events and create Transaction Security Policies when users access the Recently Viewed list view so that you can monitor and take action to block malicious users. |
| ||
|
| Yes | Leverage near real-time insights into Salesforce Apex HTTP callouts with the new distributed tracing feature, which publishes Apex callout spans as Platform Events. Built to be compatible with third-party solutions, this feature significantly reduces mean time to recovery (MTTR) during service disruptions. |
| ||
|
| Yes | Database Encryption is now available for testing in sandboxes for certain Hyperforce orgs. Database Encryption allows you to sort, filter and reference encrypted data without functional or performance tradeoffs. You can still apply Field Level Encryption to individual fields if required. |
| ||
Benefit from an Improved Deterministic Tenant Secret Workflow |
|
| Yes | When you generate or rotate deterministic encryption tenant secrets, a new in-app assistant helps you avoid issues that can occur with sync jobs for deterministic tenant secrets. |
| |
|
| Yes | The Crypto class now supports AES-GCM (Advanced Encryption Standards Galois Counter Mode) for 256-bit encryption for encryption and decryption operations. AES-GCM increases security by using a different initialization vector (IV) for each encryption. This change also includes support for the 256-bit, 384-bit, and 512-bit P1363 signature format for signing and verifying. |
| ||
Track Blocked Redirections from Hyperlinks in Salesforce Classic |
| Yes |
| To help you maintain your Trusted URLs for Redirects allowlist, Salesforce now logs blocked redirections that originate from hyperlinks in URL and Long Text Area Fields in Salesforce Classic. Previously, the Trusted URL and Browser Policy Violations list and Blocked Redirect event type captured blocked redirections only within components and pages. |
| |
Secure Redirections from Hyperlinks in Lightning Experience (Beta) |
| Yes |
| Protect your users by limiting redirections from hyperlinks in URL fields to only the external URLs that you trust. You can block those redirections or show a warning message that requires the user to confirm that they want to leave Salesforce before they're redirected. This feature is newly available to users that access Salesforce via Lightning Experience. |
| |
| Yes |
| Test changes to your Content Security Policy (CSP) with more confidence. Salesforce now records all CSP violations that originate from Lightning for the img-src (image), font-src (fonts), and frame-src (iframe content) directives. Previously, Salesforce sampled resource violations, which meant that resource violations generated for testing purposes rarely generated a CSP violation event. |
| ||
Update Your Trusted URLs for the Latest CSP Directives (Release Update) |
|
| Yes | This update has been canceled. We continue to encourage you to work the Trusted URL and Browser Policy Violations list in Setup and to enable Adopt updated CSP directives in Session Settings. Also, that setting continues to be enabled by default in new orgs. |
| |
Yes |
|
| Use Prompt Builder to alter the length and tone of Einstein Email Summaries for your business needs. |
| ||
| Yes |
| With this new organization preference, end users are notified when Email-to-Case can't process the email they sent to your organization. |
| ||
| Yes |
| The EmailMessage.AutomationType field is now set to AI-Assisted for EmailMessage records created by Draft with Einstein, including saved drafts and emails sent without being saved as a draft. |
| ||
| Yes |
| When enabled, this release update replaces the email editor in the docked and case feed email composers. This update was generally available in Lightning Experience in Spring'24 and has no scheduled enforcement date. |
| ||
Disable Ref ID and Transition to New Email Threading Behavior (Release Update) |
| Yes |
| This update turns off Ref ID threading and transitions to Lightning threading in Email-to-Case. With the new Email-to-Case threading behavior, incoming emails aren't matched using Ref IDs. Instead, they're matched using a secure token in the email subject or body. If no match is found, Email-to-Case checks metadata from the email headers. This update was first available in Winter'21 and has no scheduled enforcement date. |
| |
Hourly Single Email Send Limit Updated for Case Lightning Email Composer | Yes |
|
| The hourly single email send limit now includes emails sent using the Case Lightning Email Composer. This change ensures that each user can send emails to a maximum of 250 external recipients per hour. |
| |
Set Up SLA Management Faster with the New Simplified Setup Experience (Beta) | Yes |
|
| Configure SLA Management (previously Entitlement Management) with fewer steps with a simplified user interface. The new configuration interface is more intuitive and accessible, reduces implementation efforts, and improves the overall user experience. In this setup, you can define rules to automatically mark milestones complete. Also, you can automate entitlement mapping so that entitlements are attached to cases, work orders, and incidents based on predefined rules. Switch to the new setup experience to explore automation capabilities and streamline your processes and enhance efficiency. |
| |
Improve Customer Engagement with Rich Text and Media in Case Comments (Beta) | Yes |
|
| Add rich text and media to your case comments to improve communication with your customers. Use formatting effects in your comments to make them easier to read. Include images and videos to provide context and clarity and document your interactions better. The rich text supported field replaces the plain text field for case comments. After you enable the rich text supported field, you can't go back to using the plain text field. |
| |
Boost Rep Efficiency and Minimize Violations by Automatically Mapping Entitlements | Yes |
|
| Automatically map entitlements to the corresponding cases, work orders, and incidents based on predefined rules. This change boosts rep efficiency, minimizes SLA violations, and simplifies administration by eliminating the need to map entitlements to each case, work order, or incident. If needed, service reps can manually change the entitlement auto-applied to a case. |
| |
Yes |
|
| Create a more visually engaging survey experience by using dynamic emoji for rating questions. Dynamic emoji offer a variety of expressions to make the experience more engaging for your participants. |
| ||
Get a Visual Representation of Participants' Survey Progress | Yes |
|
| Participants can see how much they have progressed in the survey with a visual progress bar indicator that shows the percentage of progress. This update makes it easier for participants to stay on track and to see how much they have left to go. |
| |
Yes |
|
| Gather more comprehensive and accurate survey data by allowing users to upload up to 20 attachments per survey. Distribute these attachments across multiple attachment questions in the survey or allocate them all to a single attachment question. Using this option, respondents can add context and detail to their responses, with which you can make better decisions. |
| ||
Improve Response Rates by Creating Surveys with Compatible URLs |
|
| Yes | Make sure your survey invitations reach their intended recipients by turning on compatible survey URLs. These URls prevent security apps from blocking the invitations and increases the likelihood of respondents completing your survey. |
| |
Gather Feedback to Improve Your Knowledge Base (Generally Available) |
|
| Yes | Use Knowledge Feedback to capture feedback on your Knowledge articles and assign feedback responses to the appropriate people or teams for action. It's a great way to see how useful your articles are and to identify areas for improvement. This feature helps keep your articles relevant and up to date, making sure that responses are accurate and helpful. | ||
Yes |
|
| Quickly locate the information that you need in Knowledge articles with the automatically generated Table of Contents (TOC) within articles. The TOC provides a clear overview of the articles, making it easy to jump to sections of interest. It improves content discoverability and navigation, and enhances the user experience by providing a consistent structure across articles. You can add the TOC to new and existing articles in your knowledge base, but only to those in HTML format, not PDFs or other nonHTML formats. |
| ||
Yes |
|
| The improved Lightning Article Editor helps you write Knowledge articles more efficiently and take advantage of streamlined features to create great content. |
|