Automation & UAT Readiness

SALESFORCE AUTOMATION EXECUTION READINESS CHECKLIST.

Before UAT, imports, or bulk changes — understand what automation may run when records are saved. Review Flows, Apex, validation rules, and save-time constraints before testing.

Read-only diagnostics · Review-ready workbooks · No package install · No Connected App

Salesforce automation execution readiness is the practice of reviewing what automation may run when records are created or updated — before UAT cycles, bulk imports, or change work that involves record-level operations.

Admins often need to answer the question "what runs on save?" before they can confidently proceed with a test cycle or a data load. Metadata review can show what exists and what its trigger conditions are — but it does not simulate every runtime path. That distinction is what this checklist addresses.

The Core Challenge

WHY "WHAT RUNS ON SAVE?" IS HARD TO ANSWER.

Multiple automation types can be active on the same Salesforce object at the same time. Each type has its own execution timing, trigger conditions, and interaction with the Salesforce save order. In a complex org, any combination of the following may run on a single record save:

  • Before-save record-triggered Flows — modify field values before the record is written
  • After-save record-triggered Flows — run after the record is committed, may create related records or trigger downstream logic
  • Apex triggers (before and after) — custom code that fires before or after the DML operation
  • Validation rules — evaluate field conditions and block the save if they fail
  • Approval processes — may require record routing before the record can be updated in certain states
  • Legacy Workflow Rules and Process Builder automation — still active in many orgs, still fire on matching conditions

The Salesforce Platform execution order determines the sequence — but knowing which automation types are present on the object is the prerequisite for any meaningful review.

Checklist

AUTOMATION EXECUTION READINESS CHECKLIST.

Record-triggered Flows

  • List all active record-triggered Flows on the object in scope
  • Separate before-save Flows from after-save Flows — these run at different points in the save cycle
  • Note the trigger conditions for each Flow — which field values or record states cause it to fire
  • Identify whether any Flows create or update related records — these effects scale with bulk operations
  • Check for Flows that send notifications, emails, or alerts — consider the volume impact at scale

Apex triggers

  • Confirm whether Apex triggers are present on the object in scope
  • Note whether they are before-trigger, after-trigger, or both
  • Flag any Apex triggers that interact with the same fields as the change or import
  • Consider whether the Apex logic has known behavior at bulk scale — Apex should be bulkified but not all implementations are

Validation rules and legacy automation

  • List active validation rules on the object — review their conditions against the data in the test or import set
  • Check whether any Workflow Rules or Process Builder automation is still active on the object
  • Note approval process entry criteria that may trigger on field value changes

Required fields, picklists, and record types

  • Confirm all required fields are present and populated in the test or import dataset
  • Verify restricted picklist values match the valid entries for the record type in use
  • Check record type availability for the profiles and permission sets of the users performing the operation

Relevant Workbook

Automation Inventory

Automation Inventory catalogs active Flows, Apex triggers, validation rules, approval processes, and legacy automation for selected objects — producing a review-ready XLSX workbook before UAT, bulk imports, or change work.

Learn more →Run diagnostic →View sample workbook →

Relevant Workbook

Impact Awareness

Impact Awareness reviews selected-object readiness across required fields, lookups, record types, picklists, validation rules, and automation context before testing or record-level change work.

Learn more →Run diagnostic →View sample workbook →
Limitations

WHAT METADATA REVIEW CANNOT PROVE.

An automation inventory shows what exists and what its metadata configuration looks like. It does not:

  • Simulate how automation will behave at runtime for a specific set of records
  • Trace every interaction between Flows, Apex, and validation rules across a complex save cycle
  • Identify automation ordering conflicts that only appear in live execution
  • Confirm that automation marked active is correctly configured and will not produce an error at runtime
  • Replace sandbox testing before production changes

Automation inventory is the starting point — sandbox testing against a representative data set is required to validate behavior before production changes proceed.

Also see Salesforce Flow review before bulk updates for a focused look at bulk-update automation risks.

FAQ

FREQUENTLY ASKED QUESTIONS.

How do I know what automation runs when a Salesforce record is saved?

Start with an automation inventory for the object in scope. Review active record-triggered Flows, Apex triggers, validation rules, approval processes, and any legacy Workflow Rules. Each type fires under different conditions and in a defined order. Metadata review can show what exists — simulating every runtime path requires testing in a sandbox environment.

Do Flows and Apex triggers both matter during record updates?

Yes. Both can fire on the same record save. A before-save Flow runs first and can modify field values before the record is committed. After-save Flows and Apex triggers fire after the record is saved and can create related records, send notifications, or trigger downstream logic. Understanding which types are active on a given object is the first step.

Can metadata review simulate automation execution?

No. Metadata review can show what automation exists, what objects it covers, what its trigger conditions are, and whether it is active. It cannot simulate every runtime execution path, trace automation ordering conflicts in detail, or guarantee that all behavior is covered. Sandbox testing is required to validate automation behavior before production changes.

What should admins check before UAT?

Review active automation on all objects in the UAT scope — Flows, Apex, validation rules, required fields, restricted picklists, record types, and permission constraints on test users. Automation that runs in UAT may behave differently than expected if the test data does not match the conditions the automation was designed for.

How does KeelCadence help with Salesforce automation readiness?

Automation Inventory catalogs active Flows, Apex triggers, validation rules, and approval processes for selected objects in a review-ready XLSX workbook. It helps teams understand what automation exists before UAT, imports, or bulk changes — without simulating execution or making claims about runtime behavior.

Review Before Change

CREATE A REVIEW-READY WORKBOOK BEFORE MAKING SALESFORCE CHANGES.

Run a read-only KeelCadence diagnostic to surface metadata, access, automation, field, and readiness signals before cleanup, UAT, imports, handoff, or change work.

Run Automation Inventory →View Sample Workbook

Read-only · No package install · No Connected App setup · No Salesforce writes

Home/Resources/Salesforce Automation Execution Readiness Checklist

Trust & Security

KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.