Skip to main content
All CollectionsUsing RattleSettings
How to set up Rattle Sandbox
How to set up Rattle Sandbox

Use Rattle Sandbox to test workflows in a sandbox workspace before publishing to production.

Nayan Kumar avatar
Written by Nayan Kumar
Updated over 6 months ago

With Rattle Sandbox, you can now create your workflows in a Rattle sandbox workspace (linked to your account), test the same on your Salesforce sandbox environment and then publish to your production instance.


Prerequisites

  1. You need to be a Super Admin to set up Rattle Sandbox.

  2. Only Salesforce sandbox accounts can be integrated into the Rattle Sandbox workspace.

  3. If you are a Super Admin and do not see this option, please contact your CSM.


Steps to set up a sandbox workspace

  1. Hover over your profile on the bottom left. You will see an option to create a new Sandbox workspace.

  2. Follow the steps in the onboarding flow to integrate your Salesforce Sandbox and Slack accounts.

  3. You will notice a different homepage UI for the sandbox account. This is where your team can approve workflows in one go and monitor logs of workflow publishing activity.

  4. On the General Workflows page, you can create workflows just like you do on Rattle.

  5. Once a workflow is created or updated, you will notice the 'Status' of the workflow is 'Pending.' During this status, you can test your workflows.

  6. Once tested, you can proceed to add the workflow(s) to 'Queue.' You can do so by selecting multiple workflows from the listing page or by clicking on the 'more' option across each workflow.

  7. Once one or more workflows are added to the Queue, relevant approvers on the team can 'Approve' these workflows either from the Workflows listing page or from the Home page.

  8. Once approved, these workflows will be pushed into your production workspace of Rattle.


FAQs

What workflow types are supported in Rattle Sandbox accounts?

Currently, General Workflows and Deal Room Workflows are supported in sandbox accounts.

Which user types can approve workflows?

Only Admins and Super Admins can approve workflows.

Will updates made to workflows in production impact sandbox workflows?

No, updates to workflows are unidirectional from sandbox to production.

When does a Workflow fail to get pushed to production?

Workflows will fail to get pushed to production when fields present in conditions on the sandbox workspace are not present in the production Salesforce environment.

Did this answer your question?