Skip to main content
BluINFO

Deletion Considerations for BluSKY Systems

  1. Last updated
  2. Save as PDF

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:

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:

Trigger Deletion Considerations 

When deleting a Trigger, it is important to understand other objects in BluSKY that can be affected.

  • Main parent association: Controller
  • Child associations: Procedure

Since a Trigger can have a child association, note that deleting a Trigger with an associated Procedure will cause that Procedure to not show up in BluSKY searches. Also note that deleting a Trigger does not mark a child Procedure as deleted.

Person Deletion Considerations

People can be deleted in BluSKY without special consideration for other objects:

  • Main parent association: Occupancy
  • Child associations: N/A

Occupancy Deletion Considerations

When deleting an Occupancy, it is important to understand other objects in BluSKY that can be affected.

  • Main parent association: Facility
  • Child associations: People

Since an Occupancy can have a child association, note that deleting an Occupancy that is populated will cause those People to not show up in BluSKY searches. Also note that deleting an Occupancy does not mark its associated People as deleted.

Power Controller Deletion Considerations

When deleting a Power Controller, it is important to understand other objects in BluSKY that can be affected.

  • Main parent association: Server
  • Child associations: Power Module

Since a Power Controller can have a child association, note that deleting a Power Controller with an associated Power Module will cause that object to not show up in BluSKY searches. Also note that deleting a Power Controller does not mark its associated Power Modules as deleted.

Server Deletion Considerations

When deleting a Server, it is important to understand other objects in BluSKY that can be affected.

  • Main parent association: Facility
  • Child associations: Recorder (for video Servers), Power Controller (for power management Servers)

Since a Server can have a child association, note that deleting a Server with an associated Recorder/Power Controller will cause that object to not show up in BluSKY searches. Also note that deleting a Server does not mark its associated objects as deleted.

Elevator Hardware Deletion Considerations

When deleting Elevator Hardware, it is important to understand other objects in BluSKY that can be affected.

  • Main parent association: System
  • Child associations: Elevator SIO Board

Since Elevator Hardware can have child associations, note that deleting Elevator Hardware with an associated Elevator SIO Board will cause that object to not show up in BluSKY searches.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Guide
  2. Tags
    This page has no tags.