Ease of Permissions
The Admin Login Profile now grants full permissions to the user for all systems regardless of the user's codes. Previously, the user would need a code with the necessary permission to manage the system. This is still true for any user that doesn't belong to the Admin profile group.
The Login to Customer Site option on the Dealer Site has been revamped. Previously you had two options: 1) Login to the Customer Site as your dealer user with full permissions, or 2) Login to the Customer Site as a customer user with read-only permissions. The latter option has been improved. Now you can login as a customer user and see exactly the same permissions they have including all action buttons, such as save and delete. If any action is performed then it will be logged as your dealer user. Therefore the integrity of who performed the action will remain intact. However, now you can fully test the permissions of a user and truly see the same screen your customer sees.
A new Description field is provided to store notes about a profile. This applies to both Login and System profile types. It allows the user to store notes or comments about the profile rather than trying to cram all that helpful information into the profile name.
A warning message is added to DMP System Profiles when the user chooses 'Yes' to Easy Arm/Disarm. The warning explains to the user that they should use caution when applying this option. In most cases the Easy Arm/Disarm setting will convert an ordinary door access at the reader to an arming or disarming action instead. More often than not this is applied incorrectly. The warning does not prevent the setting.
Task Rule Improvement
Task Rules can now be applied to a specific area. This allows them to follow the same permissible control of the Login Profile. Once applied to an area, only users with access to that area will be able to activate the task.
The rules can also be limited by a time constraint. Since the rule activation can be delayed on the fly for up to 4 hours, an option now exists to limit this delay. For example, a user may configure a rule to open the front door and restrict the activation so it can't be delayed. Delaying the activation would unlock the door some time in the future.
Further, if only one rule exists or the user only has access to one rule then the task will be activated from one button rather than first selecting the task button and choosing the rule from a list.
Disarming an Area on a Bosch System
Now when a user chooses to disarm a Bosch area, the action will automatically perform a silence command at the same time. This prevents needing to send a secondary command to silence the siren.