Overview of sandboxes used for testing and issue reproduction in Sparkrock 365

Modified on Fri, 5 Jul at 8:35 AM


  • Products: Sparkrock 365 
  • Summary: Overview of sandboxes used for testing and issue reproduction.



Important: An Sparkrock representative will contact you when and if this process applies to your particular use case. 

This Knowledge Base Article provides an overview of the sandboxes commonly used in Sparkrock 365 for testing new releases and reproducing issues. It explains the purpose and setup requirements of two main sandboxes:

  1. PTS Sandbox: If the sandbox is named PTS, an automatic creation of a mySparkrock instance occurs. However, it is necessary to configure the mySparkrock Solution Setup page to establish a connection with the new sandbox. The PTS sandbox is primarily used for validating and testing changes before deployment to other environments.

  2. UAT Sandbox: The UAT (User Acceptance Testing) sandbox is automatically updated to a newer release, allowing users to thoroughly test changes and enhancements before applying them to the Production instance. The UAT sandbox is crucial for validating functionality and identifying any potential issues or compatibility concerns.

Mysparrock setup for the PTS or UAT sandboxes

Once the sandbox is up and running, just go to mySparkrock Solution Setup page, and add -pts or -uat after the current acronym:


Original mySparkrock URL:  https://customer.mysparkrock.com/

PTS mySparkrock URL:  https://customer-pts.mysparkrock.com/

UAT mySparkrock URL:  https://customer-uat.mysparkrock.com/


It is important to leverage these sandboxes to ensure a smooth transition and minimize disruptions during updates and releases in Sparkrock 365.



There are no specific steps for resolution in this article. The purpose is to provide an understanding of the sandboxes used for testing and issue reproduction in Sparkrock 365.


Impact / Risks 

  1. Prior to updating the Production instance, validating the changes or new features in the UAT sandbox helps ensure a smoother update and minimizes the impact on end-users.



Not applicable


Related Information    

For more detailed information on testing a Sparkrock 365 release, please refer to the following Knowledge Base Article: Testing a Sparkrock 365 Release 


Update History    





The first version of this Knowledge Base article was created.  




Not Applicable

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article