Actions Required after Sandbox Creation or Refresh

A sandbox account is a copy of your production account. However, not all features enabled in your production account are enabled in your sandbox account when it is created or refreshed. In particular, behind-the-scenes tasks that run in your production account by default do not run in your sandbox account. The following table lists some of the actions required to use specific functionality in your sandbox account.

Important:

During sandbox creation and refreshes, certain objects are not copied from your production account. For more information, see Data That is Not Copied from Production to Sandbox.

Omission from the following table does not guarantee full availability.

Feature	Actions Required	Notes
SAML Single Sign-On	Deploy SAML single sign-on. See Deploying SAML Single Sign-On on Your OpenAir Account. Enable employees to access the sandbox account using SAML single sign-on. If the SAML Authentication [`saml_auth`] box is checked, clear the box, save the form, then check the box and save the form again. See Enabling Employees to Sign In Using SAML Single Sign-On. Tip: You can use the bulk employee change wizard to copy the value of the `saml_auth` field to other user records on your OpenAir Account. See Making Changes to Multiple Employee Records at the Same Time.	SAML identity provider profiles are not copied from your production account to the sandbox account. By default, SAML single sign-on access is removed for all users when the sandbox account is created or refreshed, even if the SAML Authentication [`saml_auth`] box is checked on the sandbox account. This lets you control who can access your sandbox account using SAML single sign-on. You may want to enable SAML single sign-on access for the same users in both your production and sandbox accounts or enable it only for selected users. Make sure you keep SAML Authentication disabled for at least one administrator account for troubleshooting and configuration purposes.
Two-Factor Authentication (2FA)	If you require users to sign in to your sandbox account using 2FA, you need to enroll them after each sandbox refresh. See Enroll or disenroll users to sign in using 2FA. Enrolled users will be asked to setup 2FA on the next sign-in.	The following user information is not copied from your production account to the sandbox account: Two-factor authentication required demographic setting, the 2FA required, 2FA status, Complete 2FA setup by date information shown on the employees list view, user 2FA setup (authenticator app) information.
Business Intelligence Connector (OData Service)	Enable the Business Intelligence Connector feature. To do so, contact OpenAir Customer Support.	The feature is turned off by default in your sandbox account, even if it is enabled in the source account. This feature is a licensed add-on service. If you have purchased it for your production account, you can enable it on your sandbox account too. Published reports in your production OData feed are not copied across to the sandbox OData feed. To test access to published report in your sandbox account, you must publish the reports to the sandbox OData Service in your sandbox account.
API Integration Applications (OAuth 2.0)	Create the application profiles again in your sandbox account for all integration applications using the OAuth 2.0 feature that you want to test. See Managing API Integration Applications in OpenAir Users testing the integrations will need to authorize applications explicitly in the sandbox account. For more information about OAuth 2.0 Authorized Applications. See Authorized Applications.	Application profiles for integration applications using the OAuth 2.0 feature to connect to your OpenAir production account are copied to your sandbox account. However, these cannot be used to test integration applications using the OAuth 2.0 feature in your sandbox account.
NetSuite Integration	If you are enabling the integration between OpenAir and NetSuite sandbox accounts for the first time, additional set up may be required in your NetSuite sandbox account. See Configuring NetSuite for the Integration. Replace the credentials for your NetSuite production account with those for a NetSuite sandbox account. See Connecting OpenAir to NetSuite for the Integration. Activate again any scheduled integration runs you want to test in your sandbox account. If the Active switch is ON, toggle it OFF, save the form, then toggle it ON and save the form again. See Scheduling the Integration to Run Automatically.	OpenAir NetSuite Connector settings are copied from your production account to your sandbox account. To avoid any integration conflicts and data corruption on your NetSuite production account, enter the credentials of a NetSuite sandbox account in Administration > NetSuite Connector > Credentials.
Notifications and Alerts – Email	To avoid any confusion, change the email address for most or all employees to a generic email address. Enable the trigger for email notifications on your sandbox account. To do so, contact OpenAir Customer Support. Activate again any custom notifications you want to test in your sandbox account. If the Active notification box is checked, clear the box, save the form, then check the box and save the form again. See Setting Up Custom Email Notifications.	Alerts and notifications sent from both your production and sandbox accounts may cause unnecessary confusion for users. Consider the impact of enabling the trigger for email notifications and alerts, and take remedial steps to ensure that users do not receive email messages from your sandbox account. For more information about Notifications, see Notifications. Please note that setting Forward the undeliverable email to this email address under Administration > Global Settings > Email Settings should be blank so undelivered emails are not forwarded further.
Scheduled Events: OpenAir NetSuite Connector – Scheduled integration runs OpenAir NetSuite Connector – Exchange rate integration User Scripting – Scheduled scripts Automatic Backup Service Scheduled reports (See Configuring OpenAir to Run and Deliver a Report Automatically and Configuring OpenAir to Publish Reports Automatically and Refresh Published Reports Periodically) Daily resource utilization calculation Transactional budget calculation Leave accrual calculation (See Run Leave Accruals ) Automated billing (See Auto-Billing ) Automated revenue recognition (See Running Revenue Recognition Automatically ) Charge and revenue projections (See Charge Projections ) Delayed approval routing (Assign after `<number>` days – See Approval Processes ) Alerts Late approval alerts Overdue authorization approval alerts Overdue expense report approval alerts Transactional budget alerts Daily resource utilization alerts Late timesheet alerts Unsaved time entry alerts Account storage alerts	To enable triggers for a scheduled event, contact OpenAir Customer Support. Go to form corresponding to the scheduled event you want to test, change the scheduled event configuration and save the form. When enabling the triggers for User Scripting – Scheduled scripts, deploy again any scheduled scripts you want to test in your sandbox account. If the scheduled script shows as Deployed, undeploy it first and deploy it again. See Deploying Scheduled Scripts.	Scheduled events are behind-the-scenes tasks that run automatically in your production account. These tasks do not run in your sandbox account by default. Scheduled event are launched by triggers. Trigger information is not copied across from the production account during sandbox creation or refresh. To create the trigger again, schedule the event again by going to the corresponding form, changing the scheduled event configuration and saving the form.

Feature

Actions Required

Notes

SAML Single Sign-On

Deploy SAML single sign-on. See Deploying SAML Single Sign-On on Your OpenAir Account.
Enable employees to access the sandbox account using SAML single sign-on. If the SAML Authentication [saml_auth] box is checked, clear the box, save the form, then check the box and save the form again. See Enabling Employees to Sign In Using SAML Single Sign-On.

Tip:
You can use the bulk employee change wizard to copy the value of the saml_auth field to other user records on your OpenAir Account.

See Making Changes to Multiple Employee Records at the Same Time.

SAML identity provider profiles are not copied from your production account to the sandbox account.
By default, SAML single sign-on access is removed for all users when the sandbox account is created or refreshed, even if the SAML Authentication [saml_auth] box is checked on the sandbox account. This lets you control who can access your sandbox account using SAML single sign-on. You may want to enable SAML single sign-on access for the same users in both your production and sandbox accounts or enable it only for selected users.
Make sure you keep SAML Authentication disabled for at least one administrator account for troubleshooting and configuration purposes.

Two-Factor Authentication (2FA)

If you require users to sign in to your sandbox account using 2FA, you need to enroll them after each sandbox refresh. See Enroll or disenroll users to sign in using 2FA.

Enrolled users will be asked to setup 2FA on the next sign-in.

The following user information is not copied from your production account to the sandbox account: Two-factor authentication required demographic setting, the 2FA required, 2FA status, Complete 2FA setup by date information shown on the employees list view, user 2FA setup (authenticator app) information.

Business Intelligence Connector (OData Service)

Enable the Business Intelligence Connector feature. To do so, contact OpenAir Customer Support.

The feature is turned off by default in your sandbox account, even if it is enabled in the source account.
This feature is a licensed add-on service. If you have purchased it for your production account, you can enable it on your sandbox account too.
Published reports in your production OData feed are not copied across to the sandbox OData feed. To test access to published report in your sandbox account, you must publish the reports to the sandbox OData Service in your sandbox account.

API Integration Applications (OAuth 2.0)

Create the application profiles again in your sandbox account for all integration applications using the OAuth 2.0 feature that you want to test. See Managing API Integration Applications in OpenAir

Users testing the integrations will need to authorize applications explicitly in the sandbox account. For more information about OAuth 2.0 Authorized Applications. See Authorized Applications.

Application profiles for integration applications using the OAuth 2.0 feature to connect to your OpenAir production account are copied to your sandbox account. However, these cannot be used to test integration applications using the OAuth 2.0 feature in your sandbox account.

NetSuite Integration

If you are enabling the integration between OpenAir and NetSuite sandbox accounts for the first time, additional set up may be required in your NetSuite sandbox account. See Configuring NetSuite for the Integration.
Replace the credentials for your NetSuite production account with those for a NetSuite sandbox account. See Connecting OpenAir to NetSuite for the Integration.
Activate again any scheduled integration runs you want to test in your sandbox account. If the Active switch is ON, toggle it OFF, save the form, then toggle it ON and save the form again. See Scheduling the Integration to Run Automatically.

OpenAir NetSuite Connector settings are copied from your production account to your sandbox account.
To avoid any integration conflicts and data corruption on your NetSuite production account, enter the credentials of a NetSuite sandbox account in Administration > NetSuite Connector > Credentials.

Notifications and Alerts – Email

To avoid any confusion, change the email address for most or all employees to a generic email address.
Enable the trigger for email notifications on your sandbox account. To do so, contact OpenAir Customer Support.
Activate again any custom notifications you want to test in your sandbox account. If the Active notification box is checked, clear the box, save the form, then check the box and save the form again. See Setting Up Custom Email Notifications.

Alerts and notifications sent from both your production and sandbox accounts may cause unnecessary confusion for users. Consider the impact of enabling the trigger for email notifications and alerts, and take remedial steps to ensure that users do not receive email messages from your sandbox account.
For more information about Notifications, see Notifications.

Please note that setting Forward the undeliverable email to this email address under Administration > Global Settings > Email Settings should be blank so undelivered emails are not forwarded further.

Scheduled Events:

OpenAir NetSuite Connector – Scheduled integration runs
OpenAir NetSuite Connector – Exchange rate integration
User Scripting – Scheduled scripts
Automatic Backup Service
Scheduled reports (See Configuring OpenAir to Run and Deliver a Report Automatically and Configuring OpenAir to Publish Reports Automatically and Refresh Published Reports Periodically)
Daily resource utilization calculation
Transactional budget calculation
Leave accrual calculation (See Run Leave Accruals )
Automated billing (See Auto-Billing )
Automated revenue recognition (See Running Revenue Recognition Automatically )
Charge and revenue projections (See Charge Projections )
Delayed approval routing (Assign after <number> days – See Approval Processes )
Alerts
- Late approval alerts
- Overdue authorization approval alerts
- Overdue expense report approval alerts
- Transactional budget alerts
- Daily resource utilization alerts
- Late timesheet alerts
- Unsaved time entry alerts
- Account storage alerts

To enable triggers for a scheduled event, contact OpenAir Customer Support.
Go to form corresponding to the scheduled event you want to test, change the scheduled event configuration and save the form.

When enabling the triggers for User Scripting – Scheduled scripts, deploy again any scheduled scripts you want to test in your sandbox account. If the scheduled script shows as Deployed, undeploy it first and deploy it again. See Deploying Scheduled Scripts.

Scheduled events are behind-the-scenes tasks that run automatically in your production account. These tasks do not run in your sandbox account by default.

Scheduled event are launched by triggers. Trigger information is not copied across from the production account during sandbox creation or refresh. To create the trigger again, schedule the event again by going to the corresponding form, changing the scheduled event configuration and saving the form.

Related Topics