This week's release:
Global | Core Platform | Membership file uploads
Membership refresh uploads for larger clients can cause data mismatches and data leaks affecting a large number of members, compared to clients with smaller employee numbers.
This is because the current validation and protection logic in the membership upload is based on percentage: we allow changes to up to 10% of total registered members, and if over 10% of members are being edited, we block the upload for additional review before proceeding. For example, within a programme with 100,000 employees, each upload can edit up to 10,000 member accounts before it's flagged for review.
We decided to set a limit to the number of member accounts that can be edited without additional review. This is based on the total number of registered employees per scheme.
Here are a few examples.
- If we have a programme with more than 10,000 registered employees, we will check that changes affect no more than 1,000 members in total.
- If we have a programme with more than 20,000 registered employees, the maximum number of members that can be edited without additional checks will be 1,500.
- If we have a programme with more than 30,000 registered employees, the maximum number of members that can be edited without additional checks will be 2,000.
This logic will continue until we get to clients with more than 100,000 employees. From that number onwards, the number will always be capped at a maximum of 5,000 employees.
This new limitation will help prevent data mismatches for clients with large numbers of employees in our system. When the number of changes within a file exceeds the cap, an accurate review of the changes being made can then prevent data leaks and unauthorised access to personal data.
Global | Core Platform | BambooHR Integration
As of today, all clients using BambooHR integration will be able to segment which employees will be provisioned on their platform.
We added this new option in the Mapping step, where IT Administrators can now segment employees based on a specific field, as in the example below.
If a client wants the integration to only provision UK employees, they can segment the integration by Location and enter the United Kingdom.
Global | Reward & Recognition | On the Spot Recognition:
Testing has shown us that, when uploading On The Spot awards with different values, the Assessment page would default them all to the value of the last award edited in Reward Manager. However, when completing the file upload, all awards would still be created with the correct values.
Clients can manage On The Spot Recognition on a self-service basis. The inconsistency at the Assessment stage could prevent them from uploading their files altogether, out of concern that the system would charge the wrong amounts.
We've now fixed the issue so that all award values displayed at the assessment stage are correct.
Global | Holiday Trading | Product eligibility calculations
Clients that have employees with flexible working time want to specify how long the working week of those employees is, so their Holiday Trading allowance is correct. To do this, they add a column called Holiday Trading Work Days to their eligibility files.
So far, when our system calculated the allowance based on this data, it always rounded the numbers and didn't accept half units (e.g. 0.5). From now onwards, the column will allow half increments too.