Date: Thu, 28 Mar 2024 15:54:15 +0000 (UTC) Message-ID: <1204184939.6605.1711641255102@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6604_2013864600.1711641255101" ------=_Part_6604_2013864600.1711641255101 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are various circumstances in which an administrator might = want to "delete" a record. Various techniques are available, depending on t= he task at hand.
In many circumstances, bad data is entered from an integrated system, vi= a user error, or due to a typo. For some of these circumstances, it may mak= e sense to leave the bad data in place, but flag it as duplicate, suspended= , expired, etc. This approach leaves the full history of the record in tact= and visible for future review. See Resolving Enrollment Issues, CO Person and Person Role= Status, and Registry Validity Dates for more information.
Individual records can generally be deleted via a Delete button on the i= ndex view. This is slightly unintuitive, and will be improved in a future r= elease (CO-647). The "index" view is typically the parent view t= hat allows the selection of the individual record.
A CO Person can be deleted from the detailed CO Person view (or "canvas"= ). The CO Person cannot be deleted if they have any attached CO Person Role= s, which must be deleted first (CO-484).
A CO Person can also be expunged, using the Expun= ge button from the CO Person canvas. This will delete the CO Person an= d all of its related records, including CO Person Roles and Organizational = Identities. This is useful for clearing test records and other non-producti= on errors.
Keep in mind that = Changelog Behavior generally applies, even to delete and expunge operat= ions. Even though deleted and expunged records will no longer appear in the= user interface by default, they will remain in the underlying database, an= d can be viewed via the UI or REST API with appropriate requests. The only = ways to remove these records from the database are to delete the entire CO = (not typically recommended, except under limited test circumstances) or by = manually removing the records via the database's toolset (also not typicall= y recommended, as this can cause integrity problems if not done correctly).=