2.40 Release overview

We added phone number validation for employee records to help keep contact data accurate and consistent. The system now checks phone number format when a phone number is added or edited in an employee profile. If the format is incorrect, users will see a validation error. This validation also works in forms and requests, such as onboarding and preboarding forms or personal data change requests. Existing employee records are not affected unless the phone number itself is updated.

We improved the file upload experience in Announcements by separating attachments into dedicated sections for photos and videos, and documents. This makes it easier to add the right type of files when creating a company announcement and keeps the upload flow clearer for users.

We expanded workflow filtering to support tag-based searches. On the Workflows page, you can now filter workflows by tags and select multiple tags to narrow down the list more easily.

When an HR publishes an announcement on the Home page, employees also receive it by email with a clickable button that takes them directly to the system. Email delivery depends on the employee’s hire date and available email address:

A new sidebar navigation is now available in the Requests tab. It separates requests into different types, making the page easier to navigate.

Each type of request now has its own section (for example: Self service request, People data change request, Vacancy request, Termination, etc.). This helps you quickly find and manage specific requests without scrolling through the entire list.

We added employee status to custom reports as both a filter and a column. This gives teams more flexibility to analyze data for specific employee groups, such as Hired, Employed, or Terminated employees, depending on the user’s permissions. Employee status can also be used in conditional rules.

We also added employment status to assignable rulesets, giving teams more flexibility when building rules based on employee lifecycle stage. This helps target processes and logic more precisely for groups such as hired, active, or terminated employees.

We added new effective date placeholders for workflow tasks and emails. These placeholders can now be used for job-related changes such as position, work type, work pattern, job profile, and job level, including current, previous, and upcoming effective dates. This helps teams prepare workflow messages and tasks related to promotions, progressions, and other upcoming employment changes more accurately.

Job profiles now include three new system fields – Minimum salary, Maximum salary, and Currency – plus a new Description tab to add role details.

The Compensation section has been moved from Core HR to Payroll in the UI, with no changes to data or user access.

We added more visibility to vacancy promotions by showing the date when a promotion was created or linked in the Promotion tab. This helps teams better track promotion status and makes troubleshooting easier when checking how and when a vacancy was connected to a promotion source.

The Pipeline statistics report now includes a Vacancy status filter with multi-select support. This makes it easier to focus reporting on open or relevant vacancies only and gives teams more accurate hiring insights when analyzing dates and other vacancy-related attributes.

In the Pipeline funnel report, the column previously called Created is now renamed to Applied on. This makes the report wording more accurate, because the date reflects when the candidate applied to the vacancy.

We expanded the Pipeline funnel export with additional identifiers: Vacancy ID, Vacancy request ID, and Candidate ID. These fields make it easier to connect funnel data with other exports and build more advanced analytics. We also updated some column names to reflect the data more clearly, including Candidate full name and Applied on.

Objective exports now include a Parent objective owner column. This helps teams better understand ownership hierarchy in exported reports and reduces the need for manual adjustments after export.

In performance review templates, the “Multiple Choice” question type is now called “Single Select”, making it clear that only one answer can be chosen.

You can now filter performance review cycles by a specific employee who is participating in the review or by the manager of the reviewee. This helps ensure that all required participants have been added to the review and that no one has been missed. It also allows you to quickly check in which review cycles a particular employee or manager has taken part. ✨

We improved the time tracking experience for companies that require employees to select a project or add a comment. The updated flow now handles cases where an employee is required to select a project but has no assigned projects more clearly. Validation messages were also improved to explain why clock-in cannot be started, which helps reduce confusion and incomplete submissions.

Employees can now submit overtime requests directly from the clock-in/clock-out widget. The request form is prefilled with the relevant date and time, so employees only need to add the required details and submit it. If the clock has been running for more than one day, the employee can submit overtime for the first day of the running clock entry. This makes overtime tracking more accurate and reduces manual corrections for HR.

We expanded overtime management with API and webhook support, making the Time module easier to connect with external systems and reporting tools. API endpoints now support overtime request creation, update, deletion, retrieval, and detailed view. Webhooks can notify external systems when an overtime request is created, updated, or deleted. This helps automate data exchange, reduce manual sync work, and support integrations such as reporting tools or Jira-based workflows.

We renamed several attendance labels in My attendance to make wording more consistent across the system. The tile previously called Remaining hours is now named Difference, and the column previously called Submitted, h is now named Worked.

Attendance exports now support decimal hour format. Before exporting, admins can choose whether hours should be shown in decimal format, such as 7.5 instead of 7:30. This is especially useful for payroll systems, financial reporting, customer billing, and any calculations based on exported attendance or project statistics. It also helps eliminate manual conversion and reduce payroll calculation errors.

We improved hourly leave requests by showing the employee’s planned work hours for the selected date based on their work pattern. When an employee requests leave in hours, the system now prepopulates the time according to their assigned work pattern, if working hours are defined there. If no specific work pattern hours are set, the standard hours are shown instead. This gives employees better visibility into their expected schedule and helps prevent mistakes when submitting hourly leave requests.

Custom fields are now supported for the Position table in the API. This means any additional fields you create for positions in the system can also be accessed through the API.

The get-employees API will add a new include_historical_values option, allowing retrieval of both current and historical custom field values, including their effective dates, in a single request.

API v3 now supports CRUD operations for Job profiles and Job groups with the endpoints: POST, GET, PUT, and DELETE for employee job profiles.