Loading...

XML

Word

Printable

Type: Improvement
Resolution: Unresolved
Priority: Major
Fix Version/s: COmanage Registry 5.0.0 (Pupal Eclosion)
Affects Version/s: COmanage Registry 0.9.1 (Essential Enneagon Plus One)
Component/s: Registry
Labels:
None

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.

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

CFM-24 Changelog Behavior

In Progress

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

(8 is related to)

Assignee:: Benn Oshrin
Reporter:: Benn Oshrin
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: 21/Jan/15 2:47 PM
Updated:: 21/May/25 2:32 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates