You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Deleting data from COmanage Registry turns out to be a surprisingly complicated issue. To start, it is first necessary to understand different types of delete operations.

  • Deactivation: A deactivated record is still visible, it is just no longer in effect. For example, setting a CO Person or CO Person Role to expired or suspended will leave the record in place, but it will be deprovisioned from downstream systems. A deactivated record can easily be reactivated.
  • Soft Delete: When a record is soft deleted, it is no longer visible. However, the physical record remains in the database, and the record can even be undeleted.
  • Hard Delete: When a record is hard deleted, it is no longer visible, and the physical record is also removed from the database. The only way to restore a record that has been hard deleted is from backups. (You are maintaining backups of your database, right?)

Deactivation is currently supported in various places through Registry. Adjust the relevant records status to SuspendedExpired, or another appropriate value and the record will be deactivated.

Most delete options (where there is a button labeled "Delete", and also "Expunge") are Hard Delete operations. The exception is that, as of v0.9.4, deleting an Enrollment Flow or an Enrollment Attribute is a Soft Delete operation. (No undelete is currently available.)

Future planned changes will introduce more Soft Delete capabilities (CO-95).

 

  • No labels