重要提示
与全球其他地区的 Salesforce CRM 一样，阿里云上的 Salesforce CRM 也遵循每年三次的主要发布时间表。我们的产品目标，是在合规的情况下让阿里云上的 Salesforce 与全球其他地方的 Salesforce 尽可能保持一致。本文档是对当前时间点产品差异化的描述，并将不断迭代更新。
阿里云上的Salesforce CRM Summer'25夏季版发布说明
本文是对阿里云上的Salesforce 核心 CRM Summer'25 夏季版的更新总结，与中国以外版本的公开更新公告进行对比。
对于Salesforce整体，常规增强功能部分适用于阿里云上的Salesforce，但Einstein Search、Salesforce Data Pipelines、Salesforce Archive 、Trust Site Enhancements 以及所有 Einstein 相关更新均不适用。
Summer'25夏季版产品更新
我们在 Summer'25夏季版中：
1）正式发布Prompt Builder（依赖CXG AI Connector）；
2）正式发布 CN Pro Edition（CN专业版，简称CN PE）；
3）以邀测形式提供 Loyalty Management 相关产品的预览发布（暂不提供产品支持）。
Summer'25 夏季版关键发布
CRM 产品 | Prompt Builder |
Pro Edition - PE - CN | |
Pro Edition - Web Services API - CN | |
Identity for Employees - CN | |
Survey Response Pack (1,000) - CN | |
CXG 产品 | CXG AI Connector |
发布说明概述
功能 | 产品族 | 为所有用户启用 | 为管理员/开发者启用 | 需要管理员设置 | 说明 | 针对阿里云上的Salesforce 的特别说明 |
是 |
|
| Lightning Experience 支持多个版本，推荐在移动设备上使用 Salesforce mobile app。它支持特定的浏览器和设备，但第三方浏览器扩展程序和 JavaScript 库的使用存在一些限制和注意事项。 |
| ||
|
| 是 | 启用 Lightning Experience，使其在高放大倍率下调整页面标题和模态窗口的行为，以更好地符合 Web Content Accessibility Guidelines (WCAG) 2.2 中关于 Resize 和 Reflow 的要求。这是我们努力遵守 WCAG 2.2 Resize 和 Reflow 指南所作的初步工作。未来的版本更新中将对其他 UI 元素进行辅助功能增强。 |
| ||
是 |
|
| 为了确保 Lightning Experience 中的设置页面在浏览器阻止第三方 Cookie 时也能正确加载内容，如果贵公司通过防火墙或白名单控制用户或服务器对互联网的访问，则您的 IT 部门必须将 *.salesforce-setup.com 添加到公司允许的域名列表中。Salesforce 设置页面现在托管在该域名下。如果您的用户可以正常访问互联网，则无需采取任何操作。 | 在阿里云上的Salesforce 中，应该是*.setup.sfcrmproducts.cn。 | ||
是 |
|
| Lightning Console 现在默认延迟加载非活动工作区页面，从而最大限度地减少页面加载并提高性能。只有当用户导航到非活动工作区页面时，该页面才会加载。无论“延迟加载非活动控制台工作区页面”设置是启用还是禁用，固定区域中的内容始终被视为活动状态并立即加载。此前，如果通过导航规则打开工作区页面，即使用户停留在不同的工作区页面上，该页面也会立即开始加载。 | |||
|
| 是 | 通过访问 Lightning Console 应用程序，Salesforce Platform 和 Salesforce Platform Login 许可证用户可以在同一屏幕上查看多个记录及其相关记录。 |
| ||
|
| 是 | 通过自定义等候区管理中的组件，赋能接待员，打造更好的客户体验。接待员现在可以通过启动和使用自定义流来高效地为等候名单上的客户办理登记。此外，还可以自定义服务预约卡和等候名单参与者卡上的操作，使接待员能够使用自定义流操作。接待员还可以选择隐藏或显示没有参与者的等候名单主题。 |
| ||
|
| 是 | 此请求正文已更新。 |
| ||
| 是 |
| 您可以在对象管理器中同时编辑所有自定义权限集和简档的对象访问权限。无需分别访问每个权限集或简档页面。只需要转到特定对象的访问摘，即可查看、添加或删除对象权限。 |
| ||
| 是 |
| 现在，您无需访问多个设置页面，即可直接从摘要视图更新权限集中的用户、对象、字段和自定义权限。此前，您只能在摘要中进行最少的权限编辑。 |
| ||
| 是 |
| 现在，您无需离开摘要视图，即可直接编辑权限集组中包含的权限集。此前，此信息为只读，此更新让您在查看权限集组时更便捷地进行管理。 |
| ||
| 是 |
| 现在，您可以直接在访问摘要中查看用户可访问的选项卡，以及权限集或权限及组中包含的选项卡。相比之前需要在多个设置页面中进行搜索，使用摘要视图更加快捷。 |
| ||
| 是 |
| 现在您可以更轻松地查看和管理用户的权限集、组和队列分配。通过用户访问摘要，您可以将用户添加至或移除出一个或多个权限集、组或队列。您还可以搜索、排序和刷新每个摘要部分的列表。 |
| ||
| 是 |
| 现在，您可以通过使用外部数据增强 Agentforce 工作流。创建提示模板时，你可以选择一个外部对象，并像使用自定义对象或标准对象一样访问其字段。例如，当您的订单和履行数据存储在外部系统中，并且您想要创建一个 Salesforce 代理来查找订单状态时，即可使用此功能。 | 虽然 Agentforce 在阿里云上的Salesforce 中不可用，但您仍然可以在 Prompt Builder 提示中导入外部数据。 | ||
| 是 |
| 访问 Salesforce 组织外部的数据，无需担心限制。我们取消了以下适配器的新行和调用的限制：OData 2.0、OData 4.0、OData 4.01、Custom、GraphQL、Amazon DynamoDB 以及用于 Amazon Athena 和 Snowflake 的 SQL 适配器。此更改适用于托管在 Hyperforce 上的组织。 |
| ||
|
| 是 | 为了防止在启用数字体验时外部站点用户意外访问，Salesforce 现已增强了记录访问的安全性。角色及其下属可用的默认共享组名称已从 "Roles and Subordinates" 更新为 "Roles and Internal Subordinates"。为避免将来出现错误，请更新所有引用旧组名称（"Roles and Subordinates"）的代码和自定义设置。Salesforce 会在 Summer '25 后的过渡期内动态转换过时的引用，但我们仍强烈建议您尽快完成更新。此更新将于 Summer '25 正式推出。 |
| ||
|
| 是 | Salesforce 现已增强了非预览 Sandbox 环境中记录访问的安全性。角色及其下属可用的默认共享组名称已从 "Roles and Subordinates" 更新为 "Roles and Internal Subordinates"。请更新所有引用旧组名称（"Roles and Subordinates"）的代码和自定义设置，为强制执行做好准备。此更新已于 Spring '25 推出，并将于 Summer '25 正式强制执行。 |
| ||
| 是 |
| 为了提升大规模事务的性能，Salesforce 正在更改部分共享重新计算的后台处理机制。组成员资格或角色更新后，相关的共享规则会自动重新计算。此前，这两个操作始终同步运行。现在，当异步方法可以带来更好的性能时，则相关的基于所有者的共享规则会在组成员资格或角色更新后异步重新计算。您可以在 Setup Audit Trail 中监控这些阶段。 |
| ||
| 是 |
| 此更新，将使用International Components for Unicode (ICU) 区域设置格式将替换 Salesforce 中 Oracle 的 Java Development Kit (JDK) 区域设置格式。区域设置控制日期、时间、货币、地址、姓名、数值和一周开始日期的格式。ICU 为这些格式设置了国际标准。ICU 区域设置格式可在整个平台上提供一致的体验，并改进与全球符合 ICU 标准的应用程序的集成。此更新在 Winter '20 中首次推出，并将于 Summer '25 在尚未切换到 ICU 区域设置格式且其 Apex Classes、Apex Triggers 和 Visualforce Pages 使用 API 版本 45 或更高版本的组织上启用。 |
| ||
| 是 |
| 要转换不可恢复的州/省和国家/地区选择列表映射，请清除您的选择列表映射。这可确保在您从基于文本的州/省和国家/地区字段转换为选择列表的过程中，数据准确性和一致性。仅当无法单独编辑选择列表映射的情况时，才建议执行此清除操作。 |
| ||
| 是 |
| 为了提升准确性和用户体验，我们更新了部分标准对象、选项卡和字段名称在以下语言中的翻译：阿拉伯语、保加利亚语、中文（简体）、中文（繁体）、克罗地亚语、捷克语、丹麦语、荷兰语、芬兰语、法语、德语、希腊语、希伯来语、匈牙利语、印度尼西亚语、意大利语、日语、韩语、波兰语、葡萄牙语（巴西）、葡萄牙语（欧洲）、罗马尼亚语、俄语、斯洛伐克语、斯洛文尼亚语、西班牙语、西班牙语（墨西哥）、瑞典语、泰语、土耳其语和乌克兰语。 |
| ||
|
| 是 | 现在，移动设备也能享受到与桌面版相同的 Dynamic Related Lists 体验。此前，Dynamic Related List - Single 组件仅在桌面的记录页面上呈现，您需要配置 Single Related List 组件才能在移动设备上显示。现在，只需要配置一个组件即可同时支持桌面端和移动端。 |
| ||
是 |
|
| 现在，设置“记录类型”字段的相关列表快速筛选器更加简便。您只需从多选选择列表中选择所需的记录类型即可。此前，您需要在自由格式文本字段中手动输入记录类型的值，这有时会导致筛选结果不准确。 |
| ||
是 |
|
| 为了提升可访问性并提供更一致的用户体验，现在所有对象的列表视图下拉菜单均使用 Lightning Web Components (LWC)。用户在列表视图中的工作方式总体上保持不变，但更新后的下拉菜单有一些改进。此前，更新后的列表视图下拉菜单仅适用于使用 LWC 呈现的列表视图，而不适用于使用 Aura 呈现的列表视图。 |
| ||
| 是 |
| 当使用 |
| ||
| 是 |
| 当您尝试删除自定义对象时，如果其他标准对象、自定义对象或 Data Cloud 数据模型对象 (DMO) 包含引用该自定义对象的查找字段，您将看到一个更详细的页面。该页面包含一个表格，列出了具有相关关系的对象、对象 API 名称以及字段 API 名称。对象 API 名称带有超链接，您可以点击它直接前往该对象并移除关系。如果包含关系字段的对象是 Data Cloud DMO，您可以点击页面提供的帮助链接完成移除关系的操作。 |
| ||
| 是 |
| 为了提升可访问性，我们取消了某些记录页面文本的截断显示，该问题在浏览器高缩放级别下尤其明显。此更改适用于 Highlights Panel 和 Dynamic Highlights Panel 中的大多数字段类型，以及 Record Detail 组件和 Dynamic Forms 字段部分中的节标题文本。基本组件级别的截断保持不变。 |
| ||
| 是 |
| 在 Lightning App Builder 中，现在可以使用 Enter 键激活组件前后插入图标，从而使用键盘剪切和粘贴组件。您还可以使用 Enter 键选择画布上高亮显示的组件，并导航到其属性或将其删除。以前，虽然您可以通过在画布中使用 Tab 键突出高亮显示图标，但无法激活它们来插入组件。 |
| ||
| 是 |
| 不同版本的更改集中可用的组件有所不同。 |
| ||
| 是 |
| 更新组件的 API 版本，即可使用新功能和改进。对 Lightning Web 组件进行版本控制，可确保在 Salesforce 发布更改现有行为的新功能、错误修复和性能改进时，现有组件不会受到影响。版本控制还有助于 Salesforce 淘汰旧功能。 |
| ||
| 是 |
| 当 Aura 组件和 Lightning Web 组件 (LWC) 导入或引用其他组件或模块时，Salesforce 会执行严格的访问检查。如果遇到“找不到名为 {component or module name} 的 {COMPONENT 或 MODULE}”错误，请在部署到组织之前检查您的导入。如果您是 ISV 合作伙伴，请确保您托管包中的 Lightning 组件和模块已对订阅者公开。 |
| ||
|
| 是 | 您现在可以将本地开发实时预览单个 Lightning Web 组件。此前，您必须将组件发布到组织，然后才能使用本地开发进行预览。 |
| ||
| 是 |
| 我们扩展了 Lightning 基础组件的文档，现在提供了更多关于使用指南，并介绍了使用它们来自定义 Lightning 应用程序和组件的优势。为了保持术语一致，我们的文档现在使用名称“Lightning 基础组件”而不是“基础 Lightning 组件”。 |
| ||
| 是 |
| 为了提升性能并符合Web Components 标准，Salesforce 正在为Lightning 基础组件适配 native shadow DOM。这些更新会更改内部 DOM 结构。请确保您的测试不依赖于这些组件之前的内部结构。 |
| ||
是 |
|
| 为了帮助您为组件编写更一致、更现代的 JavaScript 代码，Lightning Web Components 现已支持 ESLint v9。此版本提升了性能、增强了规则管理和插件管理。我们建议您在 Spring '26 之前升级到 v9，因为我们计划在 Winter '26 中停止支持 ESLint v8。 |
| ||
| 是 |
| 使用 Lightning 基础组件的类型定义可以改善 LWC 开发体验。用于 LWC 的 TypeScript 处于开发者预览阶段，并且有一些限制。 |
| ||
| 是 |
| Lightning Web Security 新增了针对 Web API 的其他失真，此外，还提供了与失真匹配的 ESLint 规则。 |
| ||
是 |
|
| SLDS 组件蓝图和实用程序的最新增强和错误修复，让您获益更多。 |
| ||
是 |
|
| 使用 SLDS Linter（测试版）根据 Salesforce Lightning Design System 2 (SLDS 2 测试版) 规则验证您的代码。SLDS Linter 可以扫描代码，自动修复问题，并在存储库中批量应用建议。 |
| ||
是 |
|
| 使用 SLDS Validator 改进您的Salesforce Lightning Design System (SLDS) 代码。扫描代码，根据 SLDS 指南进行验证，并使用 SLDS Validator 的建议和自动修复功能更新代码。 |
| ||
| 是 |
| 通过使用 FormulaBuilder 类中的新方法 |
| ||
| 是 | 在元数据部署期间生成调试日志会导致测试执行时间延长，并且默认情况下处于禁用状态。但是，管理员可以选择通过此设置以及活动的调试日志跟踪标志在元数据部署期间启用调试日志。在 DebuggingHeader 中启用调试日志会覆盖此设置。 |
| |||
| 是 |
| 使用 InvocableActionExtension（开发者预览）元数据类型来指定操作输入的呈现方式。您可以设置输入的顺序、提供描述和标签，以及为 Apex 操作和类型添加扩展属性，最终改善低代码工具（如 Flow Builder）中的用户体验。无需编写自定义属性编辑器 (CPE) 即可更好地控制配置体验，从而改善了整体开发体验。 |
| ||
|
| 是 | 为防止更改实例名称的基础架构更新后出现中断，请确保到组织的 API 流量使用组织的 My Domain 登录 URL。此更新自 Summer '25 起可用。 |
| ||
|
| 是 | Salesforce 平台 API 21.0 至 30.0 版本的停用已从 Summer '23 推迟到 Summer '25。这些 API 版本不受支持，并且从 Summer '25 开始将不可用。使用它们的应用程序届时将中断。请求将失败，并显示一条错误消息，指示端点已停用。在此重大更改发生之前，请将所有使用旧 API 版本的应用程序升级到当前版本。 |
| ||
是 |
| 查询 EventLogFile 对象的 |
| |||
|
| 是 | 使用最新版本的 OpenAPI 规范，您可以查询所有可用资源并在 URI 中使用通配符。 |
| ||
| 是 |
| 检索元数据类型时，使用 RetrieveRequest 对象上的新 |
| ||
| 是 |
| 在沙盒中，启用 Apex 的“部署时执行同步编译”设置后，“部署状态”页面会显示一个横幅。 |
| ||
是 |
|
| 元数据覆盖率报告已重新设计并移至新位置。旧版报告将在 Summer '25 版本中移除。 | 元数据覆盖范围保持不变，但某些列出的功能在阿里云上可能不存在。例如，“Agentforce for Developers Settings” 具有元数据 API 覆盖范围，但在阿里云上的 Salesforce 中不可用。 | ||
|
| 是 | 现在，您可以允许组织中的开发人员部署和检索试点元数据类型。试点元数据类型仅保证可用于当前 API 版本，并可能在未来版本中更改或移除。 |
| ||
| 是 |
| 确定您正在构建的包是否接近元数据文件大小限制或包的最大元数据文件数。请使用 Salesforce CLI sf package version report 命令查看这些详细信息。 |
| ||
| 是 |
| 数据屏蔽中的“运行日志”选项卡已更名为“作业”选项卡。在“作业”选项卡的列表视图中，您可以单击数据屏蔽名称来查看每个屏蔽的特定信息，例如已配置的对象、当前作业进度以及当前作业发生的错误。 |
| ||
| 是 |
| 配置运行数据屏蔽的频率（每天、每周或每月），以屏蔽沙盒中的所有新数据。 |
| ||
| 是 |
| 我们优化了记录加载和转换，使数据屏蔽作业完成得更快。作业完成后，数据屏蔽现在会绕过自动化，而不是在作业完成时停用或重新激活。数据屏蔽会删除字段历史跟踪，而不是在屏蔽过程中将其关闭。由于作业在行锁定后会自动重试记录，因此移除了串行模式。 | Einstein 屏蔽生成在阿里云上的Salesforce不可用。 | ||
| 是 |
| 及时了解最新的 Salesforce CLI 增强功能，以了解使用 Salesforce DX 项目的更好方法。 | 在阿里云上的Salesforce CLI 设置需要不同的 Salesforce 配置。请参阅《阿里云上的Salesforce中国架构数据手册》中的设置说明。 | ||
| 是 |
| Salesforce 扩展包包含在轻量级、可扩展的 VS Code 编辑器中在 Salesforce 平台上进行开发的工具。这些工具提供了一些功能，可用于处理开发组织（Scratch Org、Sandbox 和 DE Org）、Apex、Lightning Web 组件、Aura 组件和 Visualforce。 |
| ||
|
| 是 | 系统属性 |
| ||
| 是 |
| 使用更改数据捕获，现在可以接收更多对象的记录更改通知。 |
| ||
| 是 |
| 现在，您可以在“设置”中查看 Apex 平台事件触发器的配置，其中包含新的“批大小”和“用户”列。UI 中提供这些信息，使监控和微调触发器配置更加轻松。此前，批大小和用户信息只能通过 |
| ||
| 是 |
| 更低的超时值使系统可以更好地利用资源并处理更多消息。此外，它还可以防止长时间运行的消息延迟队列中其他消息的处理。 |
| ||
| 是 |
| 在“设置”的“出站消息”页面上，我们将“队列中最旧的失败”标题重命名为“队列中最旧的消息”。此更改可帮助您识别队列中的消息，其中包含传递失败的消息以及未失败但尚未传递的消息。 |
| ||
| 是 |
| 在 Streaming API 64.0 及更高版本中，客户端有时可能会断开连接，必须重新连接到 Streaming API 端点。使用 Hyperforce 实例时，由于基础架构自动扩展，断开连接的频率会更高。要保持订阅活动状态，请为 |
| ||
是 |
|
| 将基于提示模板的生成式 AI 集成到用户工作流中，简化用户的日常任务。 | Prompt Builder 支持访问外部数据，同时支持使用分步可视化优化Prompt开发。 | ||
| 是 |
| LWR 和增强型 LWR 站点新增会话超时通知功能，会在用户会话结束前 5 分钟通知已登录用户。该通知使用户有时间保存工作并避免意外注销。如果用户单击“取消”，则会在会话结束时重定向到登录页面。 |
| ||
| 是 |
| 为了提高可访问性，Aura 记录字段组件上的信息图标现在默认为灰色，与站点主题无关。当站点访问者将鼠标悬停在图标上时，其颜色会更改为站点的操作颜色。此更改使图标的行为与 Lightning 记录字段体验一致。以前，Aura 记录字段上的信息图标在显示和悬停时都显示为站点的“详细信息文本颜色”。现在，在移动设备上，信息图标文本会在工具提示中打开，与桌面行为一致。 |
| ||
| 是 |
| 要将文件上传到 Aura 和 LWR 站点以及 Lightning Experience，请使用新的文件上传增强型（测试版）流屏幕组件。要求用户上传文件，请将“必需”字段设置为 true。此前，LWR 站点没有可用的文件上传组件。 |
| ||
|
| 是 | 将现有的 LWR 站点升级到增强型 LWR 站点，以利用最新功能，包括部分部署、增强的 CMS 工作区和渠道、基于表达式的可见性等。此更新已最早于 Spring '25 中可用。 |
| ||
| 是 |
| LWR 站点的记录列表组件可帮助站点访问者查看、搜索和排序其客户、个案和其他数据。借助组件自定义和样式设置属性，您可以确保访问者在桌面、平板电脑和移动设备上获得流畅的响应式体验。 |
| ||
| 是 |
| 将“创建记录表单”、“记录横幅”和“记录详细信息”组件升级到 Lightning Web 组件技术，以提高可访问性和性能。Summer '25 将对所有组织强制执行此升级。强烈建议您在更新之前测试所有自定义记录组件。 |
| ||
| 是 |
| 为了增强安全性，现在强制要求创建新站点的用户进行电子邮件验证。电子邮件验证可确保新站点仅与已验证的发件人电子邮件地址关联。要向站点的新成员发送欢迎电子邮件，发件人的电子邮件地址也必须经过验证。 | CDN 变更不适用于阿里云上的Salesforce。 | ||
|
| 是 | 要简化 Experience Cloud 站点中单点登录 (SSO) 注册处理程序的构建过程，请使用 Flow Builder 而不是 Apex。自定义新的“身份验证提供商用户注册”流模板，以创建和更新通过第三方身份提供商登录到您站点的用户。 | |||
|
| 是 | 借助此测试版功能，您现在可以在移动设备上使用动态相关列表。以前，“动态相关列表 - 单个”组件仅在桌面的记录页面上呈现，并且，您需要配置“单个相关列表”组件才能在移动设备上呈现。 |
| ||
是 |
| 现在，您可以使用三个新的插件通过外部客户端应用程序配置移动功能。移动应用程序插件启用特定于移动设备的功能，例如在自定义超时值后锁定屏幕。推送通知插件启用移动应用程序在 Android 或 iOS 设备上的推送通知。通知插件允许您将移动应用程序配置为接收自定义通知。 | 推送通知在阿里云上的Salesforce 不可用。 | |||
| 是 |
| 在以销售人员为中心的移动体验中添加自定义对象的原生页面并自定义记录主页的布局。用于以销售人员为中心体验的 Mobile Builder 现已正式发布。 |
| ||
是 |
|
| 现在，您可以限制哪些用户可以将“配额计划”导出和发布到 Pipeline Forecasting 中基于区域的预测类型，从而遵守公司的安全标准。 |
| ||
|
| 是 | 在配额计划中冻结特定列和标题，即使处理大量数据也不会丢失上下文。现在，在销售运营处理配额计划时，“区域”和“所有者”列以及表格标题会保持固定位置。 |
| ||
|
| 是 | 使用新的 Partner Central 2.0 模板提升合作伙伴门户体验。此模板基于 Aura 框架构建，焕然一新的 UI 允许合作伙伴体验构建器使用基于 Aura 的 Lightning Web 组件 (LWC) 创建流畅直观的门户。此更新增强了导航和可用性，为合作伙伴提供了更新的销售、支持和分析页面。最重要的是，它不需要完全迁移。 |
| ||
| 是 |
| 现在，您可以在 Flow Builder 中使用单个查询获取相关记录，从而更轻松地管理相关记录。以前，您需要添加单独的“获取记录”元素来管理相关记录。现在，使用“获取记录”元素，您可以选择相关的对象关系，从而反映复杂的业务逻辑。相关记录功能适用于屏幕流、自动启动流和模板触发的提示流。 |
| ||
| 是 |
| 在 Flow Builder 中搜索和选择资源时，您可以选择扩展搜索范围，包含更多资源，例如来自记录的字段和相关操作、组件和输出。此功能曾在 Winter '25 中发布，后被移除。现在，我们根据客户反馈重新引入了此功能。 |
| ||
| 是 |
| 使用时间数据类型的资源和字段处理仅时间相关的数据。您可以精确到毫秒指定时间。时间数据类型可用于流元素、公式构建器、表达式构建器、子流以及变量和常量等资源。它也适用于可调用操作的输入和输出。Salesforce 移动应用程序上的离线流不支持时间数据类型。 |
| ||
| 是 |
| 选择选项列表值后，为了使您的选择更清晰易懂，所选值现在会渲染为带有易于阅读标签的“圆形标签”形状。此前，选项列表选择项显示的是 API 名称，可能与提供的标签差异很大。例如，标记为“True”的选项列表选项在选择后可能显示为值“1”。 |
| ||
| 是 |
| 资源选择菜单上的新增“整个资源”菜单项简化了选择当前正在浏览的整个资源的操作。此前，要选择整个资源，您必须从资源菜单中选择资源，然后单击菜单外部，而不选择特定字段。 |
| ||
| 是 |
| 使用新的 Has Error 运算符，您可以在流测试中配置否定断言。您可以特意测试那些未按计划进行的流路径，确保流能够优雅地处理错误。以前，您只能配置测试成功结果的肯定断言，这会在测试中留下缺口。Has Error 运算符可用于记录触发流和数据云触发流的流测试。选择 Has Error 运算符可为“创建记录”、“更新记录”、“删除记录”和“操作”元素配置否定断言。 |
| ||
| 是 |
| 您现在可以使用捏合缩放手势放大和缩小 Flow Builder 画布。 |
| ||
是 |
|
| 此次更新让 Flow Builder 更轻松地为计划触发流的“开始”元素触发器以及所有流类型的“更新记录”、“获取记录”和“删除记录”元素选择资源。我们现在使用更清晰的标签将手动选择对象的字段和值分组，以便您更轻松地识别和选择资源。 |
| ||
是 |
|
| 创建记录触发流时，如果该流涉及外部系统，则必须添加异步路径。 现在，“添加异步路径”开关在“开始”节点上更加醒目，确保您不会忽略这一成功集成的关键步骤。 此外，如果尝试在未启用“添加异步路径”开关的情况下向即时路径添加包含调用的操作，系统将显示警告以确保流可以正确运行。 |
| ||
是 |
|
| 无论您的流运行良好还是需要很长时间才能完成，现在都可以更轻松地将其另存为模板以供将来使用。在“流属性”窗口中，现在可以选择“另存为模板”，这会将流添加到创建新流时可用的模板列表中。 |
| ||
是 |
|
| Flow Builder 画布中改进的元素卡片使创建和编辑流变得更加轻松。这些卡片提供更大的选择区域、一键访问配置面板、快速访问常用元素操作以及更简洁的画布体验，减少了视觉干扰。现在，所有类型的流在自动布局模式下都可使用这些元素卡片。 |
| ||
| 是 |
| 通过在后台自动运行流，使流屏幕动态化。利用屏幕操作，无需用户离开屏幕即可使用额外的流逻辑。当用户在屏幕组件中输入值时，他们会实时看到逻辑结果和屏幕更新。屏幕操作可帮助您构建更精简的屏幕流，并提供更佳的用户体验。默认情况下，自动触发的屏幕操作会在其输入值更新以及屏幕加载时运行，但用户通过点击下一屏幕上的“上一步”按钮返回当前屏幕的情况除外。 |
| ||
| 是 |
| 新的增强型文件上传（测试版）流屏幕组件与现有的文件上传组件类似，但新增了一些增强功能。现在，用户可以在 Aura 和 Lightning Web Runtime (LWR) 站点以及 Lightning Experience 中的屏幕流中上传文件。此外，您可以要求用户先上传文档，再继续执行流。 |
| ||
是 |
|
| 现在，您可以自定义屏幕组件和记录字段的宽度，无论它们是否位于分区列中。此外，还可以调整组件和字段的垂直对齐方式，以优化它们彼此之间的相对位置。 |
| ||
是 |
|
| 使用“预览大小”功能，检查屏幕在大型、中型或小型设备上的显示效果。在设计时识别并修复任何布局问题，确保屏幕在任何设备上都显示完美。 |
| ||
是 |
|
| 通过为选择资源中的每个选项添加图标，减轻用户的认知负担。图标可以一目了然地传达信息，减少用户需要阅读和处理的文本量。带有图标的选择资源只能用于“选择查找”和“可视选择器”组件。此外，这些选择资源必须是文本数据类型。 |
| ||
是 |
|
| 使用可视选择器组件，让屏幕流中的选项更具视觉吸引力。该组件结合了图标和文本，可帮助用户快速选择所需内容，而无需滚动浏览长列表或下拉菜单。 |
| ||
| 是 |
| 构建屏幕流，帮助用户创建自动启动流审批流程草稿。从用户处获取输入，然后调用新的“创建流审批流程”操作以使用最多 20 个审批级别来创建自动启动流审批流程草稿。该草稿还可以包含最终操作和撤回路径。创建后，在 Flow Builder 中配置流审批流程元素。 |
| ||
| 是 |
| 在启动关联的流审批流程之前，使用流收集审批提交信息。构建自动启动流以收集相关数据。然后添加一个“操作”元素，调用相应的已激活的自动启动流审批流程要在测试和激活流后向用户提供该流，请将自定义按钮添加到受影响对象的页面布局中。 |
| ||
是 |
|
| 配置“发送电子邮件”操作，使其包含针对收件人、发件人和电子邮件内容的清晰的输入区域。“在不同版本的“发送电子邮件”操作之间切换，以控制电子邮件内容配置参数的可见性和组织方式。直接在“发送电子邮件”操作中创建您的电子邮件内容，而无需先创建文本模板资源。按名称选择现有模板，而不是将电子邮件模板 ID 引入流中。“使用新增的“抄送”和“密送”收件人地址收集字段增强 Flow Builder 中的电子邮件操作。更轻松地选择发件人类型，输入发件人电子邮件地址，选择电子邮件模板，附加文件以及选择特定记录。仅当提供收件人或相关记录 ID 时才记录电子邮件。仅在您提供相关记录 ID 时才将线程标记添加到正文和主题中。“现在，通过在“发送电子邮件”操作的“附件 ID 集合”字段中提供文本集合变量，可以更轻松地在 Flow Builder 中为电子邮件添加附件。 |
| ||
| 是 |
| 流的调试体验现在包含元素级摘要，以帮助您更快地了解流中每个步骤的情况。例如，对于“更新记录”元素，“调试详细信息”窗格会清晰地显示执行该元素后更新的记录数量。此前，元素级摘要仅在调试 Marketing Cloud Flow 时可用。 |
| ||
| 是 |
| 现在，数据图触发流也支持调试功能。 |
| ||
| 是 |
| 如果您的流包含发送电子邮件或发送短信操作，您可以在调试运行过程中发送测试消息。设置调试运行时，请指定您要用以测试消息的电子邮件地址或电话号码。启动调试运行时，我们将尝试将消息发送到指定的收件人。 | SMS Sends 在阿里云上的Salesforce 不可用。 | ||
| 是 |
| 我们对调试体验进行了一些改进，使您的调试结果更易于导航和理解。在调试面板中，每个元素运行都显示在单独的卡片中，并提供易于浏览的信息。元素卡片会动态加载，以便在滚动时提升性能。为了优化调试结果的视图，您现在可以调整调试面板的宽度，以查看更多调试结果或更多 Flow Builder 画布区。调试面板现在还包含搜索功能，以便您可以快速查找并突出显示您要查找的内容。对于“创建记录”、“获取记录”、“更新记录”、“删除记录”、“集合筛选器”和“集合排序”元素，现在，复杂数据类型使用带有语法突出显示的 JSON 格式在代码块中呈现，使信息更易于理解。您还可以通过单击复制整个调试日志。 |
| ||
| 是 |
| 这些版本更新带来了新的流程更新。 |
| ||
| 是 |
| 将流测试集成到您的回归测试、单元测试以及持续集成和持续交付 (CI/CD) 流程中。使用 Salesforce CLI 在更多渠道中无缝运行流测试，从而增强您的测试能力。例如，在将更改部署到组织之前，您可以在 CI/CD 流程中添加流测试，以确保更改不会破坏现有流程或 Apex 代码。此前，您需要在 Flow Builder 中手动为每个流运行一组测试，这既耗时又容易出错。 |
| ||
是 |
|
| Flow Builder 的配置面板新增了“查看输出资源”区域，用于显示输出参数和资源，例如输出名称和标签、数据类型和描述。使用此区域可以帮助您调试流，并确保其使用正确的输出，从而实现更准确和用户友好的流设计。您还可以对输出参数进行排序，并在需要时手动分配变量。 |
| ||
| 是 |
| Flow Builder 现在支持多个输入控件，让用户能够灵活方便地指定输入值，并持续改进以支持更多输入类型。 您可以在不同的输入模式之间切换，包括您熟悉的资源选择器以及可从选项列表中选择的新模式。 |
| ||
| 是 |
| 使用 InvocableActionExt（开发者预览）元数据类型来指定输入和输出的呈现方式，例如设置输入的顺序、提供描述和标签等。此更改允许操作开发人员为 Apex 操作和类型添加扩展属性，从而提升 Flow Builder 等低代码工具中的用户体验，并通过简化复杂操作的配置来改善整体开发体验。 |
| ||
|
| 是 | 为了允许访问某些可用作可调用操作参数的标准类，我们正在对内置 Apex 操作强制执行一项更改，强制要求所有类都具有可见的无参构造函数。此版本更新最早在 Summer '24 夏季版中提供，原计划于 Winter '26 中强制执行，但我们已将强制执行日期推迟到 Summer '26。此版本更新之前的名称为“强制执行在用作输入的内置 Apex 类上定义的权限要求”（版本更新）。 |
| ||
|
| 是 | 此更新最早在 Winter '24 中提供，计划在 Winter '25 中强制执行，但我们将强制执行推迟到 Winter '26。启用此更新后，Salesforce 将限制用户运行流的能力。必须向用户授予正确的简档或权限集才能运行流。启用后，此版本更新将弃用 FlowSites 组织权限，该权限允许组织中的所有用户访问和运行任何流。通过此更新，流的运行更加安全，因为只有被授予正确简档或权限集的用户才能运行流。Salesforce 推迟了强制执行，以便为管理员提供更多时间来测试和准备更改。对于已经启用更新的管理员没有影响。 |
| ||
| 是 |
| 现在您可以在 Approvals 应用中直接创建自动启动的流审批流程。该向导可以轻松设置包含最多 3 个审批级别、最终操作和撤回路径的流程草稿。您也可以选择使用 Flow Builder 自行构建自动启动的流程审批流程，从而获得更大的灵活性。 |
| ||
| 是 |
| 想要在审批提交进行审核之前获取相关信息？现在，您可以从任何支持异步路径的流中调用新的动态操作“请求审批”。在流获取您所需的信息后，添加一个“操作”元素来调用相应的活动的自动启动流审批流程。 |
| ||
| 是 |
| 您现在可以向流审批流程添加撤回路径。撤回路径包含一个阶段，其中包含在用户撤回其审批提交时运行的后台步骤。当提交被撤回时，正在运行的阶段及其相关步骤将被取消，未完成的审批工作项也将被取消。之后，撤回路径中的阶段将运行。当撤回路径中的阶段完成后，审批提交将被撤回。 |
| ||
是 |
| 当 Flow Orchestration 工作指南添加到对象的记录页面布局时，它会列出分配给查看记录页面的审批人的所有未完成审批工作项。现在，委托人也可以在工作指南中查看和完成未完成的审批工作项。 |
| |||
| 是 |
| 当正在进行的审批提交出现问题或不再需要时，您现在可以将其取消。如果审批提交关联到配置了撤回路径的流审批流程，则取消审批提交不会执行撤回路径中的任何操作。 |
| ||
|
|
| 了解 Flow 审批流程的改进。 |
| ||
| 是 |
| 通过使用故障路径定义业务流程遇到错误时的处理方式。要添加错误处理，请为业务流程中的每个阶段配置故障路径。然后，向每个故障路径添加元素，这些元素将在关联的阶段或阶段内步骤发生错误时执行。故障路径上的元素仅在关联的阶段发生错误时运行。在业务流程中使用故障路径的功能可以降低业务流程以错误结束的风险。 |
| ||
| 是 |
| 有关 Flow Orchestration 的其他改进。 |
| ||
|
| 是 | 当旧版（非增强型）Salesforce 主机名的临时重定向结束时，可防止客户和最终用户遇到中断。此版本更新将在生产和演示组织中结束旧版主机名重定向。 这些重定向已在 Winter '25 中在所有其他组织中结束。 此更新最早在 Spring '25 中提供，并在 Spring '26 中强制执行。 | Salesforce on Alibaba Cloud 的域名工作方式不同。 请参阅“阿里云上的Salesforce CRM功能差异说明 - Summer'25夏季版”了解详细信息。 | ||
|
| 是 | 为了避免因基础设施更新导致实例名称变更而造成中断，请将 API 流量中的实例 URL 替换为组织的 My Domain 登录 URL。 | |||
| 是 |
| 您现在可以使用外部客户端应用框架配置移动功能和通知。 使用新的外部客户端应用移动应用插件，您可以设置特定于移动设备的功能，例如根据自定义超时值锁定屏幕。 使用新的推送通知插件，您可以为 Android 或 iOS 设备打开移动应用程序的推送通知。使用新的通知插件，您可以将移动应用配置为接收自定义通知。 | Salesforce on Alibaba Cloud Android 版本 APP 目前不可用。同时推送通知在Salesforce on Alibaba Cloud 上不可用。 | ||
|
| 是 | 无需编写代码，只需点击即可设置 SSO。在 Salesforce 中使用身份验证提供程序框架进行 SSO 时，可以使用 Flow Builder 而不是 Apex 构建注册处理程序。使用新模板快速启动您的流程设计。该模板展示了如何创建和更新通过第三方身份提供程序登录到您的组织或 Experience Cloud 站点的用户。它包含两个新的可调用操作，可帮助您从身份提供程序获取用户信息并创建完整的用户记录。它还能避免 Apex 中的混合 DML 错误，简化用户访问管理。使用流程，通过在运行时在单个分配中添加和删除权限集来控制用户访问权限。 |
| ||
| 是 |
| 为了简化使用身份验证提供程序框架的 SSO 配置的创建和更新用户的过程，我们简化了访问身份提供程序返回的信息的过程。如果身份提供程序返回用户信息响应或 ID 令牌，我们现在会将其公开在 Apex |
| ||
| 是 |
| 如果您看到此版本更新，则表示您的 Salesforce 实例使用我们最初的单配置 SAML 框架，该框架仅支持使用一个外部身份提供程序的 SSO。在此版本更新中，我们将移除对单配置 SAML 框架的支持，并且仅支持多配置 SAML 框架。要保留现有配置，请按照步骤应用此更新。否则，当此更新在 2026 年春季强制应用于生产实例时，您的 SSO 配置将停止工作。 |
| ||
| 是 |
| Salesforce 正在升级其 SAML 框架，作为常规持续维护的一部分。此维护更新改进了 Salesforce 的安全状况，从而也提高了您的安全状况。此更新可能会影响使用 SAML 的集成，包括单点登录 (SSO) 和单点注销。此更新最初于 Winter '25 宣布，并将于 Summer '25 强制执行。为避免潜在的服务中断，请在 Summer '25 沙盒可用后立即测试您的 SAML 集成。 |
| ||
SAML 单点登录的 Triple Data Encryption Standard (Triple DES) 将于 Winter '26 停止工作 |
| 是 |
| 在 Winter '26 中，使用 Triple DES 算法的 SAML SSO 配置将停止工作。此更改适用于所有使用 Triple DES 算法的 SSO 配置，无论 Salesforce 的角色是身份提供程序还是服务提供程序。为了提高安全性，请改用 Advanced Encryption Standard (AES) 算法 AES 128 或 AES 256。 |
| |
| 是 |
| 对于外部客户端应用程序和连接应用程序，我们移除了订阅者在应用程序策略中控制 JSON Web Token (JWT) 访问令牌启用的功能。如果开发者在应用程序设置中启用了基于 JWT 的访问令牌，则该应用程序的所有已安装版本都将自动颁发基于 JWT 的访问令牌。 |
| ||
| 是 |
| 为了更精确地跟踪和管理会话，您现在可以确定哪些会话与基于 JSON Web Token (JWT) 的访问令牌关联。在“设置”的“会话管理”页面上，您可以创建一个包含新字段“Associated with JWT”的视图。 |
| ||
| 是 |
| 为保持一致性，我们更改了用户登录时创建的某个会话的登录类型。将之前的“Unknown”改为“Application”。 |
| ||
是 |
|
| 为了提升可访问性，我们更新了 Salesforce 登录页面上显示的两条错误消息。现在，每条消息都以“Error”作为视觉前缀。 |
| ||
| 是 |
| 为提醒用户谨慎批准外部客户端应用或连接应用的访问权限，我们在 OAuth 应用批准页面添加了警告信息。 |
| ||
| 是 |
| 您可以在“外部客户端应用程序设置”页面找到“新建连接的应用程序”按钮。此功能由“允许创建连接的应用程序”首选项控制，默认情况下，该首选项对于新组织是禁用的。外部客户端应用程序现在支持 OAuth、SAML，并涵盖了许多与连接的应用程序相同的用例，因此建议您尽可能使用外部客户端应用程序。外部客户端应用程序现在可以在 App Manager 中创建。 |
| ||
|
| 是 | “新建外部客户端应用程序”按钮现已在“设置”的 App Manager 中提供。现在除了 OAuth 之外，还支持 SAML，这使得外部客户端应用程序比以往任何时候都更有用。这些特性使外部客户端应用程序成为连接外部应用程序与 Salesforce 数据的首选方案连接的应用程序。现在可以在“外部客户端应用程序设置”中创建。 |
| ||
|
| 是 | 使用外部客户端应用程序的 SAML 设置将服务提供商与 Salesforce 组织集成。在服务提供商或身份提供商启动流程时设置 SAML 单点登录 (SSO)。 |
| ||
| 是 |
| 为了使用户能够使用防钓鱼的身份验证方法，新组织默认启用了基于 WebAuthn 的验证设置。用户可以注册内置身份验证器（例如 Touch ID 或 Windows Hello）和物理安全密钥（例如 U2F 密钥），并使用这些方法来完成身份验证，例如 MFA。 |
| ||
|
| 是 | 利用 Threat Detection 应用中的新增“登录异常”事件，您可以调查异常登录尝试，例如在非典型时间或不常见端点的登录。 |
| ||
|
| 是 | 默认情况下访问和调查关键的 Threat Detection 事件信息。现在，所有 Threat Detection 事件都自动启用 Threat Detection 数据存储功能，使您可以立即访问关键数据。 |
| ||
|
| 是 | 通过使用由选定的实时事件提供支持的平台事件触发的 Flow，轻松触发自动化操作和创建案例。 |
| ||
|
| 是 | 当用户访问“最近查看”列表视图时，生成实时事件并创建事务安全策略，以便您可以监视并采取措施阻止恶意用户。 |
| ||
|
| 是 | 利用新的分布式跟踪功能，您可以近乎实时地了解 Salesforce Apex HTTP callout，该功能将 Apex callout span 作为平台事件发布。此功能旨在与第三方解决方案兼容，可显著缩短服务中断期间的平均恢复时间 (MTTR)。 |
| ||
|
| 是 | 现在，某些 Hyperforce 组织可以在 sandbox 中测试数据库加密。数据库加密允许您对加密数据进行排序、筛选和引用，而不会影响功能或性能。如果需要，您仍然可以将字段级加密应用于单个字段。 |
| ||
|
| 是 | 当您生成或轮换确定性加密租户密钥时，新的应用内助手可帮助您避免确定性租户密钥的同步作业可能出现的问题。 |
| ||
|
| 是 | Crypto 类现在支持 AES-GCM（Advanced Encryption Standard Galois/Counter Mode）进行 256 位加密和解密操作。AES-GCM 通过对每次加密使用不同的初始化向量 (IV) 来提高安全性。此更改还包括支持 256 位、384 位和 512 位 P1363 签名格式进行签名和验证。 |
| ||
| 是 |
| 为了帮助您维护重定向的受信任 URL 允许列表，Salesforce 现在会记录源自 Salesforce Classic 中 URL 和长文本区域字段中超链接的阻止重定向。此前，“受信任的 URL 和浏览器策略冲突”列表和“阻止的重定向”事件类型仅捕获组件和页面内的阻止重定向。 |
| ||
| 是 |
| 将 URL 字段中超链接的重定向限制为仅您信任的外部 URL，以保护您的用户。您可以阻止这些重定向，或显示一条警告消息，要求用户确认他们要离开 Salesforce 之后才会重定向。此功能现已对 Lightning Experience 用户开放。 |
| ||
| 是 |
| 现在，Salesforce 会记录源自 Lightning ，针对 img-src（图像）、font-src（字体）和 frame-src（iframe 内容）指令的所有 CSP 违规，让您更有信心地测试对Content Security Policy (CSP) 的更改。此前，Salesforce 对资源违规进行采样，这意味着出于测试目的生成的资源违规很少生成 CSP 违规事件。 |
| ||
|
| 是 | 此更新已取消。我们仍然建议您检查“设置”中的“受信任的 URL 和浏览器策略违规”列表，并在“会话设置”中启用“采用更新的 CSP 指令”。此外，该设置在新组织中默认仍处于启用状态。 |
| ||
是 |
|
| 使用提示构建器，您可以根据业务需求调整 Einstein 电子邮件摘要的长度和语气。 |
| ||
| 是 |
| 启用此新的组织首选项后，如果 Email-to-Case 无法处理发送到组织的电子邮件时，最终用户会收到通知。 |
| ||
| 是 |
| 现在，对于通过“使用 Einstein 编写”功能创建的 EmailMessage 记录（包括已保存的草稿和未保存为草稿的已发送电子邮件）， |
| ||
| 是 |
| 启用后，此版本更新将替换停靠式电子邮件编写器和个案摘要电子邮件编写器中的电子邮件编辑器。此更新已于 Spring'24 在 Lightning Experience 中正式发布，并且没有计划的强制执行日期。 |
| ||
| 是 |
| 此更新将关闭基于 Ref ID 的线程化，并在 Email-to-Case 中过渡到 Lightning 线程化。使用新的 Email-to-Case 线程行为，传入电子邮件将不再使用 Ref ID 进行匹配，而是使用电子邮件主题或正文中的安全令牌进行匹配。如果未找到匹配项，Email-to-Case 将检查电子邮件标头中的元数据。此更新最早在 Winter '21 中提供，并且没有计划的强制执行日期。 |
| ||
是 |
|
| 每小时单封电子邮件发送限制现在包含使用个案 Lightning 电子邮件编写器发送的电子邮件。此更改可确保每个用户每小时最多可以向 250 个外部收件人发送电子邮件。 |
| ||
是 |
|
| 使用简化的用户界面，通过更少的步骤配置 SLA 管理（以前称为权利管理）。新的配置界面更加直观易用，减少了实施工作，并改善了整体用户体验。您可以定义规则以自动将里程碑标记为完成，并根据预定义规则自动执行权利映射，将权利附加到个案、工作订单和事件。切换到新的设置体验，探索自动化功能，简化您的流程并提高效率。 |
| ||
是 |
|
| 通过在个案评论中添加富文本和媒体，改善与客户的沟通。在您的评论中使用格式化效果，使其更易于阅读。添加图像和视频，提供上下文和清晰度，并更好地记录互动。富文本支持字段将替换个案评论的纯文本字段。启用富文本支持字段后，您将无法返回使用纯文本字段。 |
| ||
是 |
|
| 根据预定义的规则自动将权利映射到相应的个案、工作订单和事件。通过消除将权利映射到每个个案、工作订单或事件的需要，提高了客服代表的效率，最大限度地减少了 SLA 违规，并简化了管理。如果需要，客服代表可以手动更改自动应用于个案的权利。 |
| ||
是 |
|
| 使用动态表情符号进行评分，打造更具视觉吸引力的调查体验。动态表情符号提供各种表情，使参与者的体验更具吸引力。 |
| ||
是 |
|
| 参与者可以通过显示进度百分比的可视进度条查看调查进度。此更新使参与者更容易保持进度并查看剩余进度。 |
| ||
是 |
|
| 每次调查最多允许用户上传 20 个附件，收集更全面、更准确的调查数据。这些附件可以分发到调查中的多个附件问题，或将它们全部添加到一个附件问题。使用此选项，受访者可以为他们的回复添加上下文和详细信息，从而帮助您做出更好的决策。 |
| ||
|
| 是 | 启用兼容的调查 URL，确保您的调查邀请到达目标收件人。这些 URL 可防止安全应用阻止邀请，并提高受访者调查完成率。 |
| ||
|
| 是 | 使用知识反馈来收集有关知识文章的反馈，并将反馈回复分配给相应的人员或团队以采取行动。这是了解文章的有用性并确定改进领域的好方法。此功能有助于确保您的文章保持相关性和最新性，以及回复准确无误且有所帮助。 | |||
是 |
|
| 使用文章中自动生成的目录 (TOC) 快速查找您在知识文章中所需信息。TOC 提供了文章的清晰概览，可以轻松跳转到感兴趣的部分。它通过提供一致的结构，改进了内容的可发现性和导航，并增强了用户体验。您可以将 TOC 添加到知识库中的新文章和现有文章中，但只能添加到 HTML 格式的文章中，不能添加到 PDF 或其他非 HTML 格式的文章中。 |
| ||
是 |
|
| 改进的 Lightning Article Editor 可帮助您更高效地编写知识文章，并利用简化的功能来创建优质内容。 |
|
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 AI Connector) 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 AI Connector |
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 Known Product and Feature Differences of Salesforce on Alibaba Cloud - 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. |
|