Catalog section · DATA

Element removal: keep (archive) or toss, backup first

16 planned items in Backup, Restore, Export & Import.

Element removal keeps data archived by default

DATA-0038 Planned Lite and Pro Core

Removing an element renames its tables to archive names, makes them read-only with triggers and moves the migration history aside; nothing is deleted

Depends on: DATA-0001

Archived data is read-only and excluded from normal screens

DATA-0039 Planned Lite and Pro Core

Archived tables reject writes with a clear error and are not read by any enabled element; they stay in backups and exports

Depends on: DATA-0001

Archived data comes back when the element is re-added

DATA-0040 Planned Lite and Pro Core

Starting a build that includes the element again restores the tables in dependency order before migrating; content is identical

Depends on: DATA-0001

Toss takes a verified backup before any delete

DATA-0041 Planned Lite and Pro Core

Before deleting an element's data the app writes a full database backup, opens it, checks integrity and row counts, and only then deletes

Depends on: DATA-0001

A failed backup stops removal before any delete

DATA-0042 Planned Lite and Pro Core

If the backup cannot be written or verified, nothing is changed and the customer is told

Depends on: DATA-0001

Removal is validated as a whole before it starts

DATA-0043 Planned Lite and Pro Core

The whole order is checked first (installed, typed ids, acknowledgements, remaining dependents, foreign keys); any problem refuses the entire order

Depends on: DATA-0001

Removal changes data in one transaction

DATA-0044 Planned Lite and Pro Core

Archive and delete steps for all elements run in one immediate transaction in dependency order; a failure rolls everything back

Depends on: DATA-0001

Removal log

DATA-0045 Planned Lite and Pro Standard

Every removal action (kept, deleted, restored, discarded) is recorded in the local database with time and backup location

Depends on: DATA-0001

Smaller build refuses to start over data without an order

DATA-0046 Planned Lite and Pro Core

If a build has fewer elements than the database holds, the app refuses to start instead of silently orphaning data; the launcher must supply a removal order

Depends on: DATA-0001

Export of an element's data before delete

DATA-0047 Planned Lite and Pro Standard

An element's tables can be exported as JSON lines before a toss

Depends on: DATA-0001

Delete kept data later as a separate step

DATA-0048 Planned Lite and Pro Standard

Kept data can be deleted later with the typed id, the extra acknowledgement where needed and a backup first

Depends on: DATA-0001

Logistics keep: database moved aside read-only with hash

DATA-0049 Planned Lite and Pro Core

Keeping Logistics data checkpoints the database, moves it to an archive file marked read-only and writes a sidecar with its sha256

Depends on: DATA-0001

Logistics restore checks the hash

DATA-0050 Planned Lite and Pro Core

Restoring Logistics data verifies the archive against its sidecar and never overwrites an existing database

Depends on: DATA-0001

Logistics never creates an empty database over kept data

DATA-0051 Planned Lite and Pro Core

Opening Logistics while kept data sits beside it is refused until the data is restored or deleted

Depends on: DATA-0001

Logistics toss takes a verified backup copy first

DATA-0052 Planned Lite and Pro Core

Deleting the Logistics database requires the typed id and acknowledgement and a verified backup copy; the database and its side files are then deleted

Depends on: DATA-0001

Deleted data is not securely erased

DATA-0053 Planned Lite and Pro Optional

File and page deletion does not overwrite disk contents; customers needing secure erase must use disk-level tools (documented limit)

Depends on: DATA-0001