About Premium Sandbox

Return to top

20 Comments

  • Virginia Goggins

    Having just used this for the first time, there are a number of things that I think are important to know - 

    1.  Before you use this you must delete any existing sandbox.  This is a huge leap of faith for those of us with very customized instances.  Luckily for me, I have multiple instances and was able to work with a newer one with less overhead than our main instance.  If I had used this with that one I would have been extremely unhappy.

    2. Although a number of items were created, they were not usable as is and required significant review to get correct: Not all views were created, triggers were not in the correct order, customer lists were not created, etc.

    3. Custom ticket fields do not have the same field numbers and any reference to those fields will be incorrect.  So references within emails to to a custom field must be reviewed and revised; also triggers, automations, and anything else.

    4.  All agent login emails are changed.  That's not a problem except that the passwords are also changed, so an agent can't log in with the changed email to reset their password or their email.  An administrator must manually change either the password or the email for each agent that will be using the sandbox.  If you have a lot of agents and light agents this can be a huge time waste.

    5.  The sandbox doesn't include even a stripped-down version of the Guide, so there's no way to test/train using a new request form.

    Given these restrictions, it's not as easy as we are lead to believe to create a new test or training environment.  Using my starter instance it took many days to confirm that everything was the same as production.  For the primary instance, which has over 150 triggers, macros, and views, over 30 custom fields and 10 forms with conditions, I'm not sure that this is usable as is.  If I need to review every item I'd rather maintain the existing sandbox and review anything that's changed.  In my opinion, this needs more work to be usable for anyone maintaining a more complicated system.

     

     

    6
  • Virginia Goggins

    I also forgot to mention that your sandbox will disappear if you don't use it within a certain amount of time, so if you use it twice a year for training or testing, all the work you've done to get it set up will be wiped out by the next time you want to use it, so even if there were no changes you need to start from scratch and check everything again.

     

    0
  • Sally Anne Dishong

    Thank you for sharing your experiences. I am very interested to see the response to your comments, Virginia! We have just this week upgraded our account to the new Enterprise Suite plan from an older mix of Professional and Enterprise features. We look forward to taking advantage of the many new features and functionality. However, the new Premium Sandbox, which initially appeared as quite an advantage, is now seeming to be more of a major concern. Having been "burned" when resetting the Sandbox a couple of years ago to take advantage of new features - and then realizing it deleted all the Sandboxes we had created for various brands as well as creating a new URL that was very inconvenient for developers working in the Sandboxes and APIs, I am hesitant to even test this out until more information is provided about what to expect in our situation.

    0
  • Sally Anne Dishong

    I wanted to provide a bit of an update. We did receive confirmation from a Zendesk product manager that the creation of a new premium partial sandbox would not delete and did not require us to delete our existing sandbox. So we have started the process of creating a new sandbox, and it is still in progress. It has taken over 2 hours so far and is not completed yet. We will begin testing soon.

    1
  • Lindsay Grove

    @sally, Can you confirm how long the "in progress" status lasted? I am still waiting for my sandbox to become active. 

     

    0
  • Sally Anne Dishong

    Hi Lindsay - the sandbox did finally complete processing overnight. It probably took over 4 hrs in total...but I'm not sure. Hope that is helpful.

    0
  • Virginia Goggins

    @Sally - Thanks for the updated information.  When we created our sandbox account back in February there was no way to get the "Create Sandbox" button other than deleting our original sandbox and starting over.  I'm so glad they changed that!

    0
  • Virginia Goggins

    Retraction of previous statement!  We have 3 Zendesk instances, all Enterprise.  The newest one, created in 2021, gives me the option to create more than one Sandbox, BUT only after I had removed the old one.  The two older instances do not give me the option to create a new sandbox - the button is greyed out.  I'm assuming that if I delete the current sandbox I'll be able to create a new one, and hopefully that means I'll be able to create more than one, but I'm not going to test it.  Both of them are too customized to delete if I have to re-create them from basically from scratch.

    0
  • ASHISH DIVAY

    Hello,

    My feedback would be:

    1. Provide ongoing Production to Sandbox Sync
    2. Make two sandboxes a standard for all enterprise -Dev sanbox - Test sanbox
    3. Dev sandbox will be used for dev work to design new solutions.
    4. Test sandbox will be used for testing and UAT before moving stuff to production. 
    5. Sync - Production to sandbox and sandbox to production on demand.

     

    4
  • Craig VanDeVenter

    I would echo @... comment.  Plus 1 on ongoing replication.  I have upgraded sandbox but the idea that I have to delete and create a new sandbox to get updated prod seems silly.  I'm paying extra for the sync of metadata... that should be on weekly sync or even an on-demand.  
    Setting up access for the teams that need the sandbox after updates seems crazy.  If we set up an SSO then the next time we need a snapshot of prod...we have to delete it, create new one, set up SSO and move on again.  IF that is indeed true.. this seems super odd and not well thought out.

    0
  • Kim Nylander

    I was hoping to use the sandbox environment to test a new information architecture in Guide and then push those structure changes to production. This would help avoid interruption to our Guide users. 

    However: 

    • No sync of guide content to sandbox
    • No push from sandbox to production
    • No bulk article move

    As far as guide content development goes, sandbox, whether premium or regular sandbox, is useless. 

    3
  • Daniel

    Hi team, I can't seem to change the premium sandbox selection to any option other than to include the replication of tickets. It won't let me click them at all.  I don't want to do this as we don't want real customer data in our testing environments. Any help would be appreciated

    1
  • Christopher Johnson

    I am experiencing the same as Daniel. And even when trying to create the premium partial production sandbox, it immediately fails with no indication of why. 

    1
  • Gaurav Sharma

    Hi ,

    I am trying to synch my data from prod instance to sandbox so that i can test anything i want to implement in prod.

     

    We are currently using Zendesk suite - Enterprise Plan

     

    So could anyone please suggest how can i copy all my triggers,automations ,schedules,SLA's and fields to my sandbox?

    0
  • Gregory Clapp

    I'm experiencing the same problem as Craig above. The premium sandbox documentation claims that APIs are enabled, but there is no API admin page and no way to create tokens for use in the sandbox.

    0
  • Gaurav Sharma

    Hi ,

    i have placed a request to create a partial premium sandox on 19th Oct, but the sandox is still not created and it is showing in progress.

    Please let me know how many days it takes to create a partial premium sandbox.

    0
  • Chad Susa

    Hi All

    Worth noting that you can't test Talk in the Sandbox. Talk isn't there as a product option to enable at all.

    So no testing voice workflows, IVR's, greetings etc. I suspect it's because it's a billing issue....eg: calls are paid and Zendesk can't bill a sandbox account.

    This is a decent enough missing feature but understand why it can't be done.

    Just FYI.

    0
  • Joel Hellman

    I have the same issue as some other users in this thread has reported (such as Daniel), in that the option for copy with metadata is disabled and only partial production with tickets is possible. Same use case, I'd rather not copy production tickets into a sandbox for various reasons. 

    1
  • Joel Hellman

    According to Zendesk support today (ticket 9782592), Enterprise Suite doesn't include Sandbox Premium Metadata, it only includes the more "premium" product Sandbox Premium Partial.

    Instead of using Sandbox Premium Metadata, we should then choose Sandbox Premium Partial, and then manually delete the production tickets after replication? This doesn't make much sense to me.

    Why cannot I as a custom choose if I want to use the Sandbox Premium Metadata or the Sandbox Premium Partial as the premium sandbox that is included in Enterprise Suite? Why are you forcing the Sandbox Premium Partial on me when Sandbox Premium Metadata is what I need and seems to be the inferior/simpler product? 

    1
  • Terence Tam
    Zendesk Product Manager

    Hey Joel Hellman, thank you so much for your time in reaching out. 

    The current behaviour is exactly how you've described it. Different types of Sandboxes are assigned to different plans. We understand the limitations and challenges this presents.

    Given that, we are currently working on a new feature (Sandbox Lower Tier Creations) targeting Q4 release which enables users to create Sandboxes below their entitlement level just as you have illustrated.

    This will allow you to create either a Premium Partial or a Metadata Sandbox as per your Enterprise Suite Plan

    2

Please sign in to leave a comment.

Powered by Zendesk