beqom PaySuite 24.1 - 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 24.1 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.
24.1
Deployment to staging environments: May 19th, 2026
Deployment to production environments: May 26th, 2026
| Type | Issue key | Module | Description | Feature Flag* | |
|---|---|---|---|---|---|
| Zendesk | Jira | ||||
| AC-17817 | Compensation Management | Sorting and filtering capabilities were expanded in the Planner to support any field, including calculated fields such as Guaranteed Amount. Managers can now sort columns in ascending or descending order by clicking a column header, and apply filters through a dedicated filters drawer that supports currency selection for monetary fields and label-based filtering for enumeration fields. Additionally, the Eligibility column was updated to display the Selected Column label of the associated compensation element. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-19145 | Performance Management | In Workbench > Performance Management, the top panel on the review content page did not remain visible when scrolling if the review contained sensitive words, and using the navigation arrows failed to scroll to the sensitive word locations. The scrolling logic was corrected so that the top panel now stays fixed at the top of the page while scrolling, and the navigation arrows correctly scroll to the relevant sensitive content. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24118 | Performance Management | In Passport > Goals, the 'Add my direct reports' button remained visible when a manager's direct reports were not included in the Goal Plan population, resulting in no action when clicked. The button is now hidden in this scenario, ensuring managers only see the option when they have eligible direct reports to add. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24119 | Performance Management | In Workbench > Data Management > Custom Labelling, the keys 'request_feedback_widget_dataset' and 'request_feedback_widget_dataset_about_my_team' continued to appear in the downloaded CSV file after they had been replaced by updated keys. The CSV export has been corrected and now contains only the current, valid label keys. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24548 | Data Foundation | A Formula Library was introduced in Data Foundation, giving Data Foundation Admins the ability to create, view, edit, and delete Calculated Fields (reusable formula definitions used to encode business logic such as compensation calculations and eligibility rules). Admins can define formula expressions, manage metadata such as name, return type, and description, and explicitly configure external data references — such as Custom Entities — that can be used within formula expressions. This provides the foundation for defining and maintaining reusable business logic that can later be validated and executed across the platform. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24551 | Data Foundation | A controlled lifecycle for formulas was introduced in the Formula Library, giving Data Foundation Admins the ability to manage formulas through three states: Draft, Published, and Deactivated. Newly created formulas default to Draft and can be freely edited, while Published formulas become read-only and are the only formulas available for use in downstream processes such as snapshot execution. A status summary widget was also added to the Formula Library, showing at a glance how many formulas exist in each state. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24616 | Data Foundation | Data Foundation Admins can now explicitly select Published Calculated Fields when configuring snapshots in the snapshot configuration. When a Calculated Field is added, the system automatically resolves and validates all dependencies — including required model fields, external dataset references, and other dependent Calculated Fields — at configuration time rather than at execution, preventing runtime failures before they occur. Invalid or unresolvable dependencies block the configuration from being saved, and users can view which dependencies are introduced by their selections for greater transparency. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25500 | Pay Transparency | In Planner and Workbench, the Pay Analysis grid now displays a worker count indicator showing the number of workers a user is authorized to view out of the total number of workers included in the analysis (for example, 23/240). This gives compensation users immediate visibility into the scope of their accessible data based on their organizational permission settings. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25529 | Data Foundation | Presales deployment environments were added to the automated pipeline configuration, enabling administrators to deploy all presales environments with a single action. This change is internal and has no direct impact on users. | – | ||
| AC-25933 | Compensation Management | In Planner, when Proposal Management was enabled for a compensation element, the tooltip for the compensation element and the Proposal Management tooltip overlapped, making it difficult to distinguish between the two. This issue was corrected so that each tooltip now displays independently: the Proposal Management icon shows its own tooltip, and the column header tooltip appears only when hovering over the header. | – | ||
| AC-25983 | Pay Transparency | In Email Notifications > Documents, users with the Configuration role can now optionally include the communication manager(s) of a communication round in CC on the 'A new document is available' notification sent to workers when a document is released. The CC recipients are resolved dynamically based on the live hierarchy at the time of sending, ensuring that if a worker's communication manager has changed, only the current manager receives the copy. This applies to both single and bulk document releases. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| 149674 | AC-26066 | Performance Management | User initials displayed in avatars were inconsistent for employees with three or more name words — for example, the same employee could appear with different initials depending on whether they were selected alone or alongside other employees. The initials calculation has been corrected so that avatars now consistently display the first letter of the first word and the first letter of the last word of a user's name across all relevant views, including team goal creation, inbox PDF previews, and profile panels. | – | |
| 151386 | AC-26241 | Performance Management | The 'Reassign Manager' button icon in the Year-End Review was not consistent with the icon displayed in Career Discussion for the same action. The icon in the Year-End Review has been updated to match the one used in Career Discussion, ensuring a consistent visual experience across both features. | – | |
| AC-26242 | Authorization | The Identity and Access Management (IAM) service was updated to correctly interpret worker and user provisioning flags when synchronizing employee data from Data Foundation. IAM now independently evaluates whether a worker record and a user account should each be active, ensuring that users are only created, disabled, or retained based on their specific provisioning settings rather than worker data alone. This prevents unintended user deletions or account creations when worker records change. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26323 | Performance Management | A new Talent Review Templates page was added in Talent Review, giving users with the Talent Review role a centralized view of all templates across their lifecycle. The page displays a summary of total, in-progress, and draft templates, along with a templates table showing name, owner, status, and other details. Template owners can create new templates, and edit or view existing ones directly from the list using the available actions menu. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26324 | Performance Management | In Talent Review, template owners can now publish a Talent Review template directly from the final step of the setup wizard. Publishing transitions the template from Draft to In Progress status, making it active and accessible to managers and HR users for their respective populations based on access permissions. A confirmation dialog and validation checks ensure all required fields, population definitions, and questionnaire configuration are complete before the template is published. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26428 | Compensation Management | Workflow stages can now be configured within the Workflow configuration step of the round wizard in the compensation round setup. Compensation admins can create, edit, reorder, and delete stages using the new Manage Stages modal, assigning a name, actors, and a time-based end date to each stage, with workflow steps scoped to the currently selected stage. Stages are mandatory for every round, and navigation actions such as Back, Next, and Save & Exit are blocked until all stages are fully configured and have steps assigned. | – | ||
| AC-26563 | Compensation Management | A data migration (an automated update to existing records) was performed to align all existing compensation rounds with the new workflow stages data model, which requires every round to have at least one stage. All existing workflow steps were automatically grouped into a default stage per round, preserving step order, configuration, and actor assignments without any changes to round execution or worker progression. This change is internal and has no direct impact on users. | – | ||
| AC-26580 | Compensation Management | In Workflow configuration, new cross-validations were introduced between workflow stages and their nested steps. When configuring steps, Compensation admins will see inline errors if a step's end date exceeds its parent stage's end date, and the step actor dropdown is now filtered to show only actors assigned to the parent stage, preventing misconfiguration at the source. When a stage end date is reduced or a stage actor is removed, affected steps are flagged with a red outline and errors are listed in the configuration banner, prompting admins to resolve conflicts before proceeding. | – | ||
| AC-26607 | Compensation Management | In Workbench > Pay Management > Compensation Rounds, duplicating a compensation round now copies the full workflow configuration to the new round, including all stages and the workflow steps within each stage. Compensation Admins and Global Compensation Admins can rely on duplication to replicate complex multi-stage workflow setups without manual re-entry. | – | ||
| AC-26619 | Compensation Management | In Workbench > Pay Management > Compensation Rounds > Round Management Portal, the read-only Workflow side panel now surfaces workflow stage information for Compensation Admins. A new 'Workflow Stages' section displays stage cards that, when selected, filter the workflow steps diagram to show only the steps assigned to that stage. A 'Stages details' link opens a read-only two-panel view where admins can review each stage's name, description, actors, and completion criteria. | – | ||
| AC-26622 | Compensation Management | In Workbench > Pay Management > Compensation Rounds, the Pending Draft workflow configuration now supports stage-level modifications. When a Pending Draft is created from a Ready or In Progress round, it inherits the full workflow structure — including all stages, their properties, and associated steps — from the parent round. Compensation Admins and Global Compensation Admins can add, edit, delete, and reorder stages within the Pending Draft without affecting the parent round's configuration. Any stage change is treated as a workflow modification and triggers updated warning messages noting that all workers may be reset to the first step of the first stage upon republishing. | – | ||
| AC-26625 | Compensation Management | The daily worker progression job was extended to support stage-level advancement in addition to step-level advancement. When a stage's end date has passed, workers are automatically moved to Step 1 of the next stage, regardless of their current step within that stage, with stage end dates taking priority over individual step completion. If multiple consecutive stages have expired end dates, workers advance through all of them in a single pass. | – | ||
| AC-26628 | Compensation Management | In Planner > Compensation, round visibility for HRBPs, Compensation Managers, and Compensation Managers +1 now respects a second layer of filtering based on the active workflow stage. Each workflow stage defines which roles can access a round during that stage's date range, meaning a round may appear or disappear from the list as the active stage changes over time. When all stages have completed and no active stage exists, round visibility falls back to the round-level access configuration and the round is displayed in read-only mode. | – | ||
| AC-26651 | Compensation Management | A new Pay Information widget was added to the Digital Rewards Statement configuration in Workbench > Platform Setup > Passport, allowing authorized users to enable or disable the Pay Information section for employees and configure its content, including the section header, description, country-based eligibility, and request submission mode. When enabled, the Pay Information section is displayed in the employee-facing DRS in Passport > Compensation for workers whose country matches the configured eligibility settings, using the saved configuration; when disabled, the section is hidden entirely with no placeholder shown. This widget works in conjunction with the existing Pay Transparency feature setting, meaning both must be active for the section to appear to employees. | – | ||
| AC-26666 | Compensation Management | A feature branch was established to support the next phase of Advanced Workflow development, covering round configuration and publish functionality. This change is internal and has no direct impact on users. | – | ||
| AC-26733 | Pay Transparency | In Pay Analytics, the Adjusted Pay Gap figures (Model, Recommended, Final, and After Raises) now recalculate in real time as users adjust recommended and final raise amounts, replacing the previous static display that required a manual refresh. This gives users an immediate view of how raise inputs affect pay gap outcomes directly within the analysis view, across both Planner and Workbench. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26774 | Compensation Management | In Planner > Compensation, the round list and round detail view now surface workflow stage progress to HRBPs, Compensation Managers, and Compensation Managers +1. The Workflow column in the round list displays the current stage name and a stage index badge (e.g., 'Collection 2/5') for in-progress rounds, and shows a completion date once all stages are finished. A collapsible stage progress bar has also been added to the top of the round detail view (Comp Review tab), showing each stage's name, status, and step count, with the ability to expand for a full chronological view of all stages and their completion dates. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26781 | Compensation Management | Administrators can now configure password-protected Excel exports in the Team Planner Add-ons tab during compensation round setup. When enabled, planners are prompted to enter a password each time they export compensation data to Excel, ensuring the downloaded file is protected. The toggle state is visible in read-only mode in the Round Management portal, and when the feature is disabled, the export modal continues to show only the page selection options with no password field. | – | ||
| AC-26843 | Compensation Management | In Workbench > Compensation Builder > Compensation Rounds, the eligibility rule editor was upgraded to use the advanced calculation engine — the same formula-based engine used for calculated columns. Global Compensation Admins and Compensation Admins can now write formula-based eligibility rules that reference a significantly wider set of field types, including calculated fields, custom input fields, and rule outputs such as Guidelines and Budget amounts, in addition to standard data model fields. In Team Planner, eligibility is re-evaluated automatically when any field referenced in an eligibility formula changes, keeping the Compensation Review grid up to date in real time. All previously configured eligibility rules have been converted to the new formula format with their original logic preserved. | – | ||
| AC-26926 | Compensation Management | The worker progression logic triggered on round publish and republish was extended to support workflow stages. On publish or republish, all workers are now reset to Step 1 of Stage 1, after which the system evaluates stage end dates first — advancing workers past any expired stages before applying step-level progression within the active stage — ensuring workers land on the correct step and stage based on current dates. | – | ||
| AC-26956 | Pay Transparency | In the Pay Information request creation wizard, the document generation form now adapts based on the active mapping configurations associated with a worker. When a single valid mapping exists, the template and data source are pre-selected automatically; when multiple mappings apply, only the compatible options are available in the dropdowns; and when no mappings exist, the full list of available options is shown. Additionally, 'Generate Document' is now the default selected option, and the Data Source dropdown requires a template selection before it becomes available, guiding users through the correct selection order. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27014 | Authorization | A new resolve endpoint was added to the Integration Hub to support users who require access across more than 10 Security Groups (access control groupings that define which workers a user can view or manage). The endpoint accepts a batch of users, each with a list of organizational scope criteria, and returns a deduplicated list of accessible worker IDs formatted for direct use with the access control list assignment service. | – | ||
| AC-27021 | Pay Transparency | A security issue was corrected in Planner > Pay Analysis where HRBPs could bypass publishing configuration restrictions by directly entering a Pay Analysis URL, gaining access to analysis data they were not permitted to view. The system now correctly enforces access controls, and HRBPs who attempt to access an analysis they are not authorized to view are redirected to the Pay Analysis list. | – | ||
| AC-27250 | Authorization | All Security Groups feature branches were reviewed and consolidated into a single unified integration branch across the Authorization, IAM, IntegrationHub, and Gateway services (the core platform services responsible for access control, identity management, data integration, and request routing). This work prepares the Security Groups functionality for QA and release. This change is internal and has no direct impact on users. | – | ||
| AC-27262 | Data Foundation | An incorrect error occurred in Data Management > Custom Entities when saving a custom entity with a name longer than 30 characters, resulting in a 400 error instead of enforcing the character limit at the point of entry. The character limit is now correctly applied, preventing submission of names that exceed the allowed length. | – | ||
| 150615 | AC-27273 | Performance Management | The Goals API endpoint was returning certain goal status values as raw integers instead of their corresponding string labels — for example, returning '10' instead of 'DELETED'. This occurred because the deleted status was missing from the enumeration used to convert numeric codes to readable values. The mapping has been corrected, and the API now returns the proper string representation for all goal statuses. | – | |
| AC-27276 | Data Foundation | Data Foundation now supports a configurable CSV separator to accommodate tenants working in European Excel locales, where files are commonly saved with a semicolon ( ; ) instead of a comma ( , ). A tenant-level default separator can be set via API, and manual CSV uploads can optionally override that setting on a per-upload basis. Non-interactive ingestion paths such as SFTP use the tenant-level default. Tenants without an explicit configuration will continue to use comma-based parsing by default for backward compatibility. | – | ||
| AC-27330 | Data Foundation | A confirmation message was added in Workbench to notify users when a custom entity has been successfully deleted. The message "The custom entity has been successfully deleted" now appears upon completing the deletion action. | – | ||
| 152453 | AC-27336 | Localization | Labels across multiple screens were not displaying correctly in any language other than English (US), with raw translation keys appearing instead of the expected text. This affected areas including Workbench > Data Management > Data Viewer and Workbench > Performance Management > Career Discussions. Missing standard label translations have been generated and applied, so all supported languages now display labels correctly. | – | |
| AC-27354 | Data Foundation | Three new API endpoints (programming interfaces used to access and manage data) were added to support the calculated field formula editor in the data modeler. A library endpoint now returns all data needed to build or edit a formula in a single request, while dedicated endpoints allow referenced entities (external data sources linked to a calculated field) to be added, updated, or deleted individually without resubmitting the entire field. A functions endpoint was also added to expose all supported formula functions, including array functions such as LOOKUP, for use in formula building. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27369 | Performance Management | In Passport > Goals, the Due date field on the Create Goal page is now automatically prepopulated with the Goal Plan's end date when one is defined. Users can still manually update the Due date after prepopulation. For recurring plans with no end date, the Due date field remains empty. | – | ||
| AC-27375 | Performance Management | In Passport > Goals, the Measurement criteria and Deliverable sections on the Create goal page now automatically expand when they are configured as mandatory in the selected Goal Type. Previously, these sections could appear collapsed even when required, causing users to potentially miss mandatory fields. Users can still manually collapse or expand the sections after the page loads. | – | ||
| AC-27439 | Data Foundation | In Upload Data, administrators can now configure a default CSV separator (comma or semicolon) at the tenant level, and users can override this selection during each manual CSV upload. When a tenant-level default is set, it is automatically preselected in the upload dialog; if no tenant default is configured, comma is used as the platform default. The selected separator is passed to the upload API when the file is submitted. | – | ||
| AC-27456 | Pay Transparency | On small screens, the Insights panel in Pay Analysis blocked page scrolling, preventing users from viewing the full data grid without closing the panel. This behavior was corrected in Pay Analysis results (Workbench > Pay Analysis) and the Pay Analysis page (Planner > Pay Analysis), so users can now scroll the full page to move the Insights section out of view and access the data grid. | – | ||
| AC-27457 | Pay Transparency | Additional variables are now available for use in document templates, including Document Generation Date, Document Generation DateTime, and Snapshot Effective Date. Users can incorporate these snapshot-related values into generated documents, enabling more precise and context-aware document output tied to the timing and configuration of each snapshot. | – | ||
| AC-27593 | Performance Management | End-to-end test validation was performed for the Talent Review template wizard, covering template creation, population configuration, 9-box axis setup, and questionnaire flows. All planned test cases were executed to confirm the feature behaves as expected. 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-27616 | Pay Transparency | Administrators can now configure which user roles — HR Business Partners and/or Communication Managers — are permitted to release and unrelease pay transparency documents within each communication round. In the communication round setup, a new permissions section allows these settings to be defined at the round level, and the release and unrelease actions in the Documents tab are automatically shown or hidden based on the logged-in user's role. All existing communication rounds default to allowing both roles to perform these actions, ensuring full backward compatibility. Round owners and Global Compensation Admins can update these permissions at any time, including after a round has been published. | – | ||
| AC-27628 | Pay Transparency | Three packages in the PT Service (an internal service component) — Microsoft.Extensions.Caching.Memory, System.Text.RegularExpressions, and System.Net.Http — were upgraded to versions that do not contain known security vulnerabilities. This change is internal and has no direct impact on users. | – | ||
| AC-27631 | Pay Transparency | Three packages in the ML Service (the machine learning component used for compensation-related predictions and recommendations) were upgraded to versions that resolve known security vulnerabilities. This change is internal and has no direct impact on users. | – | ||
| AC-27647 | Compensation Management | In Workbench > Round Management, the round configuration wizard now supports direct step navigation for rounds in Draft and Faulted statuses. For Draft rounds, Compensation Admins can click any previously visited step indicator to navigate directly to that step, without having to step backward sequentially using the Back button. For Faulted rounds, all step indicators are clickable, allowing free navigation both backward and forward through the configuration wizard. | – | ||
| AC-27674 | Compensation Management | Third-party dependencies flagged with high and critical severity were updated to address known security vulnerabilities. This change is internal and has no direct impact on users. | – | ||
| AC-27680 | Data Foundation | Code quality enforcement was strengthened in the DataModeler component (the module responsible for data modeling within the platform) by aligning its static analysis rules and build configuration with the established Foundation standard. This change is internal and has no direct impact on users. | – | ||
| AC-27709 | Pay Transparency | In Mapping Configuration, toast notifications displayed after bulk activate, deactivate, and delete actions now correctly use singular or plural text based on the number of items affected. Previously, messages did not account for pluralization, resulting in grammatically incorrect text. | – | ||
| AC-27718 | Pay Transparency | In Planner > Pay Analysis, the success toast displayed after submitting a Pay Analysis was closing immediately instead of remaining visible for the expected 5-second duration. This behavior was corrected, and the success toast now stays visible for the full 5 seconds before automatically dismissing. | – | ||
| AC-27730 | Performance Management | In Workbench > Performance Management > Talent Review Templates, Template Owners can now edit templates that are in Draft status. Owners can reopen a draft template and modify any previously entered configuration across all wizard steps — including template details, population, axis configuration, and questionnaire — with previously saved values pre-populated on return. Edits can be saved without publishing, and the template remains in Draft status until explicitly published. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27733 | Data Foundation | The snapshot details capability was expanded to capture and preserve the Worker Category configuration (the rules used to classify workers into categories) at the time a snapshot is generated. Users can now view the exact configuration state — including global, local, and custom Worker Category settings — that was applied when any given snapshot was produced, ensuring historical results can be understood and trusted even if configuration changes later. This supports audit, compliance, and reproducibility requirements by ensuring snapshot outputs remain fully explainable over time. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27772 | Compensation Management | In Planner, all workers in the tenant were incorrectly visible when a Bonus-only compensation round was published, rather than only the workers belonging to the Bonus plan population. This occurred because the system was incorrectly treating all workers as part of a Salary Review round, causing them to pass the visibility filter. The behavior has been corrected so that only workers included in the Bonus plan population are displayed in the Direct, Indirect, and HRBP views. | – | ||
| AC-27773 | Authorization | The dash character ( - ) was restored to the list of characters sanitized during import of subject attribute values, correcting a regression that left a gap in CSV injection protection (a security vulnerability where specially crafted values can trigger unintended formula evaluation in spreadsheet applications such as Excel). Only values where a dash appears as the leading character are affected; dashes appearing mid-string, such as in codes like ABC-123, are not sanitized. | – | ||
| AC-27786 | Data Foundation | Alias validation rules for reference entities on calculated fields were not properly enforced when adding or updating a reference entity through the dedicated endpoints. Aliases that started with a digit, contained special characters or spaces, or exceeded 128 characters were incorrectly accepted instead of being rejected. These validation rules are now correctly applied on both the Add and Update reference entity endpoints, returning the appropriate error when an invalid alias is submitted. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27787 | Data Foundation | An incorrect validation error was returned when configuring a referenced entity in Calculated Fields for effective-dated data types such as Absence, Compensation History, Individual Pay Range, and Employment. The system incorrectly identified these entities as non-effective-dated, causing the configuration request to be rejected before the correct validation rules could be applied. The classifier logic was corrected to properly recognize effective-dated entities, allowing valid configurations to be saved and the appropriate field-level validation rules to fire as expected. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27804 | Data Foundation | A fix was applied to the workspace deployment pipeline to resolve failures that occurred when deploying to a workspace without a previous publish manifest. The deployment process now correctly handles item creation and schema updates, including cases requiring a cache purge. This change is internal and has no direct impact on users. | – | ||
| AC-27806 | Data Foundation | Data Foundation Admins can now duplicate existing calculated fields in the formula management area. When duplicating a formula, admins are prompted to provide a new name, and the duplicated formula inherits the original's description, formula logic, and dependencies — enabling faster creation of similar formulas without starting from scratch. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27811 | Data Foundation | In Analytics Hub, searching for a report using a translated report name (for example, in Italian or French) failed to return results, even when a matching report existed. Only the English version of the report name produced results. The search functionality has been corrected to recognize translated report names, allowing users to find reports regardless of their active display language. | – | ||
| AC-27815 | Data Foundation | The Goal Alignment report name in Analytics was not translated when users switched their language to French, Turkish, Spanish, or German, causing the English name to be displayed regardless of the selected locale. This issue was corrected, and the report name now displays according to the appropriate translation for the user's language setting. | – | ||
| AC-27829 | Data Foundation | Users with access to Data Modeler can now add published calculated fields to new or existing Data Models via API. Up to 10 calculated fields per model can be selected from the Formula Library, and only fields in Published state are available for selection. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27878 | Performance Management | The tzdata package (a library used to provide time zone data across the platform) was updated to the latest version. This change is internal and has no direct impact on users. | – | ||
| AC-27935 | Pay Transparency | The Pay Transparency document settings reporting endpoint (used to retrieve configuration data for pay transparency documents) was expanded to return a more complete set of settings. The response now includes global anonymization thresholds and placeholder text, as well as a list of local rules organized by country, each with their own warning periods, overdue periods, and anonymization configuration. This gives reporting teams full visibility into both global and country-specific Pay Transparency document settings. | – | ||
| AC-27939 | Performance Management | In Workbench > Performance Management, the Population step of template creation wizards (Talent Review Templates, Performance Review Templates, and Career Development Plans) incorrectly allowed users to advance to the next step when only excluded workers were selected, without any valid population group or included users defined. Validation now correctly requires at least one population group or included user before proceeding, and a warning message is displayed if this condition is not met. | – | ||
| AC-27941 | Data Foundation | Several formula validation issues were corrected in the calculated fields engine (the component used to define and evaluate custom compensation formulas). The LOOKUP function now correctly resolves key-based lookups against reference datasets, and type compatibility between formula operations is properly enforced. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27942 | Data Foundation | The data modeler service (responsible for generating situation snapshots) was crashing when multiple snapshot creation requests were submitted simultaneously through the snapshot subscription endpoint. Concurrent requests were racing into a shared process in an unsafe way, causing the service to fail unpredictably under load. A fix was applied to ensure that concurrent snapshot creation requests are handled safely, preventing service crashes. | – | ||
| AC-27947 | Data Foundation | Two improvements were made to the calculated fields configuration experience for Model Admins. A new data retrieval capability was added for reference entities (reusable data definitions used in calculated fields), ensuring that the editing interface loads consistent and accurate information, including range settings. Additionally, the element library (the panel used to browse and select fields when building calculated fields) was corrected to display only the fields selected during reference entity setup, rather than all available fields. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-27968 | Data Foundation | The formula editor was updated to support array functions when working with reference entities. Compensation admins can now use array functions with reference entity aliases and receive accurate field suggestions, enabling more advanced formula authoring. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-28013 | Data Foundation | Improvements were made to the data foundation and data modeler automated test execution to reduce parallel token generation requests, which were causing authentication service timeouts and connection pool exhaustion. This change is internal and has no direct impact on users. | – | ||
| AC-28101 | Data Foundation | A Formula Library was introduced in Data Foundation, enabling Data Foundation Admins to create, manage, and maintain Calculated Fields — reusable formula definitions that can support advanced business logic such as compensation calculations and eligibility rules. Admins can define formula expressions, manage metadata (name, return type, and description), and explicitly configure external data references (such as Custom Entities) that can be used within formula expressions. This provides the foundation for defining and persisting reusable business logic that can later be validated and executed across the platform. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-28133 | Compensation Management | The Bqm.AuthZ.Common package (an internal library used to manage authorization and permissions) was upgraded to version 8.14.2 to address a security vulnerability and remove a dependency on an outdated caching component. This change is internal and has no direct impact on users. | – | ||
| 153241 | AC-28168 | Data Foundation | Several Job Architecture fields — including Job Evaluation Points, Pay Scale External ID, Job Description, and Job Alternative ID — were not displayed as available options in Workbench > Data Modeler or within Compensation Round field selection, even when those fields were present in Data Foundation. This issue was corrected, and administrators can now select all available Job Architecture fields from Data Foundation when configuring data models and compensation rounds. | – | |
| AC-28169 | Data Foundation | An adjustment was made to the worker category service endpoint used by the Snapshot drawer to ensure correct data retrieval. This change is internal and has no direct impact on users. | – | ||
| AC-28173 | Compensation Management | The workflow transition snapshot (a record saved each time a worker step is approved or rejected in Planner) was extended to include the current stage ID and stage name directly within the snapshot record. This makes snapshots self-describing, removing the need to parse additional data to determine the workflow stage at the time of the action. Existing snapshot records were updated with the correct stage information through a database update. | – | ||
| AC-28193 | Authorization | Structured audit logging was added to the authentication service to capture every authentication event, including interactive logins, external (SSO) callbacks, logouts, and token issuances. Each audit entry is enriched with fields such as user identity, tenant, client IP address, login method, and outcome, and is written to the centralized audit log store (AppAudit_CL). Failures are recorded at a distinct severity level to support alerting and incident investigation in Log Analytics. This change is internal and has no direct impact on users. | – | ||
| AC-28198 | Authorization | The Microsoft.Extensions.Caching.Memory library (used for in-memory data caching) was updated to version 8.0.1 in the Bqm.AuthZ.Common shared package (a shared authorization component used across multiple services) to address a known security vulnerability. The updated package was republished so that all dependent services automatically receive the fix. This change is internal and has no direct impact on users. | – | ||
| AC-28208 | Pay Transparency | In Planner > Pay Information, the audit trail's 'updated request' entries incorrectly displayed a misaligned icon and shrunken icon when the associated text was long. The icon and text are now correctly aligned regardless of text length. | – | ||
| AC-28222 | Data Foundation | In Data Modeler, users can now add published calculated fields from the Formula Library to new or existing Data Models. Up to 10 calculated fields can be added per model, and each field displays its name, description, result type, and formula to support informed selection. When a snapshot is generated using a Data Model that includes calculated fields, those fields are automatically executed and their results are stored as part of the snapshot data. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-28257 | Pay Transparency | In Workbench > Communication, administrators can now configure which roles are permitted to release and unrelease documents within communication rounds that have no workflow. Owners of a communication round and Global Compensation Admins can update these permissions at any time, even after publishing. By default, both HRBPs and Communication Managers have release and unrelease access enabled, ensuring existing communication rounds are unaffected. When a role does not have the required permission, the corresponding release or unrelease options are hidden from the documents tab context menu and bulk actions. | – | ||
| AC-28289 | Pay Transparency | In Communication Round > Workflow Step, the Permissions card is now always visible when viewing a compensation round in read-only mode. Previously, users who were not the creator of a round would not see the Permissions card unless the Enable workflow steps option was enabled. Permission settings are now displayed regardless of the workflow steps configuration. | – | ||
| AC-28303 | Pay Transparency | In the pay information request edit form, templates failed to appear in the dropdown when multiple mappings shared the same template and data source. The auto-selection logic was not triggered under these conditions, leaving the dropdown empty. This has been corrected and templates now populate as expected when multiple mappings are available. | – | ||
| AC-28304 | Authorization | A data initialization step was added to the IAM service (the component responsible for identity and access management) deployment process to pre-populate a hash field used for user synchronization validation. This change increases initial deployment time but reduces performance overhead during runtime by minimizing unnecessary user data updates at startup. This change is internal and has no direct impact on users. | – | ||
| AC-28319 | Compensation Management | The Notifications widget on the Home page stretched the entire page layout when a user had many notifications, as the widget had no maximum height limit. The widget now has a fixed maximum height and scrolls internally, keeping the Home page layout stable regardless of how many notifications are present. | – | ||
| AC-28320 | Pay Transparency | An issue was corrected where the 'Include communication manager(s) in CC' option was not displayed when editing the email template for the Document Released notification. The missing configuration data was added so that the checkbox now appears correctly, allowing administrators to control whether communication managers are copied on Document Released notifications. | – | ||
| AC-28329 | Data Foundation | A high-severity vulnerability in the Snappier library (a compression component used internally by the MongoDB database driver) was resolved in the Localization API by upgrading the affected package to a patched version. Build pipeline configuration was also updated so that newly disclosed advisories on transitive dependencies surface as warnings in build logs without halting the build process. This change is internal and has no direct impact on users. | – | ||
| 152754 | AC-28427 | Data Foundation | Population count queries (used to calculate the number of workers matching a population definition) were timing out for customers with large worker and employment data volumes when the population criteria included filters on employment fields such as Legal Entity. The query engine was applying these filters only after processing and joining all underlying data, rather than earlier in the process where they could reduce the data set before joining. Filters are now also applied earlier in the query, allowing the database to prune irrelevant employment records before performing joins, reducing query execution time from over 10 minutes to under 5 seconds for affected configurations. | – | |
| AC-28437 | Pay Transparency | Communication Round options in Pay Information requests were not being restricted based on the configured mappings, causing all available rounds to appear regardless of the applicable population settings. This was corrected so that the Communication Round dropdown now displays only the rounds defined in the relevant Pay Information request mapping. If only one value is available, it is automatically pre-selected; if no mapping exists, all Communication Rounds continue to be displayed. | – | ||
| AC-28476 | Compensation Management | The Snappier library (a compression package used within the compensation service) was updated to version 1.3.1 to address a known security vulnerability present in the previous version. This change is internal and has no direct impact on users. | – | ||
| 153437 | AC-28562 | Data Foundation | Pay information requests created via API were not appearing in the Pay Transparency > RTI Overview report. Only requests created directly within the application were reflected, causing the report to display an incomplete count. This issue was corrected, and all pay information requests — regardless of how they were created — are now properly displayed in the report. | – | |
| AC-28568 | Pay Transparency | In Workbench > Pay Analysis and Planner > Pay Analysis, adjusted pay gap values and their associated lower-gender labels were not updating correctly when raises were edited inline. The displayed gap could move in the wrong direction — for example, increasing instead of decreasing when a raise was applied to the lower-paid gender. This was corrected so that gap values and gender labels now reflect the expected direction of change consistently, including edge cases where raises push the gap past parity and the lower-paid gender flips. | – | ||
| AC-28607 | Authorization | The authorization layer (the component responsible for determining which data users are permitted to access) was updated to correctly handle users assigned to more than 10 Security Groups during data flow authorization. Previously, users in this configuration could receive an incomplete or incorrect set of authorized data; the fix ensures they receive the same results as users assigned to 10 or fewer Security Groups. This change is internal and has no direct impact on users. | – | ||
| AC-28613 | Authorization | The data-flow authorization service was extended to support an optional contextual role parameter, allowing authorization filters to be scoped to the specific role a user is acting in for a given request. Previously, the service always combined conditions from all security groups assigned to a user regardless of role. This change is internal and has no direct impact on users. | – | ||
| 153756 | AC-28670 | Data Foundation | Uploading a large Worker file (up to approximately 143,000 records) caused the ingestion process to time out, leaving subsequent ingestion jobs stuck in a queued state and preventing other files from being processed. This was corrected so that large Worker file ingestions of up to 150,000 records now complete successfully without blocking the ingestion pipeline, allowing other files to be processed normally afterward. | – | |
| AC-28674 | Authorization | The HR Data Sync (user synchronization) service was optimized to significantly reduce processing time and memory usage when synchronizing large volumes of users. A bug in the rollback logic was also corrected to ensure that only data from a failed batch is removed on sync failure, preventing accidental deletion of valid user data, and the manager hierarchy change detection was fixed to correctly handle all assignment scenarios. This change is internal and has no direct impact on users. | – | ||
| AC-28732 | Data Foundation | The Data Foundation ingestion orchestration (the process that handles worker, employment, and organization data imports) was updated to skip the legacy IAM synchronization step when the new shared snapshot sync mechanism is active for a tenant. When the legacy step is skipped, a clear status entry is recorded in the ingestion log so that support teams can confirm the step was intentionally bypassed. This change is internal and has no direct impact on users. | – | ||
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.
Innovation
beqom uses AI to rethink what compensation software can be. Our labs team is actively building a new generation of intelligent features for beqom PaySuite: capabilities designed not to layer AI on top of existing workflows, but to make intelligence foundational to how compensation and performance get done.
Everything in this section is currently in limited preview release or in the labs presently. General availability will be communicated through the usual channels.
| Type | Issue key | Description |
|---|---|---|
| AC-27501 | Streaming support was implemented for the beqom AI-powered assistant. Responses from the AI are now delivered progressively as they are generated, rather than waiting for the full response to be completed before displaying, resulting in a faster and more responsive experience. | |
| AC-28131 | An issue was corrected in the beqom AI assistant where authentication failed when a company's name did not match its URL prefix. The JWT authenticator (the component responsible for validating login tokens) was incorrectly checking the token's issuer URL against the company claim, causing sign-in attempts to be rejected. Authentication now succeeds regardless of whether the company name matches the URL prefix. | |
| AC-28242 | The beqom AI assistant was updated to support the MCP protocol (Model Context Protocol, a standard that allows AI agents to communicate with external tools and services). This enables it to connect to external tool sources through configuration, expanding its ability to perform actions and retrieve information during conversations. |