Today5 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 12The independent daily for Salesforce admins, developers and architects5 stories · 1 brief

Must-readFlow and admin

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?

RecommendedAgentforce and AI

Securing Agentforce against prompt injection and data exfiltration (opens in a new tab)

You will learn how untrusted input can steer Agentforce into exfiltrating data via DNS lookups, and which Einstein Trust Layer controls actually mitigate these risks.

Why read this

You will also get a practical checklist for configuring runtime identities, permissions, and safe workflows.

Research by Zenity demonstrates a prompt injection chain where untrusted text stored in a Web-to-Lead record steers Agentforce to query authorized account data. The injected instructions embed the results in an external hostname, exploiting a Trusted URLs parsing discrepancy that triggers a DNS lookup to exfiltrate information without requiring user interaction.

The Einstein Trust Layer provides several guardrails, including semantic filters, zero data retention agreements, and audit logging, but it does not enforce authorization policies or stop agents from querying records they are already permitted to see. Data masking is currently disabled for agents, and prompt defenses remain probabilistic rather than absolute.

Securing Agentforce requires strict identity and permission hygiene. Administrators must verify whether agents run under employee profiles, dedicated service users, or integration accounts, then restrict object and field access accordingly. Replacing broad query tools with custom Apex actions that enforce user mode and explicit Sharing Rules reduces exposure.

A recommended architecture isolates unauthenticated submissions behind a read-only lead triage agent, followed by human review before downstream agents handle outbound communication. This layered approach prevents poisoned data from reaching internal databases or messaging channels like Slack.

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

Worth reading?

RecommendedApex and platform

Block unwanted outbound emails in Email-to-Case using Custom Metadata and Apex (opens in a new tab)

The reader will learn how to prevent accidental outbound replies in Email-to-Case by storing blocked addresses in a Custom Metadata Type and enforcing them with an Apex trigger on EmailMessage.

Agents frequently reply to internal distribution lists or automated mailboxes during Email-to-Case interactions, causing infinite loops or unintended data exposure. Standard workarounds rely on hardcoded Validation Rules or Apex classes, which demand repeated testing and deployments whenever the blocklist changes.

The proposed solution moves the restriction list into a Custom Metadata Type. Administrators gain direct access to manage blocked addresses through Setup, removing the need for developer intervention or version control cycles for simple address updates.

Enforcement occurs via a before insert trigger on the EmailMessage object paired with a dedicated handler class. The code isolates outbound communications, verifies the fifty hundred parent identifier to limit scope to cases, and compares recipient addresses against the metadata records using case insensitive matching.

When a restricted address appears in the to or cc fields, the trigger applies an error that prevents the message from sending. This architecture keeps the logic modular, avoids interfering with inbound case creation or unrelated email automation, and provides a reusable template for other metadata driven routing rules.

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

Worth reading?

Flow and admin

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?

Agentforce and AI

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?

In brief