Metadata API

Access more metadata through these new and changed metadata types.

Automation

Add custom property editors to individual Apex action input parameters: Use the new CpeName and ConfiguredBy values of the existing key field in the InvocableActionExtensionTargetAttribute subtype of the InvocableActionExtension metadata type.
Customize an Apex action's standard property editor header: Use the new CustomHeaderLwcName value of the existing key field in the InvocableActionExtensionTargetAttribute subtype of the InvocableActionExtension metadata type.
Define picklist values for Apex action input parameters: Use the new ProvidedValueList value of the existing key field in the InvocableActionExtensionTargetAttribute subtype of the InvocableActionExtension metadata type.
Get shopping cart details when a shopper abandons a cart in B2C Commerce: Use the new trgrOnB2cCartAbandoned value of the existing eventType field in the FlowStart subtype of the Flow metadata type.
Get marketing campaign details after a shopper places an order in B2C Commerce: Use the new trgrOnPostOrdMktCmpnEngagement value of the existing eventType field in the FlowStart subtype of the Flow metadata type.
Define and manage reusable mappings between source and target values used within a flow: Use the new FlowValueMap metadata type.
Define an individual mapping record that links a specific source value to a target value within a reusable flow value map: Use the new FlowValueMapEntry subtype of the FlowValueMap metadata type.
Filter and sort collections using advanced criteria in flows: Use the new FlowCollectionFilterCriteria subtype of the Flow metadata type.
Define individual filter conditions for collection filtering: Use the new FlowCollectionFilterCondition subtype of the FlowCollectionFilterCriteria subtype of the Flow metadata type.
Configure sort options when filtering collections: Use the new FlowCollectionFilterSortOption subtype of the FlowCollectionFilterCriteria subtype of the Flow metadata type.
Control batch size for record-triggered flows: Use the new maxBatchSize field in the FlowStart subtype of the Flow metadata type.
Start a flow when an object or an object with fields related to an individual is created or updated: Use the new IndivRelatedRecord value of the existing entryType field in the FlowStart subtype of the Flow metadata type. This value is available in API version 66.0 and later.
Prevent a flow from running at a specific entry point: Use the new Never value of the existing entryType field in the FlowStart subtype of the Flow metadata type.
Trigger a flow based on activation events: Use the new Activation value of the existing triggerType field and the new activation field in the FlowStart subtype of the Flow metadata type.
Track the path and connector for a flow action call: Use the new connector and pathName fields on the new FlowActionCallPath metadata type.
Invoke activations and journeys from a recommendation strategy: Use the new activationSchema and TriggerJourney values of the existing invocableActionType field in the StrategyAction and StrategyNodeInvocableAction subtypes of the RecommendationStrategy metadata type.

Customization

Indicate whether records shared with users in a queue are also shared with users higher in the role hierarchy: Use the new doesIncludeBosses field on the existing Queue metadata type.

Data 360

Retrieve info on filters applied to data lake object fields in data spaces: Use the filterApplied, filterOperationType, and filterValue fields on the existing DataSrcDataModelFieldMap metadata type. These fields correspond to DLO filters that you configure in the Data Spaces tab. Introduced in API version 60.0, these fields have been added to the Metadata API Developer Guide.; Use the templateVersion field on the existing DataSrcDataModelFieldMap metadata type. Introduced in API version 61.0, this field has been added to the Metadata API Developer Guide.

Create dynamic market segments in Metadata API: Use the Dynamic value in the segmentType field on the existing MarketSegmentDefinition metadata type. Available in API version 66.0 and later.
Group ActivationPlatform output files by user: Use the PER_USER value in the outputGrouping field on the existing ActivationPlatform metadata type. Available in API version 66.0 and later.
Set a full refresh interval for data stream templates: Use the fullRefreshIntervalDays field on the existing DataStreamTemplate metadata type to specify the number of days between full refreshes of the data stream. Available in API version 67.0 and later.
Classify data sources with more values in DataStreamDefinition object: Use the Ad_Audience_Insights, Auxiliary, Clean_Room, Deletion_Records, and Problem_Records values on the existing DataStreamDefinition metadata type. Available in API version 67.0 and later.
Schedule calculated insight refreshes and define their data sources: Use the scheduleEndDate, scheduleInterval, scheduleStartDateTime, sourceDataGraphName, and sourceObjectDevName fields on the DataCalcInsightTemplate metadata type. Introduced in API version 65.0, these fields have been added to the Metadata API Developer Guide.
Create history and virtual metric calculated insights: Use the HISTORY_METRIC and VIRTUAL_METRIC values in the definitionType field on the DataCalcInsightTemplate metadata type. Introduced in API version 65.0, these values have been added to the Metadata API Developer Guide.

Development

Make Your Multi-Framework app visible in the App Launcher

Configure both the CustomApplication and the UIBundle metadata types to make an internal, employee-facing React app available in the App Launcher.

Use the new uiBundle field of the CustomApplication metadata type to reference your app, which you define using the UIBundle metadata type.
Use the new CustomApplication value of the existing target field of the UIBundle metadata type.

DEPRECATED: The AppLauncher value of the target field in the UIBundle metadata type is deprecated

Use CustomApplication instead.

Build Reusable UI Compositions for Salesforce Applications and Third-Party Platforms (Beta)

Use the new UiWidgetBundle metadata type to build UI for Agentforce action output in Lightning Experience and MCP server tool output in ChatGPT, Claude, and Slackbot.

Experience Cloud

Keep private LWR pages unavailable until password setup or reset is complete

In LWR sites that use custom Visualforce password-management pages, use the new disablePvtPagesForPwdResetInLWR property to block access to private site pages until visitors set up or reset their password. This property is in the site’s .network file.

Verify secondary sender configuration for Experience Cloud site emails

Use the new secondaryEmailSenderEnabled and pendingSecondaryEmailAddress fields on the existing Network metadata type.

Use the secondaryEmailSenderEnabled field to check whether Experience Cloud site email messages that contain sensitive data are sent via a secondary sender address.
Use the pendingSecondaryEmailAddress field to retrieve the email address that has been added and is pending verification as your site's secondary sender address.

Sales

Enable Salesforce to send email for users with unverified email domains: Use the enableSubstituteFromAddress field on the new EmailAuthorizationSettings metadata type.

Manage Agentforce Account Management settings: Use the new AgentforceAccountManagementSettings metadata type. The type currently has one field, enableAccountManagement, to enable or disable Agentforce Account Management in your Salesforce org. Introduced in API version 65.0, this field has been added to the Metadata API Developer Guide.

Retrieve available meeting time slots in an Inbox flow.: Use the new getAvailableMeetingTimes value in the existing actionType field, which is on the FlowActionCall subtype of the Flow metadata type.

Confirm a meeting time in an Inbox flow.: Use the new confirmSalesMeeting value in the existing actionType field, which is on the FlowActionCall subtype of the Flow metadata type.

Relate a lead's emails to the contact during lead conversion: Use the new relateEmailsToContactOnConvert field on the existing LeadConfigSettings metadata type.

Security and Identity

BEHAVIOR CHANGE: The Customize Application permission is required to access the RedirectWhitelistUrl metadata type: Previously, that permission was required only for edit access to this type. Now that permission is required for read access, too.
Disable sanitization in aura:unescapedHtml component: Use the new unescapedHtmlSanitization field in the SessionSettings metadata type.