About Mercury triggers and procedures

How Mercury triggers and procedures work in the Synergis Appliance Portal

Mercury triggers and procedures work together to create a rule. The trigger defines the when with an event, and the procedure defines the what with one or more actions. Each trigger is linked to one procedure, but each procedure can be used in multiple triggers.
If entities used in triggers and procedures fall into an unexpected state, you can restore them to their original state with the Reset to default button on the Mercury triggers and procedures page.
Note: This button is also used to restore Mercury triggers and procedures after restoring the configuration files of a Synergis Cloud Link unit.

Best practices

For optimal performance of Mercury triggers and procedures, ensure that the following settings are enabled on the Mercury controller settings page in Synergis™ Appliance Portal:

Live 'Request to exit' events: Enable this setting if you create triggers with REX events.
Mercury native area control: Enable this setting if you create triggers related to areas.

About monitoring Mercury triggers and procedures

In Security Center 5.12 and later, Mercury triggers and procedures generate custom events, which can be used in event-to-actions.

Event monitoring: You can monitor the custom events in the Security Desk Monitoring task by adding the Synergis Cloud Link unit to the Event monitoring list.
Event reporting: You can run reports on the custom events using the Access control unit events task in Security Desk and Config Tool, and filtering on the Synergis Cloud Link unit.
Capabilities: On the Capabilities report page in the Synergis Appliance Portal, the Custom triggers and Custom procedures rows in the Capabilities section lists the number of triggers and procedure that are created on the selected Mercury controller.

Limitations of Mercury triggers and procedures

Mercury triggers and procedures in the Synergis Appliance Portal have the following known limitations:

General limitations

Each Mercury controller can have up to 3,000 triggers and 3,000 procedures. The triggers and procedures that exceed these limits are ignored.

Limitations related to configuration

You can activate an output based on an input change. However, there is no option to reset the output to its original state.
Workaround: To reset the output, create a separate procedure to set the output back to its original state with a trigger set on an input change.
Inputs and outputs that are assigned to doors or elevators cannot be used as monitor point or control point triggers.
The reader LED pattern commands that Synergis™ Softwire sends to Mercury override active LED pattern procedures. This includes setting the reader LED to red on relock and setting the reader LED to green when a door enters a free access schedule.
Power cycling the Mercury controller cancels Override reader mode procedures configured with an Indefinite duration.
The temporary reader mode configuration in Override reader mode procedures overrides any manual changes to the reader mode.
Example: If you change a reader to Card and PIN mode while an Override reader mode procedure configured to change the reader mode to Locked is active, the door remains locked. However, when the procedure expires, the reader returns to Card and PIN mode.
When a cardholder badges at a reader that was disabled with the Override reader mode procedure, the Access denied event in Security Center does not include a deny reason.
For Set control point procedures configured with a Periodic command, you only see the first and last output change in Config Tool.

Limitations related to schedules

Schedules are only synced to the Synergis Cloud Link unit if they are associated to an entity controlled by that unit. To use schedules exclusive to triggers and procedures, you must add a dummy door to the Synergis Cloud Link unit and apply the schedules to that door.
Only 255 schedules can be created in Security Center, including unlock schedule and schedules only used for Mercury triggers and procedures.
Mercury has a limit of 12 schedule intervals. For more information, see Mercury limitations with door unlock schedules.