Sandbox in Qntrl – Safe Testing Environment for Workflow and Process Validation | Qntrl Online Help | Sandbox Online Help

Overview

What is Sandbox?       

Sandbox is a secure testing environment that clones your main system, enabling you to build and test new processes, changes, and configurations without disrupting your live system. During cloning, Sandbox only uses configuration data, excluding real user data.

Benefits and Advantages of Sandbox  

Data Integrity and Protection

Ensures production data remains read-only during testing, isolating test data from live systems. This safeguards against accidental changes and helps protect sensitive customer information.

Error Prevention

Identify and resolve errors or compatibility issues before they reach production. This proactive testing minimizes disruptions, ensuring a smooth and error-free deployment, reducing the risk of costly downtime or reputational harm.

Workflow Stability

Validate complex workflows in a controlled environment, ensuring the stability and reliability of processes post-deployment.

Scalability

Experiment with new ideas and test code changes without affecting the live system. It also supports running multiple projects in parallel without affecting each other.

Detailed Change Tracking

Provides visibility into data changes, making it easy to monitor, analyze, and track modifications. This enhances transparency and control over the testing process, improving troubleshooting and decision-making.

Script Validation

Safely validates script-based modules, ensuring new scripts are error-free and reliable before deployment.

Enhanced Collaboration

Multiple teams can work on separate projects simultaneously, promoting collaboration and increasing productivity.

How Sandbox Works in Qntrl     

When you have multiple processes and their related data, you can import them into the Sandbox, including modules, templates, boards, and circuits. User data is not cloned, ensuring privacy and security. All imported processes and modules function as they would in the main environment, allowing you to test and refine your processes in this cloned environment.

Sanbox supports:

  • Single-environment setup for direct testing and deployment.

  • Multi-environment setup for more robust staging, QA, or development workflows.

Example Scenarios   

Building and Testing Processes  

When building a process in Qntrl, you create flows, blueprints, and business logic. However, testing these processes directly in the main environment can lead to unwanted entries and potential disruptions. Sandbox allows you to:

  • Import processes and related data into the sandbox environment.

  • Clone modules, templates, boards, and cycles used by the triggers (excluding user data).

  • Test new processes and stages without impacting the existing workflows.

Integrating new process

Integrating new processes into an existing workflow can risk breaking the current flow. To prevent this:

  1. Create and test the new process in the sandbox environment.

  2. Validate the process to ensure it does not affect the existing workflow.

  3. Once validated, migrate the tested process to the main environment.

Trigger Testing

In Qntrl, processes are often triggered by schedules or events, such as:

  • Circuit triggers

  • Schedulers

  • Client mail triggers

  • Webhooks

  • Execution triggers

These triggers can create changes that are difficult to test and revert in the main environment. The sandbox provides a safe space to test these triggers.

Checking How a New Custom Function Works   

You want to set up a custom function that mentions the card owner and comments a congratulations message when a card is closed. Sandbox allows you to:

  • Develop a function that triggers when a card is closed

  • Ensure the function includes a feature to mention the card owner

  • Program the function to comment a congratulatory message on the card

  • Validate the function to ensure it works correctly when a card is closed 

Monitoring and Logging  

All activities within the sandbox are captured in logs, making it easy to trace any failures. Users can:

  • Monitor real-time activities

  • Identify the stage at which any issues occur

  • Review logs to understand and resolve failures

Limitations    

Sandbox does not currently support the below features:

  • Widgets

  • Email-In

  • Marketplace

  • Integrations

  • Bridge 

    • Related Articles

    • Overview of Bridge

      What is a Bridge? Bridge is an installable, lightweight independent agent that can be deployed on the customer’s local network. It is compatible both on Windows and Linux machines with 32 and 64-bit OS. Its role is to facilitate communication between ...

    • Overview

      Any system is defined by the data it receives as input, the way it processes that data, and the output it generates. In a Circuit execution, the input to the circuit is provided as JSON key-value pairs. This JSON is passed as input to the initial ...

    • Overview of Qntrl

      Qntrl helps businesses automate their everyday workflows involving wide-ranging tasks and detailed nuances under a single platform. Whether it's a straightforward workflow involving a single team, or a complex workflow involving multiple teams, Qntrl ...

    • Overview of Reports

      One of the best ways to manage teams in an organization is to take a step back and analyse the work pattern. Evaluate different aspects of your team’s progress using Reports in Qntrl. Apart from the default reports provided by Qntrl, users can also ...

    • Overview of Users

      Organization users Your employees can be added to Qntrl organization as users . Once you add a user to the organization, an invitation email will be sent to their email address. Upon accepting the invite, they will become a current user of your ...

    You are currently viewing the help articles of Qntrl 3.0. If you are still using our older version and require guidance with it, Click here.