Salesforce updates architecture diagram templates to reflect Agentforce and Data 360 (opens in a new tab)
You will learn how to select the correct diagram type for your audience and apply Salesforce updated template libraries to accurately represent current platform capabilities.
Salesforce architects spend much of their time communicating design decisions, and a clear architecture diagram gives teams a shared reference point that replaces long meeting notes and chat threads. Salesforce refreshed its Reference Diagrams, Architecture Gallery templates and Lucidchart shape libraries in June so they reflect Agentforce and Data 360, the renamed Data Cloud. The Cards library now includes preformatted Agentforce components, product names are updated, and new templates cover multi-cloud work coordinated by Agentforce, event-driven agent triggers and data flows with AI decisioning. Font sizes and border contrast were also improved for large-screen reviews, and some interaction process flow diagrams tied to Decision Guides and Fundamentals content were retired. The refresh did not change Salesforce’s five core diagram types, its Lucidchart partnership or its overall approach.
The five core types each answer a different question, so the choice should start with the audience. Capability maps show what business capabilities a solution must provide, without technical detail, and suit executives. Roadmaps add a time dimension for phased delivery and can show technical dependencies in business terms. System landscapes show the systems, products and connections in an estate, which helps with discovery and impact analysis. Solution architectures show how systems communicate and integrate, including authentication and data movement, and are the diagrams implementation teams use most. Interaction process flows show the numbered sequence of steps, agent actions and handoffs over time.
Most substantial projects use several of these diagrams, and they should tell a consistent story across each other. Architects are advised to start from a template in the Reference Architecture Gallery rather than a blank canvas, then adapt it to their scenario. For Agentforce designs, the article recommends splitting concerns across multiple diagrams rather than overloading one, and making human-in-the-loop points and data grounding visible to security, governance and business readers. Diagrams are not a substitute for entity relationship diagrams when data modeling is significant. The article closes by stressing that a good diagram makes the right information easy to understand for its particular audience, not that it contains the most detail.
Read the original at Salesforce Ben (opens in a new tab)