Skip to main content

Remove test data before going live

For weeks, you tried things out: created routes to see whether the mapping was right, started runs to see what arrives. Whatever is left of that should go before live operation begins.

There are two separate ways to do this — which one applies depends on where something came from:

What is leftHow it goes
What the test runs produced — jobs, runs, clarification cases, settled eventsthrough the retention periods, with a detour
What you set up for testing — test routes, test connectionsdelete by hand, in a set order

Each way takes care of its own half only.

What you need​

Together, the two ways require two different permissions, and at Cambira they belong to two different people:

Permissions

For the retention periods, you need System at the Full level — M. Brandt has that. To delete routes and connections, you need Routes or Connections at the Full level — A. Vogt has that. With only one of them, you can take care of only one of the two ways. More on this under Permissions.

Also plan for time: the run that deletes according to the retention periods runs on schedule only.

The processing data: set short, wait, set back​

  1. Open Settings and lower the retention periods whose data should go — Settled events, Completed operations, Resolved clarification cases. 1 is the smallest allowed value and means: everything older than one day.
  2. Under Automatic cleanup, check Next run to see when it will happen, and wait for that run. Afterwards, the deletion log shows what it deleted.
  3. Set the retention periods back to the values that should apply in operation.

A retention period stays in effect until someone changes it. If it stays at 1, Xchange keeps only one day of data in live operation too.

Leave Usage records alone. Billing questions are answered from these records, even a year later; their retention period of 395 days exists for exactly this reason.

How entering the values works in detail — including the warning strip that appears when you shorten a period — is described under Adjust retention periods.

The test configuration: by hand, and in this order​

A test route stays until someone deletes it.

  1. Open the route and choose Delete. Xchange asks for confirmation, names the route, and says two things: the route's entire configuration goes with it — trigger, filter, mapping —, and the deletion is final.
  2. Repeat this for each test route.
  3. Only then the test connection: it also has a Delete button, with the same confirmation prompt.

The order is mandatory. A connection can be deleted only once the last route that points to it has been deleted. Xchange says so when you click, and names the number of routes that still point to it — that tells you how many you missed.

At first, only the draft is changed. Routes and connections belong to the configuration, and your change takes effect only when the snapshot is activated — until then, the system keeps working with the version in which the test routes still exist. See Configuration Snapshots.

The old snapshots keep the test routes: a snapshot is the record of what applied at the time, and stays as it was.

What Reset system is for​

Reset system appears only in two fault states that arise when the service starts; during normal operation, the button is hidden.

For cleaning up before live operation, this leaves the two ways above. What the reset does, when it comes to that, is described under Retention and reset.

How you can tell it worked​

For the processing data: the deletion log under Automatic cleanup. It shows, per area, how many records the last run deleted. If it found nothing, Last run is followed by the note no records deleted. When the next run is due is shown under Next run.

For the configuration: the lists under Routes and Connections. After activation, they show only the entries you go live with.

What comes next​

See also​