Event Categories and Types
Overview
The triggering event for Rules can vary greatly. This article highlights the most common Event Categories and the subsequent Types associated with each Event Category.
Please Note, the list of all Event Categories and their Types is even more expansive than the options depicted below. We have chosen to highlight the most common and useful options here. If you have additional questions about an Event Type not detailed in this document, please feel free to send an Article Request detailing the information you need. We will update this document and notify you as soon as it is available. Thank you!
Event Categories and Types
This Event Category will be used when you are configuring a Rule that will trigger off of Alarm events.
| Event Type | Description |
|---|---|
| Invalid Mercury Controller Data | A Rule will be triggered if an error is detected in the data received from a Mercury Controller. |
This Event Category is used when you are configuring a Rule that will be dependent on the state of an Elevator/s.
| Event Type | Description |
|---|---|
| Card And PIN | This Event Type triggers a Rule when an Elevator's mode is set to "Card And Pin". |
| Card Only | This Event Type triggers a Rule when an Elevator's mode is set to "Card Only". |
| Card Or PIN | This Event Type triggers a Rule when an Elevator's mode is set to "Card Or Pin". |
| Credential Read Access Denied | This triggers a Rule when credential authorization is denied for an Elevator. |
| Credential Read Access Granted | This triggers a Rule when credential authorization is granted for an Elevator.. |
| Disabled | This triggers a Rule when an Elevator is set to disabled. |
| Facility Code Only | This Rule is triggered when an Elevator's mode is set to, "Facility Code Only". |
| Floor Selected | This Rule is triggered when a credential is authorized to use an Elevator and make a selection. |
| Locked | This Rule is triggered when an Elevator's mode is set to, "Locked". |
| PIN Only | The Rule is triggered when an Elevator's mode is set to, "PIN Only". |
| Unlocked | This triggers a Rule when an Elevator is unlocked. |
This Event Category will be used when you are configuring a Rule that will trigger off of an event from an elevators card reader
| Event Type | Description |
|---|---|
| Access Denied | This Event Type will activate the Rule when there is a successful request to gain access to a secured Elevator. This event type is a grouping that includes all the other event types that deny access, this way you do not have to create multiple rules to catch all types of access denied. |
| Access Granted | This Event Type will activate the Rule when there is a unsuccessful request to gain access to a secured Elevator. This event type is a grouping that includes all the other event types that grant access, this way you do not have to create multiple rules to catch all types of access granted. |
| Access Is About To Be Granted | This triggers a Rule right before access is granted to an elevator. |
| Access Point Locked | This triggers a Rule when an attempt for access is made and the access point is locked. |
| Access Point Unlocked | This triggers a Rule when an attempt for access is made and the access point is unlocked. |
| Anti-passback Violation | This triggers a Rule when the anti-passback policy has been broken. |
| Authentication or Validation Failed | This triggers a Rule when the authentication process is unsuccessful. |
| Before Activation Date | This triggers a Rule when someone attempts to gain access prior to their Card or Person record being activated. |
| Card Invalid At Time Of Day | This triggers a Rule when a Person or Visitor is attempting to use their credential at a Reader they have access to but a a different time. |
| Card Not In System | This triggers a Rule when a Card is detected that has not been registered in BluSKY. |
| Deactivated Card | This triggers a Rule when a Person or Visitor is using a Card that has been deactivated. |
| Duress Code Detected | This triggers a Rule when a Duress Code is detected. |
| Escort Card Required | This triggers a Rule when a Person or Visitor attempts to gain access but requires a second escort credential to gain entry. |
| Expired Card | This triggers a Rule when an Expired Card is detected. |
| Invalid Card Format | This triggers a Rule when an Invalid Card Format is detected at a Reader. |
| Invalid PIN | This triggers a Rule when a Person or Visitor enters an incorrect PIN at a Reader or Person Reader. |
| No Access Allowed | This triggers a Rule when a Person or Visitor attempts to gain entry to a Reader that they NEVER have access to. |
Rules from this Event Category are triggered when a Person, with the proper permissions, performs a manual operation. For more information about real-time control, check out our Control guide.
| Event Type | Description |
|---|---|
| Alarm Point Bypassed | This event triggers a Rule when a BluSKY user bypasses an Alarm Point. |
| Alarm Point Disabled | This event triggers a Rule when a BluSKY user disables an Alarm Point. |
| Alarm Point Enabled | This event triggers a Rule when a BluSKY user enables an Alarm Point. |
| Armed Instantly | The Rule is triggered when a BluSKY user arms an Alarm Point instantly. |
| Disarmed Alarm | This event triggers a Rule when a BluSKY user disarms an Alarm. |
| Floor Card Access | The Rule is triggered when a BluSKY user places a Floor on Card Access. |
| Floor On Schedule | This event triggers a Rule when a BluSKY user returns the Floor to normal operation. |
| Floor Timed Release | This event triggers a Rule when a BluSKY user releases a Floor for a specific period of time. |
| Lock Floor | This event triggers a Rule when a BluSKY user locks a Floor. |
| Lock Portal | This event triggers a Rule when a BluSKY user locks a Portal. |
| Portal Card Access | This event triggers a Rule when a BluSKY user puts a Portal on Card Access. |
| Portal On Schedule | This event triggers a Rule when a BluSKY user return the Portal to normal operation. |
| Portal Timed Release | This event triggers a Rule when a BluSKY user initiates a timed Portal release. |
| Release Floor | This even triggers a Rule when a BluSKY user releases a Floor. |
| Release Portal | This even triggers a Rule when a BluSKY user manually releases a Portal. |
| Simulate Credential On Portal | This even triggers a Rule when a BluSKY user simulated a credential on a Portal. |
| Unlock Floor | This even triggers a Rule when a BluSKY user manually unlocks a Floor through the real-time control menu. |
| Unlock Portal | This even triggers a Rule when a BluSKY user unlocks a Portal. |
This Event Category will be used when you are configuring a Rule that will be dependent on a particular event for the specified Portal/s
| Event Type | Description |
|---|---|
| Access Denied | This Event Type will activate the Rule when there is a successful request to gain access to a secured Portal. This event type is a grouping that includes all the other event types that deny access, this way you do not have to create multiple rules to catch all types of access denied. |
| Access Granted | This Event Type will activate the Rule when there is a unsuccessful request to gain access to a secured Portal. This event type is a grouping that includes all the other event types that grant access, this way you do not have to create multiple rules to catch all types of access granted. |
| Access Is About To Be Granted | This triggers a Rule right before access is granted to a Portal. |
| Access Point Locked | This triggers a Rule when an attempt for access is made and the access point is locked. |
| Access Point Unlocked | This triggers a Rule when an attempt for access is made and the access point is unlocked. |
| Anti-passback Violation | This triggers a Rule when the anti-passback policy has been violated. |
| Authentication or Validation Failed | This triggers a Rule when the authentication process is unsuccessful. |
| Before Activation Date | This triggers a Rule when someone attempts to gain access prior to their Card or Person record being activated. |
| Card Invalid At Time Of Day | This triggers a Rule when a Person or Visitor is attempting to use their credential at a Reader they have access to but at a different time. |
| Card Not In System | This triggers a Rule when a Card is detected that has not been registered in BluSKY. |
| Deactivated Card | This triggers a Rule when a Person or Visitor is using a Card that has been deactivated. |
| Duress Code Detected | This triggers a Rule when a Duress Code is detected. |
| Escort Card Required | This triggers a Rule when a Person or Visitor attempts to gain access but requires a second escort credential to gain entry. |
| Expired Card | This triggers a Rule when an Expired Card is detected. |
| Invalid Card Format | This triggers a Rule when an Invalid Card Format is detected at a Reader. |
| Invalid PIN | This triggers a Rule when a Person or Visitor enters an incorrect PIN at a Reader or Person Reader. |
| No Access Allowed | This triggers a Rule when a Person or Visitor attempts to gain entry to a Reader that they NEVER have access to. |
This Event Category is used when you are configuring a Rule that will be dependent on the state of a Portal/s.
| Event Type | Description |
|---|---|
| Access Cycle In Progress | This triggers a Rule when a Portal is activated to allow access. |
| Card And PIN | This triggers a Rule when a Portal's mode is set to, "Card And Pin". |
| Card Only | This triggers a Rule when a Portal's mode is set to, "Card Only". |
| Card Or PIN | This triggers a Rule when a Portal's mode is set to, "Card Or Pin". |
| Disabled | This triggers a Rule when a Portal is disabled. |
| Disconnected | This triggers a Rule when a Portal is disconnected from BluSKY. |
| Enable 2 Card Mode | This triggers a Rule when a Portal's mode is set to require two cards. |
| Extended Held Open | This triggers a Rule when a Portal is held open. |
| Forced Open | This triggers a Rule when a Portal is opened without an authorized access attempt. |
| Held Open | This triggers a Rule when a Portal is held open. |
| Held Open Prealarm | This triggers a Rule when a Portal reports a held open pre-alarm. |
| Locked | This triggers a Rule when a Portal's mode is set to, "Locked". |
| Opened | This triggers a Rule when a Portal is opened. |
| PIN Only | This triggers a Rule when a Portal's mode is set to, "PIN Only". |
| Secure | This triggers a Rule when a Portal is secured. |
| Unlocked | This triggers a Rule when a Portal is unlocked. |
This Event Category is used when you are configuring a Rule that will be dependent on the state of the System
| Event Type | Description |
|---|---|
| A controller task is consuming too many resources | The Rule is triggered when a Controller task is taking too many resources. |
| All PACS BluB0X Wiegand Converter Events | The Rule is triggered when any System level event is detected at a Wiegand converter. |
| All PACS Controller Events | The Rule is triggered when any System level event is detected at a Controller. |
| All PACS SIO Board Events | The Rule is triggered when any System level event is detected at a SIO Board. |
| BluB0X Wiegand Converter Offline | This triggers a Rule when a Wiegand converter goes offline. |
| BluB0X Wiegand Converter Online | This triggers a Rule when a Wiegand converter comes online. |
| Clock related failure caused reset | This triggers a Rule when there is a clock error that forces the Wiegand converter, Controller or SIO Board to rest. |
| Controller Card Database cleared due to SRAM buffer overflow | This Rule will be triggered when more memory is allocated than is available. |
| Controller Card Database Saved | This Rule will trigger when Card data is synced with the Controller. |
| Controller Configuration Database Saved | This Rule will trigger when Controller data is synced with the Controller. |
| Controller offline, error occurred | This Rule is triggered when an error is detected and the Controller is offline. |
| Controller online, error occurred | This Rule is triggered when an error is detected and the Controller is online. |
| Controller reset button was pressed | This Rule is triggered when the reset button is pressed on the Controller. |
| Controller reset by power cycle | This Rule is triggered when a Controller is reset by having its power supply interrupted. |
| Controller reset caused by low voltage detection | This Rule is triggered when a low power situation is detected. |
| SIO Board Online | This triggers a Rule when an SIO Board comes online. |
| SIO Board timeout | This triggers a Rule when communication with an SIO Board is unavailable or taking too long. |
This Event Category will be used to detect and trigger rules based on changes made to Person Records.
| Event Type | Description |
|---|---|
| Login Added | This will cause the Rule to be triggered if a new login is added by one of the People selected. |
| Login Changed | This will cause a Rule to be triggered when a change is made to a login is added by one of the People selected in the triggered by field. |
| Login Password Reset Requested | A Rule is triggered when one of the selected People requests to change their own password. |
| Login Reset Forced Password Change | A Rule is triggered when one of the selected People is forced to change their password because login permission was revoked and then added again. |
This Event Category will be used when you are configuring a Rule that will trigger off of Alarm events.
| Event Type | Description |
|---|---|
| Video Motion | A Rule will be triggered when movement is detected by a video camera. |
Use this Event Category when configuring a Rule based off the Visitor Management System.
| Event Type | Description |
|---|---|
| Visitor Checked In | A Rule is triggered when a Visitor is checked in for the selected System, Facility or Occupancy. |
| Visitor Checked Out | A Rule is triggered when a Visitor is checked out of the selected System, Facility or Occupancy. |
| Visitor Initial Arrival | |
| Visitor Instance Updated | A Rule is triggered when a previously defined visit is updated. |
| Visitor Invitation Added | A Rule is triggered when a new Visitor instance is added to the selected System, Facility or Occupancy. |
| Visitor Invitation Updated | A Rule is triggered when a Visitor's invitation is modified. |