Connecting an environment to Salto
To connect a SFDC environment (prod, UAT, sandbox, etc.) to Salto, follow the setup instructions in our documentation.
In many cases a salesforce org is also configured via data records, e.g., CPQ, SBAA. Salto introduces a unified approach for managing both data records and metadata items from a single place. Learn more
If using CPQ, make sure "Enable CPQ" is checked.
To update the settings for a particular environment, navigate to the settings section where you will find:
General: where to update the environment name, setup the Scheduled fetch, and optionally mark an environment as "sensitive"
Application Connections: credentials used for fetch and deploy (Note: make sure you have set up "Personal credentials" in the environment ahead of starting a deployment), the Salto adapter config file. (Note: not all types are fetched by default, review the Supported Metadata types docs page.)
Version Control: Git connection for the environment
Monitor changes: where to set up custom notifications (see below)
Integrate Git, SFDX and CI/CD for your Salesforce release process
Salto enables you to connect your Salesforce environment to Git and maintain an SFDX project within the environment’s branch.
Developers can utilize VS Code, SFDX, and Git to implement changes in the environments through pull requests (PRs).
Admin-driven deployments made via the Salto UI are automatically synchronized with the SFDX repository, fostering seamless collaboration with developers.
Learn more about:
To overview of CI/CD the Salto way can be found here.
Enabling pull requests and CI/CD automations using the Salto CLI
Fetch types
There are three types of fetches in Salto:
Full fetches all configuration updates for the environment (the scheduled fetch uses a full fetch)
Change-Based Fetch: Only fetches the elements that have changed since the last fetch. (Note: due to SFDC API limitations, Salto cannot fetch modifications to labels and descriptions of Custom Objects during a change-based fetch)
Custom: Optionally targets 1 or more specific metadata types to fetch
Impact Analysis
The explore page in Salto is used to explore your configurations, see dependencies and understand where and how configurations are used. Salto supports more than just custom fields for impact analysis.
🎥 * Ex: Finding hardcoded values
Monitoring changes
Set up notifications to alert when changes are made in production.
Comparison Overview (Compare & Deploy)
Here is an overview of the comparison screen showing you the differences between two environments, part of the compare and deploy process.
Backup and Restore
Through the scheduled fetch, Salto will automatically backup the configurations for each environment. Those backups can be used through the restore process to revert any changes made directly in the environment. 🎥 * Ex: Rolling back CPQ changes
Deployment types
There are different types of deployments in Salto
Compare & Deploy: Choose which changes to align between any two environments.
Find environment changes & deploy: Choose the changes made during a specific time period to deploy into another environment. Especially useful when deploying from a shared environment.
Deploy from Pull Request: Initiate a deployment in Salto based on the changes contained in a Pull Request in an SFDX repository
Promote a deployment: used to promote the same set up changes to another target environment. (ex: after deploying a set of updates to a page layout in
UAT, promoting those same changes up toProduction) 🎥 Example of a promotion deploymentRevert a deployment: Revert all changes made in a specific deployment (Note: to revert specific changes, use the restore process mentioned above)
Validating and testing your Salesforce deployments
When deploying changes to a Salesforce org, you can validate those changes in Salesforce without applying them and opt to run tests during either the validation or deployment process.
To configure which tests to run, click the three-dot menu and select "Deployment Settings."
Select the option the fits you best:
These settings will take effect when you click the "Validate" or "Deploy" buttons in the header.
Deployment examples
Deploying a new field with its permissions
A walkthrough from Salto of how to deploy a new field with FLS configured
Aligning and deploying CPQ data across environments
Salto can be used to align CPQ data across environments as well as deploying changes to CPQ configurations between environments. Here's a link to our documentation on managing CPQ with Salto.
Deploying changes with an approval process
An example of using Github's branch and merge protection rules to create an approval process to gate deployments to Production.
Additional References