beqom v10 HF183 - 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: October 2nd, 2024
Fix version: v10 - HF 183.7 - DB 10.0.960
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-24541 | Web App: Improper Permission Handling of the Ad hoc Report Cloning Button The ad hoc report cloning button, which is located in the property panel of individual ad hoc reports, did not follow the proper permission pattern; specifically, the "copy" permission under Admin Portal > Admin > Functional admin > Profiles > <ProfileName> > Analysis > Ad hoc Reports was not taken into account. The issue was corrected; the button now behaves as expected. | ||
| BQM-24646 | Back-end: Additional Logs for Sphere To increase the quality of the beqom TCM v10 application and improve debugging efforts, new logs were implemented for the Sphere updates. | ||
| BQM-24702 | Web App: Improvement of the Behavior of the Clone Button for Ad hoc Reports The Clone button was always displayed in the property panel of individual ad hoc reports, regardless of the permissions of the currently logged in user. To avoid any confusion, the button is no longer displayed if the user does not have the proper permission, ("Copy" permission, under Admin Portal > Admin > Functional admin > Profiles > <ProfileName> > Analysis > Ad hoc Reports | ||
| BQM-24835 | Web App: Advanced Analytics Edit Script Feature no Longer Available The script edition feature for Advanced Analytics widgets was no longer available (an error 404 was returned when attempting to perform this action). This was due to an access issue; to correct this, the URL used to edit the scripts was whitelisted. | ||
| 96391 | Mobile App: Display an Indicator when KPIs are Simulated An indicator, which displays "Simulated value" is now displayed when KPI values are simulated. This change offers users added clarity when using simulated values compared to real values. | ||
| 109951 | Advanced Analytics: Reports not Run on Replica Database The following issue was observed with Advanced Analytics: when working with a replica database, the reports were run on the primary database and not on the replica due to a connection issue. The problem was corrected and the reports now run on the correct database. | ||
| 112358 | Web App: Cannot Import Grid In the , if the user exported a grid template containing a list field with values that included the " ' ", made changes offline and selected a value with the character " ' ", and then reimported the grid, the import would fail with an error message. Investigation revealed that the issue specifically occurred because the character was included in list values because the application did not support the character in this context. The issue was corrected; the import now behaves as expected. | ||
| 113325 | Mobile App: Cannot Log in Under High Load The following issue was reported when using the TCM mobile app: when numerous users were attempting to log in simultaneously, the log in mechanism failed and users could not get into the application. To correct this problem, the login mechanism has been optimized to make sure that users can get into the application. | ||
| 114054 | Web App: Real-Time Calculation not Triggered for Percentage-Type Columns When using the real-time calculation feature with percentage-type columns, the real-time calculation was not triggered when changes were made in the configured column, specifically on the decimal part of the numbers. Investigation of the problem revealed that an incorrect calculation was performed for percentage-type columns. The problem was corrected by changing the method used to parse the RTC value and make sure that the correctly formatted value (in %) is used. | ||
| 114968 | Web App: Form not Refreshed in Active Session When working on a form attached to a process grid, if the user remained inactive for a period of time longer than the timeout duration defined by the administrator, the form would not get refreshed when the user became active again and the system would display an error. This was due to the fact that the issue was related to the information contained in the security token that checks the rights of the logged in user. The problem was corrected; forms are now properly reloaded after a timeout. | ||
Ongoing deployments
| # | Changes | Impact | Comment |
|---|---|---|---|
| BQM-24480 | API changes: - DB changes: Pay prediction permissions added to k_rights | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | This enhancement to the pay prediction feature introduces new profile permissions that can be used to grant users various rights within the feature. |
| BQM-24580 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | The behavior of the Save button in the pay prediction interface in Web App has been adjusted to clearly indicate to users whether or not they have changes to save (enabled/disabled state). |
| BQM-24654 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | Three new information cards have been added to the pay prediction interface: Current Salary , Pay Recommendation and Raw Pay Prediction. |
| BQM-24655 | API changes: - DB changes: New fields added to add additional fields to Prediction_Statement_View | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | Additional information can now be selected for the export of the pay prediction into PDF, such as the core fields used for the prediction, the model field values and the attributes. |
| BQM-24673 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | The behavior of the pay prediction feature was adjusted so that users can only see the predictions they have created in the system. Previously, all uses of the feature could see all predictions available in the platform. |
| BQM-24709 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | An issue where no pay prediction was generated when fte/fx rate calculations were applied has been corrected. |
| BQM-24723 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | The new permissions for the pay prediction feature created in ticket BQM-24480 are now applied to the front-end of the feature: when opening the pay prediction UI, users can only see the items and perform the actions defined by their assigned profile. |
| BQM-24755 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | An issue where an incorrect value (row ID instead of payeeID) was saved in the salaryPredictionPredict table was corrected to make sure that predictions are properly mapped to the correct payees. |
| BQM-24772 | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | The pay prediction API did not work correctly: when a call was made with a non-existent payee_code value, the system considered the code as a new hire, which was not necessarily the case. | |
| BQM-24776 | API changes: - DB changes: - | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | The query used to retrieve the name of employees in the employee selection drop-down list of the pay prediction UI has been optimized to improve the performance of the list and make sure that employee names can be retrieved quickly. |