beqom PaySuite 25.0 - Detailed 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 the intermediate 25.0 release of the beqom PaySuite application and in the subsequent patches.
This is an attention message.
The text in this article is AI-generated. A final version will provided shortly.
25.0
Deployment to staging environments: June 2nd, 2026
Deployment to production environments: June 9th, 2026
| Type | Issue key | Module | Description | Feature Flag* | |
|---|---|---|---|---|---|
| Zendesk | Jira | ||||
| AC-16946 | Performance Management | The pagination indicator in Workbench > Goal Types and Workbench > Goal Plans was not displaying correctly, repeatedly resetting to '1 of X' instead of reflecting the actual current page. The pagination display has been corrected to remain stable during navigation. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-17194 | Performance Management | In Passport > Goals, an unsaved changes warning dialog was incorrectly displayed when users clicked Cancel on the Create Goal form without having made any changes. The form was being flagged as modified during its initial load due to how default values were set. This behavior was corrected so that canceling the form without making changes now closes it immediately without prompting. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
145090 145102 | AC-22649 | Compensation Management | An issue was corrected where the year dropdown in the date picker (used when creating a Check-in or selecting a date with no pre-existing value) defaulted to the year 1900 instead of the current year, requiring users to scroll through the entire list to reach the correct year. The dropdown now defaults to the current year when no date has been previously selected. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | |
| 146947 | AC-23584 | Authorization | An issue was corrected in the DataFoundation ingestion process where, if one record in a batch upload failed validation (for example, due to a duplicate username), all other valid records in the same batch were also prevented from being created in the system. Because DataFoundation had already registered those valid records as ingested, any subsequent attempt to re-upload them returned a 'No changes detected' message, leaving users with no way to recover without making an artificial change. The synchronization logic has been updated so that correcting and resubmitting the failed record triggers a full reconciliation, automatically creating all previously blocked valid records without any additional workaround. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | |
| AC-23604 | Data Foundation | A new Pay Transparency Bulk Data report was added to Pay Transparency reporting, enabling large-scale compensation analysis and regulatory submissions. The report displays individual employee compensation values alongside male, female, and group averages for each compensation component, and calculates each employee's percentage distance from group averages — categorized by threshold range. The report is read-only, supports filtering and export, and applies role-based access controls to ensure only authorized data is visible. | – | ||
| AC-24446 | Pay Transparency | Outlier percentage values displayed in pay analysis results were calculated using an incorrect formula, causing misaligned data in the Outlier and distance from predicted compensation columns. This was corrected so that the Outlier percentage is now calculated as ((After Raise − Predicted) / Predicted) × 100, aligning the results with the expected values in Pay Analysis. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24796 | Data Foundation | A semantic model for the Pay Transparency Worker report was added, enabling aggregations across compensation elements including base and additional components. The model calculates average values by gender and overall group for each worker category, per snapshot, supporting pay transparency analysis. | – | ||
| AC-26245 | Authorization | A new IAM Synchronization Logs screen has been introduced, giving Support, DataFoundation Admin, and Configurator roles direct visibility into identity and access management synchronization activity. Authorized users can now monitor synchronization execution history, view status and summary metrics, trigger a manual synchronization, and download detailed log files — all without relying on Data Foundation ingestion status. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26711 | Authorization | An issue was corrected in the IAM service (Identity and Access Management) where messages notifying the system of user custom attribute updates were failing to process, which could result in user attribute changes not being reflected across the platform. This issue has been resolved to ensure custom attribute updates are correctly handled and propagated. | – | ||
| AC-26808 | Performance Management | In Planner, managers can now view a list of Talent Reviews that include their direct reports. Managers can see the name, published date, and status of each relevant Talent Review, and navigate directly into a review's details page to begin evaluations. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26833 | Compensation Management | The bqm.Common.AdvancedCalculations library (a shared package used by the compensation calculation engine) was updated to the latest 2.0.X version in the compensation service to incorporate recent platform enhancements. This change is internal and has no direct impact on users. | – | ||
| AC-26906 | Compensation Management | Admins can now configure translations for Digital Reward Statement (DRS) content in Workbench > Digital Reward Statement > Settings, allowing employees to view their DRS in their preferred language. Translatable fields include section headers, descriptions, live labels, and dropdown option labels across all DRS widgets; where a translation is not provided, the system automatically falls back to the default company language. | – | ||
| AC-26974 | Compensation Management | In Workbench > Compensation Builder > Compensation Rounds, Global Compensation Admins and Compensation Admins can now select Bool as a return type when creating calculated columns, in addition to the existing Decimal and String options. Bool calculated columns display as read-only checkboxes in Team Planner, enabling admins to build indicator columns — such as flagging whether a proposed increase falls outside a guideline — and support filtering by True/False values, sorting, use in eligibility formulas, and use as a source field in conditional formatting configuration. | – | ||
151721 151851 151934 | AC-26984 | Data Foundation | Data Viewer was not displaying ingested data for workers unless the ProvisionUserAccount flag had been set to true at some point, preventing users from validating uploaded data through the normal workflow where provisioning is not required. This issue was corrected so that Data Viewer now displays ingested data regardless of whether a worker has been provisioned as a user account, including data surfaced through the Worker Consolidated Data feature. | – | |
| AC-27068 | Data Foundation | In Performance Reviews, warnings were generated during semantic model data refresh because rating scale columns were sorted solely by their order field, which caused inconsistent sort ordering when the same scale appeared across multiple templates. This was corrected by introducing a composite sort key that accounts for both the template and the order field, ensuring rating scales sort consistently and the semantic model refreshes without warnings. | – | ||
| AC-27320 | Compensation Management | In Workbench > Compensation Round > Workflow Step configuration, Compensation Admins can now configure conditional approval logic directly within a workflow step. Each condition block lets admins define a boolean formula, select approvers with the Conditional Approver role, and specify a target step the record routes to upon approval, enabling flexible, rule-based approval flows within compensation rounds. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27339 | Data Foundation | An issue was corrected in the snapshot generation process where snapshots would fail with an error when worker category fields were not present in the currently selected model. The validation logic has been updated so that missing category fields are automatically included when fetching snapshot data, allowing snapshots to complete successfully across all worker category modes. This feature is currently behind a feature flag and is not yet available to all customers. | |||
| AC-27345 | Data Foundation | In Workbench > Data Management > Custom Entities, the drawer displayed when selecting a custom entity now includes the entity reference name. Users can view this identifying information directly within the drawer for easier reference. | – | ||
| AC-27591 | Compensation Management | Guaranteed Amount values for Bonus compensation elements were not displayed in the Planner grid, Individual View, or drawer because two separate areas of the calculation engine incorrectly assumed that Guaranteed Amount rules only applied to standard compensation elements, causing values to be excluded from calculations entirely when the Bonus category was used. This was corrected so that Guaranteed Amount rules are now properly compiled and registered for Bonus compensation elements, and values are displayed as expected across all relevant views. | – | ||
| AC-27670 | Pay Transparency | Recommended raises synced from Performance Assessment were not being converted to each worker's local currency, resulting in incorrect raise amounts being applied. Currency conversion rates are now correctly applied during the sync process. | – | ||
| AC-27671 | Data Foundation | An incorrect value was displayed for the Not Released KPI in the Pay Communication Report. The underlying variable used to calculate this metric was corrected, and the Not Released count now displays accurate figures. | – | ||
| AC-27689 | Performance Management | In the home page Home, non-clickable notifications in the Notifications widget and the bell icon dropdown incorrectly displayed a hover highlight and a pointer cursor, suggesting they were interactive when they were not. This behavior was corrected so that only clickable notifications retain hover styling and pointer cursor, while non-clickable notifications no longer appear interactive. | – | ||
| AC-27724 | Compensation Management | A new Planner Calculations tab is now available in Workbench > Pay Management > Compensation Rounds when configuring a Team Planner View, allowing Compensation admins to define rules that automatically recalculate target fields in real time when a planner actor edits a related trigger field. Default calculation rules are automatically created and managed for Salary compensation element fields (New Value, Increase Amount, and Increase %), replacing the previously hardcoded calculation logic for these fields. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27865 | Compensation Management | In Compensation Round > Column Configuration, the maximum number of calculated columns allowed per round has been increased from 20 to 50. Compensation Admins and Global Compensation Admins can now create up to 50 calculated columns within a single round, with the updated limit applying to all existing and newly created rounds. | – | ||
| AC-27927 | Performance Management | The page title in Workbench > Performance Management > Talent Review Templates incorrectly displayed as 'Templates' instead of 'Talent review templates'. This has been corrected to match the intended design. | Yes | ||
| AC-27953 | Compensation Management | In Workbench > Compensation Builder and Planner > Compensation, success and informational notifications now appear as auto-dismissing toast messages displayed in a consistent location, replacing the previous popup-style notifications. Message content remains unchanged — only the visual presentation of confirmations has been updated. | – | ||
| AC-27958 | Pay Transparency | In Pay Information requests, the audit trail drawer incorrectly described user-driven status changes — for example, a transition from New to In Progress was displayed as 'marked as resolved' rather than reflecting the actual status change. Status change entries in the audit trail now accurately describe the transition that occurred. | – | ||
| AC-27983 | Data Foundation | In Workbench > Custom Entities, adding two fields with the same name and saving would previously return a raw 400 error code instead of a meaningful message. This was corrected so that a clear error message is now displayed when duplicate property names are detected. | – | ||
| AC-27988 | Data Foundation | In Custom Entities > Grid Builder, when a field was configured with a default value but the 'Is Required' option was not selected, attempting to save would display a raw HTTP 400 Bad Request error. A descriptive validation error message is now shown instead, guiding users to correct the configuration before saving. | – | ||
| AC-28001 | Pay Transparency | The feature flag controlling document generation mappings was removed, making this functionality permanently available without conditional gating. This change is internal and has no direct impact on users. | – | ||
| AC-28011 | Pay Transparency | An error that occurred when attempting to save a Pay Information Request in Planner > Pay Information Requests with only one of the two 'Generate document' fields completed was corrected. HRBPs can now save the request successfully when either one field is filled or the previously filled field is cleared before saving. | – | ||
| AC-28047 | Data Foundation | In the custom entities configuration area, the tooltip helper displayed 'Provide a name for the entity' when adding a new column, rather than guidance specific to naming a column. This was corrected so that the tooltip now accurately reads 'Provide a name for the column'. | – | ||
| AC-28203 | Authorization | Unauthenticated cache-reset endpoints were removed from the Feedback API and API Gateway (internal services used to manage data caching across the platform) to eliminate a potential security vulnerability that could have allowed repeated cache clearing across all tenants. This change is internal and has no direct impact on users. | – | ||
| AC-28209 | Pay Transparency | In Planner > Pay Analysis, Main Analysis entries that had not been made accessible to HRBPs were incorrectly displaying a clickable hyperlink, which resulted in a redirect error when followed. This was corrected so that Main Analysis entries without HRBP access no longer appear as clickable links. | – | ||
| AC-28217 | Data Foundation | Several issues with calculated fields in the modeler were resolved, including problems with updating field names or descriptions, incorrect function behavior (such as CONCAT, IF, and LOOKUP), and misleading or disappearing error and success messages. Additional improvements were made to alias validation, input limits, and UI display when formulas exceed available screen space. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-28232 | Compensation Management | Improvements were made to the worker job scheduling system used to manage compensation round publishing, replacing the previous synchronization mechanism with a more reliable database-backed approach and correcting the calculation of job run intervals. This change is internal and has no direct impact on users. | – | ||
| AC-28251 | Data Foundation | Widget titles and column names in the Pay Transparency Report semantic model (used to configure and display report data) can now be translated into all supported Accelerate languages, allowing users to view report labels in their preferred language. | – | ||
| AC-28305 | Performance Management | Validation testing was completed for the talent review template publishing workflow, confirming that template status changes, review creation, and rating generation behave as expected under defined population and access scope conditions. This change is internal and has no direct impact on users. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-28385 | Compensation Management | Bonus comp element toggle states (Target bonus, Prorated target bonus, Calculated bonus, Bonus amount, and Guaranteed amount) in Workbench > Compensation Management > Compensation Rounds were not correctly persisted after a compensation round was saved and republished, causing previously disabled toggles to revert to enabled on re-entry. This occurred because the disabled state was being read from the wrong source during updates. The correct disabled state is now saved and preserved through Save & Exit and republishing. | – | ||
| AC-28399 | Data Foundation | Security vulnerabilities in the Snappier library (used internally by the MongoDB database driver for data compression) and OpenTelemetry packages (used for application monitoring and diagnostics) were patched at the source in the shared accelerate-common dependency repository. The Snappier package was updated from version 1.0.0 to 1.3.1, resolving a high-severity advisory, and the OpenTelemetry packages were updated from version 1.15.0 to 1.15.3, resolving two moderate-severity advisories. This change is internal and has no direct impact on users. | – | ||
| 152754 | AC-28427 | Data Foundation | Population count requests were timing out for organizations with large numbers of workers and employments when the population definition included a filter on a field such as legal entity. This occurred because the filter criteria were only applied after all underlying data had been fully processed and joined, rather than earlier in the query where they could limit the data evaluated. The query logic was corrected to apply eligible filter criteria earlier, significantly reducing execution time and allowing population counts to complete successfully. | – | |
| AC-28452 | Compensation Management | The Datadog RUM (Real User Monitoring) integration, used for tracking application performance and user session data, was removed from the platform. This change is internal and has no direct impact on users. | – | ||
| AC-28489 | Pay Transparency | Three packages in the ML Service (the machine learning component of the platform) were upgraded to versions that resolve known security vulnerabilities. This change is internal and has no direct impact on users. | – | ||
| AC-28496 | Compensation Management | In Team Planner > Compensation, custom single-select dropdown cells whose stored value has since been removed from the column's configured options now display that value with strikethrough styling and a warning icon, clearly indicating the value is no longer available rather than appearing empty. Compensation Managers and HRBPs can open the dropdown to replace the outdated value with any currently valid option or clear the cell entirely, after which the unavailable value is permanently removed from that cell's dropdown and the warning indicator disappears. | – | ||
| AC-28513 | Compensation Management | In Compensation rounds, the Compensation Elements field incorrectly allowed elements to be removed via the chip 'X' button when editing a pending draft for an in-progress round, despite the field being intended as read-only. This was corrected so that no removal button is displayed on compensation element chips and the field remains fully read-only in this context. | – | ||
| AC-28520 | Compensation Management | Security vulnerabilities in the application's Docker image (the containerized environment used to run the platform) were remediated by upgrading the base operating system to Debian 12, updating the Node.js runtime to version 22 LTS, and patching several dependencies including i18next-http-backend (used for loading translations) and qs (used for parsing URL query strings). This change is internal and has no direct impact on users. | – | ||
| AC-28523 | Performance Management | When copying a goal in Passport > Goals and assigning it to a different worker, the original owner's name was incorrectly displayed in the create goal wizard instead of the newly selected worker's name. This display issue has been corrected, and the wizard now shows the correct owner when copying and reassigning a goal. | – | ||
| AC-28526 | Pay Transparency | In Communication > Mapping Configuration, the context menu for deactivated mappings did not include an option to edit them, making previously deactivated mappings inaccessible for modification. This was corrected, and users can now open and edit deactivated mappings directly from the list. | – | ||
| AC-28527 | Data Foundation | The TCM manifest file (a configuration file used to define which reports are deployed to the reporting platform) was updated to restore the Comp Rounds (Contracted Compensation) report, which had been inadvertently replaced with an incorrect report entry. This change is internal and has no direct impact on users. | – | ||
| AC-28538 | Compensation Management | Improvements were made to the calculation library (the engine used to evaluate compensation formulas and rules). Expression return type validation was extended, and the handling of decimal precision policy was refactored to make the system more maintainable and extensible. This change is internal and has no direct impact on users. | – | ||
| AC-28541 | Data Foundation | A configuration issue in the Analytics Hub was resolved where reports failed to load due to a missing role definition in one of the deployed reports. After the roles were added, the Analytics Hub and all reports now display correctly. This change is internal and has no direct impact on users. | – | ||
| AC-28546 | Data Foundation | Several visual alignment and layout issues in the Data Modeler were corrected. Field counters, table widths, and container margins across the Data Entities & Sources and Calculated Fields pages now display consistently, and the tree element line color and empty state messaging for calculated fields were updated to match the intended design. | – | ||
| AC-28557 | Data Foundation | A Cancel button was added to the footer of the drawer in Workbench when creating a calculated field. Users can now exit the creation process without saving, providing a clearer and more intuitive workflow. | – | ||
| AC-28630 | Performance Management | The pdf-generator-api service (the engine responsible for generating PDF documents) was migrated from the npm package manager to pnpm, and its dependency packages were updated to current versions. This change improves build reliability, reduces CI pipeline test execution time, and strengthens supply-chain security by blocking newly published packages from being installed automatically. This change is internal and has no direct impact on users. | – | ||
| AC-28788 | Authorization | The Snappier library (a compression codec used internally by the MongoDB database driver) was updated from version 1.0.0 to 1.3.1, and the OpenTelemetry libraries (used for internal diagnostics and trace reporting) were updated from version 1.9.0 to 1.15.3 in the Authentication, Authorization, and IAM services. These updates address known security advisories flagged during dependency audits. This change is internal and has no direct impact on users. | – | ||
| AC-28810 | Data Foundation | An error was corrected where filtering data in the data foundation (the layer that retrieves and serves compensation data) using multi-value criteria — such as selecting multiple compensation elements or status values — caused a database syntax error and returned an HTTP 500 failure response. This was caused by a recent change that generated an invalid SQL expression when multiple filter values were provided. Filtering with multiple values now executes correctly and returns the expected results. | – | ||
| AC-28822 | Data Foundation | The calculated fields API (used to define and manage formula-based fields in compensation models) was updated so that the value "Boolean" is now consistently accepted as the result type when creating or updating calculated fields. Previously, the API rejected this value due to a naming mismatch between the wire format and the system's internal vocabulary. This change also corrects an issue where Boolean-typed calculated fields referenced in other fields' formulas were not resolving correctly. This change is internal and has no direct impact on users. | – | ||
| AC-28840 | Authorization | The authorization library used by the IAM (Identity and Access Management) and Integration Hub services was upgraded to version 8.14.4. This update natively supports users belonging to more than 10 Security Groups without requiring a previous internal workaround, and lays the groundwork for contextual role support in future releases. This change is internal and has no direct impact on users. | – | ||
| AC-28857 | Data Foundation | Code ownership records were updated across nine Data Platform repositories to reflect a change in team membership. This change is internal and has no direct impact on users. | – | ||
| AC-28860 | Performance Management | The timeout limit for the Performance Reviews report refresh request was increased from 10 seconds to 60 seconds. Previously, the short timeout caused a refresh error when loading the Performance Reviews report, preventing users from viewing up-to-date data. The report can now be refreshed successfully. | – | ||
| AC-28883 | Data Foundation | An issue was corrected in Workbench > Data Management > Calculated Fields where LOOKUP formulas incorrectly required all fields from a reference entity to be mapped. Only KeyFields are now required for the formula to be valid. | – | ||
| AC-28898 | Compensation Management | The Compensation API container base images and OpenTelemetry packages (libraries used for application monitoring and observability) were updated to address security vulnerabilities identified by automated scanning. This change is internal and has no direct impact on users. | – | ||
| AC-28909 | Data Foundation | Calculated field formulas using NULL() or IF(cond, NULL(), x) were incorrectly rejected with a FormulaResultTypeMismatch validation error, regardless of the declared result type. This occurred because the formula validation pipeline did not recognize NullType as universally compatible with any nullable result type. The validation pipeline was corrected to properly accept NullType-inferred formulas for all declared result types (Decimal, Integer, String, Date, and Boolean). | – | ||
| AC-28914 | Data Foundation | Calculated fields of type Date were incorrectly serialized using a culture-specific format that included a time component (e.g., "12/01/2020 00:00:00") instead of the standard ISO 8601 date format (e.g., "2020-01-12"), causing inconsistencies between calculated snapshot data and situation snapshot data. This occurred because date values were converted to text without a fixed format, producing results that varied depending on the system locale. Date values in calculated snapshot data are now serialized in ISO 8601 format, consistent with situation snapshot data. | – | ||
| AC-28915 | Data Foundation | An issue was corrected in the Data Modeler service where changing the calculated-field selection on a model (adding or removing calculated fields) did not publish an integration event to notify downstream components. A new dedicated event, ModelCalculatedFieldsUpdatedEvent, was introduced and wired into the save process to ensure that downstream consumers are correctly notified when a model's calculated-field set changes. This change is internal and has no direct impact on users. | – | ||
| AC-28925 | Data Foundation | Previously, certain field labels — including 'Data Snapshot' and 'Compensation Amount' — were not translated in the Pay Transparency > EUPTD report. These fields are now correctly translated in the report. | – | ||
| AC-28992 | Compensation Management | An error was corrected in Planner > Compensation where attempting to export a compensation round to Excel returned a 500 error whenever any worker had an empty monetary data point. This occurred because empty money values were not handled correctly during export processing. The export now completes successfully, rendering empty monetary values as zero. | – | ||
| AC-29018 | Data Foundation | In Workbench > Data Management > Calculated Fields, the NULL() function has been removed from the list of available functions displayed in the Conditional dropdown. Administrators will no longer see this unsupported function as a selectable option when configuring calculated fields. | – | ||
| AC-29031 | Compensation Management | Conditional formatting rules applied to data model fields were not being honored, resulting in columns never being colored even when the specified conditions were met. Because model field information was being trimmed to reduce data transfer, the formatting rules lacked the context needed to evaluate and apply correctly. This was corrected so that conditional formatting is now properly applied to data model fields. | – | ||
| AC-29081 | Data Foundation | An issue was corrected in the Worker data endpoint where users scoped to a parent org unit could not retrieve data for workers employed in descendant org units. The authorization filter (which controls what data a user is permitted to see) was only matching the exact org unit assigned to the user and was not expanding to include child org units, resulting in zero records being returned. The filter now correctly resolves descendant org units so that workers employed at any level within the permitted org hierarchy are included in results. | – | ||
| AC-29089 | Data Foundation | The default formula for the seeded FullName calculated field was updated to use the CONCAT function instead of the + operator for string concatenation, aligning the stored configuration with the platform's standard approach for combining text values. This change is internal and has no direct impact on users. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-29096 | Compensation Management | In the Audit Trail, the Increase Percentage field incorrectly displayed a currency code alongside the numeric value when a change was recorded in the Planner grid. This was corrected so that the Audit Trail now displays only the numeric value for Increase Percentage entries. | – | ||
| AC-29110 | Data Foundation | The Bqm.AuthZ package (an internal authorization library used to manage access control across Data Platform services) was updated to the latest version across several Data Platform services. This update enables Security Groups support within the platform. This change is internal and has no direct impact on users. | – | ||
| AC-29155 | Data Foundation | Incorrect distance category labels displayed in the Pay Equity > Pay Transparency report were corrected. The distance category values now display as: Within 5%, Higher (5–10%), Higher > 10%, Lower (5–10%), and Lower > 10%. | – | ||
| AC-29166 | Authorization | An error was corrected in the IAM service where processing user custom attribute update events would fail with a type mismatch in the database, causing the operation to time out after 15 seconds and leaving messages unprocessed. This occurred because a unique identifier was being passed as plain text instead of the correct UUID format when querying the database. The parameter is now properly converted before execution, ensuring the operation completes successfully. | – | ||
| AC-29176 | Authorization | When using the Integration API to clear a single custom subject attribute by sending an empty array in a separate request, all other previously assigned custom subject attributes were incorrectly removed rather than preserved. This occurred because the system performed a full overwrite of the attribute record instead of a partial update. The issue was corrected so that only the targeted attribute is cleared while all other custom subject attribute assignments remain intact. | – | ||
| AC-29193 | Data Foundation | A previously introduced change that caused errors during data model refresh (the process of updating and synchronizing the platform's data structure) was reverted. This change is internal and has no direct impact on users. | – | ||
| AC-29201 | Authorization | Synchronization logs incorrectly reported a successful status even when data ingestion failed due to validation errors, such as an invalid email format. This occurred because the success flag was not dynamically calculated based on actual ingestion results. The sync status is now accurately set to failed when one or more errors occur during ingestion, ensuring issues are immediately visible in the synchronization logs without requiring manual inspection of the downloaded log file. | – | ||
| AC-29212 | Performance Management | Calls to the reporting API through the Integration Hub were failing when the request took longer than 10 seconds to retrieve data, blocking the generation of performance review reports. The timeout threshold has been corrected so that reporting API requests now complete successfully even when data retrieval exceeds 10 seconds. | – | ||
| AC-29222 | Data Foundation | An issue was corrected in Workbench > Data Management > Workers where users with the DataFoundationAdmin role were incorrectly shown a 'You do not have access to this data' error and could not search for workers by full name. Missing authorization attributes were added to resolve the access restriction, and DataFoundationAdmin users can now view and search the Workers page as expected. | – | ||
| AC-29243 | Compensation Management | Read-only cells in Planner were incorrectly displaying all data types with right-aligned text. This was corrected so that only numeric and monetary fields remain right-aligned, while text, date, and boolean fields are now properly displayed left-aligned. | – | ||
| AC-29256 | Data Foundation | In the Pay Transparency EUPTD report, the report page name was updated from 'Individual Employee Report' to 'Individual Worker Report' to reflect the correct terminology. | – | ||
| AC-29259 | Data Foundation | In the Pay Transparency EUPTD report, column widths on the Individual Worker Report page and the Export Details page were adjusted so that all relevant columns are visible without requiring horizontal scrolling. | – | ||
| AC-29262 | Data Foundation | Translation support was added for the Individual Worker Report page in the Pay Transparency EUPTD report. This page can now be translated into the languages supported by the platform. | – | ||
| AC-29289 | Localization | Translation keys in the Pay Transparency EUPTD report were not correctly reflected in the Localization API, causing labels to display incorrectly. The Localization API has been updated to align with the current report terminology, ensuring translations are now displayed as expected. | – | ||
| 154391 | AC-29373 | Data Foundation | Snapshot generation was failing with the error 'Unable to compute due to previous errors' when the population included a large number of worker records alongside contracted compensation elements. This issue was corrected and administrators can now successfully generate snapshots under these conditions. | – | |
| AC-29447 | Data Foundation | Performance improvements were made to the situation snapshot query generation engine (the component responsible for building compensation snapshots used in planning and reporting). Queries that previously took over a minute to complete when compensation data was included in the model now execute significantly faster. | – | ||
This is a miscellaneous message.
About Feature Flags
beqom practices continuous development and continuous deployment. According to this method of work, code can be added to the code base but hidden behind a Feature Flag. When features or parts of a feature are hidden behind a Feature Flag, then they are not visible in the application interface even though the code exists in the code base. This is to make sure that new code is included in small increments, which makes it easier to test and guarantees higher code quality, without impacting end-users.
Features that are marked as behind a Feature Flag in this table are not yet available to end-users. Their release will come at a later date when the full scope of the features is done.