Limitations in SALTO Virtual Network plugin 3.1 - SALTO Virtual Network 3.1

SALTO Virtual Network (SVN) Plugin Guide 3.1

series
SALTO Virtual Network 3.1
revised_modified
2020-02-25

Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.

The SALTO Virtual Network plugin 3.1 integration includes the following limitations.
Issue Description
2315396 Events related to entities are received by the plugin even if it doesn't have access to the entity's partition.
2294859 A maximum of three authorization codes can be imported from SALTO ProAccess SPACE to Security Center.
2222296 You can update the name of a locker in Security Center, however; the update is not pushed to SALTO ProAccess SPACE.
2136041 Changing the hardware configuration of a SALTO door prevents it from receiving events.
2042615 Following an upgrade to SALTO Virtual Network 3.1, if you create a mobile credential in SALTO Pro Access while running Salto Virtual Network 3.0 with the plugin role active, it will be deleted.
2042406 Following an upgrade to SALTO Virtual Network 3.1, you must deactivate and then reactivate the plugin role to connect to the SALTO SHIP server.
2025472 Following an upgrade to SALTO Virtual Network 3.1, the plugin will synchronize with SALTO ProAccess SPACE. If changes were made in SALTO ProAccess SPACE since the last synchronization, those modification will override the values in Security Center.
1992917 Cardholder credentials that are set to expire in SALTO ProAccess SPACE at a specific time, will expire at the 10-minute mark prior. For example, if the credential is set to expire at 12:56, it will actually expire at 12:50.
1960060 If a cardholder credential is set to disable after first use, a read on a SALTO lock is not taken into account.
1956403 If a custom data type created by SALTO is manually deleted, the associated custom field will not work as expected.
Workaround: To recreate the field, delete the associated custom field and restart the plugin. Perform a synchronization to update the field.
1956135 Regardless of the privileges they are assigned, Security Desk users cannot view the SALTO section in the dialog box to create or modify a cardholder.
947819 In Security Center 5.7 SR4 or earlier, if you create access rules for a SALTO door or area, and then add cardholders or a cardholder group to the door or area, they will not have access.
Workaround: Create an access rule, and then add the door or area, and cardholders or cardholder groups to it.
947812 Members of cardholder groups are only imported the first time a group is imported into Security Center. Changes made to members later are not imported in subsequent synchronizations.
941660 The warning message Door locks should normally be configured appears at the bottom of the Door Hardware tab because the door lock is unassigned. Security Center expects a door to lock, but the locks are managed in SALTO.
Workaround: You can ignore this message.
941502 If you delete a reader unit associated to a SALTO door in Security Center, the reader can only be restored by importing entities from SALTO ProAccess SPACE.

Details: Readers do not exist in SALTO. When you import a door from SALTO, Security Center creates a reader for that door. If you delete the reader in Security Center, and then want to restore it, you simply re-import SALTO entities.

941406 When the SALTO Virtual Network role is restarted, the monitored events that occurred in the past minute are displayed again in the Monitoring task of Security Desk, so you see duplicate events.
937959 If you create an empty schedule in SALTO ProAccess SPACE, during import, the schedule is ignored by Security Center.
937957 If you change the name or description of a locker in Security Center, your changes are not updated in SALTO ProAccess SPACE.
937956 Access rules for SALTO can only grant access. Denying access is not supported for SALTO. Deny rules that are created in Security Center are not exported to SALTO ProAccess SPACE.
937955 You can only assign one schedule to a cardholder for a specific door.
Workaround: Use cardholder groups to manage multiple schedules for a single cardholder.
937954 Access rules created in Security Center overwrite the rules created in SALTO ProAccess SPACE.
937947 In SALTO, a cardholder schedule (timetable) can only contain eight periods, where a period is a unique block of time, regardless of the day of the week.
937946 SALTO calendars include holidays and two special days. Security Center does not support Holiday, Special 1 and Special 2 schedules, so the data is deleted during import.
Workaround: Manually create holiday and special-day schedules into Security Center after import.
937945 The Genetecâ„¢ Server that runs the plugin role and the SALTO SHIP server must have matching computer dates, times, and time zone. If there is a mismatch, events are not reported accurately and the system does not sync properly.
937062 When doors that are not part of a SALTO Virtual Network zone are imported into Security Center, they are added to the SALTO Virtual Network plugin's default area (zone). You cannot remove these doors from the SALTO Virtual Network plugin area, but you can add them to other areas.
Workaround: After the systems have already been synchronized: copy the door to another area by pressing CTRL while clicking the door, and then drag the door to the desired area.
Workaround: Before you import SALTO doors into Security Center for the first time, use SALTO ProAccess SPACE to add the new doors to zones.
930312 In the Cardholder configuration report, the Last access column displays unknown, even when there was access.