New and Changed Objects

Access more data through these new and changed standard objects.

Salesforce Overall

Store a record each time a utilization signal is reached for your org's consumption-based or seat-based products.

The TenantConsumptionAlert object supports these alert types:

Consumption Threshold Alerts — Previously available through the Consumption Threshold Alerts flow template, this feature now stores alert records in TenantConsumptionAlert, giving you direct API access to query and manage your consumption threshold alerts.
License Utilization Alerts (New) — Triggered when user license or permission set license utilization reaches a specified threshold. Use the License Utilization Alerts flow template and associated invocable actions to set up and manage these alerts. This alert type will be rolled out as a staggered release starting in late May 2026.
User-defined Alerts – Create user-defined alerts directly on this object to track any custom signal that meets your use case.

Automation

Link parent and child approval work items for approval steps with unanimous approvals: Use the new ParentWorkItem field on the existing ApprovalWorkItem object.
Link underlying parent and child orchestration work items for approval work items from approval steps with unanimous approval: Use the new ParentWorkItem field on the existing FlowOrchestrationWorkItem object.
Get information about the error rate of the last occurrence of a flow: Use the new Health, ElementEntries, and ElementError fields on the existing FlowRecord object.
Specify the type of audience flow: Use the new supported values CampaignMember, List, and RecordQuery in the existing FlowType and Type fields on the FlowRecord object.
Specify when a flow is launched from MuleSoft: Use the new supported value EnterpriseScaleExternalSystemChange in the existing FlowType and Type fields on the FlowRecord object.
Associate a flow record versionand flow record version occurance with a data space: Use the new DataSpaceId field on the existing FlowRecordVersion and FlowRecordVersionOccurance objects.
Identify new flow types for flow record versions: Use these new values of the existing flowType field on the existing FlowRecordVersion object: AgenticGuidedExperienceBackgroundFlow, AgenticGuidedExperienceOrchestrationFlow, AgenticGuidedExperienceScreenDataFlow, AgenticGuidedExperienceScreenFlow, BroadcastFlow, ExternalSystemChangeTriggerApprovalProcess, ExternalSystemChangeTriggerOrchestration, ExternalSystemChangeTriggerFlow, and OnDemandFlow.

Commerce

Track cart collaboration with new fields on the WebCart object: With Advanced Cart Management, multiple users can collaborate on a single cart. Use the new CollaborationStatus, CollaborationLockedById, and CollaborationLockedAt fields on the existing WebCart object to see whether a cart is shared for collaboration, and to identify who locked the cart and when. Advanced Cart Management isn't enabled by default. To enable it, contact your Salesforce account team.
Track the count of items added to the webcart from quotes: Use the new QuoteLineItemCount field on the existing WebCart object.
Store shopper profile data from an external Commerce organization: Shopper Profile Sync uses the CommerceCustomerReference, CommerceGroupReference, and CommerceOrganizationReference fields on the existing Account and Contact objects.
Determine whether the payment link is for a business account: Use the new IsBusinessAccountPayment field on the existing PaymentLink object.

Determine the asset quantity when the subscription starts and ends: Use the new fields StartQuantity and EndQuantity on the existing CartItem object.

REMOVED: The OrderPaymentSummaryId field is removed from the PaymentGatewayLog object: The OrderPaymentSummaryId field is removed from the PaymentGatewayLog object in API version 67.0 and later.

Customization

BEHAVIOR CHANGE: The DoesIncludeBosses field on the existing Group object is available for queues: Use the DoesIncludeBosses field to indicate whether records shared with users in the queue are also shared with users higher in the role hierarchy.
REMOVED: The CUC picklist value was removed from the IsoCode field on the CurrencyType and DatedConversionRate objects: Update any references to the Cuban Convertible Peso (CUC), a deprecated currency code, in API version 65.0 and later. Existing DatedConversionRate records for CUC are no longer supported.

Deployment

Track and audit DevOps Center activities.: Use the DevopsActivityLog object.
Monitor individual metadata components and configuration data records as they're deployed to the DevOps Center pipeline environments.: Use the DevopsEnvDeploymentMbr object.
Manage DevOps Center environments.: Use the DevopsEnvironment object.
Track Pipeline Operations.: Use the DevopsEnvDeployment object.
Define pipelines for DevOps Center projects.: Use the DevopsPipeline object.
Associate pipelines with environments.: Use the DevopsPipelineEnvironment object.
Configure pipeline stages and deployment sequence to define individual stages in your release path.: Use the DevopsPipelineStage object.
Track changes as ‌work items move through pipeline stages.: Use the DevopsPipelnStgProm object.
Track merge status of the work item into the target stage branches.: Use the DevopsPipelnStgPromWkItem object.
Create DevOpsCenter projects that serve as the primary workspace for team collaboration.: Use the DevopsProject object.
Associate DevOps Center projects with pipelines.: Use the DevopsProjectPipeline object.
Manage deployment requests and track operation status of asynchronous DevOps Center operations.: Use the DevopsRequestInfo object.
Connect to source control systems.: Use the SourceCodeRepoProvider object.
Manage version control repositories for DevOps Center projects.: Use the SourceCodeRepository object.
Track repository branches and their environment associations.: Use the SourceCodeRepositoryBranch object.
Create and manage logical units of work such as user stories, tasks, and bugs.: Use the WorkItem object.
Provide real-time notifications for work item status changes in DevOps Center projects.: Use the WorkItemEvent object.
Track metadata components and configuration data records associated with WorkItemComponentList record in a DevOps Center project.: Use the WorkItemComponent object.
Trigger quality checks when a work item transitions to a stage in the pipeline.: Use the DevopsPipelineStageTrigger object.
Configure and connect third-party test providers to a specific pipeline stage.: Use the DevopsPipelineTestProvider object.
Define criteria or automated quality gate rules that a deployment must satisfy to progress to the next pipeline stage.: Use the DevopsQualityGate object.
Track the high-level evaluation results and metrics for a specific quality gate run.: Use the DevopsQualityGateResult object.
Set quality gate rules for specific conditions, thresholds, or logic that make up an overall quality gate.: Use the DevopsQualityGateRule object.
Capture the detailed, granular evaluation data for a single quality gate rule.: Use the DevopsQualityGateRuleResult object.
Represent the definition or metadata configuration of an individual test case or test script.: Use the DevopsTest object.
Record the lifecycle, execution state, and outcome of a test case.: Use the DevopsTestExecution object.
Manage the integration details, authentication, and settings for a third-party automated testing tool.: Use the DevopsTestProvider object.
Track synchronization events and errors in Salesforce test providers and third party test providers.: Use the DevopsTestProviderSyncLog object.
Define grouping of test cases that are executed together as a unit.: Use the DevopsTestSuite object.
Track the runtime lifecycle, code coverage, and errors in Salesforce test providers and third party test providers execution status of a test suite within a pipeline stage.: Use the DevopsTestSuiteExecution object.
Group test suite execution runs during a single deployment or a collective execution event.: Use the DevopsTestSuiteGroupExec object.
Assign and configure test suites to execute automatically within a particular pipeline stage environment.: Use the DevopsTestSuiteStage object.
Maps individual test cases to their respective test suite.: Use the DevopsTestSuiteTest object.
Links a specific work item's deployment lifecycle to its corresponding test suite group execution record.: Use the DevopsWkItmTstSteGrpExec object.

Development

Use new EventBus.publishWithAccessLevel() methods for better access control: Prefer the new publishWithAccessLevel methods over the existing publish methods when writing Apex code to publish events.
Set an expiration for a managed package subscriber’s ability to block push upgrades to their org: Use the new ExpirationDays field on the existing PushUpgradeCustomization object.
Query test results by test category, test class, or namespace: Use the TestCategory, TestName, TestNamespace fields on the existing ApexTestResult object. Introduced in API version 65.0, these fields have been added to the Object Reference for the Salesforce Platform.

Event Monitoring

Track invocation sources for invocable actions in Invocable Action Event Type files: Use the new AGENT_ACTION, API_CALLER, INVOCATION_SOURCE, INVOKING_APEX_CLASS_NAME, and PROMPT_TEMPLATE fields in the Invocable Action Event type of the existing EventLogFile object. These fields were introduced in API version 66.0 and have been added to the Object Reference for Salesforce Platform.
See Authentication Context Class Reference (ACR) values sent by your identity provider: Use the new AuthContextClassRef field on the LoginEvent object.; Use the new AuthContextClassRef field on the LoginEventStream object.
Monitor usage of the OAuth 2.0 device flow: Use the new supported value OAuthDevice in the existing LoginSubType field on the LoginEvent object.; Use the new supported value OAuthDevice in the existing LoginSubType field on the LoginEventStream object.

Experience Cloud

Configure and verify secondary sender addresses for Experience Cloud site emails: Use the new OptionsSecondaryEmailSenderEnabled, PendingSecondaryEmailAddress, and VerifiedSecondaryEmailAddress fields on the existing Network object to manage secondary sender addresses for site emails that contain sensitive data.

Field Service

Model a Service Bill of Materials for an asset on the ProductRelatedMaterial object: Use the new RelationshipType, ComponentRelationship, ComponentLifecycleStatus, and SourcingType fields on the ProductRelatedMaterial object as the source of truth for Service Bill of Materials data, including data brought in from a PLM or ERP system.

Revenue

Specify the duration type for ramp deals for groups segments on quotes and orders in Revenue Cloud: Use the new SegmentType field on the OrderItem object.

Sales

BEHAVIOR CHANGE: You can now edit the field IsRecurrence2Exclusion on the Event object: In API version 67.0 and later, IsRecurrence2Exclusion is writable through Apex and the API. Use this field to indicate that a specific event is different from all other events in a recurring series. In API version 66.0 and earlier, IsRecurrence2Exclusion remains read-only.
REMOVED: The AccountCleanInfo and ContactCleanInfo objects are removed: Deprecated in API version 65.0, the AccountCleanInfo and ContactCleanInfo objects are removed in API version 67.0 and later.
Store additional context, associated record, suggested values, and utterances for AI-generated action items: Use the new AiGenActionItemInfoId, ParentId, SuggestedNewValue, and Utterance fields on the existing AiGenActionItem object.
REMOVED: The WhatId field is removed from the AiGenActionItem object: Instead, use the new ParentId field on the existing AiGenActionItem object to reference the associated Account or Opportunity record.
Store the location and configuration of synthetic columns on pipeline and intelligence views: Use the new PplinInspListViewCalcClmn object.
Store AI-generated research prompt results for contacts: Use the new supported value Contact in the existing ReferenceRecordId field on the AiResearchPromptResult object.
Store the structure of a voice call recording , which includes voice call participants, speaking order, start offset, and end offset: Use the new VoiceCallRecordingStructure object. Introduced in API version 66.0, this object has been added to the Object Reference for the Salesforce Platform.
Store the complete transcript text and metadata of a recorded video call: Use the new VideoCallTranscript object. Introduced in API version 66.0, this object has been added to the Object Reference for the Salesforce Platform.

Track link engagement and reply activity on email messages: Use the new FirstLinkClickedDate, HasReply, IsLinkClicked, IsLinkTracked, and LastLinkClickedDate fields on the existing EmailMessage object.
Track delivery responses from email recipients: Use the new DeliveryResponse field on the existing EmailMessageRelation object.
Set the carbon copy addresses and reply-to name on list emails: Use the new CcAddress and ReplyToName fields on the existing ListEmail object.
Indicate whether email archiving is required or if synthetic CC is enabled on list emails: Use the new IsEmailArchiveRequired and IsSyntheticCcEnabled fields on the existing ListEmail object.
Specify that a list email was sent via Distributed Marketing: Use the new supported value Distributed Marketing in the existing SentVia field on the ListEmail object. Available in API version 66.0 and later.
Store informational fields related to AI-generated action items that can be used for reporting: Use the new AiGenActionItemInfo object.
Identify the type of message for a sales engagement step: Use the new MessageType field on the existing ActionCadenceStep object.
Identify that a target exited a cadence because of a previously executed step: Use the new supported value AutomaticallyExitedPreviouslyExecutedStep in the existing CompletionReason field on the ActionCadenceTracker object. Available in API version 60.0 and later.
Identify that a target exited a cadence because a review expired: Use the new supported value ReviewExpired in the existing CompletionReason field on the ActionCadenceTracker object. Available in API version 66.0 and later.
Track the message type, review criteria flow status, and review disposition for a sales engagement step: Use the new MessageType, ReviewCriteriaFlowStatus, and ReviewDisposition fields on the existing ActionCadenceStepTracker object.
Identify when a sales engagement step needs review or has been approved: Use the new supported values Approved and NeedsReview in the existing State field on the ActionCadenceStepTracker object. Available in API version 66.0 and later.
Identify when a sales engagement step approval has expired: Use the new supported value ExpiredApproved in the existing State field on the ActionCadenceStepTracker object.
Identify additional error conditions for sales engagement steps: Use the new supported values EAC_CONFIG_EMAIL_CAPTURE_OFF, EAC_CONFIG_IS_NOT_ACTIVE, EAC_CONFIG_LIMITED_CAPTURE, INITIAL_OUTREACH_ACCOUNT_DEACTIVATED, SOBO_MEETING_LINK_GENERATION_FAIL, SOBO_QNA_NO_ANSWER, STORAGE_LIMIT_EXCEEDED, UNAUTHORIZED_EMAIL_DOMAIN, and USER_NOT_IN_EAC_CONFIG (available in API version 66.0 and later) and INSUFFICIENT_ACCESS_ON_TARGET and REVIEW_CRITERIA_FLOW_EXECUTION_FAILED in the existing ErrorCode field on the ActionCadenceStepTracker object.
Track an opportunity’s applied sales methodology and lock state: Use the new OppSalesMethodology object to store the methodology definition linked to an opportunity, including editability and lock status.
Store scored criteria and notes for an opportunity’s methodology items: Use the new OppSalesMethodologyItem object to capture values and notes for each scored methodology criterion tied to an opportunity.
Define reusable sales methodology templates by category and object type: Use the new SalesMethodologyDef object to define active methodology templates, including category, language, and target object type.
Define ordered criteria and input types for methodology templates: Use the new SalesMethodologyDefItem object to configure per-criterion metadata, such as input type and order.

Security and Identity

Define a recurrence schedule for running a data detect scan in the schedule creator's time zone.: Use the new IsScheduled field on the existing DataDetectPolicy object.

Define if encrypted fields are enabled in a data detect policy.: Use the new IsEncryptedFieldsEnabled field on the existing DataDetectPolicy object.

Get information about a recurring data detect scan.: Use the new DataDetectPolicySchedule object.

Store the excerpts of the scan results in the form of encrypted text.: Use the new SensitiveValues field on the existing DataDetectScanResult object.

Permit users with appropriate permissions to see classic encrypted fields in data detect scan results.: Use the new HasClassicEncryptedField field on the existing DataDetectJobSession object.

Get information about a data detect keyword dictionary.: Use the new DataDetPlcySrchExpsDict object.

BEHAVIOR CHANGE: The Customize Application permission is required to access RedirectWhitelistUrl: Previously, the Customize Application permission was required only for edit access to the RedirectWhitelistUrl object. Now that permission is required for read access, too.
View the type of login flow used to access a session: Use the new LoginSubType field on the AuthSession object.
View Authentication Context Class Reference (ACR) values from your identity provider in the login history: Use the new AuthContextClassRef field on the LoginHistory object.
Monitor usage of the OAuth 2.0 device flow in the Login History and Session Management pages: Use the new supported value OAuthDevice in the existing LoginSubType field on the LoginHistory object.; Use the new supported value OAuthDevice in the existing LoginSubType field on the AuthSession object.

Define a recurrence schedule using the schedule creator's time zone