Skip to main content

Cleardown process

In this article, we explain what the cleardown process is, and how it's done.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

We provide the Cleardown procedures as a tool to selectively remove data from a Mosaic database, mainly for migration testing. Once the migration is complete, a fresh install should be used for Live, because the Cleardown Process might leave data fragments behind.

While normally used during the data migration, they can also be used to clear data from training and test databases.

📌 Note: This process irrecoverably removes data from the database, so shouldn’t be used on Live environments or ones that will be live in the future.
We’ve split the process into sections so you can select the area of data to update.

See below for a table of the procedures:

Procedure

Description

activity_logger_runtime

Deletes activity longer runtimes date, but it’s not configuration.

alerts

Deletes data generated by alerts. Will not delete the notification rules set up with the alerts manager.

audit_trail

Deletes from audit trail tables, but not audit data change.

budgets

Deletes budget data. Will not delete budget codes or budget code groups.

care_packages

Deletes data relating to the purchase of care package services, and their payments. Will not delete service or element types or standard rates.

carers

Deletes the carer register and associated carer data, care packages and payments.

cases

Deletes data for workflow, conferences and visits including all data entered during a step or visit. It also runs the cleardown procedures for alerts, audit trail, care packages, documents, external systems runtime, forms runtime, payments, registrations and unit meetings.

cpis_runtime

Deletes all CPIS runtimes dates, but not the CPIS configuration.

documents

Deletes attached document and form runtime data. Will not delete XML data or the form template configuration.

education_runtime

Deletes from Mosaic Event Management runtime tables, leaving configuration intact.

education_config

The will clear education runtime and education config tables.

event_management_runtime

Deletes the Mosaic External system runtime data.

forms_runtime

Deletes forms and form answer runtime data but not form template configuration or attached documents.

payments

Deletes data relating to payments for Care package services.

people

Deletes general data for clients and other people. It will also delete service use groups, case notes, file locations, financial assessments and LAC, education and health data.

registrations

Deletes child protection and other registration data including CP enquires. Runs the cleardown for alerts, documents and forms runtimes.

service_provisions

Deletes data relating to the provisions of care package services by suppliers, including service rates and budget codes. Also deletes budget codes specific to purchasing teams. Will not delete standard rates or budget codes.

nonconfig_workers

After clearing down the above runtime data, workers who have not been in Mosaic configuration will also be deleted.

nonconfig_organisations

This does the same as both nonconfig workers and service provisions but then removes any organisations that are not used in other mosaic configurations.

If you want to complete this process please raise a new case, referring to the article and provide the following information:

  • When would you like the process to be performed? Please provide a date with at least one week’s notice, as approval from the Change Advisory Board’s required.

  • Which environment will the Cleardown take place in?

  • Which procedure would you like us to follow? Select from the above table.

Did this answer your question?