beqom v10 HF208 - Release notes

This article lists the new features that have been added to the platform, as well as the bugs that have been corrected in this release.

Deployment date: NPR: July 15th 2025 - PRD: July 22nd, 2025

Fix version: v10 - HF 208.5 - DB 10.0.1009

Type	Reference		Description
	Zendesk	Jira
		BQM-25791	In the Pay Prediction UI, the predicted pay is now capped by a configurable range defined using min and max values. The possibility to have a raw uncapped predicted pay is however retained.
		BQM-25912	The following issue was observed: the parameter PRM_Bulk_Insert_Batch_Size parameter was not documented or present in the k_parameters table, though a default value of 2500 was used in the code. To avoid any potential issues, the parameters was included to the k_parameters table with a default value of 2500, making it visible and manageable in the database.
	130336	BQM-25922	When teams were used in the Web App interface of the v10 application, the data security was sometimes not correctly applied and some records in data grids were visible to team members who should not have seen them. The issue was corrected and data security is now correctly applied.
	132130	BQM-26102	An issue where the RTC (Real-Time Calculation) was not triggered when a date field was manually cleared was reported. Clearing the date now correctly triggers the RTC, ensuring calculations and updates are performed as expected.
		BQM-26103	Capped salary prediction values are now visible in the Pay Prediction UI, with the pay prediction cards displaying the min value, max value and the prediction value (with any eventual adjustment to fit the min/max range).
		BQM-26110	This update ensures that local development environments are compatible with the latest authentication and passport configuration.
		BQM-26130	As part of Q3 Accessibility Enhancements, minor UI changes were implemented and a significant update to the date picker component was performed to improve screen reader accessibility.
		BQM-26142	In the Pay Prediction feature, the MinRange and MaxRange values were null when pay prediction capping was disabled.Now the default min and max values are populated when capping is disabled.
		BQM-26143	In the Pay Preduction UI, no warning message was displayed when changing the job level because the back-end was sending an invalid value for the tenureInLevelReset field. The issue was corrected and the application now behaves as expected.