Articles in this section

Install and test your integration app in your sandbox

Sandbox 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 the Sandbox environment freely to test, tweak, and improve your integrations.

The sandbox environment for your integrations within integrator.io enables you to test new flows and change the existing flows before you make any changes to the production environment.

Access my integrator.io sandbox environment

To access the integrator.io sandbox environment:

  1. Sign in to your integrator.io account.

  2. Toggle to your Sandbox environment. If you do not see this option, you don’t have a license to an integrator.io Sandbox environment yet. Contact your Celigo account manager to get access.

Toggle to Sandbox environment.png

Install integration apps into my integrator.io sandbox environment

To install integration apps into the integrator.io sandbox environment:

  1. In the left pane, click Marketplace.

  2. Browse to the integration app you want to install.

  3. Install it in your integrator.io Sandbox environment.

Marketplace.png

Best practices

  • 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 Sandbox FAQs.

Was this article helpful?
0 out of 2 found this helpful

Comments

2 comments
Date Votes
  • 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.

    What's the Best Practice for migration? Just download from Sandbox and install the zip file to Production?

    0
  • Great question, Greg Nofi

    Please see the Sandbox/Production option (step 4) in the following article:

     

    0

Please sign in to leave a comment.