This month’s release brings several impactful improvements across job setup, reporting, billing, and internal controls.
As these fixes do not require separate documentation, instead this article includes more detailed descriptions for a change. It’s to help you understand how each change affects your workflow.
Job-type selection clarity
What changed:
Job-type dropdowns now display both the job type code and description. This is enabled when using the new UI is enabled. This helps users distinguish between similarly named job types.
Example:
- ALM01 – Alarm Response
Why it matters:
This reduces errors during setup and dispatching, especially in environments with many similar job types.
-> A similar update has been added to the Job Type visibility article.
Decimal support in contracted hours
What changed:
You can now enter decimal values (up to two decimal places) in the Contracted Hours field when creating or editing contracts.
Why it matters:
This allows for more accurate tracking and reporting, especially for contracts with non-whole hour requirements (e.g., 37.5 hours).
Controls to prevent self-approval
What changed:
Administrators can now be restricted from approving their own shifts or creating ad-hoc pay items for themselves.
Why it matters:
This strengthens internal controls and reduces the risk of unauthorized approvals.
Report recommendations
What changed:
AI-driven recommendations are now available to help users improve report quality. These suggestions highlight missing or unclear information before submission.
Why it matters:
Helps users submit more complete and professional reports, reducing follow-up and improving operational oversight.
-> A short mention of this can be found in Understand and use ReportPro AI.
Billing exports – performance improvement
What changed:
A date-range filter has been added to the batch export tool, allowing users to export only relevant time periods.
Why it matters:
This significantly improves export speed and system stability, especially for large datasets.
-> For future reference, we also updated the Billing: Prepare in Batch article.
Activity feed loading fix
What changed:
Resolved an issue where the activity feed failed to load when logged into a parent region with many sub-regions.
Why it matters:
Ensures consistent visibility into recent activities across all regions.