Since version 15.1
An issue was identified where, upon deletion of a Condition Record Set (CRCS) through the user interface, the associated Condition Record Items (CRCI) remained in the database tables (specifically in the conditionrecorditem*key tables). The expectation was that deleting a CRCS should also result in the removal of all related CRCIs, but due to the CRCS being only soft-deleted, CRCIs persisted. This resulted in orphan CRCIs, potentially leading to data inconsistency.
To address this issue, a new Hourly Janitor Task was introduced. This automated task identifies CRCS records that have been softly deleted and proceeds to hard delete them. The hard deletion of a CRCS triggers a cascade delete process, ensuring that all related CRCI and CRCIH records are also removed from the system. This enhancement ensures that when a Condition Record Set is deleted, all associated Condition Record Items are consistently and completely removed, maintaining data integrity.
Log Example
09:50:07.000 [main] [system] INFO [104] [] n.p.s.b.h.PurgeConditionRecordRelatedObjects - Hard deleted 1 soft deleted CRCSs