To enable Kone AK integration, the GuardPoint10 license must explicitly include support for it.

With the Kone AK integration, Kone lift manages authorizations and access control directly within the Kone environment. GuardPoint10 acts as a passive observer, logging all related access events in both the Event Log and Event History Access grids.

To support this integration, GuardPoint10 has undergone extensive GUI enhancements. All user interface elements related to Kone AK use native Kone terminology to ensure consistency and clarity. The key enhancements are outlined below:

• Options: In General Communication Setting there is a new Display Kone AK Lift item. When set to Yes, Kone AK related GUI elements are displayed and communications with the Kone server is established.
• Profiles: A new item, Cardholder Kone AK, has been added to the Authorization tree under Management > Cardholders. This enables the Kone AK tab in the cardholder’s detail popup, allowing users to configure Kone-specific settings for the cardholder.
• Note: The following configuration elements should be managed by users familiar with the Kone environment, terminology, and installation practices.
• Infrastructure: When a new Kone AK Group is added to the infrastructure tree, detailed information about the associated Kone server and environment is displayed. Most of these fields are read-only
• Access: A new Kone Profiles sub-screen has been added to the Access screen. Here, users can define Kone profiles and configure profile associated attributes.
• Cardholder Details popup: A dedicated Kone AKtab is now available in the cardholder popup. For each Kone AK group, the following configurations are available:
  • Select the language displayed on the Kone reader.
  • Assign a Kone Profile to the cardholder.
  • Choose Direct Call Destinations.
  • Enable Mobiex functionality.

In the Event History screen, when the system has different log archives, you can now filter an event in all the archives instead of searching for it in each archive database. A new Select multiple archived journals checkbox is available. When selected, checkboxes appear next to each journal archive in the journal drop-down list. You can select multiple checkboxes to load several journal archives into the Event History grids. Additionally, a Go button will appear next to the journal selection drop-down. The selected archives will only be loaded after clicking the Go button.

This Journal Archive button creates a timestamped archive on demand. The button is only enabled when the values declared in the For Events Older Than (in Days) field is satisfied. This button allows manual archiving when the archive criteria are met, regardless of the Restart ACS Services option setting. The button is in Options > System & SQL, under the Journal Archive section.

The archive criteria is now based solely on the number of days specified in the For events older than (in Days) field.

With BioEntry W3 devices, GuardPoint10 can now scan for access events using a badge code or facial recognition.

Enhancements

Cardholder

A new profile authorization called Non-Visitor Type Managing has been added to the profile authorization tree. This authorization restricts access to cardholders who are not of the type Visitor. In practice, it allows an GuardPoint10 user to view only cardholder events and details related to visitors.

For cardholders who are also GuardPoint10 users, their GuardPoint10 login privileges will be automatically blocked if they are declared as invalid cardholders.

The Cardholder details popup now includes an expanded Assigned Badges list where more than two badge rows can be displayed at once without the need to scroll.

Until now, the Search functionality allowed filtering by a single field—either First name, Last name, or Employee number. Now we have added the ability to search by both First name and Last name, either individually or in combination. This enhancement would enable more flexible and efficient searches, allowing users to find cardholders using multiple criteria simultaneously (e.g., searching for "John Smith" by entering both first and last names or "Smith John").

Security Centre

The Security Centre screen’s Access Events pane can now filter the event list to display LPR access events.

Biometrics

GuardPoint10 supports Corporate 48-bit cards on Suprema BioStation 3 devices (only BS3-APWB model). These formats are associated with HID Corporate 1000 card technology.

Reports

A new Multiple Access Group Report has been added to the Access screen. This report displays the name and description of each MAG (Multiple Access Group). From the Access Report view, users can toggle between the Access Group Report and the Multiple Access Group Report using the toggle button located to the right of the Edit button. The name shown on the toggle button changes based on the currently displayed report.

In the Event History > Audit grid, a cardholder’s name will now appear along with their number.

Adding a new cardholder with a new LPR will now record the new LPR as a separate record in the Event History > Audit table.

Any update to an LPR in the system will now have a record in the Event History > Audit table.

The Event History > Audit table now displays a record of a badge status change when a badge is detached from a cardholder via the cardholder’s details.

In the Event History screen, a 'Defer Filtering' button has been added next to the grid type selection buttons. When working with millions of records, and multiple filters across multiple grids in the Event History screen, it's more efficient to click (enable) 'Defer Filtering', set your desired column filters, and then click the 'Defer Filtering' button again to apply all column filters with a single action.

Also, the Reader Permissions screen now includes a Defer Filter button. When the screen is initially opened, the Defer Filter button is engaged by default, all column filters are cleared, and the Permissions table is empty. A user can either release the Defer Filter button to load all permissions (which may take some time), or apply column filters first and then release the button to load only the filtered permissions.

API

Departments can now be added to the database via a POST.

A cardholder’s Do not apply APB rules setting can now be edited via a POST.

The Call API_AuditEventLogs now includes an auditChanges field. This field returns a cardholder’s status change (created, updated, deleted, archived, or restored). This also includes any change to a cardholder’s photo and badges.

The GET Cards CALL that includes a filter now executes without interruption until successfully completed.

When freeing a cardholder’s badge via a PUSH, the cardholder UID of the last cardholder to own the badge will now appear in the results.

The badge Audit will now include a cardholder UID, where a badge edit includes a cardholder.

Cardholder CALLs will now include ResetAPBLevelWhenDownload field. The field has a default value of true.

General

GuardPoint10 now supports Qognify SDK 7.5.

When adding a Global Reflex action using an item from the Action Group: User Interface Action (such as Display message on PC or Play sound), users can now select the workstation(s) where the action will be executed. Select the Workstation checkbox next to the action’s new parameter to specify the target workstation(s). If not selected, the action will be executed on all workstations.

An internal routine has been added to the default SQL backup directory. This routine automatically backs up the main database and journal on a regular basis.

The icon for deactivated controllers has been hidden by default. A new Display icon for deactivated controllers’ option has been added to the Options > System & SQL screen to display this icon on the dashboard. When set to Yes, this icon will appear on the dashboard. Clicking the icon will display a message identifying the deactivated controllers by name.

If a controller experiences repeated table errors within a defined interval, it can now be automatically deactivated to prevent further issues. The settings that control this behaviour are located in Options > System & SQL, under the Repetitive Events section.

To prevent an unrecoverable error by a user, the Options screen’s Restore Defaults button has been removed.

The Allow automatic lock after a period option has been renamed to Allow automatic lock after a period of inactivity and now locks the GUI after the specified number of inactive minutes.

The Help > License screen now includes the First activation date and the Last update date.

In a MultiSplit environment, the network details shown in the Diagnostic screen now include the name of the Network Agent selected for that network via the infrastructure screen.

When the GuardPoint10 GUI language is French, the F1 key will open the PDF version of the Help.

Fixes

Fixed: API: GET outputs now work correctly while a DOM controller is active.

Fixed: API: The Update Cardholder Call now functions consistently without affecting LPR values.

Fixed: The Get All Photos API now reliably returns data.

Fixed: The Alarm Zone Security screen now consistently displays an alarm state’s text.

Fixed: All unsuccessful access attempts are now correctly recorded in the Event History.

Fixed: Inputs fired constantly will now appear correctly on a Security Centre map.

Fixed: Dates are now consistently displayed correctly in reports that have been exported to Excel spreadsheets.

Fixed: Edits to a cardholder’s details, which include adding a photo, and switching badge ownership now consistently appear correct in the Event History > Audit table.

Fixed: Badge print operations now consistently appear correct in the Event History > Audit table, regardless of the screen where the Badge print operation was initiated.

Fixed: Assigned user permissions have been stabilized in a Multisite environment.

Fixed: APB level update commands are now consistently sent to other controllers.

Fixed: Saving changes to a cardholder’s details popup are no longer slowed down due to parking commands.

Fixed: The Event History screen now loads quicker.

Fixed: The APB module now works reliably regardless of the number of times a badge is swiped.

Fixed: In every situation, the area occupancy counter now refreshes accurately.

Fixed: After freeing a badge, via a cardholder’s popup, the Save button in the popup no longer temporarily enables.

Fixed: In the Reader Permissions grid, column filters now work for right-to-left languages.

Fixed: After freeing a badge via a cardholder’s popup, the list of assigned badges will now immediately update.

Fixed: Freeing or assigning an LPR to a cardholder via a cardholder popup will now work smoothly in the popup.

Fixed: It is no longer possible to duplicate an existing LPR badge code via saving and editing a new LPR badge code.

Fixed: Two cardholders with the same LPR assignment will now have unique internal badge codes associated with each LPR.

Fixed: A license plate number (LPR) can now be removed from a cardholder’s details reliably without impacting other badges or LPRs assigned to the cardholder.

Fixed: A new cardholder no longer encounters an issue when an LPR is assigned, and the cardholder is then saved for the first time.

Fixed: An LPR now imports correctly even when the import spreadsheet contains minor LPR-related data entry issues.

Fixed: An LPR can now be reliably added to a new cardholder, regardless of the state of mandatory Custom Fields.

Fixed: Large numbers of LPRs in the database no longer impact the Acs Server service and the login screen.

Fixed: Network details can now be updated in a right-to-left language GUI, regardless of the length of the network’s name.

Fixed: The Event History > Audit grid now appears correctly after editing a department.

Fixed: After an Area, which has a GAPB option, is cleared via a Global Reflex action, an Area Roll Call screen’s occupancy/capacity value and the relevant cardholders’ details are now automatically updated

Fixed: Updated to an Access Group are now reliability uploaded to relevant controllers.

Fixed: When the Event Log is the first screen opened by the user, it will now open smoothly.

Fixed: A large number of Power Supply Alarm messages no longer prevents the Event Log screen from loading.

Fixed: In a cardholder’s details popup, deleting a badge code using the red ‘X’ now successfully frees the badge code.

Fixed: In a cardholder’s details popup, any change to the cardholder’s photo will appear in the Event History > Audit grid as Photo: ‘xxx’ -> ‘…’ in the Audit Change column.

Fixed: Converting a Single Site environment to a Multisite environment now completes successfully and reliably.

Fixed: The infrastructure > Setup Wizard now successfully completes when used a second time.

Fixed: Journal Archives should use the same collation as the SQL Server. If the collations differ, anomalies may occur.

Fixed: Duplicated cardholders will now include only the basic information provided in the original cardholder’s details.

Fixed: GuardPoint10 can now be successfully installed on a Windows O/S that is set to Korean.

Fixed: An ‘Access Granted’ event originating from a Destination Dispatch lift (e.g., Otis) will now be displayed correctly in the Event Log table.

Fixed: A user belonging to more than one Active Directory group can now successfully log in to GuardPoint10 using their Windows credentials.

Fixed: DOM readers are now displayed correctly in the Reader table on the infrastructure screen, without red frames around each row.

Fixed: A cardholder can now reliably be imported with multiple semicolon separated badge codes.

Fixed: When removing a badge code from a controller (i.e., invalidating a cardholder), unrelated parking commands are now sent as expected.