Deploying business rules to production from a premium sandbox

Fastpath: Admin Center > Account > Sandbox > Deployment

Business rule deployment enables you to create, update, and test automations (beta) and triggers in your premium sandbox environment and then implement the same trigger and automation configurations in your production account without the risk of manually recreating it. This two-click solution speeds up the change management process and prevents keying errors, giving you more control over what’s copied into production. This article describes how to deploy trigger and automation configurations from a sandbox to your production instance.

This article contains the following sections:

• About trigger deployment
• Preparing for a problem-free deployment
• Deploying business rule configurations from sandbox to production
• Resolving dependencies
• Reverting a deployed business rule configuration
• Checking the new business rule configuration in production

About trigger deployment

Note: Trigger deployments only work for premium sandboxes created on or after August 30, 2021. Automation deployments (beta) only work for premium sandboxes created on or after May 23, 2022. You can find creation dates on the Sandboxes page.

Being able to deploy business rules to production that have been thoroughly tested in a realistic but low-risk environment provides peace of mind. However, there are a few things to consider before deployment:

• Sandbox-to-sandbox deployments are not possible. You can only deploy a business rule from a premium sandbox to production.
• The deployment happens immediately and can't be scheduled. You may want to deploy during off-hours or at a low-volume time of day.
• A deployed business rule can have no more than 100 dependencies. A dependency is any reference in a condition or action, such as a group or a custom field.
• The trigger or automation can't have any dependencies that are missing from production.
• After deployment, the trigger or automation may not be in the same position or category when it appears in production. After you deploy the business rule, you might need to reorder them or move it to the correct category to ensure it fires properly.
• Deployments can't be reverted automatically. You have to manually revert it in production.
• Deployments are recorded in the production audit log, so you have a record of the change.

Preparing for a problem-free deployment

Here are some steps you can take ahead of time to ensure the deployment goes smoothly.

• Replace your sandbox before making changes to it, so it’s the freshest version.
• To deploy triggers, ensure you’re working in a premium sandbox created on or after August 30, 2021. For automations, ensure you’re working in a premium sandbox created on or after May 23, 2022.
• Notify agents and admins of the time window when you plan to deploy the changes and ask them not to make any changes of their own during that time.
• When deploying an update to an existing automation, capture a record of the automation as it exists in production prior to the deploy. This will help in the event you need to manually revert the changes.
• If possible, deploy outside of business hours, or when there are fewer inbound tickets.
• Publish release notes to communicate the changes to admins and team leads.

Deploying business rule configurations from sandbox to production

After you create and test your trigger or automation in a premium sandbox, you can deploy it to your production account.

To deploy a business rule configuration to production:

1. In Admin Center, click Account in the sidebar, then select Sandbox > Deployment.

2. (Automation deployment beta only) In the Configuration type drop-down, select the type of business rule you want to deploy: Automation or Trigger.
3. In the Premium sandbox drop-down, select the sandbox that has the trigger you want to deploy.
4. In the list that appears, locate the trigger and click Next.
5. If prompted, resolve any missing and duplicate dependencies, then click Next.
6. Review your mapped dependencies and click Deploy.

After the business rule configuration is deployed, you can check it by viewing the trigger or automation in production and comparing it to the sandbox.

Resolving dependencies

A dependency is anything referenced in a business rule's conditions or actions, such as a group or a custom field. For example, in the following trigger condition, the combination of a custom ticket field called “Office location” with a drop-down option called “Winston-Salem” is a dependency.

In preparation for deploying the business rule configuration, dependencies in a sandbox configuration are compared to the corresponding dependencies on production. If it can’t find all of them or identifies multiple possible matches, a list of the unresolved dependencies is returned. All dependencies must be mapped to production before you can deploy the business rule configuration.

Missing dependencies

A missing dependency happens when the system can't identify an object, field, option, or value in production that corresponds to a dependency defined for the trigger or automation in your sandbox. This includes nested dependencies, such as an option within a field. There are two possible solutions for missing dependencies:

• rename the dependency in your sandbox to match something in production
• create the equivalent object, field, option, or value in production

In either case, the names must be identical, including capitalization.

To resolve a missing dependency

1. From the Admin Center > Account > Sandbox > Deployment page in your sandbox, review the list of dependencies under Resolve missing dependencies.

   A list of missing dependencies is displayed.

2. If you need to create the dependency in production:
   1. Click Go to create next to the dependency.
   2. Create the missing object, field, option, or value making sure to match the dependency's name in the sandbox exactly. To make this easier, the list of missing dependencies includes a description, such as Group or Organization field option.
3. If the dependency does already exist in production, but the names aren't identical, you can rename the dependency in either your sandbox or production.
4. Back on the sandbox deploy page, click Refresh matches.

5. After all dependencies are mapped, click Next to move to the final step of deploying the business rule configuration.

Duplicate dependencies

A duplicate dependency happens when there are multiple potential matches in production for the business rule's dependency. In this case, you must select the correct item in production to map the dependency to.

To resolve a duplicate dependency

1. From the Admin Center > Account > Sandbox > Deployment page in your sandbox, review the list of dependencies under Resolve duplicate dependencies.
2. In the Select match dialog, select the appropriate match and click Next.

   If you're unsure of the correct match, you can click View to see it in production.

3. Back on the sandbox deploy page, click Refresh matches.

4. After all dependencies are mapped, click Next to move to the final step of deploying the business rule configuration.

Reverting a deployed business rule configuration

There isn't an automatic way to revert triggers and automations that have been deployed. In the event you need to revert a deployed configuration, you can do so manually. If you deploy a new trigger or automation, you might just need to deactivate it.

Reverting a deployed trigger configuration

If you deployed an update to an existing trigger, you'll need to use the trigger's revision history to manually restore the conditions and actions to their previous state.

To revert a trigger on production:

1. In Admin Center, click Objects and rules in the sidebar, then select Business rules > Triggers.
2. Click the trigger you want to revert, then click Revision history. (This is located below the trigger title.)

   We recommend opening the revision history in a separate tab.

3. On the trigger history page, you’ll see all the available versions in a sidebar. Click the version you want to revert to and view its configuration, or you can turn on Show changes to see the most recent changes made to the trigger.
4. On the trigger's details page, modify the trigger to match the earlier version and click Save.

Reverting a deployed automation configuration

Automations don't have a revision history. Before deploying an update to an existing automation, we recommend recording the current production settings, which you could use as a reference if you need to revert your deployed changes.

To revert a trigger on production:

1. In Admin Center, click Objects and rules in the sidebar, then select Business rules > Triggers.
2. Click the automation you want to revert.
3. On the automation's details page, modify the conditions and actions to match the earlier version and click Save.

Checking the new business rule configuration in production

To check that the deployment happened correctly, compare the business rule configuration in production to the one in the sandbox. It may be easiest to do this in separate side-by-side browser windows.

Since triggers and automations run in order, it’s also important to check the location of the business rule in the list. It may not be deployed in the same order or in the same category as it appears in the sandbox. If that’s the case, move the trigger or automation to the correct location. This may entail reordering it (see Reordering and sorting triggers or Reordering automations) or moving it to the intended category (see Organizing triggers within categories).