Section 4 · AI Agents · 35% of exam
4.4 Agentforce Builder: Canvas and Script Views
Exam objective
Explain the purpose of Canvas and Script views in Agentforce Builder and how builders use them to inspect, configure, and validate an agent.
Canvas view for visual configuration
Canvas view presents Agent Script as readable blocks and configuration panels. It helps a builder understand the agent’s definition, routing, subagents, actions, variables, and instructions without starting from a code editor. Canvas supports common configuration tasks and quick actions for adding resources or logic. It is useful when reviewing an agent’s structure, editing natural-language instructions, or configuring common conditions. The visual representation does not mean the agent is a simple flowchart; it is a view of a script-backed agent with both language instructions and programmatic behavior.
Script view for direct editing
Script view lets advanced users inspect and edit Agent Script directly. Salesforce describes developer aids such as syntax highlighting, autocompletion, and validation. Direct editing can be useful for reviewing expressions and transitions, making precise changes, or understanding control flow across several components. A builder should still know the business meaning of the script before modifying it. A syntactically valid expression can still implement the wrong policy. Use comments or clear names where supported, keep conditions readable, and validate the outcome in preview after edits.
The views stay synchronized
Canvas and Script are two ways to work with the same agent configuration. Salesforce states that configuration and edits are consistent across views. A builder can use Canvas to inspect the broad design, then use Script to review logic in detail, or edit script and return to Canvas to confirm that resources and behavior are represented as intended. The Explorer provides an inventory of agent elements, while Preview lets the builder try utterances and inspect what the agent selected. The Console can surface errors and warnings such as syntax problems or unexpected values. These features support a review loop; they do not replace scenario testing. A practical review workflow
Before editing, identify the user outcome and the part of the agent that controls it. Inspect the relevant subagent or topic, instructions, actions, variables, filters, and transitions. Use Canvas for configuration clarity and Script for expression detail. Preview a normal request and at least one boundary case. If the change affects action inputs or conditions, confirm that values are populated as expected. Look at the interaction details or trace to see which subagent and action were selected. Save draft changes, resolve warnings that could affect behavior, and follow the organization’s version and activation process before making the agent available to users.
TIP: Use Canvas to understand and configure the agent visually, Script to inspect precise logic, and Preview or trace to verify what happens for an actual utterance.
The exam guide explicitly expects understanding of how Agent Script functions in Canvas and Script view; screen labels may change between releases.
Extra concept: A Preview trace can reveal whether a problem came from routing, instructions, an action, or response generation.
Official references:
- Agent Script https://help.salesforce.com/s/articleView?id=ai.agent_script.htm&language=en_US&type=5
- Explore Agentforce Builder https://help.salesforce.com/s/articleView?id=ai.agent_builder_tour.htm&language=en_US&type=5
- Building Agents in Canvas View https://help.salesforce.com/s/articleView?id=ai.agent_canvas.htm&language=en_US&type=5
Key takeaways
- Canvas summarizes the script-backed configuration in an approachable editor.
- Script view offers direct editing and aids for expressions and logic.
- The views stay consistent; inspect, preview, and validate changes before deployment.
