After you validate and approve your changes, deploy them to the production environment. You can deploy only one change set at a time. Deploy subsequent change sets only after the prior deployment completes.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
| Available for an additional cost in: Professional Edition with Web Services API Enabled |
| User Permissions Needed | |
|---|---|
|
To deploy change sets in Salesforce Spiff: |
A Spiff user role with these permissions turned on.
|
Note To prevent data collisions, you can’t modify the target environment or access Designer
while a deployment is in progress. Because you can’t undo a deployment after it starts, verify
all changes before you begin. You can’t deploy change sets from multiple sandboxes to a single
parent environment.
- In the parent environment, go to Admin and select Settings.
- Under Environments, select Inbound Change Sets.
-
In the Name column, click the change set to deploy.
You can only deploy a change set that you’ve approved and with the status Ready to Deploy.
-
Click the History tab to review the change set's workflow history,
including Submission, Validation, and Approval steps.
This is useful for compliance audits and for confirming the correct approvals are in place.
-
Click Deploy Changes.
If the deployment fails, Spiff notifies all users who have Read permission in Spiff Designer or Read permission for change sets. You can turn off these notifications in your email and in-app notification settings.
-
Go to Spiff Designer in the parent environment and wait for the page to load.
Complete this step to finalize the deployment.After you deploy a change set, Spiff sends an email that tells you to access Designer and finalize the deployment. This email goes to all users with Read permission in Spiff Designer or Read permission for change sets, even if you've turned off Spiff email notifications in your settings. Accessing Designer is necessary to trigger the remapping of formulas and to ensure calculations run correctly. After you deploy a change set to the parent environment, you can’t revert the changes.