Other Setting options in Sandbox

View Saved Changes in Repository     

The configuration changes are saved in the repository(only the configuration data not the real user data). The changes between the current version and previous version can only be saved. To view the saved configuration changes in the repository:

1. Navigate to(settings) >> Advanced >> Sandbox and select Projects.
2. Click on the name of the project you want to view the saved changes for, then click Saved Changes.
3. Click Repository View on the top-right corner of the page. This will display all the saved changes as individual files within the project's repository.
   

Managing Portal Access during development   

Enable/Disable Read-Only Mode     

When you associate a project with a Sandbox environment, your live (production) portal automatically switches to read-only mode. This prevents unintended changes in the production environment while development and testing are in progress. 

If you need to make updates directly in the live portal during this time, you can temporarily disable read-only mode. After completing your changes, it's important to re-enable read-only mode to ensure those changes can be exported and deployed properly.

While the portal is not in read-only mode, you cannot initiate deployments or raise deployment requests. Once read-only mode is turned back on, your Sandbox changes will be moved to the Live Queue in the production environment, allowing you to deploy or revert them.

To enable or disable read-only mode:

1. Navigate to your Sandbox portal.
2. Locate the Read-Only Mode toggle in the top-right of the portal.
3. Use the toggle to enable or disable read-only mode as needed.

Disabling read-only mode permits changes in your live environment. Make sure you have a backup or rollback plan in place before proceeding.

Next: Use Case 1: Implementing a New Order Fulfilment Process

• Related Articles

• Key Concepts in Sandbox

  Key Terms to Understand Sandbox A testing clone of your live environment. Environments A container for one or more instances. Sandbox can have multiple environments for various levels of testing. Types include Development, Staging, and Production. ...

• Using Sandbox in Qntrl: A Step-by-Step Guide

  Step 1 - Setting Up Environments Environments Types Sandbox is built as a multi-environment model, supporting both simple use cases with direct deployment to Production and complex setups with multiple environments for development and testing. ...

• Working with Projects

  Step 1: Create a Project An admin or user with Manage Settings permission can create Projects. To create a project (test environment): Navigate to and select Projects under Advanced. Click New Project at the top-right corner. Enter the following ...

• Managing reports and folders

  New report Navigate to Reports and click New Report in the left panel. Fill in the details, Name : Enter a name for the report. Description : Enter a short description of the report. Form : Select a form for which the graph must be plotted. Folder : ...

• Environment Scope for Parameters in Sandbox

  In the Sandbox module, you can assign dynamic values to parameters for different environments (e.g., development, testing, production), ensuring consistent configurations across multiple stages of the deployment process. These parameters can be ...