Frequently Asked Questions about System Refreshes

A system refresh means that a non-productive Clarity environment is overwritten with a copy of production data. 

There will be a downtime of the non-productive environment. There will be no interruption to the production system.

Finish and back up all ongoing work on the Clarity target system, since it will be overwritten with production data.

• Any remediation or anonymization of productive data on the non-productive environment lies in the responsibility of the customer. This includes hard-coded links to productive sites, configuration objects for interfaces, or the color scheme.
• Email addresses of all users are overwritten with a default address to prevent that emails are sent to clients by accident. It is possible to skip this step. Please ask explicitly not to overwrite email addresses in the Service Request.
• All scheduled jobs of type "Execute a process" are paused per default. They must be rescheduled by the customer according to their requirements for non-productive environments. This includes an update of any hardcoded configuration to productive interfaces.

• A backup of the productive database is created and imported into the target non-productive database.
• All email addresses are reset to an invalid value to prevent unwanted emails to the clients.
• All scheduled Clarity jobs of type "Execute a process" are paused and have to be started manually by the customer.
• Optional: The Clarity filestore may be refreshed. Please ask explicitly for a filestore refresh in the Service Request.