A sandbox is an isolated environment where you can try out changes to an application without affecting the version people are already using. Think of it as a practice area. You can try new things, make changes, and check how they work before making them available to everyone.
Once everything is ready, you can move those changes to the live application.
In Quixy, Sandbox is a separate space where Citizen Developers, Business Analysts, and other stakeholders can experiment with new features, make application changes, and test how they work before releasing them to users.
Note
Traditional software development often follows a process called Continuous Integration and Continuous Deployment (CI/CD). This process involves building, testing, and deploying application changes. Quixy simplifies this process through its no-code Sandbox environment, allowing users to develop and release application changes without writing code.
Quixy provides a Multi-Stage Sandbox that supports different stages of application development and testing, including Dev, QA, UAT, and Live. These stages allow teams to develop applications, test changes, validate them with users, and release approved changes to the Live environment.
With one-click deployment, users can move application changes from one stage to another without manually recreating them. Once the changes are deployed to the Live stage, they become available to end users.
Quixy provides two types of Sandbox: Basic and Advanced. They differ in the number of stages and in the tools they include.
| Feature | Basic Sandbox | Advanced Sandbox |
|---|---|---|
| Stages | Dev, Live | Dev, QA, UAT, Live |
| How you deploy | Dev to Live in one step | One stage at a time: Dev to QA, QA to UAT, UAT to Live |
| Branches | General and Admin | General, Admin, and branches you create |
| Collaborators | Not available | Up to 7 per branch |
To see which one you have, open the stage selector on the top bar. Basic lists Dev and Live. Advanced lists Dev, QA, UAT, and Live.
Sandbox makes managing data easier. With the help of the Data Admin role, your data is handled in a more private and secure way.
The Sandbox applies not only to the apps and reports you build, but also to account preferences. Account preferences are organization-wide settings, such as notifications, themes, and the payment gateway, that control how Quixy works for your users.
Since the Sandbox has different stages, a preference set in one stage does not carry over to the other. Some preferences are therefore set separately for each stage, while others must be deployed to Live before they take effect. The following preferences work this way:
Citizen Developers can keep users informed about changes in the latest versions of applications, views, and reports. Within 72 hours of deploying to the Live stage, you can send release notes with a quick overview of what's new, so that users are always up to date.
When you send release notes, they reach all users who have access to the updated applications, views, or reports.
Users see the release notes in their notifications.
Tip
Keep your release notes clear and concise, so that users easily understand the changes made.