Background
When checking whether an object (e.g. a CustomAction) can be safely deleted, the current guard only considers working versions and published versions. Discussion on PR #3187 concluded that all versions (i.e. those that are not working and not the default) must be considered.
Backlink: #3187 (comment)
Requested by: @SmittieC
Requirements
1. Extend reference checks to all versions
- Non-published versions that reference the object should also be detected and reported in the modal.
- Deletion must be blocked when any version (working, published, or otherwise) references the object.
- Archived versions can safely be ignored, as is the case currently
2. Bulk-archive button for non-working / non-published versions
- Add a button on the "Cannot delete" modal that allows the user to bulk-archive all non-working, non-published (non default) versions that reference the object.
- This reduces the manual effort when many such versions exist.
3. Manual cleanup for working + published versions
- Working versions and published versions that reference the object must be cleaned up manually, one-by-one — no bulk action should be offered for these.
- The modal should clearly indicate which references require manual intervention.
Background
When checking whether an object (e.g. a
CustomAction) can be safely deleted, the current guard only considers working versions and published versions. Discussion on PR #3187 concluded that all versions (i.e. those that are not working and not the default) must be considered.Backlink: #3187 (comment)
Requested by: @SmittieC
Requirements
1. Extend reference checks to all versions
2. Bulk-archive button for non-working / non-published versions
3. Manual cleanup for working + published versions