To address inefficiencies, leading to faster processing times and reduced errors a new order fulfilment process can be implemented using multi-environment sandbox environment.
Business Scenario
Swerio Corp is facing delays and errors in its order fulfilment process, causing customer dissatisfaction. To resolve this, the company plans to implement an automated workflow using sandbox environments for thorough testing and validation before deployment.
Solution
To fix the inefficiencies in Swerio's order fulfilment process, the process will be designed, tested, and validated across multiple sandbox environments for thorough testing and validation before deployment. This approach involves four key stages:
Development Environment
QA Environment
Team: QA testers and business stakeholders
Move to QA: Transfer the workflow to QA.
Extensive Testing: Test thoroughly, handle edge cases, and gather feedback for improvements.
Staging Environment
Production Environment (Final Deployment)
Implementation Steps
Step 1: Create Sandbox Environments
Create a Staging Environment
Navigate to
(settings) >> Advanced >> Sandbox and click Development Systems. Click New Environment.
Select Staging as the type.
Enter a name and description for the environment and click Create New System Environment.

Inside the staging environment, click Add Instance.
Enter the instance details, associate a project, and create an instance.

If needed, create a new project by filling in the required details and clicking Create Project.

Create a QA Environment
Click New Environment under the staging environment.
Follow the same steps as creating the staging environment, but select Staging as the type.
Create an instance and link it to a project as described in the previous step. When creating the project, set the parent project to the one in the staging instance.

An instance will be created in the QA environment with a project associated to it.
Create a Development Environment
Click New Environment under the QA environment.
Follow the same steps as creating the staging environment, but select Development as the type.
Create an instance and associate a project. When creating the project, set the parent project to the one in the QA instance.
Step 2: Work in Your Development Environment
Design the Workflow
In your development environment, Import the project. Once imported, click Access Instance in the development environment and design the workflow.

Click Generate Changes to generate changes between the previous process and the current process. You can view the status of the generated change logs in the window. Once successful, close the log window.

Validate the changes, perform unit tests, identify bottlenecks, and make modifications if required.
Click Save to Repository and save the changes with a message. The changes will be saved to the repository log.

After saving, you can review the changes for validation in the Saved Changes section by clicking View Differences in the Difference column.
Sync and Deploy to QA Environment
You can directly send the changes to the upper environment if there are no changes made in the upper environment.
If any changes are made in the upper environment, click Sync with Instance in the top-right corner of the page to sync the changes with the parent project in the QA instance.
- Select the QA instance as the target and click Sync with Instance.

Once synced, click the Send to [Environment Name] button at the bottom of the page and send to the QA environment with a deploy message.
The project will be added to the deployment queue in the QA instance where you can either deploy or reject the deployment.
Step 3: Work in Your QA Environment
Review and Test Workflow
Access instance in your QA environment by navigating to
(settings) >> Advanced >> Sandbox >> Deployment Queue.
Click the Deploy button at the top-right corner of the page.

After deployment, you can check the deployment status and logs by clicking View Logs at the top-right corner of the page.
In the Deployment Logs page, click the Send to [Environment Name] button at the bottom of the page to send the deployed changes from the QA environment to the instance in the next environment with a deploy message.


If modifications are needed, update the process, generate changes, and save them to the repository as done in the development environment.
If there are any changes in the Staging environment,(changes can be deployed from other instances or can be direct changes in that staging instances) the instances have to be synced.
Once synced, click Send to [Environment Name] and send to the next environment with a deploy message.
The process will be added to the deployment queue of the instance in the upper environment where you can either deploy or reject the deployment.
Rejecting a deployment removes the request from the live queue and moves the project back to the Development state.
Troubleshooting
If deployment fails:
Access your instance in the Development Environment and navigate to Saved Changes.
Click Sync with Instance. by selecting the target instance as QA instance.
Access the instance in your QA environment by navigating to
(settings) >> Advanced >> Sandbox >> Deployment Queue. Click the Deploy button at the top-right corner of the page.
Repeat this process in all environments: if deployment fails, sync with the instance, then go to the upper environment and deploy.
Step 4: Work in Your Staging Environment
Final Testing and Validation
Once the process is sent to the deployment queue of the staging environment:
Access the instance in the staging environment; navigate to
(settings) >> Advanced >> Sandbox >> Deployment Queue. Click the Deploy button at the top-right corner of the page.
Click View Logs; logs will be generated. Close the generated logs to view the status of deployment and the logs once deployed.
Deploy to Production Environment
In the deployment logs page, click Send to Production and send to the production environment with a deploy message.
If updates are needed, update the process, generate changes, review, and save the changes to the repository.
Once saved, click Sync with Production as it is the final stage, and sync with production.
Once synced, click Send to Production and send to the production environment with a deploy message.
The process will be added to the deployment queue of the production environment where you can either deploy or reject the deployment.
Step 5: Production Deployment
Deploy to Production
In your Live environment, navigate to
(settings) >> Advanced >> Sandbox >> Deployment Queue.
Click the Deploy button at the top-right corner of the page.

Upon successful deployment, click View Logs in the top-right corner; once logs are generated, close the logs to review the deployment process details, including the deploy message, deployed user, time of deployment, deployment status and Revert option.
Revert Changes (Optional)
If you need to revert the deployed project in the production environment (this can be done only once), navigate to
(settings) >> Advanced >> Sandbox >> Deployment Logs. Click Revert Changes in the top-right corner of the page and confirm your action.