beqom Pay Suite 22.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 22.1 release of the beqom Pay Suite application and in the subsequent patches.
22.1
Deployment to staging environments: March 25th, 2026
Deployment to production environments: March 31st, 2026
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| AC-17035 | Performance Management | In Workbench > Performance Management > Career Development Plans, admins can now view career development plan details directly from the results table. A 'View plan' button is displayed under each worker's name and is always enabled regardless of the worker's status or Career development stage. When viewing a plan for an inactive worker, a confirmation pop-up is shown before proceeding. The career development plan opens in read-only mode from the manager perspective, meaning admins cannot edit any inputs; only published or submitted data is visible, draft manager inputs and the manager–employee chat are hidden, and linked documents uploaded by the manager are accessible for download once the manager has submitted their inputs. When exiting the Career development view, admins are returned to the HR Portal results page with their previously applied filters preserved. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-18169 | Authorization | A vulnerability in a library used in the application was corrected, which improves the overall quality of the code. This change is internal and has no direct impact on users. | ||
| AC-21523 | Authorization | The architecture of an internal code repository was documented. This change is internal and has no direct impact on users. | ||
| AC-22048 | Pay Transparency | In Pay Analysis, the Worker, Line Manager, and Compensation Manager columns in the results grid now display each worker's profile picture alongside their name. If no profile picture is available, a circle with the worker's initials is shown instead. The Worker column also displays the worker's job title beneath their name. The Line Manager and Compensation Manager are now resolved from the Live Snapshot hierarchy, and column tooltips have been updated to reflect this. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-22798 | Compensation Management | In Workbench > Round Configuration, Global Compensation Admins and Compensation Admins are now protected from making breaking changes that would create unresolved dependencies across the compensation round setup. When attempting to remove a compensation element, disable a data point, delete a calculated or custom field, remove a conditional formatting rule, or delete or disable an eligibility, budget, guidelines, or guaranteed amount rule, the system now validates whether any of these items are referenced elsewhere — such as in calculated field formulas, conditional formatting rules, bonus calculation equations, or payroll data drops. If dependencies are detected, the action is blocked and a 'Dependency conflict' pop-up is displayed, listing each affected target item, the dependent item that relies on it, and the specific location of the usage. Admins can download a CSV log of the conflict details for further review. If no dependencies are found, a confirmation dialog is presented before the deletion proceeds. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23046 | Pay Transparency | When exporting a snapshot to Pay Analytics, the 'Use worker category from snapshot as main group' option in the dataset mapping configuration now functions as intended. Previously, this checkbox had no effect and the selected Data Model field was always used as the main group. Now, when the option is enabled, the snapshot's Category field is used as the main group. If the snapshot does not contain worker category data, users are shown a warning and presented with two options: proceed with the export without a main group defined, or cancel the action to create a new snapshot or update the configuration. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23206 | Authorization | In Workbench > Performance Management > Career Development Plans, plan owners can now manually include individual workers in a Career Development Plan in addition to any population-based assignments. A new 'Include Workers' option is available via the 'Manage Workers' button in Draft mode, and a dedicated 'Include Workers' button is available in Published mode. Clicking either option opens a searchable, paginated modal displaying each worker's name, job title, worker ID, organization, and country, allowing plan owners to select and add specific workers directly. Individual inclusions are additive and do not affect or modify global populations. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23207 | Authorization | Plan owners can now explicitly exclude individual workers from a Career Development Plan in Workbench > Performance Management > Career Development Plans. Using the new 'Exclude Workers' option in the Manage Workers area, plan owners can search for and select specific workers to remove from the plan's effective population while the plan is in Draft mode. Individual exclusions take the highest precedence in population resolution — overriding both population-based assignments and individual inclusions — ensuring plan owners have precise control over the plan's final scope. Exclusions are scoped to the plan only and do not affect global population definitions. Once a plan is published, no new exclusions can be added. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23212 | Authorization | A manual overrides view was added to career development plans in Workbench > Performance Management > Career Development Plans. Plan owners can now see a consolidated, searchable list of all workers who have been individually included or excluded from a plan, with each record displaying the worker's name, job title, worker ID, organization, country, and a color-coded status indicator distinguishing inclusions from exclusions. In Draft mode, plan owners can remove individual overrides using the kebab menu; in Published mode, overrides added before the most recent publish are locked and cannot be removed, while overrides added after publish remain editable. This view covers only manual overrides and does not include workers added through population-based assignments. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23219 | Authorization | Attribute-based access control (ABAC) — a system that restricts which users are visible or accessible based on predefined rules and ownership context — is now consistently enforced when assigning workers to the scope of a career development plan in Workbench > Performance Management > Career Development Plans. When a plan has multiple owners, the primary owner's ABAC rules serve as the single source of authority for all assignment decisions. This applies to population-based assignments as well as manual individual inclusions and exclusions, ensuring that only workers permitted under the primary owner's access rules can be added to or removed from the plan scope. This feature governs who can be assigned to a plan and does not affect outcome visibility or reporting access. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23277 | Authorization | Role-based filtering was added to career development plans in Workbench > Performance Management > Career Development Plans. Plan owners can now filter the plan scope by worker and manager roles, with options to include all roles, workers only (users with no direct reports), or managers only (users with at least one direct report). The filter applies consistently to both population-based and manually included participants and is evaluated using the current live line hierarchy at the time the population is resolved. The selected filter is persisted when the plan is saved or published, and becomes read-only once the plan is published. Existing plans created before this feature was introduced will default to All roles, preserving their current behavior. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23303 | Performance Management | In HR Portal > Manage CD Plans, Local and Global owners can now reassign the responsible manager for an active career development plan directly from the plan list. A three-dot action menu (⋮) has been added to each career development plan row, containing a Reassign manager option. Clicking this option opens a pop-up displaying the current manager (read-only) and a search field to select a new manager, with search results filtered according to the admin's access rules (ABAC). Once reassigned, the new manager gains access to the career development plan in Planner > Passport > Assigned career development plans and receives an email notification, while the previous manager loses access. The reassignment does not affect the stage or workflow of the career development plan and can be performed multiple times. The worker also sees a label in their career development plan list indicating the plan was reassigned to another manager. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23492 | Data Foundation | The end-to-end workflows for exporting bundles/manifests for the data bridge was documented for future implementations. This change is internal and has no direct impact on users. | ||
| AC-23529 | Pay Transparency | In Workbench > Pay Analysis, users can now export Pay Analysis grid results as a CSV file. The exported data respects worker access restrictions (ABAC), meaning the CSV will only contain the workers the exporting user is permitted to view. Column visibility settings configured in the Workbench column configuration are also applied, so only the columns defined in that configuration are included in the export. The CSV is packaged inside a password-protected ZIP file, with the user defining the password at the time of export. Passwords must meet the application's standard requirements: between 5 and 15 characters, including at least one uppercase letter, one lowercase letter, and one number. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23646 | A new third-party JWT (JSON Web Token — a secure way to transmit identity information between systems) authentication scheme was added to the Accelerate Gateway API (the entry point that manages access to beqom platform services). This scheme allows users authenticated by PayAnalytics to access AI features without requiring a separate account in the beqom identity system. Incoming tokens from PayAnalytics are validated using a JWKS endpoint (a published set of cryptographic keys used to verify token authenticity), with checks covering token signature, issuer, audience, and expiration. Authenticated third-party requests bypass internal user validation while still populating full user context — including tenant, user identity, and source application — ensuring proper audit logging for all cross-product interactions. This feature is currently behind a feature flag and is not yet available to all customers. | |||
| AC-23753 | Data Foundation | A new Global Worker Category configuration capability was introduced, allowing GlobalCompensationAdmin, DataFoundationAdmin, and Support role users to create or edit a centralized worker category configuration. Administrators can select worker fields (such as Gender or Ethnicity) from the General schema, define a separator character, set a blank value strategy (skip blanks, replace with a default label, or replace with custom values per field), and reorder fields using drag-and-drop. A read-only preview section reflects the configured field order, separator, and blank handling logic before saving. The configuration is stored centrally and applies only to future snapshots; deletion is not supported in this release. DataModelerAdmin users have read-only access to this page. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23756 | Data Foundation | Administrators can now create, edit, and delete Local Worker Categories as reusable configuration objects within the snapshot configuration workflow. These categories allow administrators to define targeted exceptions to the global worker category behavior for specific worker populations, using a combination of worker fields, a separator, and one or more assigned populations. Once created, Local Worker Categories are stored centrally and can be reused across multiple snapshots. Editing a category applies changes only to future snapshot generations and does not affect previously generated snapshots; the platform notifies administrators of this behavior at the time of editing. A category can only be deleted if it is not currently referenced by active snapshot configurations, and deletion does not alter any previously generated snapshot results. The platform enforces governance rules, including unique category names, mandatory worker field and population selection, and population exclusivity — each population may belong to only one Local Worker Category. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23868 | Performance Management | Admins can now apply filters within the HR Portal when managing Career Development Plans in Workbench > Performance Management > Career Development Plans. Six filters are available across both the Move Stages and Manage Plans tabs: Career Development Stage, Organizational Unit, Manager, Specific Worker, Cost Center, and Country. Filters operate using AND logic, meaning results must satisfy all selected criteria simultaneously. Once applied, the result count is displayed in the table, and active filters are shown at the bottom of the filter panel for visibility. Filter drop-downs pre-populate with relevant options when opened and reload dynamically as the search phrase is changed. On the Move Stages tab, the count shown in the filter panel reflects only the selected stage, while the table result count accounts for all applied filters combined. Filters are reset automatically when switching between tabs, and individual filters can be removed using the X icon or cleared all at once via the Clear Filters link. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23885 | Pay Transparency | In the Pay Equity Analysis workbench grid, the Number of Raises and Total Cost of Raises widgets now update in real time as users modify recommended raise values. The Number of Raises widget displays both the model-suggested raises and the recommended raises entered in the workbench. The Total Cost of Raises widget displays costs in the currency defined in the Dataset Mapping Configuration, using exchange rate snapshots stored at the time of the dataset upload to ensure consistent conversions. Editable raise columns display values in the user's local currency, and all monetary fields show the three-letter currency code alongside the value. If no main currency is configured in the Dataset Mapping settings or currency conversion is not enabled, the system falls back to the global system currency for conversions. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23946 | Compensation Management | Under Planner > Compensation Management, a new Proposal Management execution capability was introduced that pre-populates the 'New value' field for compensation elements when a round with Proposal Management enabled is published. Compensation Managers and HRBPs will see proposal values automatically calculated at publish time — either drawn from an existing Data Model field or evaluated from a configured formula — based on each worker's data. A Proposal Management icon next to the field header allows users to open a read-only view of the configuration, and a pencil icon indicates when a value has been overridden by a Compensation Manager or HRBP. When clicking into an overridden cell, users can view a tooltip showing the original default value and use a 'Restore value' button to revert to it. Prepopulated values are fully editable; if a value is saved without modification, the audit trail records the action as attributed to 'System', while any user-modified value is attributed to the actual Compensation Manager or HRBP who made the change. Proposal values are calculated once at publish and remain stable throughout the round lifecycle, with recalculation occurring only when the round is republished, at which point current source field or formula data is used to refresh values. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23954 | Pay Transparency | In Pay Analysis, the Pay Analysis grid now applies attribute-based access control (ABAC) filtering to ensure that users with the PayAnalysisAdmin role only see worker data they are authorized to access based on organizational permission policies. The grid, along with insight widgets showing the total number of raises and total cost of raises, will reflect only the workers within the user's authorized scope. The Adjusted Pay Gap by Demographics insight widget continues to display totals across the full analysis, unfiltered by worker. Users who previously had visibility into all workers may now see a reduced set depending on their authorization level, and search and filter operations within the grid will apply only to the authorized worker subset. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-23992 | Authorization | Azure Active Directory (Azure AD) authentication has been enabled for the Accelerate Back-Office application, securing access to both the web user interface and API endpoints. Administrators and users must now authenticate via their organization's Azure AD account before accessing the application. Authentication is bypassed for health check endpoints to ensure uninterrupted system monitoring. Environment-specific configuration is supported for development, staging, and production deployments. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24148 | Compensation Management | A background job was introduced to automatically enforce time-based progression in advanced compensation workflows. When a workflow step's end date has passed, the job advances all workers on that step through any consecutive expired steps in a single execution, landing them on the first step whose end date has not yet passed. Workers who reach the final step after its end date has expired are automatically marked as Completed. The job runs daily at 00:05 UTC by default and can be enabled, disabled, or rescheduled via compensation service configuration. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| 147867148253 | AC-24210 | Authorization | An issue was corrected where users who had been successfully ingested were unable to access the application due to incomplete account creation across all required schemas. Although the initial stage of user creation in the identity management schema completed successfully, the process failed silently for subsequent schemas, leaving users without the necessary records to function in the system. The root cause was that the user synchronization logic skipped update events for any schema where the user record was missing, instead of triggering the appropriate creation flow. This has been corrected so that when an update event is received and a user is found to be missing from any schema, the system now automatically initiates the full creation process for that schema, ensuring data consistency across all areas and restoring normal login and application access. This feature is currently behind a feature flag and is not yet available to all customers. | |
| AC-24235 | Compensation Management | In Workbench > Round Management, administrators can now modify Advanced Workflow configuration within a Pending Draft for compensation rounds that are in a Ready or In Progress state. Supported changes include editing step names, modifying actors and actor actions, updating field permissions, and adding or deleting steps and configurations. When editing the workflow configuration step, a persistent warning message is displayed to inform administrators that workflow changes may reset all workers to the first step. When the parent round is In Progress and the administrator proceeds past the workflow step, a confirmation modal is shown at publish time stating that all workers will be reset to Step 1; the administrator can choose to preserve existing worker proposals ('Yes, keep entries') or delete them ('No, delete them'). Workers whose current step was deleted as part of the workflow changes are automatically moved to Step 1 upon publication. This feature applies exclusively to rounds using Advanced Workflow and is not available for legacy workflow types. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24238 | Compensation Management | Existing compensation rounds configured with legacy workflow types (Time-driven and Collaborative) are now automatically migrated to the Advanced Workflow system, enabling all rounds to use the unified workflow configuration interface. For Time-driven workflows, each active step (those previously enabled via toggle) is converted to a corresponding Advanced Workflow step, preserving the step name, end date, actor assignment, and time-based progression. Steps that were previously set to read-only are not migrated as workflow steps; instead, their actors are granted read-only access through the Round Access Actors configuration. For Collaborative workflows, a single Advanced Workflow step named 'Collaborative Workflow' is created, with per-actor configurations reflecting the original permissions: actors with Read and Write access receive Write field permissions, actors with Read Only access receive Read field permissions, and actors with No Access are excluded from the workflow step entirely and removed from round access. In both cases, the migration preserves the original access control behavior while making rounds fully manageable through the Advanced Workflow configuration UI. Old workflow data is retained in the database to allow rollback if needed, and the migration script can be run multiple times without adverse effects. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24287 | Compensation Management | In Workbench > Pay Management > Compensation Rounds, configuration cards within the workflow step configuration drawer now support collapse and expand functionality. Compensation Admins and Global Compensation Admins can collapse individual configuration cards to reduce visual clutter when multiple configurations are present, with only the card header remaining visible in the collapsed state. All cards open in the expanded state by default each time the drawer is opened. Additionally, if a collapsed card contains a validation error when the Apply button is clicked, the card automatically expands to surface the inline error. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24290 | Compensation Management | A new 'Actors and round access' configuration step was added to the compensation round creation and edit wizard in Planner > Compensation. Global Compensation Admins and Compensation Admins can now control which hierarchy-based actor types — HRBP, Comp manager, and Comp manager +1 — have access to a compensation round in Team Planner. All three actors are preselected by default, ensuring backward compatibility with existing rounds and immediate visibility for new ones. Admins can customize access by selecting or unselecting actors via checkboxes; if all actors are unselected, a warning message is displayed to indicate that the round will not be visible in Team Planner. The configuration is reflected in the round overview tile, is carried over when duplicating a round, and can be updated for published or in-progress rounds by creating a Pending Draft and republishing. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24296 | Compensation Management | Under Team Planner > Compensation Review, advanced workflow execution is now supported for active compensation rounds. Compensation Managers, Compensation Managers +1, and HRBPs can view each worker's current workflow step displayed as a pill badge in a dedicated Workflow Step column, and take actions (Submit, Approve, Reject, or Complete) on individual worker proposals directly from the grid. Action controls are shown per worker row based on the actor's configured permissions for the current step — including Approve-only, Reject-only, both, or neither — and are never displayed to users who lack a matching permission for that step. Confirming an action transitions the worker forward or backward through the configured workflow steps, with distinct confirmation modals and success banners for each action type. Rejected workers are visually indicated with a red highlight on the first two columns and an informational tooltip whose message varies depending on whether the viewing actor has available action controls. Field editability per worker is determined first by eligibility rules, then by the field-level permissions configured for the actor at the current step, defaulting to read-only when no permission is defined. Workers at different workflow steps are displayed simultaneously in the same grid, each reflecting their own current step and available actions independently. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24313 | Pay Transparency | In Workbench > Data Management > Snapshot Manager, the Create Pay Analysis Dataset modal now prepopulates the dataset name field with a generated name based on the format {SnapshotName}-{CreationDate}, replacing the previous placeholder text. The name field is now marked as required, and users must provide a value before the dataset can be created — an error message is displayed if the field is left empty. If the generated name exceeds 100 characters, the snapshot name portion is automatically truncated to fit within the limit. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| 150340 | AC-24365 | Data Foundation | An issue was corrected in Workbench > Data Viewer where applying a filter on a custom field returned a 400 error and no data was retrieved. The error occurred because the query builder was generating incorrect SQL that referenced the custom field as a direct column rather than using the correct path within the JSONB storage structure (a PostgreSQL data format used to store flexible, schema-defined fields). The query builder has been updated to correctly resolve the full field path for custom fields, and filtering on these fields now returns results as expected. This feature is currently behind a feature flag and is not yet available to all customers. | |
| AC-24374 | Compensation Management | In Team Planner, the backend queries that determine which compensation rounds are visible to HRBPs, Compensation managers, and Compensation managers +1 have been updated to enforce round-level actor configuration. Previously, the actor flags stored per round (controlling which roles should have access) were not yet applied to visibility logic. Rounds will now be filtered out immediately for any role not enabled at the round level, without proceeding to further access checks. This ensures that round visibility in Team Planner accurately reflects the actor configuration set by administrators. Existing rounds, which were migrated with all actor flags enabled, are unaffected by this change. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24421 | Data Foundation | Tests were added to the live snapshot retrieval function for specific workers. This change is internal and has no direct impact on users. | ||
| AC-24438 | Compensation Management | In Planner > Compensation, the 'Workflow Type' and 'Workflow Status' columns have been removed from the Compensation Rounds list table. Additionally, the 'Current workflow step' label and workflow step name have been removed from the top bar of the Team Planner for time-driven rounds. These elements are no longer displayed to any user, including Global Compensation Admins and Compensation Admins. All other columns and top bar elements remain unaffected. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24448 | Pay Transparency | A Predicted Salary column was added to the Pay Analysis Grid. This column displays the salary value predicted by the Pay Analysis model for each worker, representing the model's estimate prior to any pay gap adjustments — distinct from the Suggested Raise value. Users can view, hide, and reorder this column within the grid. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24528 | Compensation Management | The code repository was prepared for advanced workflow work. This change is internal and has no direct impact on users. | ||
| AC-24690 | Data Foundation | A maximum field limit has been introduced for custom entities. Administrators can now add no more than 20 fields per custom entity, protecting against configurations that could negatively impact system performance or maintainability. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24713 | Pay Transparency | An issue was corrected where triggering the 'Sync Analysis' action in Performance Administration would reset the statuses of previously synced PA results back to 'New' and overwrite any updated raises. This occurred because the sync process was deleting and fully recreating all analyses, causing previously recorded statuses and raise values to be lost. The process has been corrected to update existing analyses in place, ensuring that current statuses, raises, and deletion states are preserved when a sync is performed. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24740 | Data Foundation | In Custom Entity Management, administrators can now create and manage Custom Entities through a guided front-end flow. Admins can define entity-level properties — including name, description, and effective dating options (None, Effective Date, or Effective Range) — and save the entity in Draft state before publishing. Within the Draft, admins can add up to 20 fields, each configurable with a name, type (String, Integer, Boolean, Enum, Entity Reference, Number, or Date), and attributes such as Required, Business Key, and PII. Conditional UI behavior is enforced: selecting Enum or Entity Reference field types displays the appropriate reference selectors, and the PII toggle is only enabled when a field references the Worker entity. Draft entities are exclusively visible within Custom Entity Management and do not appear in data viewer or upload screens. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24799 | Data Foundation | Unused datasets were removed from the PowerBI semantic model. This change is internal and has no direct impact on users. | ||
| AC-24844 | Compensation Management | In Workbench > Pay Management > Compensation Rounds > Round Management Portal, Compensation Admins and Global Compensation Admins can now view the Advanced Workflow configuration in read-only mode from the Configuration Overview. Clicking the 'Workflow' tile opens a side panel displaying the full workflow diagram with all configured steps in a vertical layout, including step numbers, names, and assigned actor pills. Each step card is clickable and opens a detailed read-only panel showing the step name, actors, step actions, field permissions, and time-based progression settings. For rounds in Ready or In Progress status, a 'Create pending draft' or 'Edit pending draft' button is available directly from the workflow side panel, allowing admins to initiate or continue workflow edits without leaving the overview. Additionally, the 'Workflow type' card has been removed from the Overview header for all rounds regardless of workflow type or status, as this information is now accessible through the Workflow configuration tile. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24881 | Data Foundation | The localization API was migrated from .NET8 to .NET10. This change is internal and has no direct impact on users. | ||
| AC-24948 | Data Foundation | Changes were made to the synchronization logs of PowerBI reports. This change is internal and has no direct impact on users. | ||
| AC-24962 | Compensation Management | In Workbench > Compensation, input validation in the compensation round configuration wizard now runs when Global Compensation Admins and Compensation Admins click the Back or Save & Exit buttons, in addition to the existing validation on the Next button. Previously, validations were only triggered when moving forward through the wizard, meaning errors could go undetected when navigating backwards or exiting early. This ensures that invalid configurations are caught at any point during the round setup process. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24969 | Compensation Management | In Workbench > Compensation, the Formula builder help panel accessible via the 'Learn more' link in the formula editor drawer has been extended with a new overview section. Compensation admins can now view four introductory items at the top of the panel — 'Build dynamic formulas', 'Choose your formula type', 'Calculation workspace', and 'Nest your calculations' — each with an icon, title, and descriptive text to help less experienced users understand the formula builder before they begin writing formulas. The existing functions and operators content remains unchanged below the new overview. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24973 | Compensation Management | In Planner > Compensation, the Audit Trail now captures actions performed by the proposal management feature, giving Compensation managers and HRBPs full visibility into how default proposal values were applied. Three new action types have been introduced: 'Set default value' records one row per worker per field when proposal management sets a default value on publish or republish; 'Republished (proposals kept)' records one row per worker per field when an existing proposal value is retained during republish; and 'Republished (proposals removed)' records a single summary row when a Compensation admin explicitly removes all proposal values during republish. For all three action types, the editor is displayed as 'System Administration' with a gear icon. Calculated fields such as increase amount and increase percentage are not tracked as separate rows — only the primary input field is recorded. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-24995 | Data Foundation | Property panels (drawers) across Workbench > Data Foundation were updated to ensure consistent visual formatting. Inconsistencies in font size, spacing, special characters, colon usage, and row sizing have been corrected across the Custom Fields, Data Modeler, Snapshot Manager, Populations, Data Upload, and Custom Labeling areas. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25053 | Data Foundation | An issue was corrected in the Documents module where unlinking a user from a document caused the Worker Id, Worker Name, and OrgLevel 1 fields to appear empty on the Communication Status, Communication Details, and Communication Audit Trail pages of the Pay Communication report. This occurred because the user identifier was being set to an empty placeholder value rather than resolved against the user record. The Pay Communication data model was updated to handle this scenario correctly, ensuring the affected fields are now populated as expected. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25057 | Data Foundation | An issue was corrected in the Pay Transparency data model where, after a user was unlinked from a document in the Documents module, the Is Read flag incorrectly displayed 'No' for all workers regardless of whether they had actually read the document. This occurred because the user identifier field was no longer populated with a valid user ID after unlinking, causing certain data joins in the report to produce incorrect results. The Is Read flag now correctly reflects each worker's read status, and the Read Date is also displayed as expected. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25111 | Performance Management | An issue was corrected in Workbench > Performance Management > Performance Reviews where Local Owners who modified the Population step and then clicked 'Next' before clicking 'Republish' would not have their changes saved or properly applied. The republish request was triggered but the updated population values were not persisted. This occurred because republishing was only supported when initiated directly from the Population step. The fix now allows Local Owners to successfully republish a review template from any stage, ensuring that population changes are correctly saved and the plan is fully republished. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25115 | Data Foundation | A new Global Worker Category registry was introduced in Workbench > Data Management, providing a central location where administrators can view and manage the global worker category configuration. The registry displays the selected worker fields (such as Gender or Ethnicity), the configured field separator, and metadata including the creation date and creator. If no configuration exists, an empty state is shown with a prompt to create one. GlobalCompensationAdmin, DataFoundationAdmin, and Support roles can access this page, with DataFoundationAdmin limited to read-only access; deletion of the global configuration is not supported in this release. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25132 | Pay Transparency | An issue was corrected in Pay Analysis Results where attempting to save changes in the Column configuration (the data grid display settings modal) would result in a 422 error, preventing users from applying their configuration. This behaviour has been corrected and users can now successfully save changes in the Column configuration as expected. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25147 | Data Foundation | An issue was corrected in the System Usage & Roles report where widgets and tables failed to display data related to the Check-ins feature. The root cause was a data type conversion step in the Check-ins usage dataset that incorrectly attempted to cast worker ID values to an integer data type, causing an error that prevented the data from loading. The report now correctly displays Check-ins data. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25160 | Data Foundation | A new regular expression was added for PowerBI report translation keys, for added consistency in translation efforts. This change is internal and has no direct impact on users. | ||
| AC-25165 | Data Foundation | An issue was corrected where creating a Custom Entity of type NonReferenceableEntity with a composite business key (i.e. multiple fields jointly identifying a record) was incorrectly rejected with a validation error stating that exactly one identifier field was required. The validator has been updated to allow one or more identifier fields, enabling composite business keys to be defined for Custom Entities. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25176 | Authorization | Unused fields were removed from the authorization model. This change is internal and has no direct impact on users. | ||
| AC-25179 | Data Foundation | An issue was corrected where data operations (ingestion, querying, and deletion) for custom entities failed with a database error indicating the expected table did not exist. This occurred because the schema provider responsible for mapping entity types to database tables always used the entity's own name as the table name, rather than routing custom entities to the shared CustomEntities table as intended. The routing logic has been corrected so that custom entities are now directed to the shared CustomEntities table with the appropriate type filter applied, consistent with how other shared-table entity types are handled. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25180 | Data Foundation | Test environments were set up for PowerBI reports. This change is internal and has no direct impact on users. | ||
| AC-25183 | Data Foundation | Two new endpoints were added to the Analytics API to support Power BI semantic model (dataset) refresh operations. The first endpoint, POST /api/v1.0/Report/TriggerDatasetsRefresh, allows administrators to trigger a refresh of all configured Power BI semantic models (the data sets that power reports). The second endpoint, GET /api/v1.0/Report/DatasetsRefreshStatus, allows administrators to poll the current refresh status across all models, returning per-model status details and an aggregated global status. Both endpoints return structured JSON responses indicating whether each model is completed, in progress, or failed. These endpoints are authenticated using the reporting API scope via the integration hub. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25211 | Data Foundation | An issue was corrected in the Data Foundation API where attempting to edit a custom data type (Custom Entity) that was in an Active state via a PUT request returned an unhandled server error (HTTP 500) instead of a meaningful response. The API now returns a clear error message indicating that custom entities in Active state cannot be edited. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25217 | Pay Transparency | A Pay Analysis tab was added to the Planner section of the platform. Users can now navigate to the Pay Analysis area within Planner and view the Pay Analysis list page. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25241 | Pay Transparency | In Workbench > Pay Analysis, long user names displayed in the hierarchy columns (Worker, Line Manager, and Compensation Manager) of the Pay Analysis Results grid were not being truncated. Names that exceeded the available column width are now truncated with an ellipsis (…) to maintain a clean and readable layout. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25250 | Data Foundation | The configuration of the internal PowerBI development environment was updated. This change is internal and has no direct impact on users. | ||
| AC-25286 | Data Foundation | An issue was resolved where the Career Development semantic data model (an internal data structure used to power reporting and analytics) could not be refreshed due to a schema change in the career development plan populations configuration. The model can now be refreshed successfully without errors. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25292 | Data Foundation | A new Global Worker Category configuration module was introduced, allowing administrators to define how worker categories are constructed from worker fields. GlobalCompensationAdmin, DataFoundationAdmin, and Support roles can access the configuration wizard to select worker fields (such as Gender or Ethnicity), define field ordering via drag-and-drop, choose a separator character, and configure a blank value strategy (skip blanks, replace with a default label, or replace with custom values per field). A read-only preview reflects the configured order, separator, and blank handling before saving. DataModelerAdmin role has read-only access to this page. Configuration is stored centrally and applies only to future snapshots; deletion of the global configuration is not supported in this release. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25294 | Data Foundation | An issue was corrected where the live data snapshot API endpoint (used to retrieve filtered worker and employment data) returned instance keys in scientific notation (e.g. 4.12e9) instead of standard numeric notation (e.g. 4120562471). Instance keys are now returned in regular numeric format as expected. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25310 | Data Foundation | An issue was corrected where custom entities in Draft or Deactivated states were not properly filtered from consumer-facing APIs. These entities were accessible through the data viewer, data upload entity selectors, CSV template downloads, and data ingestion endpoints regardless of their lifecycle state. Custom entities in Draft or Deactivated states are now excluded from all of these interfaces — data viewer queries will no longer return them, ingestion attempts for such entities will return a clear error message, and CSV template downloads will return an appropriate error. Custom entities in all states remain visible within Custom Entity Management as expected, and standard (non-custom) entities are completely unaffected by this change. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25313 | Data Foundation | Admins can now edit and save custom entities while they are in Draft state. All entity and field properties are editable during the draft phase, and standard validations are enforced on save — including uniqueness of the data type name and field names, the requirement for at least one business key field, valid enum and entity references, and a maximum of 20 fields per entity. Editing schema properties is restricted to Draft entities; attempts to modify Active or Deactivated entities are rejected with an appropriate error. When a field referencing Worker is added to a draft entity, the entity is automatically marked as worker-related and PII configuration options become available; PII options are disabled when no Worker reference exists. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25323 | Data Foundation | Updates were made to the backend handling of Global Worker Category configuration. The internal representation of certain special characters now uses the actual character (such as the pipe symbol "|") rather than a text label, improving alignment with the broader system. Additionally, the identifier field was changed from a text-based key to a numeric unique identifier, and validation was added to confirm that the provided identifier exists within the schema before it is accepted. These changes improve data consistency and reliability for Global Worker Category management. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25372 | Data Foundation | The label for the Consolidated contextual data viewer has been updated to 'Workers FYI' to better reflect its purpose. This change is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25375 | Data Foundation | A new API endpoint was added to the Custom Labels API to allow integration administrators to check whether a tenant has active custom label translations for specific key prefixes. The endpoint (`GET /api/v1.0/custom-labels/customization-status`) accepts one or more key prefix values as query parameters and returns whether any matching customizations exist, as well as which culture codes (language/locale configurations) have been customized. This enables automated processes, such as integration hub workflows, to detect whether Power BI report translations have been customized before taking further action. | ||
| AC-25396 | Pay Transparency | Updates were made to tables for the PayAnalytics integration. This change is internal and has no direct impact on users. | ||
| AC-25399 | Data Foundation | Dedicated endpoints were added to the custom data type schema. This change is internal and has no direct impact on users. | ||
| AC-25412 | Compensation Management | A validation restriction in workflow step configuration was removed to allow greater flexibility when setting up compensation round steps. Previously, two successive steps could not share the same end date, which prevented administrators from configuring fast-forward progression scenarios. Compensation admins can now save two or more steps with the same end date without encountering a validation error. The existing rule requiring each step's end date to fall within the round's overall date range remains in effect. | ||
| AC-25417 | Data Foundation | In Workbench > Data Management > Custom Fields, fields belonging to custom entities were incorrectly displayed in the custom fields grid alongside standard custom fields. This behavior was corrected and fields associated with custom entities are no longer shown in this grid. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25466 | Authorization | Error handling was added for missing tenant databases, preventing crashes when a tenant database doesn't exist. This change is internal and has no direct impact on users. | ||
| AC-25496 | Data Foundation | Development was started for custom translations on PowerBI reports. This change is internal and has no direct impact on users. | ||
| AC-25507 | Pay Transparency | An issue was corrected in Planner where the Pay Analysis tab remained visible even when the Pay Analysis feature had been disabled in configuration. The tab is now correctly hidden when the feature is disabled. | ||
| AC-25508 | Compensation Management | An issue was corrected in Workbench > Pay Management where the Workflow Status column incorrectly displayed 'In progress' for all workers when a round configured with Advanced Workflow was in a Ready or Not Started state. Because the round had not yet started, no workflow step should have been actively progressing. The Workflow Status column now correctly displays 'Not Started' and the Workflow Step column remains empty for rounds in these pre-start states. | ||
| AC-25511 | Compensation Management | When a compensation round with an advanced workflow is published or republished, workers in that round are now automatically reset to step 1 and immediately advanced to the correct workflow step based on step end dates. Previously, workers would remain on an incorrect step until the next scheduled daily job ran. On publish or republish, the system evaluates each worker's step end dates in sequence: workers are advanced through any steps whose end date has already passed, and placed on the first step that is still active or not date-driven. Workers whose first step has no date-driven end date, or whose end date is today or in the future, remain on step 1. If all steps have expired end dates, the worker is marked as Completed. This ensures workers are always on the correct step at the moment a round goes live, without waiting for the overnight automated process. | ||
| AC-25514 | Data Foundation | In Analytics Hub, report and page names displayed in the interface are now translated based on a mapping configuration. Previously, the system returned the raw internal report names directly to the interface. The system now maps internal report names to translatable keys, allowing the interface to display localized names. If no mapping is defined for a given report, the original name is displayed as a fallback. Compensation admins will see translated report and page names where translations are configured. | ||
| AC-25550 | Compensation Management | A point-in-time snapshot is now recorded each time a worker's compensation proposal is approved, rejected, submitted, or completed in Planner > Compensation. Each snapshot captures the acting user's identity, the workflow step transition (the state before and after the action), and a full copy of the worker's compensation data at the moment the action was taken. This provides a complete and reliable audit trail of workflow state changes, supporting accountability and traceability across the approval process. Snapshots are saved atomically within the same operation as the transition itself, ensuring that no record is created if the action does not succeed. | ||
| AC-25557 | Data Foundation | The API endpoint for updating custom data types (PUT /api/data-type/custom) has been updated to support renaming. Previously, the current name was used both to look up the data type and as the name value, making it effectively immutable during an update. The endpoint now accepts the current name as a route parameter for lookup (PUT /api/data-type/custom/{dataTypeName}), while the request body can supply a new name. The same name validation rules that apply at creation — including format, length, and uniqueness checks — are enforced on the new name. Renaming is only permitted while the data type is in Draft state. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25562 | Data Foundation | An issue was corrected where exporting reports and pages to PDF or PPTX format did not apply the current user's cultural settings (such as language and regional formatting). Exports now correctly use the culture of the user initiating the export. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25582 | Data Foundation | A loading panel is now displayed in Analytics Hub while a report or page export is in progress. Previously, no visual feedback was provided during the export process. Admins can now clearly see when an export is underway and will receive the downloaded file once it is ready. | ||
| AC-25601 | Data Foundation | An issue with the validation of a json variable file was preventing the PowerBI deployment pipeline from working properly. This change is internal and has no direct impact on users. | ||
| AC-25676 | Data Foundation | An issue was corrected in Performance Reviews where refreshing the semantic data model failed with an error stating that the column 'WeightFactor' did not exist. This prevented the data model from being successfully refreshed. The underlying data model definition has been corrected and the refresh now completes without error. | ||
| AC-25680 | Data Foundation | An issue was corrected where querying a custom data type that included a reference to a Worker record would result in a 500 error when security filtering (ABAC — attribute-based access control, a mechanism that restricts data access based on user attributes and policies) was applied via the Data Viewer. The error occurred because the SQL query generated for custom entities incorrectly omitted the required join to the Worker table, causing the database to reference a table that was not included in the query. The query builder has been updated to correctly detect and apply the Worker table join for custom entities, ensuring that security-filtered queries execute without error. Standard worker-related entities and custom entities without a Worker reference are unaffected by this change. This feature is currently behind a feature flag and is not yet available to all customers. | ||
| AC-25703 | Authorization | A new sorting order was applied to the identity provider list in the application back-office. This change is internal and has no direct impact on users. | ||
| AC-25814 | Compensation Management | An issue was corrected in Round Management where attempting to duplicate a Payroll resulted in an HTTP 500 error (an unexpected server-side failure). This was caused by an internal data tracking configuration issue. Payrolls can now be successfully duplicated as expected. | ||
| AC-25944 | Performance Management | An issue was corrected in Workbench > Performance Management > Career Development Plans where the 'Delete selected' and 'Generate PDF' buttons were incorrectly visible to Configuration role users in the Manage Plans view. The 'Delete selected' button appeared in the Manage Plans action bar and the 'Generate PDF' option appeared in the per-plan 3-dot actions dropdown. Both buttons have been removed from this view and are no longer visible to Configuration role users. | ||
| 150760 | AC-26012 | Authorization | An issue was corrected where CSV files exported from the professional roles section could not be properly opened in Microsoft Excel when users operated in non-English locales (e.g. French). In these locales, Excel expects semicolons as column separators rather than commas, causing all exported data to appear in a single column. Additionally, users who manually adjusted and saved such files using their locale's separator were unable to re-import them into the platform. Exported CSV files now include a formatting hint that instructs Excel to apply the correct column separator regardless of locale settings. The import process has also been updated to automatically detect whether a file uses comma or semicolon separators, making both formats accepted on upload. These changes are backward compatible and existing comma-delimited files are unaffected. | |
| 148838 149014 | AC-26082 | Data Foundation | An issue was corrected where the Review Details page could not be displayed in the Performance Review report, resulting in an error that prevented the page from loading. The issue has been resolved and the Review Details page now displays correctly without errors. | |
| AC-26095 | Authorization | An issue was corrected where users who had an Access Control List (ACL) assigned to their account were unable to log in to the platform. After an ACL was assigned to a newly created user, the login flow would fail with an internal server error because the authorization service could not correctly retrieve the user's roles from the database. This was caused by a serialization incompatibility (a mismatch between how data was read from the database and how the system expected it to be structured) in the role-resolution logic. The issue has been resolved: roles are now retrieved correctly, and users with no roles assigned receive an empty role set rather than an error. Users with ACL assignments can now log in successfully and the ACL is applied as expected. | ||