Today4 stories · 4 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 29The independent daily for Salesforce admins, developers and architects4 stories · 4 briefs

Must-readReleases

Which Salesforce Certificate changes actually affect your org (opens in a new tab)

You will learn which of the three upcoming certificate changes apply to your org, how to check for mutual TLS and certificate pinning, and what to ask your integration team before the March 2027 deadlines.

  1. Check whether the org uses inbound mTLS
  2. Review which systems connect to Salesforce
  3. Plan renewals as certificate lifespans shorten
  4. Confirm connected systems trust Mozilla's roots
Three certificate changes, each checked in turn to see whether an org is affected

An “ACTION REQUIRED” email from Salesforce on October 29, 2026, warned of three certificate changes that could cause security problems or service disruption. The article argues that many orgs need only a few checks. Admins should first ask three questions: whether mutual TLS (mTLS) is in use, which is checked under Certificate and Key Management (the Mutual Authentication Certificates section is hidden until Salesforce Support enables it); whether external systems such as middleware or on-premises servers connect to Salesforce; and whether their team renews public certificates by hand.

The first change affects only orgs using mTLS. Under Chrome Root Program Policy v1.8, a certificate can no longer serve both server and client authentication, so existing dual-use certificates may not be renewable after March 2027. The fix is a dedicated client certificate from a supported public authority, such as DigiCert, SSL.com, Sectigo or GlobalSign. Salesforce does not currently accept private certificate authorities for inbound mTLS. The integration owner handles the replacement, while the admin confirms who that is and that a plan exists.

The second change shortens the maximum lifespan of publicly trusted TLS certificates: 398 days before March 2026, 200 days from then, 100 days from March 15, 2027, and 47 days from March 2029. Salesforce rotates its own certificates at least 45 days before expiry, so the risk lies with systems that pin a specific certificate, which Salesforce strongly advises against. Self-signed certificates are not subject to the new limits but still expire after a year. Admins should decide who owns manual renewals, assign the Expired Certificate Notification permission, and consider automation through the Metadata API Certificate type.

The third change concerns root certificates and trust stores. Salesforce recommends that connecting systems trust all roots on Mozilla’s Server Authentication list, since it may switch roots. Older Java or SAP integrations, particularly those more than ten years old running JDK 8 or earlier, may need extra files to support its cryptographic algorithms. Self-signed and custom CA-signed certificates are exempt, and MuleSoft users should follow separate guidance. The admin’s role is to pass three questions to IT about trust stores, pinning and Java versions, and then confirm that each check has an owner. Salesforce is also running webinars for engineering and security teams on November 4 and 5, 2026.

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

Worth reading?

RecommendedFlow and admin

Showing an Apex Collection in a Screen Flow Data Table without a Custom Object (opens in a new tab)

You will learn how to define an Apex row type, return it from an invocable action and bind it to a Screen Flow Data Table with a Unique Identifier, avoiding helper objects.

Why read this

You will also learn the current limit that inline editing is not yet supported.

  1. Define row class with @AuraEnabled fields
  2. Return list from invocable action
  3. Store output in Apex-typed collection variable
  4. Bind to Data Table with Unique Identifier
How an Apex collection reaches a Screen Flow Data Table

Since Winter ’26 (API 65.0 and later), a Screen Flow Data Table can take a collection of an Apex-defined type as its Source Collection. Choosing a field as the Unique Identifier lets the table treat each item as a record, so users can select rows and the flow can reuse them. Display and selection work now, but inline editing for these collections is still pending.

The article contrasts this with older workarounds: creating a Custom Object that mirrors the Apex class, inserting and deleting temporary records, using a Transform element, or building a custom Lightning Web Component. Each works but leaves extra metadata to maintain. The walkthrough shows a sample FxRate class with @AuraEnabled fields, an invocable GetFxRates action that wraps the list in a result class, and the flow wiring that stores the output in a collection variable and feeds it to the table.

The author advises choosing a stable, unique key such as a record Id, an ISO currency code or a business key as the Unique Identifier, and generating one in Apex if the source has none. The pattern suits currency or stock quotes from an external API, financial calculations resolved in Apex, and batch results that should not be persisted.

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

Worth reading?

Architecture

A small owned trigger framework built around an explicit handler contract (opens in a new tab)

You will learn how to structure an Apex trigger framework with a single dispatcher, a recursion guard that tracks record IDs, layered bypass controls via Custom Metadata and a permission, and user-mode selectors with a savepoint-based unit of work.

Why read this

The author also explains why they chose an owned baseline over a third-party framework.

  1. Check bypass layers
  2. Confirm trigger context
  3. Check recursion guard
  4. Mark records as handled
  5. Call context hook
The trigger lifecycle checks run in a fixed order before the context hook is called

The author argues that Salesforce trigger frameworks usually fail on their contract rather than their code: when a handler runs, when it is skipped, what happens on re-entry, and who may bypass it. Their baseline is deliberately small, with a one-line trigger that delegates to a dispatcher. The lifecycle checks bypass settings first, confirms the code is running inside a trigger, resolves the context, verifies the SObject type, checks the recursion guard, marks records as handled, and then calls the context hook. Handlers only override the contexts they need and delegate rules to domain classes.

The recursion guard tracks which record IDs a named handler has already processed in the transaction, instead of using a static boolean. This avoids both blocking legitimate second passes for different records and re-entry from after-triggers. Bypass works in three layers: a runtime bypass for tests and controlled operations, an Is_Active__c flag on Custom Metadata to disable a handler without deployment, and a Custom Permission for integration users during data loads. Metadata is read once per transaction. The surrounding layers keep business logic out of the trigger, with selectors running in user mode and a unit of work that commits DML in a fixed order inside a savepoint.

The author reports that static checks and a check-only compile against an org caught configuration issues, and that the test suite exposed a null dereference outside trigger context and a wrong assumption about scheduled job execution in tests. The article closes by listing next steps, including removing defaults from test factories and enforcing the Permission Set in the deploy pipeline.

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

Worth reading?

Career and certifications

Platform App Builder exam refresh puts more weight on Flow and Agentforce (opens in a new tab)

You will learn what the August 2026 refresh of the Platform App Builder exam changed, including the heavier Flow focus and the new Agentforce coverage, and how to adjust your study plan accordingly.

  • 63%: Previous pass rate
  • 73%: Pass rate after the refresh
  • 32%: Share of exam for Business Logic and Process Automation
The exam refresh moved the pass rate up by ten percentage points

The Certified Platform App Builder exam was refreshed on August 21, aligned to the Summer ’26 release, and its pass rate moved from 63% to 73%. According to a podcast interview with Salesforce’s Alexis Kingma, the largest change is depth on Flow. Candidates are now asked to choose the right flow type for a scenario, troubleshoot a broken flow, and maintain and monitor flows over time, rather than simply show they can build one.

Agentforce is also included, but framed as one automation tool within the app builder’s toolkit rather than as a specialist topic. Candidates should recognize when it is an option and when reaching for it makes sense. Salesforce said the passing score was set using the Angoff method, in which a panel of experts estimates how many minimally qualified candidates would answer each question correctly. A higher passing score therefore means the panel expected a borderline candidate to get more questions right, which the author reads as a higher bar for the role.

The author advises budgeting time for Flow troubleshooting and monitoring, studying Agentforce under the Business Logic and Process Automation section (32% of the exam), using the Trailhead trail as a guide to likely topics, and reading the verbs in the exam guide objectives closely, since “create and configure” implies hands-on skill while “describe” implies conceptual knowledge.

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

Worth reading?

In brief