Platform App Builder · Domain 3 of 5

Platform App Builder Domain 3: Business Logic and Process Automation

The heaviest section at 32%: formula fields, roll-up summaries and validation rules, then building, choosing, approving with and troubleshooting flows, plus where Agentforce takes over parts of a business process.

Exam weight
32%
Official objectives
8
Estimated questions estimate
~19
Suggested study time estimate
18–22 hrs

About 17 min read Reviewed October 2026

Overview

Business Logic and Process Automation is the largest section of the Platform App Builder exam, now 32% of the score after rising from 28% in the Summer '26 update. Its eight objectives fall into two halves. The first three cover record-level logic: formula fields, roll-up summary fields and validation rules. The other five are about Flow and Agentforce: creating and configuring flows in Flow Builder, Flow Approval processes, choosing the right flow type, maintaining and troubleshooting flows, and using Agentforce to automate business processes.

The outline has caught up with the platform. Workflow Rules and Process Builder are gone from the objectives, classic approval processes are replaced by Flow Approval processes, and the old objective about avoiding automation errors has become a dedicated maintenance and troubleshooting objective. Flow is now the declarative automation tool you are expected to know in depth.

How it's tested

Questions present a business rule and ask which feature implements it, or present a broken automation and ask why it fails. Flow items often hinge on trigger type, timing such as before-save versus after-save, and entry conditions. Agentforce items ask what an agent can automate and how flows become agent actions.

  • Formula, roll-up, validation or flow

    A requirement calculates, aggregates, blocks or automates something, and you choose the lightest feature that fully meets it.

  • Pick the flow type

    The trigger is described, such as a button click, record save, schedule or platform event, and you select screen, record-triggered, scheduled, platform event-triggered or autolaunched flow.

  • Find the failure

    A flow errors, loops or hits limits, and you identify the cause or the tool to diagnose it, such as debug runs, fault paths or failed interview details.

Reasoning it through

A requirement says that when an Opportunity's stage changes to Closed Won, a Project record must be created and the account owner emailed. A formula cannot create records and a validation rule only blocks saves. Creating a related record needs an after-save record-triggered flow with an entry condition on stage changed to Closed Won, so the flow runs once rather than on every later edit.

Objectives 8

Official objectives from the Salesforce outline, in outline order.

3.1 Given a scenario, demonstrate the use of formula fields to meet stated business requirements.Calculated, read-only fields using functions and cross-object references.
What it means
A formula field calculates its value each time the record is read, using fields on the same record, fields on parent records through relationships, and functions such as IF, CASE, ISPICKVAL, TEXT, TODAY and HYPERLINK. The result type, such as number, text, date or checkbox, is chosen when you create it. Formulas are read-only and are not stored in the database.
What to understand
Know the limits: formulas can reference parent records up to ten relationships away but cannot reference child records, and there are character and compiled size limits. Know the common functions for picklists (ISPICKVAL, TEXT), blank handling (ISBLANK, BLANKVALUE) and dates. Because values are calculated on read, a formula change does not fire flows or triggers, and formula fields cannot be used in some places such as criteria-based sharing rules.
How it shows up
Expect a requirement to display a derived value, such as days open or a parent's field, and options mixing formulas, flows and roll-ups.
Common confusion
Trying to use a formula to sum child records, which requires a roll-up summary field instead.
3.2 Given a scenario, determine the capabilities, use cases, and implications of roll-up summary fields.COUNT, SUM, MIN and MAX of child records on the master record.
What it means
A roll-up summary field on the master of a master-detail relationship calculates COUNT, SUM, MIN or MAX across related detail records, optionally filtered by criteria. It also works on some standard relationships, such as Account to Opportunity and Opportunity to Opportunity Product. The value is stored and recalculated when child records change.
What to understand
Know the implications: roll-ups require master-detail on custom objects, there is a per-object limit on how many you can create, and a relationship with roll-ups cannot be converted back to lookup until they are removed. Filter criteria cannot reference certain field types, such as formula fields that refer to other objects. Changes to roll-ups can trigger mass recalculation, and they can drive automation on the master because the value is stored.
How it shows up
A scenario wants a total or count on a parent; you check whether master-detail exists and choose roll-up summary over a flow.
Common confusion
Assuming roll-ups work across lookup relationships on custom objects without additional automation.
3.3 Given a scenario, demonstrate the use of validation rules to meet stated business requirements.Formulas that block saves when data does not meet a rule.
What it means
A validation rule contains an error condition formula; when the formula evaluates to true, the save is blocked and a message is shown at the top of the page or next to a chosen field. Rules apply to every save from any channel, including the UI, imports and the API. They are used to enforce data quality and process conditions.
What to understand
Know common patterns: require a field only at a certain stage (ISPICKVAL with ISBLANK), stop backdated dates, restrict changes with ISCHANGED and PRIORVALUE, and use REGEX for formats. Validation rules run after before-save flows and before after-save automation, so a before-save flow can update a value that is then validated. Remember to account for integrations and data loads, which validation rules also block.
How it shows up
Look for words like prevent, must not save or require when; a validation rule is usually the lightest correct answer.
Common confusion
Writing the condition for valid data instead of the error condition that should block the save.
3.4 Create and configure flows using Flow Builder.Elements, resources, variables and configuration in Flow Builder.
What it means
Flow Builder is the declarative tool for building flows on a canvas. Flows combine elements such as Get, Create, Update and Delete Records, Decision, Assignment, Loop, Screen, Action and Subflow, with resources such as variables, constants, formulas and record collections. Flows are saved as versions and must be activated to run.
What to understand
Know the configuration basics: entry conditions and optimization for record-triggered flows, input and output variables for subflows and actions, collection handling with Loop and Transform, and keeping data operations outside loops to avoid hitting limits. Know the run context options, such as system context with or without sharing, and that screen flows can use reactive components. Flow Builder can also draft flows from a natural-language description with Agentforce.
How it shows up
Questions give a goal and ask which element or setting achieves it, or why a configuration fails.
Common confusion
Putting Get or Update Records elements inside a loop, which risks governor limit errors on bulk saves.
3.5 Describe the capabilities and use cases for Flow Approval processes.Approvals built in Flow with stages, steps and approval work items.
What it means
Flow Approval processes are approvals built in Flow Builder using the autolaunched approval orchestration flow type. They organize an approval into stages and steps, assign approval work items to users, groups or queues, and run background automation between steps. A record page component shows approval progress and history, and the approval is usually launched by a record-triggered flow or from a button or action.
What to understand
Know why they matter: they support parallel and sequential approvers, dynamic routing through flow logic, and actions on approve, reject or recall within one design tool. Approvers work from approval work items. Understand that Flow Approval processes replace the classic approval process objective in the current guide, so the exam frames approvals through Flow.
How it shows up
A scenario needs multi-step or conditional approvals with automated actions; you recognize a Flow Approval process as the declarative answer.
Common confusion
Assuming a flow approval runs without being launched; it still needs a trigger such as a record-triggered flow or action.
3.6 Given a scenario, determine the appropriate flow type to meet stated business requirements.Screen, record-triggered, schedule-triggered, platform event-triggered and autolaunched flows.
What it means
Each flow type starts differently. Screen flows run when a user launches them from a page, action or utility bar and can collect input. Record-triggered flows run when a record is created, updated or deleted. Schedule-triggered flows run at set times over a batch of records. Platform event-triggered flows run when an event message arrives. Autolaunched flows with no trigger are called from other flows, Apex, buttons or agents.
What to understand
For record-triggered flows, know the timing: fast field updates (before-save) change the triggering record efficiently, while actions and related records (after-save) can create or update other records and send emails. Run asynchronously paths suit callouts and slow actions, and scheduled paths run a set time after a date. Orchestration flows coordinate multi-user, multi-step processes.
How it shows up
A trigger and goal are described; you choose the flow type and, for record-triggered flows, before-save or after-save.
Common confusion
Choosing an after-save flow to update fields on the same record, when a before-save flow is faster and simpler.
3.7 Maintain, monitor, and troubleshoot flows.Versions, debugging, fault paths, error emails and run history.
What it means
Maintaining flows means managing versions, activating the right one, and keeping automation per object organized. Monitoring includes reviewing paused and failed flow interviews, flow error emails and the Automation app. Troubleshooting uses Debug mode, rollback test runs, fault paths that catch errors, and Flow Trigger Explorer to see the order of record-triggered flows on an object.
What to understand
Know that only one version of a flow is active at a time, and that deactivated versions can be reactivated. Add fault connectors to handle errors gracefully and log or notify. Use trigger order values to control sequence when several record-triggered flows run on one object. Know that Workflow Rules and Process Builder should be moved to Flow with the Migrate to Flow tool, since they are no longer the recommended automation.
How it shows up
Expect a flow that fails on bulk updates or behaves unpredictably; you name the diagnosis tool or design fix.
Common confusion
Editing an active version and assuming the change runs, rather than saving a new version and activating it.
3.8 Describe the capabilities and use cases for using Agentforce to automate business processes.Agents, topics and actions that call flows, prompt templates and Apex.
What it means
Agentforce lets you build AI agents that understand requests in natural language and complete tasks. An agent is organized into topics, each with instructions and actions. Actions can run flows, Apex, prompt templates and standard actions, so existing declarative automation becomes something an agent can use. Agents can serve employees inside Salesforce or customers on channels such as messaging.
What to understand
Know where an app builder contributes: building autolaunched flows that agents call as actions, writing clear topic instructions, and using prompt templates in Prompt Builder to ground generated text in record data. Agents respect the running user's permissions and sharing. Recognize good use cases, such as answering order status or updating case fields, and that deterministic rules still belong in flows and validation rules.
How it shows up
A scenario asks how to let users complete a task by conversation; the answer usually exposes an existing flow as an agent action.
Common confusion
Expecting an agent to replace deterministic automation that must run on every record save.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Formula field

    Read-only value calculated when the record is read.

    Remember
    Can reference parents, not children, and is not stored.
    Tested as
    Lightest answer for displaying derived values.
    Trap
    Expecting formula changes to trigger automation.

  • Cross-object formula

    Formula that references fields on parent records through relationships.

    Remember
    Up to ten relationships away.
    Tested as
    Used to show account or owner data on a child record.
    Trap
    Trying to reference child records or siblings.

  • Roll-up summary field

    Stored COUNT, SUM, MIN or MAX of detail records on the master.

    Remember
    Needs master-detail on custom objects and can be filtered.
    Tested as
    Common answer for totals on a parent.
    Trap
    Planning it on a lookup.

  • Validation rule

    Error-condition formula that blocks a save when true.

    Remember
    Applies to UI, API and imports alike.
    Tested as
    Answer for prevent or require scenarios.
    Trap
    Writing the condition for valid data.

  • PRIORVALUE and ISCHANGED

    Functions that compare a field with its value before the save.

    Remember
    Used in validation rules and flow formulas to detect changes.
    Tested as
    Appear in rules that block changes after a stage.
    Trap
    Using them in formula fields, where they are not available.

  • Before-save record-triggered flow

    Fast field updates on the triggering record before it is saved.

    Remember
    Cannot create other records or send email.
    Tested as
    Preferred for same-record field updates.
    Trap
    Choosing after-save for same-record updates.

  • After-save record-triggered flow

    Runs after the save to work with related records and actions.

    Remember
    Can create, update other records, send emails and call actions.
    Tested as
    Answer when other records must change.
    Trap
    Using it to set a field on the same record.

  • Schedule-triggered flow

    Runs at a set time and frequency over records matching criteria.

    Remember
    Useful for batch reminders and nightly updates.
    Tested as
    Chosen when no user or record event starts the process.
    Trap
    Confusing it with a scheduled path on a record-triggered flow.

  • Flow Approval process

    Approval built with the approval orchestration flow type, using stages and steps.

    Remember
    Assigns approval work items and runs automation between steps.
    Tested as
    Replaces classic approval processes in the current objectives.
    Trap
    Assuming it starts on its own without a launching flow or action.

  • Fault path

    Connector that runs when a flow element fails.

    Remember
    Lets you log, notify or show a friendly error.
    Tested as
    Common fix in troubleshooting questions.
    Trap
    Leaving elements without fault handling and relying on error emails.

  • Flow Trigger Explorer

    Shows all record-triggered flows on an object and their order.

    Remember
    Trigger order values control sequence.
    Tested as
    Used when several flows on one object conflict.
    Trap
    Assuming flows on the same object run in creation order.

  • Agentforce action

    A capability an agent can invoke, such as a flow, Apex or prompt template.

    Remember
    Autolaunched flows are a common action type.
    Tested as
    Shows how flows extend into agent automation.
    Trap
    Thinking agents bypass user permissions.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Record logic tools

ConceptMeaningKey differenceCommon trap
Formula field Calculates a value on read. Not stored; cannot aggregate children. Using it for totals of child records.
Roll-up summary Aggregates detail records on the master. Stored; needs master-detail. Using it on a lookup relationship.
Validation rule Blocks a save when a condition is true. Stops data rather than changing it. Using a flow to block bad data that a rule handles.
Record-triggered flow Runs automation on create, update or delete. Changes or creates data. Using it to display a value a formula could show.

Flow types

ConceptMeaningKey differenceCommon trap
Screen flow User-launched with screens for input. Needs a user to run it. Using it for automation on record save.
Record-triggered flow Runs on record changes. Before-save or after-save timing. Ignoring entry conditions so it runs on every edit.
Schedule-triggered flow Runs on a schedule over a batch of records. Time-based, not event-based. Using it when the action must happen immediately on save.
Platform event-triggered flow Runs when an event message is received. Reacts to system or integration events. Confusing it with record change triggers.
Autolaunched flow (no trigger) Called by other flows, Apex, buttons or agents. Reusable logic with input and output variables. Expecting it to start on its own.

Approval and agent automation

ConceptMeaningKey differenceCommon trap
Flow Approval process Structured approval stages and steps built in Flow. Human decisions routed as work items. Using an agent for formal sign-off.
Agentforce agent Conversational AI that runs actions within topics. Interprets natural-language requests. Expecting it to enforce rules on every save.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Flow to block saves

    What candidates pick
    Build a record-triggered flow that shows an error when data is wrong.
    Why it looks right
    Flow seems like the modern tool for everything.
    Why it's wrong
    A validation rule blocks invalid data more simply and applies consistently across every channel.

    Clue to watch for Words like prevent, must not, or require before saving.

  2. Formula for totals

    What candidates pick
    Write a formula summing related child amounts.
    Why it looks right
    Formulas handle calculations.
    Why it's wrong
    Formulas cannot reference child records; a roll-up summary or flow is needed.

    Clue to watch for The value aggregates many related records.

  3. After-save for same record

    What candidates pick
    Use actions and related records to set a field on the triggering record.
    Why it looks right
    It can update any record, including the trigger.
    Why it's wrong
    A before-save fast field update is more efficient and avoids an extra save cycle.

    Clue to watch for Only fields on the triggering record change.

  4. Process Builder answer

    What candidates pick
    Create a process in Process Builder.
    Why it looks right
    Older study material uses it heavily.
    Why it's wrong
    Salesforce directs all new automation to Flow, and the current outline does not cover Process Builder.

    Clue to watch for Any option naming Workflow Rules or Process Builder for new automation.

  5. No entry condition

    What candidates pick
    Trigger the flow on every update.
    Why it looks right
    It guarantees the flow sees all changes.
    Why it's wrong
    Without conditions such as only when a field changes to a value, the flow repeats work and can send duplicate emails.

    Clue to watch for The requirement says when the status changes to a value.

  6. Agent for a hard rule

    What candidates pick
    Ask an Agentforce agent to enforce a pricing rule on all records.
    Why it looks right
    Agents sound capable of handling any process.
    Why it's wrong
    Rules that must apply on every save belong in validation rules or flows; agents act on requests.

    Clue to watch for The requirement must apply to every record, every time.

Answer framework

Pick the lightest correct automation by asking these questions in order.

  1. If the value only needs to be displayed and comes from the same or parent records, use a formula field.
  2. If the value aggregates child records across master-detail, use a roll-up summary field, possibly with filter criteria.
  3. If bad data must be stopped at save time from any channel, write a validation rule using an error condition formula.
  4. If data must change or actions run, choose a flow type by what starts it, and for record changes pick before-save or after-save with entry conditions.
  5. Add approvals with a Flow Approval process, expose reusable autolaunched flows as Agentforce actions when users need conversational access, and test with debug runs and fault paths.

Practice question

When a Case is created with Priority set to High, its Escalation_Due__c date/time field must be set to four hours after creation. Nothing else changes. Which solution should an app builder use?

Want more like this? The Platform App Builder practice test has questions for every domain.

Checklist

0 of 13

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Give this section about a third of your total study time, matching its weight. Start with formulas, roll-ups and validation rules in a playground: write a days-open formula, a cross-object formula from Account, a filtered roll-up on a master-detail child, and three validation rules that use ISPICKVAL, ISCHANGED and PRIORVALUE. Test each rule with a Data Import Wizard load as well as the UI so you see that every channel is blocked.

Then move to Flow and build one of each type. Make a before-save flow that sets a field, an after-save flow that creates a related record, a scheduled flow that sends reminders, and a screen flow launched from a quick action. Break one deliberately with an element inside a loop and a missing fault path, then use Debug and the failed interview email to find the problem. Build a two-step Flow Approval process and watch the work items. Finish with the Agentforce trail modules to see how flows become agent actions, and do timed sets of mixed automation questions.

FAQ

How heavily is Business Logic and Process Automation weighted?

Business Logic and Process Automation is 32% of the Platform App Builder exam, about 19 scored questions, making it the largest section. It rose from 28% in the Summer '26 update.

Are Workflow Rules and Process Builder still on the exam?

No. The current objectives cover Flow Builder, flow types and flow troubleshooting. Salesforce directs new automation to Flow and offers Migrate to Flow for existing rules and processes.

Are classic approval processes tested?

The current guide names Flow Approval processes instead. Learn how approvals are built in Flow with stages, steps and approval work items.

What is the difference between before-save and after-save flows?

Before-save flows update fields on the triggering record quickly before it is written. After-save flows run once the record is saved and can create or update other records and send emails.

How much Agentforce do I need to know?

Know how agents use topics and actions, how flows and prompt templates become actions, and which processes suit an agent rather than deterministic automation.

Can a formula field trigger a flow?

No. Formula values are calculated on read and not stored, so changes in a formula result do not fire record-triggered automation.

Do validation rules affect data loads?

Yes. Validation rules run on saves from imports and the API as well as the UI, so loads that break a rule will fail for those rows.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 3 knowledge

This section carries almost a third of the score. Test yourself on formulas, roll-ups, validation rules, flow types and Flow Approval processes before your exam.

Take the Platform App Builder practice test Check your Platform App Builder readiness

Keep going