A tenant refresh is a process that involves copying data from a source tenant to a target tenant. Please note that if a target tenant already exists prior to the refresh, it will be replaced during this operation. Therefore, it is important to ensure that your production tenant is never designated as the target tenant for a tenant refresh.
Typically, a tenant refresh is used to create a copy a of the production tenant that can be used for:
- developing and modifying solutions
- testing and troubleshooting
For details on how sensitive data is obfuscated (masked) during a tenant refresh, please refer to the following article:
https://readinow.knowledgeowl.com/docs/sensitive-data
Before refresh
If the target tenant already exists, replacing it through a tenant refresh will impact other users currently utilizing that tenant. Before requesting a tenant refresh, please verify whether the target tenant exists. If it does, check the following:
- Are all users in agreement with the proposed refresh date?
- Is there data or users that need be retained by XML export?
- Are there any special integrations, such as API or SSO, that need to be recorded or exported via XML?
- Are there specific mail settings, including an email forwarding address, that should be recorded?
- Navigate to Administration > Settings > General settings. Record the current general settings in the existing tenant.
Post refresh
You will receive notification from ReadiNow once your tenant refresh request has been actioned. The target tenant is now ready for your post-refresh actions:
- Import any data that was exported during your preparation
- Re-create any special integrations, such as API or SSO, from your notes or via XML import
- Update specific mail settings, including an email forwarding address, as required
Regardless of whether the target tenant existed before the tenant refresh, you should verify the General Settings match your requirements. Navigate to Administration > Settings > General settings. Update these settings as necessary.
Our recommendation is to disable communications, API callouts and scheduled workflows to prevent confusion caused by any overlap with your production tenant. For this reason, enabling communications does not automatically enable API callouts. To enable API callouts you must first enable communications and then explicitly enable API callouts.
How to request a tenant refresh
Tenant refreshes can be requested via ReadiService, the ReadiNow Service Desk.
Create a ticket with the title "Tenant Refresh", including the name of the target tenant and the preferred date for the refresh.
In the ticket description:
- Clarify the 'source' tenant, typically your production tenant (i.e. a production tenant) and 'target' (i.e. a non-production tenant). Remember the tenant refresh process will delete any existing target tenant.
- Indicate if sensitive data should not be masked / obfuscated during the refresh. See here for information on obfuscation.
- Default is for data to be obfuscated
- Indicate if internal data should be included in the refresh. See here for an explanation of internal data.
- Default is for internal data to be excluded
Standard Maintenance & Support allows customers up to 2 tenant refreshes per month free-of-charge with a minimum of 3 days notice to ReadiNow.