*Architect picks #7*
Salesforce Winter '27 (API 68.0) adds native actions for marketing follow-ups and decision-table calls, plus Flow Tags for discovery. The first candidates to review: flows with repeated notification logic and Apex controllers that exist only to invoke a decision table.
New Salesforce Winter '27 automation features
Attach marketing follow-ups to flow outcomes
Marketing Completion Actions attach follow-up actions to flow outcomes without separate logic for each outcome. Add an Action element and select Marketing Completion Actions. Supported actions include notifying a user and assigning a lead to a user or queue. Availability starts in August 2026.
Test against one flow’s existing notification or lead-assignment logic. Confirm the outcomes with the campaign owner, and schedule the work around August availability.
Call decision tables without an Apex controller
An Omniscript or Integration Procedure can call an activated decision table directly through a Decision Table action. Map incoming JSON to table inputs using Omnistudio merge-field syntax; results merge back into the JSON. Business Rules Engine must be enabled.
Read the controller before proposing its removal. Compare the native action’s input mapping and returned JSON with the existing invocation against the activated table. Identify any controller behavior beyond the call, and include its replacement in the code review.
The architect should review those comparisons before code removal. Bring in the process owner if the change extends beyond the invocation.
Classify flows with tags and tag groups
Flow Tags add structured classification to the flow list. Create tags and tag groups in the Automation App’s Tags tab, assign tags individually or in bulk, and filter the Flows list by one or more tags. Authors can also set tags from Flow Builder’s Save As modal.
Start with a search you actually need, such as finding flows for a business process. Tag a small set and inspect the filter results before expanding the scheme.
Flow Builder interface and decision table refresh changes
Revisit refresh runbooks
Decision table refreshes default to processing only changed data after the table’s first full refresh. Multiple tables can refresh concurrently rather than queuing. These changes apply where Business Rules Engine is enabled.
Measure the first full refresh separately from subsequent incremental runs, and check whether the selected tables refresh concurrently. Revise runbook steps that assume full processing on every run or wait for another table to finish.
Use those measurements for scheduling. The release data gives no numerical speed guarantee.
Flow Builder interface changes
- **Denser canvas.** The auto-layout canvas is more compact. Element-card info tooltips expose the element type and API name, and the End element becomes a small icon. Use the tooltips to match canvas elements to API names during technical reviews.
- **Direct decision navigation.** Decision elements gain path highlighting, resizable property panels and inline path-name editing. Click a path to jump to its conditions, drag to resize the panel, or double-click a path name to rename it.
- **Cosmos theme.** Flow Builder automatically matches the org’s active theme, with updated spacing and palette. No setup is required. SLDS 2 Dark Mode is not supported in Flow Builder.
Find unused resources in auto-layout
The Unused filter in the Flow Builder Toolbox shows resources with no recorded usage. It is available only in auto-layout and clears when Flow Builder closes. Cleanup instructions should include reapplying the filter after reopening the builder.
Licensing and audience-flow copy defaults that need attention
Automatic labels require an Agentforce license
Auto-generated element labels derive from configured properties and update as you build. The behavior is on by default when Flow Builder opens and requires an Agentforce license. Manually edited labels are preserved.
Before adding generated labels to authoring standards, confirm that the authors have the required license. Test the wording after property changes and verify that manual edits survive. Use those results to document when authors should supply their own labels.
Decide which campaign assets to copy
Save As New Flow for audience flows lets authors duplicate associated email, SMS, WhatsApp and RCS messages or link to the originals. Authors can also choose whether to copy segments and list trigger definitions. Segments remain linked by default to conserve asset limits, and Flow Builder validates quota before creating copies.
Agree with the campaign owner which assets to copy and which to reuse before using Save As New Flow. Check the segment choices and quota validation explicitly: a new flow still shares its default-linked segments with the original.