Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, demonstrate the use of formula fields to meet stated business requirements.
0/15
Given a scenario, determine the capabilities, use cases, and implications of roll-up summary fields.
0/9
Given a scenario, demonstrate the use of validation rules to meet stated business requirements.
0/14
Create and configure flows using Flow Builder
0/21
Describe the capabilities and use cases for Flow Approval processes
0/13
Given a scenario, determine the appropriate flow type to meet stated business requirements
0/5
Maintain, monitor, and troubleshoot flows
0/11
Describe the capabilities and use cases for using Agentforce to automate business processes
0/9
Agentforce capabilities for autonomous process automation
Learn this conceptEmployee versus Service agent use cases
Learn this conceptAgentforce topics, actions, and reasoning
Learn this conceptStandard versus custom Agentforce actions
Learn this conceptReference action types for Agentforce custom actions
Learn this conceptAgentforce versus Flow for process automation
Learn this conceptAgent execution context and data access
Learn this conceptSetup with Agentforce for administrative processes
Learn this conceptPrepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
Agentforce automates work through a conversational agent that interprets a user's request and chooses actions, while Flow is the deterministic engine you put behind those actions when the outcome must follow business rules every time. They are complementary: the agent decides what to do in the conversation, and an autolaunched flow (or invocable Apex) enforces the rules. Sensitive or deterministic requirements belong in the flow-based action itself, not in the agent's natural-language instructions.