Skip to main content

Enable and Disable Salesforce Automations

Automation Control allows you to quickly disable or enable automation in your org with the option to easily roll back your changes, even after you have closed your browser.

The following automation is supported:

  • Apex Triggers
    • Apex triggers are not supported in production orgs because of Salesforce code coverage requirements
  • Validation Rules
  • Workflow Rules
  • Record Triggered Flows
  • Process Builders

Object and metadata type selection​

Select as many objects as you would like and choose the type of automation that you would like to view.

tip

If you choose Process Builders, it may take additional time initially for Jetstream to determine which Process Builders are associated to the selected objects. Jetstream will cache this information so that subsequent visits to this page will be much faster.

Automation control - select objects

Toggling automation​

After the page loads, you will see a list of all the metadata items in a table and you can easily toggle which ones are active.

For Process Builders and Record Triggered Flows, you will need to choose the version that you want to activate or deactivate. Only one version can be active at any given time.

tip

Before you deploy any changes, you can export the current state of automation in case you need to refer back in the future.

Automation control overview

Pending changes are highlighted in yellow.

Automation control pending changes

Deploying changes​

When you are ready to deploy your changes, click Review Changes. This will display a summary of all changes before making changes in Salesforce.

If you need to make any corrections, click cancel and adjust your selections. Otherwise, click Deploy Changes to submit the changes to Salesforce.

Automation control review pending changes

Rolling back your changes​

Once the changes are submitted, you will be given the option to roll back the changes. This is useful if you just needed to disable some automation temporarily and want to roll back to the previous state.

To rollback your changes, click the Rollback button.

Automation control pending changes modal

History​

Every time you deploy changes from Automation Control, the changes are saved to your history, including what each item was set to before and after the deployment and whether it succeeded. This means you can still roll back your changes after closing the browser, or apply the same changes again later, for example if you disable the same automation before each data load.

Click History on the object selection page or from the editor to see the deployments for the selected org, newest first. Choose a deployment to see each item that was changed.

  • Roll Back restores every item that was deployed successfully to the state it was in before the deployment.
  • Re-deploy applies the same changes again, including any items that failed the first time.

If a deployment is interrupted, for example by closing the browser before it finishes, it is still saved to your history and any items without a result are marked as Not confirmed. Rolling back includes these items, and any that were never changed are skipped because they already match Salesforce.

Jetstream first loads the current state of each item from Salesforce and then opens the editor with the changes staged, so only the items that are different from what is in Salesforce are included. Items that already match are skipped, and items that no longer exist, such as a deleted validation rule or flow version, are listed so you know they were not included. Review the highlighted changes, adjust them if needed, and click Review Changes to deploy them as usual.

note

History is stored in your browser, not on the Jetstream server, and the last 100 deployments are kept for each org. Only the active state of each item is saved, not the full metadata.

Downloading a package​

From Review Changes or from a deployment in History, click Download Package and choose either Before these changes or After these changes. This downloads a metadata package that sets each item to its active state from before or after the changes, which you can deploy at any time from Deploy Metadata by choosing Upload Metadata Zip. For example, download the "before" package prior to deploying so you always have a way to roll back, or use the "after" package to make the same change in another org.

The package is built from the current metadata in Salesforce when you download it, with only the active state changed. For Flows and Process Builders, the package only sets the active version. Items that no longer exist in Salesforce are left out of the package and listed when you download it.

Exporting metadata​

There are two options for exporting your metadata:

  1. Export as Zip
  2. Export as Spreadsheet
info

Exporting will not include any pending changes you have made, it will always match what is currently configured in Salesforce.

Export as Zip​

This option will download a metadata package based on the current state of all metadata in Salesforce. This is a full backup of all the metadata and will allow you to re-deploy the metadata at any point in the future using the Deploy Metadata > Deploy and Compare Metadata page and choosing Upload Metadata Zip.

Re-deploying changes​

For Validation Rules and Workflow Rules, re-deploying will also include the configuration in addition to the active state. This means that if you made changes to a Validation Rule, when you re-deploy it would get reverted back to the previous state.

For Flows and Process Builders, re-deploying will only update the active version.

Export as Spreadsheet​

Choosing this option will download a spreadsheet or csv with all of the metadata similar to what is displayed in the table. This is a great option to save a reference to what was active or inactive at a specific point in time.