Elements.cloud for Salesforce architects
Well-Architected solutions require rigorous business analysis, from a wish list to a complete user story passed to DevOps. Elements strategic partnership with Salesforce means the Elements platform has been optimized for Well-Architected from business analysis through to training and user adoption.
You are going to be able to use our shapes and templates in Elements.cloud. You told us. We are coming to the tools you use.
Zayne Turner – Senior Director, Architect Relations, Salesforce (DF22 Architect keynote)
Elements is a Salesforce strategic partner
Elements is an enterprise architecture application. It enables you to be more productive, drawing diagrams that are instantly integrated into the other architectural artifacts. Siloed documentation increases the risk of miscommunication, increases rework and wastes time.
Architecture diagrams are important living documents that need access controls, versioning and collaboration.
Extending the Salesforce notation
Salesforce Diagrams’ potential has increased due to the robust collaboration and connection features.
Whenever Salesforce develops a new template, it will be created using Elements and can be freely downloaded.
Everything in one place
Architecture diagrams. Process maps. Brainstorm canvases. Requirements. User Stories. Metadata dictionaries. Documentation.
So much more than a drawing tool
Elements has been designed to create and manage enterprise documentation and treat them as living, valuable artifacts that have a life long beyond the project. Any enterprise application must have access controls, versioning, collaboration, an authorization cycle, and linkages to other systems artifacts.
Trusted: Secure, Compliant, Reliable
All the architecture artifacts on one collaborative application enable you to build secure, compliant, reliable solutions.
Easy: Simple, Automated, Engaging
Quickly build content easily understood by all stakeholders, combined with system-generated documentation.
Adaptable: Resilient, Composable
Accelerate change with automated org impact and dependency analysis and system-generated documentation.
Architect best practice
Extending the Salesforce Diagram standard
Elements has opened opportunities to make the current Salesforce Diagram standard more powerful.
Such as the dynamic header that is hidden when not needed or the ERD objects automatically linked to the object in the metadata dictionary when resources are added. Or version control is managed down to 4 levels.
Single documentation platform
Every architecture diagram and more
With Elements, you can draw the different Salesforce diagram types, document automation (Flow and Process Builder Workflows) and map business processes. Automatically building a diagram for existing Flow will be a game changer.
The power is in the connected view
Every artifact is a data point. But when you can see the connections between them, you move from information to intelligence. And because they all live in Elements, creating the linkages is automated or just a click away.
It’s made our lives easier using Elements. I feel more confident that we’ll be able to answer questions accurately and quickly. It’s a tool that we can rely on to offer accurate, quick support to our end users, so really, it makes us look good.Vivian Ralls
Salesforce Enterprise Architect – J.D.Power
Frequently asked questions
Does an Architect need an enterprise architecture app or a drawing tool?
The architecture diagrams are living documents. They need to be managed, support collaboration and have version control. They are also connected to other artifacts. That can only be achieved (without a huge admin overhead) with an enterprise architecture tool.
Is this relevant to just Salesforce CTAs?
CTA is the highest level of certification. But there are different types of architects who all need a tool for documentation solution architects, functional architects, data architects, and technical architects.
What are the different types of architect?
There are no hard and fast definitions and there is obviously some overlap in the roles or titles. But here is our view:
- Solution Architect: Responsible for the overall design of the Salesforce solution.
- Technical Architect: Responsible at a deeper level for the technical implementation of Salesforce and integrated systems.
- Data Architect: Responsible for defining and designing the data architecture in such a way that it is scalable.
- Enterprise Architect: Has oversight of all involved Architects. An all-encompassing role that includes the business.
- Transformation Architect: Responsible for defining the target operating model, skill sets, managing resources, governance and stakeholders.
Where do you find out more about Salesforce Well-Architected?
You can find more information about Salesforce Well-Architected, here.
Where can you find the Salesforce Diagram notation?
Salesforce diagramming framework can be found here. Elements support this notation and more.
Can I trial Elements?
Yes. Talk to us.