Contents
Portal Release notes - 30th July 2025
This page outlines the new functionality and changes included in the Portal update available on Wednesday 30th July 2025
New Device Name! - Smart Biometric Clock
What have we done?
We have updated references to the device name (previously T2) within the Portal, Firmware and help docs to reflect the new name for our devices - Smart Biometric Clock!
Why have we done this?
We have spoken to customers and taken the decision to move away from a code-based naming system to something more descriptive, allowing our devices to be more recognisable to customers.
How will you benefit?
The new naming convention will allow customer to speak to us about our hardware with confidence, they can simply reference the Smart Biometric clock without having to remember a T reference that wasn't descriptive to the customer.
Details of the change
You will begin to see references to Smart Biometric Clocks moving forward rather than T2 devices, rest assured its the same hardware with a fresh new name.
Smart Biometric Clocks on Turnstiles
What have we done?
This feature allows Smart Biometric clocks to connect to a turnstile allowing a user access through a turnstile whilst also clocking them in or out of work.
Why have we done this?
To extend the use cases around the use of Smart Biometric Clocks.
How will you benefit?
This change will allow users on secure sites to both clock and release the turnstile allowing them access.
Details of the change
Full feature documentation can be found here
Clocking History - Improved transaction load time
What have we done?
We have made a change on the web portal to ensure that when accessing the Clocking history against a user that the screen returns the data in a timely manner.
Why have we done this?
To ensure that the data is returned quickly for the end user, without trying to load unnecessary historical data.
How will you benefit?
Improved user experience with the screen load time.
Details of the change
We have now defaulted the User Clocking History to load data one month back from the current date. You will still be able to access the historical data by adjusting the the Start and End dates of the query.
Audit Records - Potential blank values
What have we done?
We have corrected an issue where in certain circumstances, when changes instigated by a Consultant profile where made, the triggered by field was blank.
Why have we done this?
To ensure that the Audit History reflect a full record of changes made and by who.
How will you benefit?
Complete audit records are available in User Admin.
Details of the change
We have corrected an issue where when a consultant profile made a change, the triggered by field was not being displayed in the audit record. This field will now display the user that triggered the change irrespective of their profile.
PeopleConnect - Update import.exe
What have we done?
We have made a change to PeopleConnect for the import.exe to update the command line to FROMSRVC=Y.
Why have we done this?
This is a setting that will supress onscreen messages and add these to the background file instead.
How will you benefit?
On screen messages will be supressed in PeopleConnect and accessed via a background file as this information was not providing value being shown via onscreen messages.
Details of the change
We have updated PeopleConnect import.exe to include the default command line of FROMSRVC=Y to supress onscreen messages and add these to the background file instead.
