Salto fits into your existing workflows so you can start at your own pace and choose which Salto capabilities to adopt and when. Once you connect your business applications to Salto and Fetch your existing configurations - you already have all the information at your disposal, and you're ready to start.
See the changes you make in your own business application UI and Fetch it in Salto with one click
With your configuration represented in textual files, searching and investigating all the elements' end connections is easy
When you're ready to move configurations from Salto back to your business applications, or from one environment to another - simply use Deploy
Using the Push to Git option in Salto enables version control, contextualized documentation, superior compliance, troubleshooting, and roll-backs
Sometimes you're asked to fix something and your only input is an error message or a line out of an automated email.
Salto lets you paste that string into a search box and find what you need in seconds.
Changing existing configurations can be scary - it's hard to be sure you've considered all potential implications of your change.
Salto's structured references enable fast and powerful ways to map out dependencies and plan changes with confidence.
Making sense of long conditions, and other complex pieces of logic, especially when you didn't write them in the first place, isn't easy.
Salto's in-line documentation lets you add valuable summaries right where you need them, so the next person (or future-you) can make sense in no time.
It's hard to constantly refresh your sandbox from Prod while keeping the features you're working on. It's even harder when your setup includes config data, like SF CPQ or NetSuite items.
Salto manages metadata and config data with the same tools and, combined with Git, lets you deploy any config state to any environment.
Some tasks involve repetition, like renaming a field (and all references), or adding many new fields in one sitting.
Since Salto is text-based, you can do all that much faster with "find and replace" or "copy-paste".
Manually keeping track of changes, e.g. in a spreadsheet, is a prevalent best practice. It's especially useful on teams using multiple environments in their change pipeline, since these notes are used as reference when handpicking what to sync from one environment to the next.
In a single workspace you can build your change, Fetch it into your NaCls, point Salto to the next environment, run Deploy, and Salto will know exactly what needs to be deployed.
Environments tend to drift away from alignment for multiple reasons, like changes done directly in Prod, or changes pending in a sandbox.
Salto's environment diff tools let you clearly understand differences, identify the ones to align, and choose between aligning just once and keeping everything aligned across the board.
Changing existing config can be scary - it's hard to be sure you've considered all potential implications of your change.
Salto's structured references enable fast and powerful ways to map out dependencies and plan changes with confidence.
Bugs in Prod can be hard to diagnose and solve, and can bring critical business processes to a halt until they are fixed.
Salto [with Git] makes these incidents much easier: you can revert Prod to the previous deployment that did not contain the bug and review the contents of the buggy deployment to figure the root cause.
Salto's IDE helps you make the most out of the power of NaCl. On top of the indispensable text search, Salto's IDE leverages NaCl's structure with elements-based search, "Find all References" and "Go to Definition" navigation, and context-aware autocomplete. The IDE runs Salto's configuration validation engine, providing real-time feedback with a wide range of built-in warnings and errors.
Salto Environments (Envs) enable testing before changing production. An Env is a container of one or more service instances, inspired by approaching all your business apps as one cohesive "stack". Env configurations can be shared among team members. Credentials can be set as either required from each individual member, or configured once as shared.
Salto's Fetch operation connects to all the applications in your Env and downloads their latest configurations. Thus, Fetch allows you to develop changes in the application UI, while using Salto for everything else, like versioning and deploying. Fetch enables you to learn NaCl at your own pace, and slowly start developing changes by simple copy-pasting-and-modifying.
Salto's Deploy automatically calculates the differences between your own NaCls and your applications' configurations, and then deduces an execution plan based on those differences . Dependencies are added to the calculation, to generate a plan with maximum parallel execution without breaking anything. Deploy can run on an entire Environment, including all of its applications, or run only on selected applications.
Easily assess differences between Envs' configurations and decide what to deploy to align Envs, and what to keep different. Move NaCl configurations into your Salto common configuration folder to indicate to Salto that these elements should be the same across all Envs. Salto's Fetch and Deploy operations will behave accordingly, helping you prevent Envs from drifting apart.
Salto's Git client was created to provide you with a simple and clear experience while enjoying most of Git's benefits. The UI was designed to focus on the task you want to achieve and not on the technical details. Salto provides real time recommendations about when to push or pull changes, helping you stay in sync with your team.