1. All Regions
Enhancements
[#69765] BE: Use the correct agreement to close the project
We implemented an update to ensure the correct agreement is used when closing projects for Global Workers, improving consistency in how projects are completed across various brands and products. Now, when projects meet specific agreement conditions, the system will automatically handle the closure process based on these settings:
- Close Pending Approval: Some projects will prompt users to confirm if a linked “Phantom Job” should also be closed.
- Create Amendment: Certain projects will generate an amendment request to close related jobs after approval.
- Remain Active: For projects where closure is not needed, the “Phantom Job” will stay active as required.
This enhancement reduces manual steps, making project closures more seamless and accurate for Global Worker agreements.
Fixes
[#69123] Bug: Finance Summary Report – INVOICE search bar not working
We fixed an issue with the search functionality in the Finance Summary Report and Finance Detail Report under the Invoices tab. Previously, users could only find invoices by entering the invoice number without the prefix “IN_” (e.g., entering “662431” instead of “IN_662431”). Now, the search will recognise and display results for both formats, allowing users to search using the full invoice number, with or without the “IN_” prefix, ensuring consistency and accuracy across all invoice search results.
[#67597] Phantom Job: Name is incorrect
We resolved an issue where Phantom Job approval emails were mistakenly addressing the invited user instead of the actual recipient. Now, the email correctly addresses the person receiving it, ensuring clarity and accuracy in communication.
[#70281] FE: Unable to re-enable agreements
We fixed an issue where re-enabling agreements between two offices would incorrectly trigger a “not unique” error, even when each agreement was unique.
[#70328] Bug: Error when modifying hours on existing booking
Fixed an issue where you got an error “The RequestedBy.O must be an integer.” When editing then saving a booking.
Features / Enhancements / Fixes
2. US
[#69683] BE: Alien User Name not populated correctly.
We resolved an issue with usernames in Agresso reports where some entries created from Pulse were showing only the first name, missing the preferred last name for new users. Now, both the preferred first and last names will display correctly in all reports and browsers, ensuring full names appear consistently across Agresso. This update improves name accuracy and helps users identify resources more easily in reporting.
3. TECH DEBT
[#64721] Move Estimate Accounts Sync to V2
We upgraded the existing Estimate Accounts sync from v1 to v2 for UK and EU clients, ensuring more reliable daily synchronization of estimate account data with Agresso. This update includes enhanced scheduling, optimized performance, and better permissions management. The new sync also provides more precise error handling, gracefully exiting if a sync is attempted with unsupported profiles.
[#64728] Move Supplier Sync to V2
We upgraded the Agresso Supplier sync from v1 to v2 for UK and EU profiles, enabling more efficient supplier data updates every two hours. The refactored sync includes improved permissions, better handling of missing records, and soft deletion capabilities for managing suppliers no longer active in Agresso.
[#70107] Inconsistencies in the API
We fixed an issue with the Customer Sync process to ensure that it accurately updates the audit table and displays the correct schedule in the system. Previously, some inconsistencies prevented London’s sync schedule from displaying correctly, showing mismatched values.
[#70217] Division By Zero Error
We resolved a critical error that was causing issues with job progress calculations. Previously, if the project budget was zero or negative, users encountered a “division by zero” error, which disrupted operations and led to system errors.
- The system now handles cases where the budget is zero or negative by setting the progress to a capped value, avoiding errors.
- Progress calculations are now more reliable, even when budget data is missing or unusual.
[#70394] Bug: Green Flag check failing
We addressed an issue in the InvoiceService where an undefined key error occurred when checking for the “AgressoQE” value. This error was caused by the assumption that this key would always be present, leading to system disruptions.
- We implemented enhanced checks in the isGrnFlagSet method to ensure that if the “AgressoQE” key is missing, the system will safely return false instead of throwing an error.
- This fix ensures that users can create and manage purchase orders without encountering unexpected errors, improving the overall stability and reliability of the invoicing process.
[#70397] Agresso Sync Schedule displaying the incorrect type
The Sync Schedule page will now correctly display the ‘type’ value as ‘profile’ for the selected sync name ‘Activities.’ This ensures that users receive accurate information and can rely on the data being presented.