- A new API call On Postman, in the Departments folder called "POST Create new department" is now available
This API adds a new department with its associated default MAG to the system. This call is only available in our last Postman Collection available. Contact us for latest collection - An API call "Get photos" is now available
The Get photos call returns the following data:
- Cardholder UID
- Cardholder First name
- Cardholder Last name
- Photo string
- Integration with KONE smart elevator solutions
The Kone smart multi-car and multi-door elevator systems manage car efficiency according to the floors that passengers select from the elevator panel while waiting for a car’s arrival.
By integrating GuardPoint10 with Kone elevators, you can use cardholder information to manage the lift’s elevator panel. This allows you to restrict floor and car door selection via the elevator panel access to those floors where the cardholder may be granted access.
To use this integration, set the Display Kone Lift option to Yes in the Options > General screen. Then you will be able to create lift controllers via the infrastructure screen and add Kone Lift access groups via the Access screen. A Kone Lift access group (LAG) can then be managed and assigned to cardholders like any other LAG. - A new controller emulator is now available. The new Emulator addresses some of the short comings found in the old Emulator
The new Emulator is a web application with the following benefits:
- Each controller’s events can be set to repeat a specific number of times per minute.
- Cardholders in the database are used when emulating Access and Denied Access events.
- Existing infrastructures can be imported into the Emulator.
- A network with multiple controllers can be imported.
- All controller types supported in GuardPoint10 are also supported in the Emulator.
- Easily restore a customer's infrastructure.
- A quick and simple method to transfer emulator data between machines.
- Compatible with GuardPointpro and GuardPoint10 software.
- Crisis Level authorization override is now available
The Crisis Level feature is designed for high-risk violent situations, where a quick and comprehensive security response is required to limit movement.
Instead of changing the access authorizations for multiple cardholders, which would involve downloading new parameters for each cardholder to each controller, the Crisis Level feature provides a security setting for the whole system that can be changed with a single click.
The Crisis Level override is achieved by taking a crisis level value assigned to a cardholder and a crisis level value assigned to a reader. Then make the following two evaluations:
- If Crisis Level was not enabled, would the cardholder be granted access via the reader?
- Is the crisis level value assigned to the cardholder equal to or greater than the crisis level value assigned to the reader?
- Programmable Badge Format
A badge format is used as a key to tell a controller how to decode strings of data bits received from the controller’s reader. The Programmable Badge Format allows you to design your own decoder.
The infrastructure screen now includes a new Programmable Badge Format button in the Action bar. This button opens a new Programmable Badge Format screen, where you can add a virtually unlimited number of user-defined badge formats. From this screen, you can specify a badge code length, position, and code system (Hexadecimal or Decimal). Optionally, you can also specify a site code length, position, value, and code system (Hexadecimal or Decimal). - Reader details’ Miscellaneous tab redesign
The Reader details’ Miscellaneous tab has been redesigned to support Programmable Badge Format and other new features.
In the Miscellaneous tab’s Format drop-down list a new list item called Programmable has been appended to the end of the list. Select Programmable to display a Programmable Format field where you can select a user-defined format previously saved in the Programmable Badge Format screen.
Click the Edit Format button next to the field to open the Programmable Badge Format screen with the selected format in focus.
Other new features in the Reader details ’Miscellaneous tab:
- The interfaces available have been expanded. Click the Interface field, and select one of the following interfaces from the drop-down list:
- Clock & Data (ISO2)
- Wiegand TTL
- DDS serial reader
- APERIO reader
- OSDP reader
- UZ reader
- The Cardholders screen has a new Select Mandatory Fields drop-down list
Users will now be able to choose cardholder fields (including Custom Fields) that will require a value before a cardholder details popup can be saved. Determine which fields will be mandatory via the new Select Mandatory Fields list found on the Cardholders screen.
The Select Mandatory Fields list can be hidden from a user via the profile assigned to the user. In a Profile’s Authorizations tree, go to Management > Cardholders > Select Mandatory Fields to edit the setting.
Enhancements
- A more comprehensive Audit system has been added to GuardPoint10. This system includes more details about audited events and a larger range of events that will be audited. A comprehensive list of audited events is displayed in the Event History > Audit table and more focused audit events display in the Event Log table.
- After of specified number of invalid login attempts, by a user who is not a Superuser, the user’s login will be Locked out. The lockout action will include an Audit event.
- A cardholder who has no GuardPoint10 activity for a specified number of days may now be automatically invalidated.
- An option has been added to automatically Free badges from any automatically invalidated cardholder.
- Logging in with Active Directory (AD) credentials will now be blocked when the AD user is disabled. An explanation about the failed login will appear on the GuardPoint10 Login splash screen.
- GuardPoint10 now supports Facelite (FLDB) facial recognition reader. Be aware that FaceLite face templates are not supported on Facestation and vice versa.
- API: A Verification log type has been added to the Software /Log Into Events Log. This means that Log Into Events Log now supports “Information”, “Warning”, “Alarm”, and “Verification” types.
- API: Department has been added to all relevant API calls.
- The AcsNMService has been updated to streamline processes and run more efficiently.
- User login with Active Directory credentials can now be forced. This means that users will not have the option to log in with GuardPoint10 credentials and must use their Active Directory credentials.
- A user will now require the machine with the Active Directory to be connected to successfully log in to GuardPoint10. Login data will no longer be retained in a cache on the GuardPoint10 system. Each GuardPoint10 login event will also check if the user’s Active Directory credentials are enabled. If the credentials are not enabled, the login will be unsuccessful.
- With Active Directory enabled, the Users screen will now display a Sync User DataThis button will update or add user information with the Active Directory profile information of the profile linked to the GuardPoint10 user.
- Two Lift Access Groups (LAGs), regardless of the lift type (lift controlled by DDS relays, ELGSW smart lift, or KONE smart lift), can now be assigned to a cardholder. One LAG included in the Multiple Access Group (MAG), and the other LAG assigned in the cardholder’s details as a Personal Lift Access Group (PLAG).
- When accessing on Mitsubishi smart lift (ELGSW) reader, no relay of the Lift controller will be automatically activated on access.
- In the Diagnostic tree, select a controller and click Refresh. A popup appears with a new option that allows the user to refresh the remaining commands every second.
- GuardPoint10 now supports Uhlmann & Zacher (UZ) readers. The UZ reader appears in the Reader Miscellaneous tab’s drop-down list of supported interfaces.
- Advanced parameters (F1, 3, 4, 5, 6) have been added to the Reader’s Miscellaneous tab. These parameters relate to firmware customization requests. These parameters can be hidden or displayed via the Display advanced parameters in reader details setting found in the Options > System & SQL tab.
- A new Import Cardholders spreadsheet has been added to GuardPoint10. It includes the following columns:
- Crisis Level
- Personal Weekly Program (Personal WP)
Use the new spreadsheet to ensure cardholder import success.
- A new Import Cardholders Global Reflex action has been added to the system.
- The behavior of the option Display flashing non-compliant icon has been updated. When set to Yes the Machine Compliance icon will display in the Dashboard. When the option is set to No, the icon will be hidden.
- An access event row displayed in the Event Log table now include a context menu. The context menu, opened with a simple right-click, includes an item to Display cardholder details and an item to Display reader details. After a context item is clicked, the details will display.
- In the Options > Event Log screen, there is a new parameter to show/hide and change the text color of Send Free Command event displayed in the Event Log table.
- French and Spanish translations are now available in the Badge Print Report Designer.
- A new French resx file has been added with updated translations.
Bug Fixes
- Fixed: Badge Template assignment and design operations now work consistently.
- Fixed: A Badge Template’s date format (DD/MM/YYYY), regardless of the date field, is now standardized throughout the system.
- Fixed In a cardholder’s Print Badge popup the assigned Badge now displays correctly regardless of the GuardPoint10 installation type (server or workstation).
- Fixed: A License’s serial code is now available for a single GuardPoint10 system installation. Other system installations must have their own unique serial code.
- Fixed: API: POST LogIntoEventsLog now returns the correct data, without internal errors.
- Fixed: A scheduled reader added, and then deleted via API and later readded (all, via API), now works reliably regardless of other previous API scheduled reader.
- Fixed: API: Item fields in the Get all photos response (under GET cardholders) have been renamed:
- Item1 -> "cardholderUID"
- Item2 -> "lastname"
- Item3 -> "firstname"
- Item4 -> "photo"
- Fixed: API: In Chinese, the Relays details will now display correctly regardless of the Display API keys setting in Options.
- Fixed: API: Correct results will now appear when, in POSTMAN, you execute a Get Scheduled Readers query.
- Fixed: Cardholder Report now exports reliably to an Excel spreadsheet while maintaining badge code format in the Excel cell.
- Fixed: Reader can now consistently save specific Clock & Data (ISO2) with selected Badge Formats.
- Fixed: A method has been added that prevents the system from downloading a badge code to the same memory location as a previously downloaded badge code on the same controller.
- Fixed: In a cardholder’s details popup, the Badge group’s Add button now works reliably.
- Fixed: The Select button in the Add Readers dialogbox now works correctly on double-click.
- Fixed: Biometric readers no longer automatically initialize after restarting the GuardPoint10 server installation.
- Fixed: When the monitor is scaled higher than 100 percent, the Video Setup screen will now display correctly.
- Fixed: A user with read-only permissions for cardholders can no longer delete cardholders from the Cardholders screen.
- Fixed: In the Import Cardholder spreadsheet, the Badge type tool-tip has been updated. Item 11 ‘Type H’ has been replaced with ’Smartcard 13.56 MHz’.
- Fixed: When using a Global Reflex that sends emails via a Gmail account host, you must have a 2-step-verificationoption and sign it with App Passwords.
- Fixed: After initializing a LIFT readers’ controller, the LIFT reader will now be available, and the assigned relays will fire correctly during an access event.
Comments
0 comments
Please sign in to leave a comment.