beqomPay Suite 22.0 - Detailed release notes
This article lists the new features that have been added to the platform, as well as the bugs that have been corrected in the intermediate 22.0 release of the beqom Pay Suite 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.
22.0
Deployment to staging environments: March 10th, 2026
Deployment to production environments: March 17th, 2026
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| AC-15656 | Performance Management | An issue was corrected in Passport > Check-ins where managers navigating to a check-in via an email notification would briefly see the Check-ins list page before being redirected to the view check-in page. This was caused by outdated redirect URLs included in notification links. Notification links have been updated so that managers are now taken directly to the View Check-in page without the intermediate list page appearing. | ||
| AC-17031 | Performance Management | Under Workbench > Performance Management > Career Development Plans, a new HR Portal was added for Career Development template owners (HRBPs and local owners). For published templates, owners can now access the portal by clicking the Manage option in the 3-dot menu or by clicking the template name directly. The portal displays a page titled 'Manage {Plan name}' with two tabs: Move stages (opened by default with filters including Career Development stage prepopulated to 'Closed', organizational unit, manager, workers, cost center, and country) and Manage plans (same filters without default selection). Both tabs include collapsible filter panels with an always-active Apply filters button. The Manage option is not shown for draft templates, and clicking draft template names continues to open edit mode. | ||
| AC-17032 | Performance Management | Template Owners can now move Career Discussion plans between workflow stages directly from the HR Portal > Career Development moderation view. Plans in the Closed stage can be moved to either Manager Feedback or Worker Self-Assessment, while plans in the Manager Feedback stage can be moved to Worker Self-Assessment. Template Owners can select one or more plans at a time using checkboxes, including bulk selection, and must confirm the action before it is applied. After a move, previously submitted inputs are retained in draft mode so that managers and employees can review and resubmit through the standard workflow. A success banner displays the number of plans successfully moved, including partial results where some plans could not be moved due to a stage change occurring during the operation. Filters applied before the move are preserved and the list refreshes automatically to reflect the updated stages. | ||
| AC-19968 | Compensation Management | Data fetching for compensation round configuration was migrated from the Remix framework's built-in data loader to React Query (a data management library that provides more robust request handling and error reporting) within the Compensation Round Wizard. This change improves error visibility by ensuring that request failures are surfaced to users in the interface, and lays the groundwork for broader adoption of React Query across the platform. | ||
| AC-20572 | Pay Transparency | Status tracking was added to pay analyses in the Pay Analysis module. Analyses now move through a defined lifecycle — New, Validation, In Progress, Closed, and Archived — with status transitions triggered automatically by user actions such as opening an analysis, publishing it, closing it, or deleting it. The current status of each analysis is now displayed in the Pay Analysis list page, the analysis details drawer, and the Pay Analysis information grid. The list page also shows a count of analyses per status, excluding In Progress and Closed from the count display. For datasets containing sub-group analyses, each sub-group carries and updates its own individual status independently from the main analysis. | ||
| 141456 | AC-20586 | Performance Management | An issue was corrected where closing a tab while in proxy mode caused the proxy session to persist when the application was reopened in a new tab. As a result, users would find themselves logged in as the previously proxied user rather than their own account. The proxy session is now discarded when a new tab is opened, ensuring users always access the application under their own identity. | |
| AC-21145 | Compensation Management | Security hotspots identified by SonarCloud (a code quality and security analysis tool) were reviewed and resolved in the accelerate-compensation-api service (the backend service responsible for compensation data processing). This work improves the overall security posture of the compensation platform. | ||
| AC-21340 | Performance Management | A new notification was added in Workbench > Performance Management > Career Development to alert managers when a Career Discussion has been reassigned to them. When a Career Discussion is reassigned, the new manager receives an in-app notification and an email with the subject 'A Career Development about [employee name] was reassigned to you' and a message identifying who performed the reassignment. The notification appears in the Career Development notification group and can be enabled or disabled in Notification Settings under the Career Development section, where it is labeled 'Career Development reassigned' with the description 'A notification will be sent to the manager to whom a Career Development has been reassigned.' | ||
| AC-22546 | Pay Transparency | In Workbench > Pay Analysis Results, users can now enter and store recommended raise amounts directly in the Pay Analysis data grid. Raises cascade automatically across analysis levels — updating a raise on a main analysis applies it to all sub-group analyses, and updating a sub-group analysis updates the main analysis in turn. Four new columns were added to the grid: Raise (editable), Raise %, Compensation (after raise), and Outlier % (after raise). The Raise % and after-raise columns are calculated automatically based on the entered raise value and refresh in real time as values are edited. Two insight cards — Number of Raises and Total Cost of Raises — also update to reflect current raise data. Column visibility for all four new columns is configurable via the Column Config settings. An 'All changes saved' confirmation message appears briefly on the page after each change is made. | ||
| AC-22609 | Data Foundation | The CI/CD pipeline (an automated process for building and deploying software) was configured for UAT (User Acceptance Testing) environments. Deployments to UAT are now triggered automatically whenever the UAT branch is updated, ensuring the environment always reflects the current release under test. This eliminates the need for manual deployments, reducing effort for the team and enabling smoother promotion to higher environments. | ||
| AC-22615 | Data Foundation | A CI/CD pipeline and automated deployment workflow were configured for Power BI report releases across staging and production environments. Release managers can now deploy a specific version of Power BI reports to a target environment and region on demand, as well as roll back to a previous version if needed. Access to trigger deployments is restricted to authorized release managers, reducing the risk of unintended changes. Report auto-refresh schedules are configured per customer and run without errors. These changes eliminate the need for manual intervention by the support team and reduce the risk of configuration errors during releases. | ||
| AC-22744 | Data Foundation | A Slack notification is now sent to administrators upon completion of an automation deployment. The notification includes a summary of the deployment result, allowing admins to confirm the outcome without manually checking the system. | ||
| AC-22805 | Pay Transparency | An issue was corrected where HRBPs could not see workers who do not have an active user account (ProvisionUserAccount set to false) in the Pay Information Requests page. This occurred because access checks were performed against an index that only included workers with user accounts, causing non-user workers to be excluded from all views and actions. Following this fix, HRBPs can now view, create, edit, and close Pay Information Requests for all workers within their scope, regardless of whether those workers have a user account. Note: closing a Pay Information Request that includes an attached document is not supported for workers without a user account, as the document storage layer requires a valid user identity. | ||
| AC-23194 | Performance Management | The GET performance-reviews/total-scores API endpoint (used to retrieve aggregated performance review scores for reporting) was extended with additional query parameters to support more flexible reporting. Callers can now filter results by template language, template creation date range, template status, and record last updated date range, all using standard ISO 8601 date formats. The response payload was also updated: pagination metadata fields (currentPage, pageSize, rowCount, pageCount) are now returned, the score field was renamed to weightedScore, a weightFactor field was added to each score entry, and widget names are now returned in their original casing. Existing request parameters (page and count) remain backward compatible. Callers of this endpoint must update their integrations to use the new response field names. | ||
| AC-23203 | Authorization | Plan owners can now assign one or more global populations to a Career Development Plan in Workbench > Performance Management > Career Development Plans. Populations are sourced from the centrally managed Population Service and only published populations are available for selection. In Draft mode, plan owners can freely add or remove populations using a multi-select dropdown with checkbox selection and pill display. In Published mode, populations that were assigned prior to the most recent publish are locked and cannot be removed, while additional populations can still be selected and added. This feature follows the same interaction patterns as Performance Review Template population configuration and ensures consistent population management across the platform. | ||
| AC-23316 | Performance Management | In the HR Portal, Admins can now filter career development plans by plan stage across two tabs: Move Stages and Manage Plans. On the Move Stages tab, the plan stage filter is pre-populated with 'Closed' and includes the values 'Manager Feedback' and 'Closed'. A label displays the total number of plans in the selected stage, and clicking 'Apply Filters' renders a table of matching plans — ordered alphabetically by worker name — with columns for Worker, Global ID, Email, Organization, Organization External ID, Cost Center, Manager ID, and Manager. Admins can select individual, multiple, or all rows on the current page, and the selection summary displays the current selection count, current plan stage, and a dropdown to move plans to a new stage. On the Manage Plans tab, the filter opens in an empty state and includes the values 'Worker Self Assessment', 'Manager Feedback', and 'Closed'. When no stage is selected, a 'View All' button is shown; selecting a stage changes the button label to 'Apply Filters'. The resulting table includes the same columns plus a three-dot menu per row with 'Reassign Manager' and 'Generate PDF' options. Both tabs support pagination, respect ABAC-based visibility rules, and reset their filters when the Admin switches between tabs. | ||
| AC-23337 | Compensation Management | The round configuration API was refactored to split the previously single, large update endpoint into dedicated endpoints for distinct configuration phases. Two new endpoints were introduced: PUT /api/v1.0/rounds/{roundId}/subscription (which handles subscription-level fields such as data model, compensation elements, population, and dates, and regenerates datapoints when structural changes are made) and PUT /api/v1.0/rounds/{roundId}/configuration (which handles datapoint configuration, rules, workflows, and feature settings). The original update endpoint (PUT /api/v1.0/rounds/{roundId}) is retained for backward compatibility, ensuring that existing integrations continue to work without modification. This change reduces payload complexity and makes the intent of each API call clearer for system integrations. There is no impact on end-user functionality. | ||
| 146664 | AC-23348 | Data Foundation | Administrators can now explicitly revert custom labels to their standard values via CSV upload in Custom Labelling. Previously, clearing a custom value in the CSV did not remove it — the label would retain the previously uploaded custom value with no clear way to undo it. A new 'Is Custom Value' column has been added to the CSV export and import. When set to 'False', the system ignores any custom value and reverts the label to its standard default; when set to 'True', the provided custom value is applied. CSV files uploaded without the new column continue to behave as before, ensuring backward compatibility with existing imports. | |
| AC-23382 | Data Foundation | An issue was corrected where the table on the Review Challenge page of the Performance Reviews report appeared empty and did not display any data. The issue was caused by the presence of the 'Final Overall Performance Rating Scale Has Changed' column, which prevented data from rendering. After removing this column, data is now correctly displayed in the table. | ||
| AC-23636 | Data Foundation | A semantic model was created to support pay transparency report pages, covering pay information, inbox workers, role-level security (RLS) organizations, and contracted and paid compensation data. The model was designed with performance in mind to avoid placing excessive load on the database (PostgreSQL) when handling large volumes of data. Support teams can now use this semantic model as a foundation for building pay transparency reports. | ||
| AC-23753 | Data Foundation | |||
| AC-23765 | Pay Transparency | An issue was corrected where Pay Analytics tenant data could be incorrectly saved to the database even when storing the associated API key in the Key Vault (the secure credential storage service) failed. As a result, subsequent attempts to provision the same tenant would return an 'already exists' error, while the tenant remained non-functional due to the missing API key. The fix ensures that the database entry and the Key Vault entry are now saved as a single atomic operation, so if either step fails, neither change is persisted. | ||
| AC-23773 | Pay Transparency | Document management has been updated so that documents, summaries, and related actions are now tied to worker records rather than user accounts. This means workers who do not have a login account (provisioned as active workers without a user account) are now fully supported across all document workflows. Workers can access their own documents in self-service, communication managers see the correct documents for their direct reports, and HRBPs see documents for their assigned populations. Bulk actions such as releasing documents or changing workflow steps, as well as document imports (including from pay information requests), now operate against the correct worker. Notifications for document releases are sent only to workers who have an associated user account. A data migration updates existing document records to reference the worker identifier, while the previous user identifier is retained in the database for continuity. | ||
| AC-23891 | Pay Transparency | In Workbench > Model Factory > Pay Analysis Results, Compensation admins can now publish pay analyses and configure the level of access granted to HRBPs at the time of publishing. When publishing, admins specify whether HRBPs can view comments, admin comments, compensation recommendations, and final offers, as well as whether HRBPs can edit final offers. These permission settings follow cascading rules: access must be granted before any individual options can be enabled, and view permission on the final offer must be granted before edit permission can be toggled. Publishing transitions the analysis to an In Progress state, and a new widget on the Pay Analysis List view displays the total count of In Progress analyses. Admins can revisit and update the publishing configuration at any time from the grid view without republishing the analysis. This feature is controlled by the ff_planner_payanalysis feature flag. | ||
| AC-23909 | Compensation Management | A Proposal Management configuration capability was added to compensation round setup in Workbench > Compensation. For each compensation element (salary and bonus) in the Team Planner View step, Compensation Admins can now open a dedicated 'Proposal Management' drawer to control how proposal values are pre-populated when a round is executed. Admins can choose to prefill proposals using an existing data model field or generate values using a custom formula, with the same advanced conditional and non-conditional formula editor available for calculated fields. Safeguard prompts are displayed when disabling the configuration or switching between source types, warning that existing settings will be cleared and cannot be recovered. This feature is controlled by a feature flag and is disabled by default. | ||
| AC-23980 | Compensation Management | In Round Management > Overview > Configuration Overview > Team Planner View, Compensation Admins can now preview Proposal Management configuration for individual compensation elements without leaving the portal. A new 'Proposal management' action appears in the Column Configuration actions list for each compensation element that has Proposal Management enabled, positioned after the existing 'View' and 'Conditional formatting' actions. Clicking the action opens a nested read-only drawer displaying the compensation element name, enabled status, and full configuration details — including the selected method (source field or formula), field path, formula type, and formula expression with syntax highlighting and a copy option. The drawer follows the nested drawer pattern, closing only via the X button, and returns the user to the Team Planner View drawer. This feature is controlled by a feature flag. | ||
| AC-23995 | Performance Management | In Planner > Manage, the display of reassigned reviews was updated to align with the intended design. Reviews that have been reassigned to another manager now show a 'Reassigned' label, and hovering over this label displays the name of the manager the review was reassigned to. Additionally, the ability for managers to view and open completed reviews from the team dashboard is now correctly governed by the 'Allow new managers to see closed reviews' setting: when enabled, managers can open the completed review; when disabled, the review is visible but cannot be opened. | ||
| AC-24004 | Data Foundation | Customers can now configure which columns appear in the Worker List grid without requiring code changes or a new deployment. Fields are grouped by entity (Worker, Employment, Demographics, and others), and administrators can add, remove, or reorder fields within a group, as well as reorder the groups themselves. Configuration changes are reflected immediately. Worker Full Name and Worker ID are mandatory frozen columns that are always visible and cannot be removed. To improve performance, only the selected columns are fetched from the data source when the grid loads. | ||
| AC-24007 | Data Foundation | Back-end security filtering was applied to the worker list to enforce user permissions and access rights. Only worker records that a user is authorized to view are now returned when the worker list is queried. Users with no access to worker data will see an empty list. This change is implemented on a new endpoint and does not affect existing functionality. | ||
| AC-24016 | Data Foundation | In the Worker List, user interface configurations are now automatically saved and restored without any manual action required. When users modify their Worker List setup — including visible columns, column order, applied filters, sort order, and search terms — the state is persisted automatically and restored the next time they return to the Worker List. Each user's configuration is stored independently, ensuring that multiple users working in the same environment each see their own last-used state. If no prior state exists, the default configured grid state is displayed. | ||
| AC-24041 | Data Foundation | A new API endpoint was added to Data Foundation that allows administrators to create Custom Entity schemas in a Draft state. Custom Entities created through this endpoint support lookup and calculation use cases and are defined by specifying entity-level properties (such as a unique data type name) and one or more fields (with properties including data type, nullability, PII designation, business key, and effective dating configuration). Entities remain in Draft state — invisible in the data viewer and unavailable for data upload, querying, or ingestion — until explicitly published. Validation rules enforce naming conventions, uniqueness of data type and field names, the presence of exactly one business key field, and valid references for Enum and Entity field types. | ||
| AC-24051 | Pay Transparency | An issue was corrected in the Pay Analysis Grid where numerical fields were displayed without rounding, showing more than 2 decimal places. This occurred because the API response did not include field type information, leaving the front-end unable to distinguish between numerical and string fields. The backend now provides field type metadata alongside field values, and numerical fields in the Pay Analysis Grid are correctly rounded to a maximum of 2 decimal digits. | ||
| AC-24058 | Pay Transparency | An issue was corrected in Pay Analysis where the details drawer displayed the total number of subgroups from Pay Analytics rather than the count of subgroups that had been synced. This occurred because the detail endpoint was reading from an outdated snapshot stored at sync time, which was never updated when subgroups were later removed, while the list endpoint correctly retrieved live data from the database. The fix aligns the details drawer with the list endpoint so that both now reflect only the synced subgroup count, giving users an accurate and consistent view. | ||
| AC-24077 | Compensation Management | Compensation admins can now configure multiple bonus plans within a single compensation round in Planner > Compensation. On the Round Details step, an 'Add bonus plan' button allows additional bonus plan sections to be added in Draft mode, each requiring a unique bonus plan selection and a unique compensation element. The Population step displays each bonus plan separately with its own population configuration, and the Bonus Calculation Formula step lists all bonus plans individually in the left panel, showing Achievement Calculation, Calculated Bonus, and Target Bonus per plan. The Round Management Portal provides dedicated drop-downs for previewing population and formula details per bonus plan. This feature is controlled by a feature flag. | ||
| AC-24131 | Data Foundation | The consolidated worker view data endpoint was updated to support full name search by combining the first name and last name fields into a single searchable value. Administrators can now search for workers using a full name (first name and last name together), rather than being limited to searching each field separately. This enhancement also supports sorting by full name. | ||
| AC-24144 | Pay Transparency | Pay Analysis Admins can now add, edit, and delete notes on individual employee rows in Pay Analysis Workbench > Pay Analysis to document and justify compensation decisions such as raises and salary adjustments. A new Notes column has been added to the data grid, displaying the note count per employee row. Clicking the column opens a drawer where multiple notes can be viewed in chronological order, and new notes can be added up to a maximum of 5,000 characters. Notes are tied to their creator, meaning only the author of a note can edit or delete it. This functionality is restricted to users with the Pay Analysis Admin role. | ||
| AC-24216 | Data Foundation | Admins can now deactivate custom entities that are no longer in use. When an admin initiates deactivation, a confirmation dialog is displayed before the action proceeds. If the entity is currently in use — for example, because ingestion data has been loaded against it — the deactivation is blocked and a meaningful error message is returned, including details such as the ingestion ID or consuming process, so the admin can take appropriate action. Historical data associated with the entity is preserved after deactivation. Standard (non-custom) entities cannot be deactivated and will return a validation error if attempted. | ||
| AC-24220 | Data Foundation | Admins can now publish custom entities from Draft state to Active state within Custom Entity Management. Publishing a custom entity makes it available for data upload and viewing in Data Viewer, while locking the entity's schema to prevent further edits or deletions. A confirmation dialog is presented before publishing to prevent accidental transitions. The custom entity lifecycle enforces strict state rules: Draft entities are fully editable and visible only to admins in Custom Entity Management; Active entities are immutable and visible in Data Viewer and Data Upload; Deactivated entities are read-only and no longer visible in data-facing areas. Deactivation is available for Active entities that are not currently in use, and no other state transitions are permitted. | ||
| AC-24221 | Data Foundation | Admins can now edit and save custom entities while they are in Draft state. All entity and field properties are editable during this stage, and standard validations are enforced on save — including uniqueness of data type and field names, the requirement for at least one business key field, and valid references to existing enums and entities. Entities in Active or Deactivated states remain protected and cannot have their schema properties modified. The worker-related status of an entity is automatically derived based on field references and is not manually editable. A maximum of 20 fields per custom entity is enforced. | ||
| AC-24222 | Data Foundation | Admins can now permanently delete custom entities that are in Draft state. When deleted, the entity and all associated field definitions are fully removed from the system with no schema artifacts remaining. Deletion is restricted to Draft entities only — attempts to delete Active or Deactivated entities are rejected, and an error message is returned indicating that only draft entities are eligible for deletion. | ||
| AC-24232 | Pay Transparency | In Workbench > Pay Analysis, the raise columns — 'Compensation after Recommended Raise', 'Recommended Raise', and '% Increase after Raise' — are now fixed in position within the Pay Analysis Grid. These columns are permanently placed after the Comp Manager column and can no longer be hidden or repositioned, ensuring consistent visibility across all sessions. | ||
| 148338 | AC-24306 | Back-end localization strings were updated to remove all instances of the product name 'CPM by beqom' from active translation keys. This ensures that platform notifications and other back-end-generated content reflect current product branding across all supported languages. | ||
| AC-24360 | Data Foundation | The system now publishes a DataModelUpdatedEvent notification (a message sent between internal services to signal a change) when a field is extended in a data model via the model administration API. This allows any services subscribed to this event to be automatically informed of data model updates, including the affected field identifiers and subscription details. Previously, no such notification was sent when model fields were extended. | ||
| AC-24407 | Compensation Management | In the reminder configuration for compensation rounds, HRBP has been added as an available recipient option. Compensation Admins and Global Compensation Admins can now select HRBP from the Recipients list when creating or editing a reminder, and save or send the configuration accordingly. Additionally, the enable/disable toggle for the notification bell has been removed from the reminder configuration. | ||
| AC-24464 | Data Foundation | Custom Entities can no longer be modified using the generic custom field customization APIs (the endpoints previously used to add custom fields to standard entities). Any attempt to use these APIs on a Custom Entity will now return an error message explaining the restriction and directing administrators to use the dedicated Custom Entity schema management endpoints instead. Custom field customization continues to work as before for standard entities and other supported entity types. | ||
| AC-24495 | Pay Transparency | An issue was corrected in Snapshot Manager where the 'Create PA dataset' button was not displayed immediately after creating a data modeler, mapping, or snapshot. This was caused by a cache invalidation delay. The button now appears correctly as soon as a snapshot is created, provided a mapping exists. | ||
| AC-24499 | Pay Transparency | An issue was corrected in Workbench > Data Management > Pay Analysis Data Mapping where Currency Code fields were not displayed in the Currency Field dropdown when configuring Dataset Mapping for a Data Model. The dropdown was incorrectly showing only categorical (text-based) fields, while Currency Code fields — stored as a different field type — were excluded. The dropdown now correctly displays only Currency Code fields, allowing users to select them and enabling currency conversions to be performed as expected. | ||
| 148596 | AC-24501 | Data Foundation | An issue was corrected in Population > Criteria where previously selected legal entities were not visually indicated when an admin returned to edit an existing population. As a result, it was impossible to determine which entities had already been selected, making it difficult to make informed changes. Selected items are now correctly displayed in the list, allowing Compensation admins to clearly see their existing selections when editing population filters. | |
| AC-24510 | Compensation Management | An issue was corrected in Planner > Compensation where closing the calculation screen after entering an invalid formula and then clicking Apply would send a request to the server and return a 422 error (an invalid request error). The invalid formula expression should have been blocked on the first Apply click, as it correctly was on subsequent attempts. The behavior has been corrected so that requests containing invalid formula expressions are now blocked from the first Apply click. | ||
| AC-24527 | Data Foundation | The CPM (Compensation Management) and TCM (Total Compensation Management) manifests (configuration files that define the default components and reports available in a module) were updated to include the Pay Communication report. Compensation admins can now set up workflow configurations using these manifests with Pay Communication included as a default report. | ||
| AC-24573 | Compensation Management | An issue was corrected in Planner > Compensation where the Owners search field on the Create Compensation Round page incorrectly displayed dropdown elements — specifically an X (clear) icon and an arrow (expand) icon — giving it the appearance of a dropdown component. These indicators were not appropriate for a search input and have been removed. The field now displays correctly as a search input without dropdown elements. | ||
| AC-24574 | Data Foundation | The Power BI deployment process was updated to trigger a full synchronization (an automated process that aligns report data and access permissions after deployment) at the end of each deployment run. This ensures that if a report is recreated during deployment, admin access to that report in Analytics Hub is preserved without interruption. Additionally, error monitoring was improved so that any deployment failures are now observable in Datadog (the platform's monitoring and logging service), enabling faster detection and resolution of issues. | ||
| AC-24586 | Data Foundation | An issue was corrected in the Consolidated Contextual Data Viewer where date and boolean field values were not displayed correctly. Date fields appeared blank and boolean fields were not rendered at all. These fields now display their values correctly. | ||
| AC-24589 | Data Foundation | An issue was corrected in Data Management > Consolidated Contextual Data Viewer where applying filters on Date or Boolean field types resulted in a server error (500 — an internal error preventing the request from completing). Filters using Date fields (such as a start date) or Boolean fields (such as checked/unchecked flags) now apply correctly and return the expected data. | ||
| AC-24592 | Compensation Management | A backend enforcement was added to prevent the deletion of compensation rounds in Closed status. Previously, it was possible to delete a Closed round by calling the deletion API directly, bypassing expected restrictions. The system now returns a 403 error (access denied) when an attempt is made to delete a Closed round via the API. | ||
| AC-24596 | Data Foundation | Role-based access control was configured for the Consolidated Worker module. The Configuration, Support, DataFoundationAdmin, CompensationAdmin, and GlobalCompensationAdmin roles were granted access to the relevant endpoints, ensuring that all roles with access to the Data Viewer module can also access Consolidated Worker without errors. The GetDataModelSchema action (controls access to data model structure) was enabled for these roles on the schema endpoint, and a new LiveSnapshotAccess action (controls access to live data previews) was introduced and assigned to the same roles on the live data endpoint. | ||
| AC-24599 | Data Foundation | The front-end dependency on the feature flag controlling the worker consolidated view was removed. All tenants now have access to the worker consolidated view by default, without requiring any flag configuration. | ||
| AC-24629 | Performance Management | The feature flag controlling visibility of manager reassignment settings was removed. Reassignment settings are now always visible to users with the relevant settings permissions, without requiring the flag to be enabled. | ||
| AC-24642 | Compensation Management | In Workbench > Pay Management > Compensation Rounds, the validation behavior on the Details step of the round creation and editing wizard was updated for Compensation Admins and Global Compensation Admins. Previously, duplicate selections between salary and bonus plan compensation element dropdowns were prevented in real time through filtering. Validation now runs when the 'Next' button is clicked instead: if duplicate compensation elements or bonus plans are detected, affected fields are highlighted with a red border and an inline error message, and navigation to the next step is blocked until duplicates are resolved. Errors clear immediately when a duplicate is corrected, and clicking 'Next' triggers a fresh validation check. The 'Save & Exit' option remains available at any time and does not trigger validation. When the multiple bonus plans feature is enabled, this same on-submit validation applies across all bonus plan dropdowns and the salary compensation element dropdown. | ||
| AC-24654 | Performance Management | An issue was corrected in Passport > Reviews where the Comment text area in the 'Edit question' pop-up for the Widget section displayed an incorrectly reduced height and expanded the modal layout when long content was entered, rather than resizing within fixed dimensions. This behavior was inconsistent with the 'Edit response' pop-up for the Overall performance section. The sizing constraints on the textarea have been corrected so that it now displays at a proper initial height, expands consistently within the modal, and the modal itself is capped at a maximum height with scrolling for overflow content. This fix affects the Manager-reviewer role when editing question comments in the Widget section of a Performance Review. | ||
| AC-24658 | Data Foundation | Cypress automated tests were configured for PowerBI integration and workspace environments to support full test automation across all deployment environments. Tests are now region-aware and connected to the appropriate database for each region, enabling reliable execution in staging and production. Clear separation has been established between Cypress test deployments and other deployment types, as well as between performance, presales, and UAT environments. | ||
| AC-24667 | Pay Transparency | An issue was corrected in Workbench > Data Management > Snapshot Manager where the Confirm button in the Create Dataset modal was disabled when mandatory fields were left empty or contained validation errors. The button now remains enabled at all times, and validation is triggered only when the user clicks Confirm, allowing users to attempt submission before being informed of any missing or incorrect inputs. | ||
| AC-24668 | Authorization | Code ownership configuration (the records that define which team members are responsible for reviewing changes to specific repositories) was updated for the Authentication and Authorization repositories to reflect current team assignments. | ||
| AC-24669 | Pay Transparency | In the column configuration unsaved changes pop-up, the 'Discard Changes' button has been changed to a secondary button style, ensuring that 'Save & Close' is the only primary button displayed. This update aligns with the platform's design principle of having a single primary action per contextual screen, making the intended action clearer for users. | ||
| 147499 | AC-24693 | Performance Management | An issue was corrected where managers received a 403 error (access denied) when clicking on a shared feedback item in the Useful Info section of the Review editing view. This occurred because the navigation logic was directing managers to a page they did not have permission to access, instead of the correct shared feedback view. Navigation logic has been corrected so that shared feedback items now route managers to the appropriate shared feedback page, while non-shared feedback items and employee views continue to use the standard feedback route. | |
| AC-24694 | Performance Management | An issue was corrected in Workbench > Performance Management > Career Development Plans where clicking 'Republish' after modifying the Population step as a Local Owner did not trigger the republish request, leaving the plan's population unchanged. The root cause was that republishing was only permitted on the Population step for Local Owners on published templates. The behaviour has been corrected so that Local Owners can now successfully republish at any stage, and changes to the population are properly saved and applied. This fix also applies to Performance Review templates. | ||
| AC-24695 | Data Foundation | In Worker 360, a dedicated empty state was added to the grid for users whose access permissions (ABAC — attribute-based access control) do not allow them to view any data in the grid. Instead of displaying an empty table or loading indicator, the grid now shows a clear message informing users that their current permissions restrict access and directing them to contact their administrator or HR team if needed. The action bar is hidden in this state, as no actions are available. When a user has partial access, the grid renders normally. | ||
| AC-24736 | Compensation Management | Several visual consistency improvements were made across the Compensation Rounds, Bonus Plans, and Payout Curves list pages in Workbench. Number formatting now uses a consistent font across all three pages, and tiles are displayed in a standardized sequence showing the entity name followed by status indicators (Draft, Pending Draft, Ready, In Progress, Deactivated, Closed) where applicable. On the Compensation Rounds page specifically, the word "Round" was removed from the search field placeholder text for a cleaner interface. | ||
| AC-24739 | Performance Management | Translations for newly added notification keys were generated and are now available in all supported languages. | ||
| AC-24749 | Compensation Management | A Close button was added to each tab in the Round management page under Compensation Round Management. Compensation admins can now close individual tabs directly from the tab bar. Additionally, a default value was introduced for pagination on this page, providing a more consistent browsing experience. | ||
| AC-24755 | Compensation Management | In Planner > Compensation, the eligibility icons displayed in the Compensation Review manager grid now reflect the configured theme color. This update ensures visual consistency across the interface in line with each organization's branding configuration. | ||
| AC-24777 | Data Foundation | Twelve unused datasets were removed from the Performance Reviews > Goals & Behaviors report. This change reduces processing overhead and improves the report's performance, with no impact on the data displayed to users. | ||
| AC-24782 | Data Foundation | The request statuses available in Pay Transparency were updated to reflect a revised set of values: New, In Progress, Pending Document Release, Closed, and Closed Without Document. For requests with the status 'Closed Without Document', SLA-related columns are now displayed as empty, as SLA calculation is not applicable in this case. Additionally, when no workflow is defined for a communication round, closing a request is treated as equivalent to releasing a document. These changes are reflected in Pay Transparency reports. | ||
| AC-24791 | Data Foundation | Several validation and enforcement improvements were made to the Custom DataTypes feature in the Data Foundation API (an interface used to define and manage custom data structures). The following issues were corrected and behaviors enforced: field names within a custom entity are now required to be unique, and attempts to create duplicate field names will return a validation error. Default values are now validated against their declared field type, so a field of type Integer will no longer accept a non-numeric default value. Fields marked as required now correctly reject null values at submission time, enforcing the defined contract. The IsPii (personally identifiable information) flag is now properly validated — it is only supported when a Worker reference is present, and is otherwise set to false by default. In addition, Referenceable Entity and Enum types can no longer be selected as the base type when creating a new custom entity, and Enum types are no longer permitted as EntityReference targets. Only non-referenceable entities are now supported, in line with the architecture design. | ||
| AC-24805 | Performance Management | A Plan stage column was added to the Manage plans table in Workbench > Performance Management > Career Development Plans. HR administrators can now see the current workflow stage for each employee's career development plan directly in the list view, without needing to open individual records. The column displays one of three values: Worker self assessment, Manager feedback, or Closed. | ||
| AC-24821 | Compensation Management | In Workbench > Round Management Portal > Statement Generation, the Criterion dropdown in Distribution Rule conditions now includes all available data model fields, including fields that belong to groups. Previously, only top-level fields were listed, making grouped fields unavailable for use as distribution criteria. Group fields now appear flat in the list alongside non-grouped fields, consistent with the behavior already in place in other areas of the platform. | ||
| AC-24826 | Compensation Management | An issue was corrected in Workbench > Round Management Portal > Statement Generation where Distribution Rule criteria using the IN operator with multiple values were not displayed correctly after saving. Upon reopening a saved statement rule, all values were concatenated into a single text string instead of being rendered as individual tags. This was a display-only issue — values were saved correctly in the backend. The display now correctly renders each IN criteria value as a separate tag, matching the state at the time of saving. | ||
| AC-24831 | Pay Transparency | The dataset configuration was updated so that Performance Analytics (PA) datasets can be created without requiring manual database intervention. The following data fields were populated for all workers: Employment FTE; Compensation History fields including Base Pay and Vacations (contracted amounts, actualized amounts, paid amounts, and currencies); and Demographics data (male/female). This change removes a manual setup step previously required during PA dataset creation. | ||
| AC-24834 | Pay Transparency | Support for the EnablePayAnalysis property was added to the global settings PUT endpoint (an API call used to update platform-wide configuration). Global settings can now be updated to include Pay Analysis settings, enabling configuration of Pay Analysis functionality through the standard settings update mechanism. | ||
| AC-24880 | Data Foundation | An issue was corrected in Workbench > Data Management > Custom Fields where attempting to create a custom field via the UI or the API returned a success response (HTTP 200) but the field was not actually created. This behavior has been corrected and custom fields are now created successfully as expected. | ||
| AC-24902 | Data Foundation | A pre-commit code formatting hook was added using Husky.NET (a tool that runs automated checks before code is saved to the repository). The hook automatically applies formatting rules to staged code files at commit time, enforcing consistent code style across the development team. The implementation includes safeguards for partial staging scenarios and is automatically installed when developers set up their local environment. Docker build pipelines are unaffected by this change. | ||
| AC-24955 | Data Foundation | The schema search endpoint (GET /api/data-type/schema/search) was extended with an optional customizability filter parameter, allowing callers to retrieve only standard data types, only custom data types, or all data types (the default). Previously, the endpoint supported filtering by data type kind and name, but had no way to distinguish between standard and custom data types server-side before results were paginated. The new filter is applied before pagination, meaning result counts accurately reflect the filtered subset. The REST client (the library used to communicate with the API) was also updated to support the new parameter. | ||
| AC-25004 | Data Foundation | The FluentAssertions library (a testing utility used to validate expected behaviour in automated tests) was replaced with Shouldly (an equivalent testing assertion library) across the Foundation test projects. This change was made because FluentAssertions updated its licensing terms, requiring its removal from the codebase. As part of this update, the Shouldly library was also upgraded to version 4.3.0 to bring .NET 8 compatibility and performance improvements. Test method naming conventions were also aligned to the established project standards. This change has no impact on platform functionality and affects only the internal automated test suite. | ||
| AC-25010 | Data Foundation | Input sanitization was added to the snapshot search and population management endpoints to address SQL injection vulnerabilities (a security risk where unvalidated user input could be used to manipulate database queries). In the affected areas, user-supplied search terms and population names are now properly escaped before being used in database search operations. The fix applies to the paginated snapshot list endpoint, and the create and update population endpoints. | ||
| AC-25038 | Pay Transparency | |||
| AC-25060 | Compensation Management | An issue was corrected in Workbench > Bonus Plans where an application error occurred when viewing the goal plans step of the view wizard for bonus plans in Ready status, if the associated goal plans contained goals without a goal type assigned. The error prevented users from seeing the goals list. This behavior has been corrected and the goals list now displays as expected. | ||
| AC-25069 | Data Foundation | State-based visibility rules for Custom Entities are now enforced across Foundation APIs, including the data viewer, data upload (ingestion) endpoints, and CSV template generation. Custom Entities in Draft or Deactivated states are excluded from consumer-facing APIs: they no longer appear in data viewer results, cannot be targeted by data uploads (the ingestion endpoint returns an error with a descriptive message), and CSV template downloads for these entities return an appropriate error. Custom Entities in Active state continue to be available as before. All states remain visible within Custom Entity Management for administrative purposes. Standard (non-custom) entities are unaffected by these changes. | ||
| AC-25139 | Data Foundation | An issue was corrected where attempting to change the state of a Custom Entity from Draft to Active via the Data Foundation API returned a 500 error (an unexpected server error that prevented the operation from completing). The state transition now completes successfully and the Custom Entity is updated to Active as expected. | ||
| AC-25142 | Data Foundation | An issue was corrected where the Performance Review report failed to refresh. The error occurred because the API endpoint returning performance review total scores produced two arrays containing a field with the same name, which the semantic data model (the underlying structure used to process and display report data) could not handle. The data model was updated to correctly process the response, and the Performance Review report now refreshes as expected. | ||
| AC-25305 | Authorization | An issue was corrected in Workbench > Performance Management > Career Development Plans where Local Owners (HRBP role) were unable to edit the Population step of a draft Career Development plan. Affected users could not add or remove workers, navigate through the population step, or save changes. Edit access for Local Owners on draft plan population settings has been restored, and these actions now complete successfully. | ||
| AC-25307 | Authorization | An issue was corrected in Workbench > Performance Management > Career Development Plans where clicking the 'Back' button on the Population step during plan creation triggered a 500 Internal Server Error. This occurred because navigating back with an empty population caused a null value to be submitted to the server. The population save logic was corrected to always submit a valid default object, allowing HRBPs to navigate back to the Details step without errors and with their previously selected options intact. | ||
| AC-25347 | Performance Management | An issue was corrected in Passport > Reviews where the 'Send to Documents' button was not displayed for Manager-reviewers when a review was in the Pending sign-off stage. The button is now correctly shown, allowing Manager-reviewers to send review documents as expected. | ||