beqom PaySuite 28.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 28.0 release of the beqom PaySuite application and in the subsequent patches.
28.0
Deployment to staging environments: August 25th, 2026
Deployment to production environments: September 1st, 2026
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| AC-24655 | Data Foundation | On the back end, time-in-role can now be calculated on a calendar-month basis instead of only by exact days, with configurable rules for handling situations that start mid-month. Existing tenants keep the day-based calculation by default. | ||
| AC-29702 | Data Foundation | On the back end, Analytics Hub now supports deploying customer-specific reports alongside the standard report catalog without requiring a platform release; once a report is assigned to a tenant, existing tenant and row-level security controls continue to apply. | ||
| AC-30722 | Pay Transparency | Under Workbench > Platform Setup > Passport > Compensation > Digital reward statement, administrators can now configure the visibility of the Worker information widget as a whole, or show and hide its individual sections and fields, such as Work country, Work city, and other general information. The configured visibility is reflected on workers' digital reward statement pages. | ||
| AC-30933 | Data Foundation | Data Foundation data revisions older than one year are now automatically deleted by a monthly scheduled job. The anonymization process that already runs on personal data is unaffected; this only removes historical revision rows once they are more than a year old. | ||
| AC-31713 | Pay Transparency | HRBPs are now notified when a document moves to the HRBP review workflow step, whether that happens through a workflow change, a document import into a workflow-enabled round, or a bulk close-and-release action; bulk actions send a single combined notification instead of one per document. The notification's subject, body, and whether it is enabled at all can be configured from Workbench > Platform Setup > Email Notifications > Documents. | ||
| AC-32370 | Data Foundation | On the front end, under Workbench > Data Management > Situation & Absence Configuration, administrators can now set time-in-role to a calendar-month calculation basis instead of only day-based proration; the setting defaults to Days for existing tenants. | ||
| AC-32688 | Data Foundation | On the front end, Analytics Hub can now show customer-specific reports alongside the standard report catalog, visible only to the tenants they are assigned to; when a tenant has no customer-specific reports, the report tree is unchanged. | ||
| AC-32760 | Pay Transparency | The redundant Usage checkbox, which was always selected automatically, has been removed from the Create and Edit pages of Mapping under Workbench > Pay Transparency. | ||
| AC-32817 | Compensation Management | Previously, the Live Info drawer in a worker's Planner view failed with a server error on large tenants, and each attempt could drive the compensation service toward its memory limit, risking stability for other users on the same instance. The drawer's data access has been optimized so it now loads correctly for any population size without the excessive memory use. | ||
| AC-28000 | Performance Management | Previously, goals deleted in Performance Management were visible in the compensation round, so the round's goal count did not match what was shown there. Deleted goals, including a goal removed for one worker within a group goal, are now removed from the round as well. In-progress or completed goals remain unaffected. | ||
| AC-32616 | Data Foundation | The Goal description field, previously available only in the legacy Goal Details report, now also appears in the DataLake Goal Details report, next to Goal title. | ||
| AC-32864 | Performance Management | The Draft mode for goal results is now available for organizational goals whenever the result section is editable for the goal owner, rather than only when the owner also holds the Worker role in that goal type's authorized editors list. Previously, some organizational goal owners entered results with the draft mode unavailable, publishing values to the whole population immediately. | ||