The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Flow Test Mode adds saved Test Scenarios, assertions and mock outputs to Flow Builder (opens in a new tab)

You will learn how to create and save Flow test scenarios, add assertions and mock external action outputs, and why these tests are not yet enforced at deployment.

Why read this

The piece also notes that FlowTest is a separate metadata type to include when deploying.

  1. Save Test Scenario with inputs
  2. Enable Automated Test Scenario
  3. Add assertions and mock outputs
  4. Run All for coverage and results
How a saved Test Scenario runs automatically with assertions

Salesforce’s Winter ’27 release introduced Flow Test Mode, a dedicated testing canvas for Autolaunched and Record-Triggered Flows that is currently in beta. It is enabled through the Process Automation Settings page in Setup, and the author recommends trying it in a sandbox first. Within the new canvas, builders can debug by record Id or name, test primitive collection variables by separating values with semicolons, and save reusable Test Scenarios with labels, descriptions and run options such as rollback mode. Scenarios can be run manually or set to automatic, with assertions checking expected results, such as whether an element was visited or a field has a given value, and with the choice of which flow versions to test. Mock outputs let builders supply fabricated responses for external action elements, so tests can run without calling the endpoint and can force success or fault paths.

The author highlights practical uses: rerunning a scenario that reproduces a bug until it is fixed, using saved assertions for regression testing after org changes while watching coverage and results, and testing integrations without configuring live connections. He also explains deployment: FlowTest is its own metadata type, separate from the flow, so tests must be packaged and deployed individually. Currently a flow can be deployed without its tests, making them a nice-to-have rather than an enforced requirement as Apex tests are, and the author hopes enforcement will come once the feature reaches general availability.

The piece concludes that Flow Test Mode still falls well short of Apex testing, which requires at least 75% coverage before production deployment and cannot be bypassed, while flows can currently be built directly in production. Mock outputs are a point-and-click analogue of Apex’s HttpCalloutMock approach, and the Test Discovery API can run Apex and flow tests together. Overall, the author sees the feature as a significant and promising step for Flow, though it is still in beta.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Ten Flow design mistakes that break Salesforce orgs as they scale (opens in a new tab)

You will learn how bulk record processing, database operations inside loops, repeated writes, hard-coded IDs and weak fault handling make Flow fail under load, and how to design around each one.

Why read this

The piece is practical guidance for anyone whose orgs run record-triggered automation at volume.

This Salesforce Ben article, written for architects, lists ten Flow design mistakes that cause failures as orgs grow, and suggests a fix for each. The first concerns treating Flow as a single-record tool: bulk operations from Data Loader or List Views share one transaction’s governor limits, so authors should use before-save flows for same-record updates, tighten entry conditions, and make invocable Apex bulk-safe. The second warns against database operations inside loops, recommending retrieving records before the loop, changing values in memory, and saving a collection once afterwards, with Collection Filters and Transform as alternatives. The third covers writing to the database too often, since each write can fire further automation and cause record-locking, so decisions should come first and writes should be batched near the end.

The next several points cover maintainability, testing and error handling. Hard-coded IDs break when flows move between environments, so the article recommends looking up records by DeveloperName, using Custom Metadata, Custom Labels or Custom Settings. Flows without deliberate fault handling leave failures to Salesforce’s default response, so authors should choose between blocking saves, guiding users, or logging failures, and should understand how rollback differs for unhandled errors, handled faults and explicit rollbacks. Testing with a single record gives little assurance, so the article urges bulk tests of at least 200 records, representative data, and separate logic, transaction-limit and load testing.

The final points address structure and design. Monolithic flows are hard to maintain, so the piece suggests subflows for repeated logic, self-contained processes and frequently changing rules, while warning against too many tiny subflows and recommending grouping flows by business purpose. Transaction boundaries matter because governor limits apply per transaction, and asynchronous paths, scheduled paths, screens, Wait elements and Platform Events can move work out of the original save, with the trade-off that committed changes cannot be rolled back. Screen Flows need care when users click Previous, which can cause duplicates, so the article advises saving at the end and making steps idempotent. Finally, it cautions that data model problems such as data skew, non-selective queries, recreated roll-up functionality and master-detail choices can limit what Flow design alone can fix. The conclusion advises reviewing the highest-volume objects first.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Salesforce's Braze acquisition raises questions for Marketing Cloud teams (opens in a new tab)

You will learn what the announced Braze acquisition means for Marketing Cloud Engagement and Marketing Cloud Next, and which skills and architectural decisions it may affect.

Why read this

The article also makes clear that no combined roadmap exists yet.

Marketing Cloud Engagement

  • Relies on Journey Builder
  • Established automation offering

Marketing Cloud Next

  • Emphasises Data 360 and AI
  • Automation through Flow Builder
The two Marketing Cloud platforms the Braze deal must fit alongside, as the article describes them

Salesforce has agreed to acquire Braze, an engagement platform that reacts to customer behaviour in real time across email, push, in-app messaging, SMS and WhatsApp, in a deal valued at around $5.66B. Salesforce expects to close during fiscal 2028, subject to shareholder and regulatory approval. Braze says in an SEC filing that its integration with Data 360, Customer 360 and Agentforce remains a possibility and that no decisions have been made.

The article notes that Salesforce has not published a combined roadmap showing how Braze’s capabilities will overlap with Marketing Cloud Engagement, which relies on Journey Builder, and Marketing Cloud Next, which centres on Data 360, AI and Flow. Salesforce’s president of applications and marketing suggested Braze would extend Marketing Cloud Next with real-time, mobile-first engagement rather than replace Marketing Cloud.

For practitioners, the piece argues that the greatest risk is over-specialising in one orchestration tool, and that event tracking, identity, API integration and data architecture skills will grow in value. It also expects consulting work around integration, migration and platform rationalisation, while warning that pricing, packaging and third-party integration openness remain unknown.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Five timing decisions that determine whether a Scheduled Flow runs reliably (opens in a new tab)

You will know five design choices to settle before activating a Scheduled Flow: run window, repeat-safety, batch sizing, failure handling and run context.

Why read this

The article is a practical checklist rather than new platform information.

  1. Pick a quiet run window
  2. Make repeat runs safe
  3. Size batches for volume
  4. Catch failures loudly
  5. Confirm the run context
The five timing decisions to settle before activating a Scheduled Flow, in order

The author argues that a Scheduled Flow should be designed around timing, since nobody watches it run. The run window should avoid overnight integrations, data loads and backups that might lock the same records, so admins should check scheduled Apex jobs and ask integration owners before choosing a start time.

Because a daily Scheduled Flow re-evaluates its entry criteria on every run, records that still qualify will be processed again. The article recommends a flag field, a date stamp or a processed checkbox so that updates happening once are not repeated, and it treats batch sizing as a deliberate design decision, warning that a Flow tested on fifty records can hit governor limits at fifty thousand.

The piece also covers failure handling, which is quieter than for Record-Triggered Flows, and run context, since Scheduled Flows run in system context by default and bypass Sharing Rules and field-level security. It closes by suggesting a monthly review of every active Scheduled Flow as business rules and fields change.

Read the original at dev.to (opens in a new tab)

Worth reading?

Handling Flow errors with Fault paths, logging and notifications (opens in a new tab)

You will learn why a Flow can fail without anyone noticing, and five practices for using Fault Paths to log, notify and test failures.

Why read this

The advice is standard but practical for admins maintaining automation.

  1. Data element fails
  2. Fault Path runs
  3. Log failure record
  4. Notify admin or owner
How a failed Flow element is handled once a Fault Path is in place

A Fault Path is the branch a Flow takes when one of its elements fails, such as a record update blocked by a Validation Rule, a create that trips a duplicate rule, or a lookup that returns nothing. Without one, a Screen Flow shows the user a generic error, while a Record-Triggered Flow rolls back quietly and tells no one. The author argues that failures are easy to miss for this reason and that a missing branch is usually the cause.

The article gives five practices. Add a Fault Path to every data element, since failures often come from changes made elsewhere, such as a new Validation Rule or a permission change. Log each failure to a Custom Object, capturing the Flow name, element, record ID and the $Flow.FaultMessage value. Pair the log with a notification to an admin group or record owner so failures are seen the same day. Decide for each Flow whether a failure should stop the process or let it continue and flag the record for follow-up. Finally, test the failure paths in Flow Builder’s debug mode by feeding in data that violates a rule before each deployment.

The author also notes that a Flow can fail for different reasons depending on whether it runs in system or user context, because of Sharing Rules, field-level security or missing permissions. If a Flow fails only for some users, the run context should be checked first.

Read the original at dev.to (opens in a new tab)

Worth reading?

Must-read

How a local Apex runtime speeds up testing without replacing your org (opens in a new tab)

You will learn how a local runtime executes Apex and Flow metadata against an embedded database while enforcing governor limits and order of execution.

Why read this

The article explains how this approach accelerates the edit-test cycle and fits into your standard deployment workflow.

Local Apex runtime

  • Apex interpreter
  • Local database for SOQL and DML
  • Rule engine for limits and execution
The local Apex runtime is built from three core components

The article, written by the maker of renmy runtime (formerly Nimbus, renamed in October 2026), introduces a local Apex runtime: a program that executes Apex, SOQL and DML on a developer’s own machine without a Salesforce org. It argues that Salesforce developers work in a slow loop, where every edit is deployed to an org and tested there, while developers in Java, JavaScript and Go run tests locally in about a second. The author attributes this gap to Apex being multi-tenant and tied to the platform’s data model and order of execution. Cited costs include round trips to the org, CI that needs org credentials, outages that halt testing, and AI coding agents that cannot iterate quickly. A local runtime has three parts: an Apex interpreter, an embedded PostgreSQL database for real queries and DML, and the platform’s rules, including enforced governor limits, triggers and Flows in order of execution, and per-test rollback. A sample test runs in tens of milliseconds, and the article says the runtime is not a mock, not a Scratch Org and not a transpiler.

The article is clear that a local runtime does not replace the org. Lightning pages, user-facing Screen Flows, permission checks, real integrations and the deploy itself with Salesforce’s metadata validation still happen in the org. The author compares this to a Java team’s staging environment, which stays for integration and final checks but is not the only place code runs. The renmy deploy is described as running local test and coverage gates first, then a check-only validation in the target org, then the deploy. The tool also offers coverage reporting, mutation testing, a debugger in VS Code and JetBrains, an MCP server for AI coding tools, and an IDE plugin. A published benchmark reports that 837 tests from four open-source suites ran in about 2.4 seconds locally versus about 1 minute 46 seconds in an org, with all tests passing in both.

Installation is a single binary for macOS, Linux and Windows, with no JVM, Docker or org required, and the commands are renmy test “” from the project root, plus options for single classes, coverage and a browser dev UI. The free tier covers individual developers, while Pro and Team tiers are free during the public beta and listed at $19 per month and $49 per developer per month. The article links to a parity record, which it describes as not a claim of 100 percent accuracy, and to GitHub for issues and releases.

Read the original at dev.to (opens in a new tab)

Worth reading?

Must-read

Winter '26 adds multi-column sorting and Flow version comparison (opens in a new tab)

Readers will learn which Winter '26 updates improve daily admin workflows, including multi-column List View sorting, enhanced Flow debugging, and localized report labels.

Winter '26 release

  • List Views
  • Flow Builder
  • Reporting and dashboards
Main update categories in the Winter '26 Salesforce release

The Winter ’26 release introduces several quality of life improvements for administrators, starting with List Views. Users can now sort records by up to five columns simultaneously, each set to ascending or descending order. Configuring this stays persistent until manually reset. Field pickers within List View controls also support type ahead search, allowing admins to quickly locate fields by typing characters and using keyboard shortcuts.

Flow Builder receives substantial updates to streamline automation design and management. Decision elements can now leverage Generative AI to analyze unstructured data and route records based on tone or urgency. Flows can automatically trigger when files attach to records, and newly created records can be referenced immediately without additional query elements. Debugging becomes easier with a resizable side panel and card based results that jump directly to canvas elements. Administrators can also compare flow versions side by side to track changes across autolaunched, scheduled, and record triggered types.

Reporting and dashboard capabilities expand with localization and security features. Labels for reports and dashboards can now be translated through the Translation Workbench, covering widget titles and footers. Exported reports include a beta option to block spreadsheet formula interpretation, preventing accidental execution of malicious strings. Dashboard charts in Lightning Experience will soon support reference lines, mirroring functionality previously limited to report charts. The author recommends testing these updates in a sandbox before production deployment.

Read the original at dev.to (opens in a new tab)

Worth reading?

Recommended

How to invoke a Salesforce Screen Flow directly from a Slack workspace (opens in a new tab)

Readers will learn the exact steps to configure the Sales Cloud for Slack integration and route a Screen Flow into a Slack channel or direct message without leaving their messaging app.

The article outlines a method for running a Salesforce Screen Flow inside Slack by leveraging the Sales Cloud for Slack application. It begins with the prerequisite one-time connection between the Salesforce org and a Slack workspace, followed by assigning a Permission Set that includes system permissions for managing Slack app organization connections and user mappings.

Administrators must enable the Sales Cloud for Slack feature in Setup and install the corresponding app in their Slack directory. Once connected, creators can design a standard Screen Flow in Flow Builder and activate a hidden advanced setting labeled Make available in Slack during the save process.

To actually trigger the flow, a second autolaunched or Record-Triggered Flow acts as an invoker. This parent flow uses an action element to call the enabled Screen Flow, passing a Slack conversation identifier to determine whether the interactive button appears in a public channel or a private direct message. The piece concludes by noting that Salesforce automatically generates a background action for each enabled flow and advises clear button labeling for end users.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Must-read

Salesforce delivers long-awaited Flow actions, List View permissions, and User history tracking (opens in a new tab)

Readers will learn how to configure mass Screen Flow actions in List View layouts, restrict List View sharing without granting broad permissions, and enable Field History Tracking on the User object.

Delivered IdeaExchange Features

  • Flow Quick Actions in List Views
  • Manage Shared List Views Permission
  • Inline Editing on List Views
  • Field History Tracking for Users
  • Restart Superbadge Progress
Five long-requested IdeaExchange ideas finally shipped in recent releases

The latest IdeaExchange updates highlight several features delivered in Winter ’27 and Summer ’26 that resolve long-standing administrative limitations. Administrators can now execute Screen Flow actions against multiple records selected in List View layouts or Related Lists by passing record identifiers into a text collection variable, eliminating the need for custom components or workarounds.

A new Manage Shared List Views permission replaces the broad Manage Public List Views requirement, allowing targeted sharing without exposing all public views across the organization. Winter ’27 also removes the restriction preventing inline editing in List Views containing multiple record types, though administrators must manually activate the setting in User Interface Settings and test it carefully due to varying Validation Rules and picklist values.

Field History Tracking is now available for the User object, monitoring up to twenty fields such as profile, role, and manager changes for eighteen months. The article also notes that Trailhead Superbadges can now be restarted after completion, supporting skill reinforcement rather than single-use certification, while additional roadmap items like dark mode and Opportunity restriction rules remain in development.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

New Collection Filter Criteria Resource simplifies Flow Builder data manipulation (opens in a new tab)

You will learn how the new Collection Filter Criteria Resource moves collection filtering out of the Flow canvas and into reusable resources.

Why read this

The piece explains how this change reduces visual clutter, optimizes governor limits, and enables in-memory sorting and filtering.

Collection Filter Criteria

  • Configured via Manager tab
  • Returns only first match
  • Eliminates extra Loop steps
  • Supports child relationships

Collection Filter and Sort

  • Placed directly on canvas
  • Returns full record collection
  • Requires additional Loop steps
  • Standard element configuration
Comparison of the new Collection Filter Criteria resource against existing Flow elements

Introduces the Collection Filter Criteria Resource as a Winter ’27 preview feature that shifts collection filtering from canvas elements to the resource manager. It replaces the traditional Collection Filter node, allowing administrators to define dynamic filter conditions and sort orders directly in memory without triggering additional SOQL queries or DML operations.

Explains the practical benefits, including cleaner Flow Builder canvases and optimized transaction limits. Multiple distinct filter views can now point to a single source collection, eliminating sequential logic and reducing visual complexity while speeding up execution across screen and autolaunched flows.

Covers advanced integration with Apex defined variables, noting that future updates will allow filtering based on child relationships within custom data structures. This capability aims to remove unnecessary loops during collection processing and hints at upcoming list and map functionality resembling native Apex collections.

Read the original at Salesforce Break (opens in a new tab)

Also told by Salesforce Admins Blog (opens in a new tab), Salesforce Time (opens in a new tab)

Worth reading?

A practical workflow for cleaning Salesforce data before implementing AI (opens in a new tab)

Readers will learn a structured five-step process for auditing and cleaning Salesforce records before deploying artificial intelligence features.

Why read this

The piece explains how to automate ongoing data hygiene using standard administrative tools to prevent model failures.

The article argues that artificial intelligence initiatives in Salesforce consistently fail when trained on unclean data, emphasizing that pattern matching models amplify existing record errors rather than masking them. Common issues include duplicate contacts and leads, incomplete required fields, inconsistent Picklist values, and stale records that cause Agentforce assistants to route cases incorrectly or generate inaccurate summaries.

To address these problems, the author recommends running a comprehensive data audit before approving any artificial intelligence project. This involves generating reports on empty key fields, executing Duplicate Jobs, and manually sampling records to create a data health summary for leadership approval. The cleanup must follow a strict sequence starting with deduplication, followed by populating critical fields, standardizing formats through Validation Rules, archiving inactive records, and enforcing data entry standards at the source.

Sustainable data quality requires moving beyond one-time projects by implementing automated maintenance routines. The author suggests scheduling recurring Duplicate Jobs, distributing weekly exception reports to record owners, and tracking completeness metrics on a dashboard. Once real data ownership is established and the operational layer is secured, Salesforce artificial intelligence capabilities such as lead scoring and case classification can function reliably without undermining user adoption.

Read the original at dev.to (opens in a new tab)

Worth reading?

Send Custom Notifications in Salesforce using Flow Builder without writing Apex (opens in a new tab)

You will learn how to configure Notification Builder and build a Flow that pushes targeted alerts to desktop and mobile users.

Why read this

The guide covers recipient targeting, deep linking, and best practices to avoid notification spam.

The article explains how to implement Custom Notifications in Salesforce using Flow Builder instead of Apex. It begins by outlining the prerequisite setup in Notification Builder, where administrators define a notification type and select delivery channels such as desktop or mobile.

It then walks through creating a Record-Triggered Flow with entry criteria to control when alerts fire. The guide details how to use the Send Custom Notification action element, wire up the notification type ID, construct dynamic titles and bodies with formula resources, and populate recipient collections using Get Records. It also explains how to set a target ID to enable deep linking directly to the relevant record.

A practical scenario demonstrates using a scheduled Flow to alert managers about stalled high-value opportunities. The author concludes with implementation tips, emphasizing concise titles, aggressive filtering to prevent spam, verifying sharing settings for non-admin testers, and reserving mobile push notifications for urgent escalations.

Read the original at dev.to (opens in a new tab)

Worth reading?

Connecting Slack to Salesforce for record context and automated alerts (opens in a new tab)

Readers will learn how to use Guided Slack Setup to link a workspace, place the Slack component on record pages, and route Flow notifications to channels.

The article outlines the steps for linking a Slack workspace to a Salesforce org using the native Guided Slack Setup flow. Administrators verify the connection status, authenticate with Slack, and mark each configuration step as complete to maintain a clear rollout trail.

Once the connection is active, the Slack component can be added to Lightning Record Pages through App Builder. This places conversation history directly on layouts for objects like Accounts, allowing team members to view messages and reply without leaving the CRM while preserving record context.

The guide also demonstrates how to send automated alerts to Slack channels by configuring Flow Builder processes that trigger on stage changes or escalations. Users gain the ability to search for records and update fields from within Slack, with modifications syncing back to Salesforce in real time.

Rollout recommendations stress validating permissions with standard profiles, launching with a single object, enforcing consistent channel naming, and tracking adoption rates to optimize component placement and workflow design.

Read the original at dev.to (opens in a new tab)

Worth reading?

Decouple dynamic business rules from Salesforce Flow using reference tables (opens in a new tab)

You will learn how to move static routing logic out of Flow elements into external reference tables, reducing deployment risk and enabling non-technical staff to manage updates.

The article argues against hardcoding business rules directly inside Flow decision nodes or Formula Fields, explaining that this practice creates maintenance debt and increases deployment risks. Instead, it recommends externalizing ever-changing logic into reference tables stored as either Custom Objects or Custom Metadata Types.

A detailed comparison outlines when to choose each storage method, noting that Custom Objects are better for frequently updated operational data managed by business users, while Custom Metadata Types suit static configuration moved through deployment pipelines. The author walks through building a territory assignment engine using a Custom Object to route Opportunities based on postal codes.

Key implementation details include optimizing the Flow for fast field updates, using a Get Records element with a CONTAINS filter, and sorting results by last modified date to handle overlapping rules safely. The piece also warns about partial string matching pitfalls and suggests padding delimiters to prevent incorrect matches.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?

Salesforce Winter '27 brings Flow testing, bulk screen actions, and higher heap limits (opens in a new tab)

Readers will learn how to implement the new Flow Test Mode, process multiple records via List Views, and adjust to increased Apex heap limits and updated REST API versioning without manual tracking.

The release introduces Test Mode for Flow Builder, enabling repeatable testing with assertions and mock outputs for external callouts. Screen Flows launched from List Views or Related Lists can now process multiple selected records by accepting a lowercase ids collection variable. Reactive Formulas allow Conditional Visibility to evaluate same-screen inputs instantly, while new save-time validation catches missing Required Fields and character limit breaches before runtime.

Logic handling gains Split by Field Value and Split by Date elements, which create automatic branches but do not fully replace Decision elements. Navigation improves through an Unused Resources filter, Element Grouping, and an Edit History panel. Security receives a User Context option that enforces running user permissions, and an org-wide toggle preserves Manual Shares when record ownership changes.

Synchronous Apex transactions now support a 10 megabyte heap limit, while asynchronous transactions reach 25 megabytes, with a transition setting available to manage the shift. List View inline editing expands to include off-page layout fields and mixed Record Types. Integrations may use latest for REST API versioning, and Field History Tracking becomes generally available for the User object.

Read the original at Salesforce Ben (opens in a new tab)

Also told by Salesforce Ben on YouTube (opens in a new tab)

Worth reading?

Replicate the standard Recently Viewed List View inside a Screen Flow (opens in a new tab)

You will learn how to query the Recently Viewed object, merge its results with parent records using the Transform element, and sort the combined data for display in a Screen Flow.

Why read this

This approach replaces the missing native sorting capability in Flow Builder.

The article addresses the limitation of Flow Builder when trying to replicate the standard Recently Viewed List View, noting that direct sorting by view date is unavailable through standard Get Records elements. It introduces the Recently Viewed object as the underlying source that tracks records accessed by each user without requiring explicit user filtering.

The author demonstrates a six-step process starting with a Get Records element to fetch Recently Viewed entries filtered by the Account type. A Transform element extracts the record identifiers, which are then used in a second Get Records element to retrieve full Account data.

Because the original view date field resides outside the Account collection, another Transform element joins the two datasets using the record identifier as the key. The merged collection is subsequently ordered by the Last Viewed Date field using a Collection Sort element before being rendered in a Data Table component.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?

Use the new Group Element to organize Flow Builder canvas sections (opens in a new tab)

Readers will learn how to use the new Group Element in Flow Builder to visually organize related components and collapse sections for better navigation.

Why read this

The feature simplifies maintenance without altering execution logic.

Complex Flows often become difficult to navigate as they grow in size and handle multiple processes. Salesforce has introduced a Group element that lets administrators place related components inside a single container directly on the canvas. This visual organization makes it easier to locate specific logic and understand the overall structure.

Users can collapse these containers to hide detailed steps and reduce screen clutter while working on other areas. Expanding the group restores the full view when review or editing is required. The arrangement exists solely for layout purposes and does not modify how the automation runs.

The element supports standard editing operations such as cut, copy, paste, and ungroup. These tools allow teams to quickly restructure diagrams or duplicate entire logical blocks when replicating similar processes elsewhere in the same automation.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?