beqom v10 HF200 - 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: April 22nd 2025 - PRD: April 29th, 2025
Fix version: v10 - HF 200.4 - DB 10.0.1002
| Type | Reference | Title | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-25708 | Previously, forms attached to a process did not have the ability to define dynamic drop-down lists where options depend on process values. This hotfix introduces that functionality: dropdown lists in forms can now be dynamically populated based on values in the process. Applicable fields: the association is allowed on indicator and information fields only. Configuration options can be set up via database or APIs only. API contract change: the API api/forms/{Uid of Form} has changed from GET to POST to support this functionality. Impact Existing integrations using api/forms/{Uid of Form} will need to be updated to use POST instead of GET. | ||
| BQM-25478 | A change has been made to display the position code under the candidate's name in the new hire prediction scenario of the Pay Predictor. | ||
| BQM-25510 | An enhancement to the Pay Predictor prediction page has been introduced to add a validation of the values of the fields selected by the user after each change. This allows the user to receive information about incorrect data input. | ||
| #126370 | BQM-25540 | In process grids, it was not possible to manually enter dates such as 31-03-2024, 30-03-2025, 29-03-2026, 28-03-2027, 26-03-2028 because of a date-type value formatting issue. This issue has now been corrected. | |
| #124983 | BQM-25545 | In process grids and data grids, empty ('') and NULL values were treated differently in filters and yielded different outcomes. This fix standardizes their handling, so both are now treated the same. Specifically, the IsEmpty operator will now retrieve rows where the value is either NULL or empty. This impacts filtering behavior in both data grids and process grids. | |
| #127702 | BQM-25593 | Docx files can now be generated / delivered with report subscriptions through a new Word 2007 option when creating a report subscription in Admin Portal. | |
| BQM-25607 | A justification comment field to the final bid card in the prediction page of the Pay Predictor. | ||
| BQM-25608 | A new endpoint was created to validate field values in the Pay Predictor. | ||
| BQM-25611 | A new comment field "justification_comment" was added to the final offer card edit dialog of the pay prediction page. | ||
| #105530 | BQM-25617 | Previously, submitting or revoking all rows in a process grid required individual actions. Now, two new buttons‚Submit All and Revoke All‚ enable users to validate all rows in a single click. | |
| BQM-25668 | In the Pay Predictor, it is now possible to reset the tenure_in_level value to 0 whenever the job level is modified in a prediction request. | ||
| BQM-25672 | In the pay prediction page, the name of the prediction is now displayed in the page header. | ||
| BQM-25686 | In the pay prediction UI, it is now possible to apply a custom ordering of field groups. For this, a new table, bqm_field_group_order, was added. | ||
| BQM-25703 | In the pay prediction page, a notification warning is now displayed indicating that the tenure field is automatically set to 0 when the value in the job_level field is changed and the prediction is updated. | ||
| BQM-25729 | The position code and name are now returned in the results of the GET api/ml/position/{id} endpoint used in the Pay Predictor. | ||
| BQM-25732 | A change has been made to exclude validation of non-categorical fields in the POST api/ml/field/validate endpoint used in the Pay Predictor. | ||
| BQM-25733 | The order of field groups was modified in the prediction page. | ||
| BQM-25735 | A change was made to the GET endpoint /api/ml/prediction/{predictionId}/results to retrieve payee salary in destination currency in the pay prediction UI. A new field, called current_pay_value_in_prediction_currency, was added . | ||
| BQM-25737 | In the prediction page, the current salary is now displayed in the target currency. After changing the currency on the prediction page and recalculating the prediction, the amount in the target currency appears. | ||
| BQM-25808 | When the isEmpty or IsNotEmpty filter was applied on numeric columns or percentage columns, an error was displayed. This issue is now corrected. | ||
| BQM-25832 | When password protection was enabled for a report, the list of formats available during the creation of a new subscription was incorrect. The issue was corrected; the list of available formats is now accurate. | ||