Winter '27 (API 68.0) adds configuration controls, LWC state refresh, Marketing Cloud Next content APIs, and component-level styling hooks.
What's new
Configure flow behavior and API access
API: New and changed items in API version 68.0 adds a FlowSettings field in Metadata API for the Enable the Automation Lightning App preference. It also adds admin control over guest user access to GraphQL API, explicit user-context flow execution, and access to related Data Model Object records in a Record Query Flow.
Guest GraphQL access and flow execution context deserve separate review, not incidental changes during a version update.
Refresh LWC state without reloading the page
Refresh state manager data adds refresh() to LWC built-in state managers for list- or query-shaped state, including related list records. It fetches current server data without reconfiguring the manager or reloading the page.
The manager must have a status of loaded when you call it. Await the returned Promise before running UI work that depends on the refreshed data.
Manage Marketing Cloud Next content through REST
Create and manage content programmatically using REST API adds programmatic management of all content in the Marketing Cloud Next CMS. You can create, modify, and search content for Email, SMS, WhatsApp, and Mobile App channels. Video content, content blocks, tracked links, and forms are also supported.
Ingest marketing data through Bulk API 2.0
Ingest marketing object and consent data at scale with Bulk API 2.0 adds marketing-object support for insert and upsert. It also adds refresh, a marketing-object-only operation that replaces all data in the target data set.
Style individual components with SLDS 2 hooks
Customize components with the SLDS 2 Styling API and component-level hooks introduces CSS custom properties named --slds-c-{component}-*. These customize spacing, color, border, shadow, and typography for one component without changing global hooks. They inherit across Shadow DOM boundaries for use in LWC.
The component-level hooks reference global hooks by default and support a modifier pattern in which variant styles cascade. They are in developer preview.
Test Apex against archived data
Apex: New and changed items in API version 68.0 introduces the SF_Archive namespace, with methods for testing Apex against archived data without live callouts. The same reference documents new and changed classes, enums, interfaces, and ConnectApi classes.
License and preview constraints
Bulk API 2.0 marketing-object operations require a Marketing Cloud (Marketing on Core) license.
For SLDS 2 component-level hooks, consult each component's Specifications tab on the SLDS 2 site. Test the variant behavior of the hooks you choose. I would keep delivery commitments independent of this developer preview unless the team has accepted that dependency.
Before shipping
Review the full input for marketing refresh
Choose insert, upsert, or refresh for each marketing ingestion path. For refresh, review the complete replacement input with the data owner: all target data is replaced, and omitted records are not retained.
Review Apex changes before compiling at 68.0
Compare the Apex change reference with the classes you plan to compile at API 68.0. For archived-data tests, review the new SF_Archive methods separately.