beqom PaySuite 27.3 - 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 27.3 release of the beqom PaySuite application and in the subsequent patches.
27.3
Deployment to staging environments: August 18th, 2026
Deployment to production environments: August 25th, 2026
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| 153058 | AC-28007 | Performance Management | A manager could be unable to create team goals for a population such as "All Company" even with the correct goal plan and goal type configured, because a role-lookup check did not correctly recognize the manager's subordinates. Goal creation now accurately falls back to the manager's direct reports when resolving eligible roles. | |
| 153608 | AC-28890 | Performance Management | Some Year-End Review documents that were migrated from a legacy system remained shown as "In progress" instead of "Closed" when a manager proxied the affected worker. This was due to a concurrency issue in the historical data migration. The migration process now handles concurrent updates correctly and includes self-healing for affected records. | |
| AC-29658 | Data Foundation | The Feedback report in Analytics Hub was migrated onto the centralized lakehouse-based analytics architecture, with report output validated to match the previous implementation. | ||
| AC-29661 | Data Foundation | The Check-ins report in Analytics Hub was migrated onto the centralized lakehouse-based analytics architecture, with report output validated to match the previous implementation. | ||
| AC-29664 | Data Foundation | The Career Development report in Analytics Hub was migrated onto the centralized lakehouse-based analytics architecture, with report output validated to match the previous implementation. | ||
| AC-30123 | Data Foundation | Several Comp Rounds reports (Process Status, Salary Increase Allocation Overview, Pay & Performance, and related salary and bonus round export reports) in Analytics Hub were migrated onto the centralized lakehouse-based analytics architecture, with report output validated to match the previous implementations. | ||
| AC-30169 | Pay Transparency | Under Workbench > Platform Setup > Email Notifications > Documents, administrators can now configure an Automated action failures notification that alerts chosen users (any application user, not filtered by role) when automated actions such as document generation or close-and-release have failed. The notification supports a daily, weekly, or monthly schedule with a configurable delivery time, is sent both by email and in-app, requires at least one recipient, and links straight to the Automated Action Monitoring page pre-filtered to the failed items. | ||
| AC-30352 | Pay Transparency | Previously, communication managers received no alert when a worker's document moved into the Document review workflow step. A new notification, Document ready for communication manager review, now emails the primary and secondary communication managers when this happens. They receive an in-app notification as well. The notification also links directly to the relevant document in the Planner.This enhancement concerns workflow-enabled communication rounds with communication manager access. | ||
| AC-31638 | Compensation Management | Under Workbench > Compensation Management > Compensation Rounds, manager access based on the hierarchy access type (Compensation manager direct/indirect) previously came from a hierarchy snapshot frozen at the round's cut-off date. As a consequence, organizational changes made while a round was open were not reflected in who could access it. A new Hierarchy source option on the round's Define hierarchy step now lets Configuration and Compensation Admins choose Live hierarchy instead, so a manager's round access, round-list visibility, and Planner worker visibility stay current with the live organization while the round is open. Round population, proposal data, and calculations are unaffected. | ||
| AC-32071 | Pay Transparency | Planner > Pay Information now has a third tab, Audit trail, giving HRBPs and read-only role users a global, cross-request view of audit activity instead of only a per-request history. The table shows action date, executed by, action, request ID, worker, and details; it is paginated, sortable, and filterable by executed-by, worker, action, request ID, and date range. Each row links to the underlying request's detail page. Access is scoped to the same workers a user already has visibility into on the main Requests list. | ||
| AC-32175 | Data Foundation | A manually created snapshot for a worker with two effective-dated records on adjacent days could include an extra, incomplete record from the day before the chosen snapshot date, instead of only the single record valid on that date. This also affected salary review generation from a compensation round, which snapshots on a single date the same way. A snapshot for a given date now includes exactly one record per worker, reflecting that worker's data as of that date. | ||
| AC-32283 | Pay Transparency | The Mapping page within Workbench > Pay Transparency included the Usage column that displayed the same value for every mapping and the Usage type filter whose Bulk generation option was never used. Neither helped distinguish one configuration from another. Both have been removed from the Mapping list. Creating and editing a mapping configuration works exactly as before; only the elements that added no distinguishing information are no longer there. The page is now shorter and clearer to review, with no change to how mapping configurations are built or maintained. | ||
| AC-32348 | Performance Management | Because review titles can be up to 1000 characters within Workbench > Performance Management, exported file names for the review rating upload template, historical review file, and historical review log file could exceed the length Microsoft Excel allows, causing the file to fail to open. Exported file names are now capped to the appropriate limit for their type (200 characters for spreadsheet formats, since Excel on macOS rejects longer names), with the review title truncated as needed and special characters replaced. Truncation never affects the exported data itself. | ||
| AC-32565 | Data Foundation | Under Workbench > Data Management, Data Viewer export actions are now recorded in the backend audit log, capturing the user, session, export mode, entities and filters used, row count, output format, and success/failure, so security and compliance staff can trace who exported which data and when. | ||
| 157863 | AC-32791 | Authorization | Workbench, including Platform Setup > Feature Enablement, remained visible and accessible for certain role combinations while a user was acting on behalf of another user (proxying), instead of being hidden during proxy mode. Missing proxy-mode checks were added, so Workbench is no longer accessible while proxying, regardless of role combination. | |