Sandboxes are useful for trying out new things and helping with change management. Creating a change in a sandbox and then testing meant that you knew what was going to happen in your production Account without impacting customers. However, migrating these changes from a Sandbox to your production Account has always been a manual process. Good practice was having two windows with the Admin copying the configuration from one to the other.
That's where the new Deploy Triggers come in.
Deploy Triggers is an exciting new feature for Premium Sandboxes which enables you to copy Trigger configuration from a Sandbox back into your production Account. The process of change management for Triggers and their dependencies is a simple push-button solution. These deployments allow you to have control over what is copied, removing any manual keying errors and speeding up the time to deploy changes.
How does Deploy Triggers work?
In Admin Center, navigate to Sandboxes and click on the Deployment link.
Select the sandbox in which the trigger you want to deploy lives
Select the trigger you want to deploy, and click on the Deploy link
Click on the Deploy trigger button
Congratulations you just deployed a trigger to Production!
Supported use cases for this EAP
For this initial release we are supporting the following use cases:
- Creating new Triggers with existing dependencies
- Updating existing Triggers and existing dependencies
Note: A trigger dependency is a Condition or an Action. E.g. a status, brand, type, priority, channel or ticket. Anything you can select as a dependency or action.
⚠️ We do not yet support the creation of new dependencies in Sandboxes, we have a solution in the works. E.g. this is where you might create a new organisation in your sandbox and use it in a Trigger. As a work-around, if you create this new organization in your Production Account then create the sandbox you would have the Organization in the Sandbox for use.
What gets deployed from the Sandbox to your production Account?
The selected trigger and its dependencies are copied from the sandbox to your account. We don’t yet handle any new dependencies that have been created in a sandbox. This means if you want to add a new dependency (e.g. org) you should create this in your production Account before you create the Sandbox.
How to roll back changes
If you have deployed a change and you need to reverse the change, you can rollback by following these steps:
Navigate to the trigger that you want to roll back
Click on Revision History and open this in another window
Select the version you want to revert to
Update the triggers fields to reflect the old changes and save
How do I get started with the EAP?
First, sign up! 😉 We plan to get new accounts going as soon as we can.
Once you get confirmation that you've been enrolled in the EAP you can begin Deploying Triggers from Sandbox to Production.
Who can sign up for the EAP?
This EAP is available to all customers with access to Premium Sandboxes.
We would love your feedback!
This is an Early Access Program and we expect that there may be some bugs in the system. We'd appreciate any feedback and reproduction steps if you run into unexpected issues.
If you have any thoughts, wishes, dreams or any other Sandboxes related feedback please leave it in this community forum. We are looking forward to it!
When will other Business Rules be available?
We have been busy building out the new Deploy feature and have a backlog full of enhancements to improve the process. We are planning to start work on other Business Rules in the upcoming months and will share progress.
Please sign in to leave a comment.