Deletion Considerations for BluSKY Systems
Overview
An important aspect of BluSKY is the lack of cascading deletion for associated data entries. This prevents accidentally deleting an entire configured System with a single button press; however, this design also necessitates a particular process to fully delete an access control System in BluSKY. It is best practice to entirely clean out the data of a System that is being decommissioned. This ensures that all data associated with the System is marked as deleted.
Glossary of Terms
Please refer to this section to understand key terms used in this guide:
- Object: a data entry in BluSKY.
- Active: the state of an object in BluSKY where it is not deleted and usable/viewable.
- Deleted: the state of an object in BluSKY where it is deleted and not usable, but viewable when setting a View filter to "Active + Deleted". Deleted objects are still in BluB0X's database. Deleted objects can also often be restored to active by using the Undelete button when viewing them.
- Removed: different than deleted; this object does not exist in BluB0X's database.
- Association: a relationship between two objects in BluSKY.
- Parent-child association: a specific relationship between two objects in BluSKY, where one acts as the "parent" and the other as the "child". Often, the parent object is used to filter and search for the child object (ex. using a System to search for associated Facilities).
- Orphan: an active object that has a deleted parent. Since deleted objects cannot be selected in a filter, if an object's only parent is deleted, it will not show up in BluSKY searches. If an orphan is not viewable, it cannot be deleted and will remain active but invisible.
- Note: the goal of this guide is to provide a walkthrough that minimizes or eliminates orphans created during the deletion process.
Starting Out (No Child Associations)
The following objects in BluSKY do not have any child associations; therefore, they can be deleted without consideration for creating orphans. It is recommended to clean out all of these objects first in the process, in no particular order:
- Access Level
- Access Level Group
- Badge Design
- Card
- Card Upload
- Camera
- Command
- Control Point
- DDE Floor Matrix
- Delegate Point
- Distribution List
- Elevator SIO Board
- Holiday
- Intercom
- IPS Point
- Location
- Map
- Monitoring Point
- Notification
- Portal
- Power Module
- Procedure
- Reader
- Recorder
- Role
- Rule
- Schedule
- Watchlist
Sequence for Deletion to Avoid Orphans (Child Associations)
After clearing out the objects above, delete the objects below in the order which they are presented to avoid creating orphans in BluSKY: