Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
COmanage Registry 0.9.1 (Essential Enneagon Plus One)
-
None
Description
Refactor handling of suspend (setting status to "Suspended") and delete operations. The general problem is that when an item is suspended, related models may still reference it.
For example: if an extended type affiliation has been suspended but is still referenced by an expiration policy, what should happen?
As a general rule, models being suspended should check for related models and throw a warning (similar to expunge) or error (similar to checkDeleteDependencies) before proceeding.
Attachments
Issue Links
- is related to
-
CO-375 Do Not Allow Extended Type To Be Deleted If Referenced By Enrollment Flow
- Open
-
CO-332 Deleting Extended Attribute Does Not Delete From Enrollment Flow
- Open
-
CO-1012 CoGroupsController checkDeleteDependencies
- Open
-
CO-739 admin group for CO should not be deleted
- Resolved
-
CO-404 Delete CO Person Referenced From History Violates Foreign Key Constraint
- Resolved
-
CO-568 Deleting a COU Does Not Delete The Corresponding COU Admin Group
- Resolved
-
CO-1161 Enable Changelog For CoNotifications
- Open
-
CO-149 Delete should become expire/invalidate
- Open
-
CO-790 Don't Allow Primary Name To Be Deleted
- Resolved
-
CO-95 Table-level point in time audit
- Resolved
-
CO-1760 When deleting a pipeline, the OrgIdentitySource link is not removed
- Open
-
CO-1103 Evaluate Soft vs Hard Delete
- Open