Non-production environments are one of the many reasons to choose an iPaaS over a native integration. When you rely on integrations to power your essential business processes, it’s crucial to have a consequence-free testing environment to eliminate the risk of disruption. You can use a non-production environment freely to test, tweak, and improve your integrations.
A non-production environment allows you to test new flows and change existing flows before you make any changes to the production environment.
Legacy production and sandbox licenses
In legacy Production and Sandbox environments, changes in one environment affect both environments. The Production and Sandbox environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other.
This includes connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment.
This behavior doesn't apply to accounts on the multi-environment license, where each environment maintains its own isolated resources.
Migrations from the legacy Production/Sandbox license to the new multi-environment license are underway. Your account has not migrated to the new multi-environment license if you can toggle between environments.
All integration apps in your original sandbox environment will be migrated to a new non-production environment called sandbox_migrated. You must review the migration guide to perform post-migration tasks.
You are not required to purchase an integration app license for each non-production environment. You can purchase a license and install it in multiple environments. However, you will be charged for the number of active integration app flows enabled in your Celigo environments.
To summarize, after you purchase an integration app license, you can install the integration app in any or all environments. You do not have to purchase a license for each non-production environment. You will be charged based on the number of enabled integration app flows.
-
Before installing in the integrator.io Production environment, install integration apps in the integrator.io Sandbox environment and connect them to the corresponding sandbox/test instances of the applications, such as NetSuite, Salesforce, and Shopify.
-
Test flows and mappings within the Sandbox environment. Validate the configuration between Sandbox and Production environments before turning on the flows to ensure that the field mappings or the request bodies are accurate.
-
Once you are live with your integration app in your Production environment, test any subsequent changes to the integration first in the integrator.io Sandbox environment, then migrate them over to the Production environment. For more information on how to migrate an integration, see Clone integrations and flows.
-
For NetSuite’s sandbox account, NetSuite (by design) does not allow App Developers (like Celigo) to push updates to SuiteBundles/SuiteApps and therefore, the NetSuite admins must manually upgrade the SuiteBundles/SuiteApps to get updates as new releases are made available by the App Developers. You must periodically upgrade your bundles in the NetSuite sandbox environment to ensure your integration app in your integrator.io Sandbox environment stays up to date. Otherwise, Celigo cannot keep your integration app updated to the latest bundle.
-
Multiple instances of NetSuite sandboxes are considered a single endpoint, even if there are multiple connections to each NetSuite account in integrator.io with different tokens and permissions. However, it's important to note that this rule may not apply to all applications. For example, for generic connectors such as the REST API connector, different URIs, even if they belong to the same app, would count as separate endpoints.
For information on the licensing requirements, see Integration app multi-environment FAQs.