Salto for
Salesforce
Articles
SHARE
Sagi Bracha
March 19, 2025
3
min read
Making sense of complex metadata types can be time-consuming and frustrating. Picture this: your overseas colleague just published a new Apex class, but you have no idea what the logic is about. Maybe you're a Salesforce admin who just inherited a complex org, and you're trying to understand how everything fits together. You need to figure out what each Flow does, which Validation Rules are active, and whether any outdated automations are still in use. Without clear documentation, this process can take hours or even days.
Now imagine you're an implementation partner starting to work with a new client. You need to quickly understand their Salesforce implementation—what every Flow does, how Approval Processes are structured, and how CPQ configurations interact.
In all these cases, hours can be lost deciphering metadata, chasing down explanations, or troubleshooting unexpected issues. What if you could instantly understand what each metadata element does, saving time and letting you focus on more strategic work?
To solve this, we built Salto and introduced NaCl, which stands for Not Another Configuration Language. NaCl translates Salesforce metadata and configuration data (aka CPQ records) into a human-readable format first and into an easy-to-use UI second, turning metadata sprawl into something that can be managed fast and with confidence.
Our dependency analysis, deployment, and monitoring features are all powered by NaCl, which describes the configuration of your Salesforce org using text.
Guess what else is great at working with text?
Salto is the only solution on the market that represents Salesforce metadata—including Flows, Custom Objects, Profiles, Permission Sets, and CPQ configuration data—using a proprietary textual language instead of XML. This approach enables us to bring AI into the future of Salesforce DevOps.
Building on this foundation, Salto AI enhances our capabilities with advanced features that provide even deeper insights into Salesforce metadata. One such feature is Salto Explain, which helps Salesforce professionals quickly understand their metadata without unnecessary complexity.
With Explain, you get an instant, plain-English description of each metadata element, making it easier to grasp its purpose and structure. Whether it’s a Salesforce Flow, a CPQ Price Rule, a Validation Rule, or any other metadata component, Explain generates a comprehensive overview of what it does and how it’s structured. Instead of spending time searching through documentation or asking colleagues, you can instantly see what a Flow, Approval Process, or CPQ rule does.
Among the most frequently asked-about elements in Explain, Flows take the top spot. Salesforce professionals often need to quickly grasp how a Flow is built, what inputs it relies on, and how it interacts with other automations. Apex code is the second most requested element, as developers and admins frequently need to interpret newly written or inherited code, ensuring they understand the logic before making any changes.
Why not give it a spin? Sign up for our 30-day free trial and see Salto Explain in action. It’s the easiest way to make sense of your Salesforce setup—no more guessing, no more endless digging. Just clear, instant insights!
Salto for
Salesforce
Salesforce
SHARE
Sagi Bracha
March 19, 2025
3
min read
Making sense of complex metadata types can be time-consuming and frustrating. Picture this: your overseas colleague just published a new Apex class, but you have no idea what the logic is about. Maybe you're a Salesforce admin who just inherited a complex org, and you're trying to understand how everything fits together. You need to figure out what each Flow does, which Validation Rules are active, and whether any outdated automations are still in use. Without clear documentation, this process can take hours or even days.
Now imagine you're an implementation partner starting to work with a new client. You need to quickly understand their Salesforce implementation—what every Flow does, how Approval Processes are structured, and how CPQ configurations interact.
In all these cases, hours can be lost deciphering metadata, chasing down explanations, or troubleshooting unexpected issues. What if you could instantly understand what each metadata element does, saving time and letting you focus on more strategic work?
To solve this, we built Salto and introduced NaCl, which stands for Not Another Configuration Language. NaCl translates Salesforce metadata and configuration data (aka CPQ records) into a human-readable format first and into an easy-to-use UI second, turning metadata sprawl into something that can be managed fast and with confidence.
Our dependency analysis, deployment, and monitoring features are all powered by NaCl, which describes the configuration of your Salesforce org using text.
Guess what else is great at working with text?
Salto is the only solution on the market that represents Salesforce metadata—including Flows, Custom Objects, Profiles, Permission Sets, and CPQ configuration data—using a proprietary textual language instead of XML. This approach enables us to bring AI into the future of Salesforce DevOps.
Building on this foundation, Salto AI enhances our capabilities with advanced features that provide even deeper insights into Salesforce metadata. One such feature is Salto Explain, which helps Salesforce professionals quickly understand their metadata without unnecessary complexity.
With Explain, you get an instant, plain-English description of each metadata element, making it easier to grasp its purpose and structure. Whether it’s a Salesforce Flow, a CPQ Price Rule, a Validation Rule, or any other metadata component, Explain generates a comprehensive overview of what it does and how it’s structured. Instead of spending time searching through documentation or asking colleagues, you can instantly see what a Flow, Approval Process, or CPQ rule does.
Among the most frequently asked-about elements in Explain, Flows take the top spot. Salesforce professionals often need to quickly grasp how a Flow is built, what inputs it relies on, and how it interacts with other automations. Apex code is the second most requested element, as developers and admins frequently need to interpret newly written or inherited code, ensuring they understand the logic before making any changes.
Why not give it a spin? Sign up for our 30-day free trial and see Salto Explain in action. It’s the easiest way to make sense of your Salesforce setup—no more guessing, no more endless digging. Just clear, instant insights!