1. ALL REGIONS
FEATURES
Enhacements
[#81838] Missing Time Report Update
Improved the accuracy of the Missing Time Report so it only flags users as missing time within their actual employment dates.
Previously, users could incorrectly continue to appear on the report for missing time before their start date or after their end date, regardless of their status in Agresso. Now, missing time is only shown between a user’s correct start and end dates. To remove a user from the report entirely, their Agresso link must be removed and their timesheet requirement turned off (Timesheet Required set to No or Min Timesheet Hours set to 0). Suspending a user alone will not remove them from the report.
[#81039] FE: Improve Finance Document Messaging – Finance Document Line Limit
Fixed an issue where Estimates, POs, and Invoices with more than 300 rows could silently lose data — rows beyond the limit were being removed on save without any warning. Now, once a document reaches 300 rows, all “Add Row” controls are disabled with a message explaining that the maximum has been reached and rows must be removed to add more. If a document somehow exceeds 300 rows, saving, submitting for approval, or approving will now show a clear validation error instead of silently deleting rows.
[#80067] Feature: Export modal column order
Improved the Export modal on Finance Detail Report, Finance Summary Report, Time Report, Pending Approval, and Missing Time so the column order shown in the modal now correctly matches the order set in the grid.
Previously, reordered columns could appear out of sync or revert unexpectedly — on Finance Reports this happened after a page refresh, and on Time Report it happened immediately when reopening the Export modal.
Now, if you reorder columns in the grid, that order is reflected correctly in the Export modal for the rest of your session. As before, column order is not saved permanently and will still reset to default after a page refresh.
[#79616] Finance Builder: Description character limit improvement
Fixed an issue where invoice data sent to Agresso could fail due to the Category Title field exceeding Agresso’s character limits. The Category Title field now enforces a 200-character limit, with the field’s hint text updated to show “Category Title (200 char limit)” and text automatically cut off if it exceeds this limit. Additionally, data sent to Agresso (such as PO number and invoice descriptions) is now truncated to 200 characters on the backend to ensure invoices submit successfully without errors.
[#74284] FE: Add validation to change office
Added a warning when moving a user’s Primary Office in Address Book > Users to a different finance profile, helping prevent timesheet and payroll issues caused by moving users outside the Admin Tool. Pronto helpdesk now see a reminder to use the Admin Tool, with options to either proceed anyway or open the Admin Tool directly in a new tab.
Everyone else will see a message advising them to contact Pronto Support to move the user via the Admin Tool, with the option to close the warning and continue. Moves within the same finance profile continue to save without any warning shown.
FIXES
[#82364] Fix: Resubmit on Error Report does not work
Fixed an issue where the Resubmit button on the Error Report page was not working. Resubmit (and Resolve) now function correctly on both the Error Report and Timesheet Submission Error Report pages.
[#81816] Project Details widget swaps labels and values and has lines misaligned
Fixed a display issue in the Project Details widget on the Project Summary tab where labels and values could appear misaligned or swapped, particularly for legacy projects. Labels now consistently appear on the left with their corresponding values on the right, ensuring fields like Status and Timesheet Status display correctly.
[#81719] Fix – Enable Partial Editing of Stage Settings for In Progress Stages (Unlock Decision Rule and Deadline)
Copilot said:
Users can now open Stage Settings for review stages that are In Progress and continue updating governance-related settings such as Decision Rule and Deadline without disrupting the active workflow. Trigger Settings, trigger conditions, and stage dependencies remain locked and clearly identified as non-editable, with guidance provided when users attempt to interact with them. Changes to editable fields are saved and audited, while Completed stages continue to remain fully read-only.
[#79681] BE: Job API not setting Custom Fields in Project List
Fixed an issue where Custom Field values set when creating a project via the Job API were not appearing in the Project List, even though the values were correctly saved and visible on the project itself.
Custom Field values (such as Client Contact, Agency Contact, Alternate Job Extension, Alternate Job Title, Client PO, PIA Number, and Project Sale Status) submitted through the Job API now display correctly in the Project List without requiring a manual update to the project details.
[#81804] Fix – UX Update for Stage Header in Review Settings & Review Detail
Expand/collapse functionality is now restricted to the chevron control only, preventing accidental stage expansion when interacting with other header elements. New hover states, tooltips, cursor feedback, and visual affordances have been added to status, trigger, decision rule, settings, and start-stage controls, while alignment and spacing have been updated, improving usability and discoverability throughout the review workflow.
[#81576] Integrate Expanded Review Triggers with Review Template Storage and Application
Review Templates now fully support the enhanced Review Trigger framework, ensuring that all trigger configurations are saved, persisted, and restored when templates are reused. Templates created with the new trigger model will accurately retain all trigger settings, while legacy templates remain compatible and automatically apply default values for newly introduced fields. This update improves consistency between Review Trigger configuration and template-based review creation, reducing the risk of missing or incomplete trigger setups.
[#81556] Fix: Duplicated users in the Notify Reviewers modal
The Notify Reviewers modal now correctly displays each reviewer only once, preventing duplicate user entries from appearing when a project team member is also assigned as a reviewer. This fix ensures the reviewer notification list accurately reflects the unique users associated with the review, providing a clearer and more reliable experience when sending review notifications.
[#79636] Review Details screen: Incorrect message after deleting an edited comment in Ziflow
The Review Details activity feed now displays accurate messaging when proof comments are edited and then deleted. Activity entries correctly reflect the final action performed on a comment
.