1. ALL REGIONS
FEATURES
[1984] AUTO APPROVAL OF TIMESHEETS
1) Finance Profile Auto Approval Rules:
We replaced the Auto Approval Settings in the Finance Profile with the Auto Approval Rules by Office. The settings in the Finance Profile have been removed, and the old scheduler has been disabled.
2) Approval Rules Based on the Office of the Project:
The old feature auto-approved timesheets based on the rules of the Finance Profile of the User’s Primary Office. The new feature auto-approves timesheets based on the rules of:
- The Office of the Project
- The Employee Type of the User
This means that each Office governs how time is approved for projects originating from their office.
3) Compatibility with Agresso and Non-Agresso Agencies:
The old feature only auto-approved time for Agresso-linked Offices. The new feature is compatible with all offices that submit timesheets.
4) Auto Approval Rules Based on User’s Employee Type:
The old feature treated all timesheets the same, regardless of employee type, except for UK users, who had a hardcoded rule for immediate approval for “Regular Employees” and required approval for “Freelancers”.
The new feature allows you to set different approval rules based on the user’s Employee Type.
- For Agresso Linked Users, Employee Type comes from the Staff Feed in Agresso (via TalentSpace in the US).
- For Non-Agresso Users, this needs to be manually set in the User Record. New Users are created with an Employee Type of “Regular Employee” by default.
5) Approval Exceptions & Rules:
When you enable Auto Approval, you have the option to add exceptions and rules:
- An exception to always require approval for Non-Charge Time (Agresso Linked offices only).
- An exception to always require approval based on certain Finance Types (Agresso Linked offices only).
- The option to “Skip Weekends”. For example, if you have set auto-approval after 2 days and the user submitted time on Friday, the time would only auto-approve on Tuesday/Wednesday.
- The option to “Skip Office Holidays”. For example, if your office had a holiday for Christmas and Boxing Day and time was submitted on the 24th, it would start to count the days after Boxing Day.
5) Date Limit
If an office has never used auto-approval of timesheets in Pulse and decides that they want to turn it on, we only go back 180 days from the submitted date (not the timesheet date) i.e. from the date the user clicks “submit timesheets”.
If the office decides to enable “approve immediately” this will only be for new timesheets. We do not go back to auto-approve historic timesheets in this case.
6) Pending Timesheets
Auto-approval of timesheets only auto-approves timesheets that have been submitted. Any timesheets that are ‘saved’ or ‘rejected’ will be ignored.
ENHANCEMENTS
[#66038] FE: LABEL CHANGES IN TIMESHEETS
In this release, we have updated the labels in the User Settings > Timesheet Tab for clarity and consistency.
- From: DEFAULT TIMESHEET ACTIVITY -> To: TIMESHEET ACTIVITY
- From: ADDITION TIMESHEET ACTIVITY -> To: ADDITIONAL TIMESHEET ACTIVITY
[#65564] BE: LOCK TIMESHEETS AFTER THE USERS END DATE
In this release, we’ve addressed an issue that caused over 165 errors for users attempting to add and submit time after their termination from the company. The problem stemmed from the Timesheet End Date validation logic, which was not consistently applied to all users.
Key Changes:
- Validation Adjustment: Previously, the codebase only correctly applied the end date checks to Agresso users with ledgers of either HH or HW. This led to errors for users with different ledger types.
- Removal of Ledger Check: To resolve the issue, we have removed the ledger check from the validation logic, ensuring that the Timesheet End Date is consistently validated for all users, regardless of ledger type.
FIXES
[#64923] BUG: AUTO REQUEUE FOR THE NEW INSTANCE ISN’T WORKING AS EXPECTED
This release addresses an issue with the auto requeue feature, which was not functioning as expected, leading to a failure. However, upon subsequent attempts, the issue is resolved. This was affecting timesheets that needed to be processed across Agresso Instance.
The issue occurred because when the restarted job was sent, it initiated a new job on a different queue worker, potentially leading to immediate processing before the previous job had fully set up the period to be processed.
The issue has been resolved to ensure that the auto requeue feature functions correctly on the first attempt, without requiring subsequent reprocessing.
2. UK
ENHANCEMENTS
[#64480] ENHANCEMENT: INVOICE BASELINE SYNC IS SLOW DUE TO PROCESSING DELETED ITEMS
We’ve made improvements to the Invoice Baseline sync, also known as Supplier Expense or Supplier Invoice sync. This sync brings Supplier Expense lines into Pulse from Agresso for use in the Invoice Composer, facilitating the passing on of agreed Supplier costs to the Client.
Key Changes:
- Handling of Missing Information: Previously, missing information in the agresso_supplier_invoices table was marked as “available = ‘n'”. We’ve updated the sync to change the way it handles marking these entries as ‘not available’.
- Enhanced Processing: The sync now excludes items marked as ‘not available’ during processing, ensuring more accurate handling of Supplier Expense lines from Agresso.
[#64573] BE: ADD MAGNITUDE CODE TO THE BRANCH SYNC
Sync Magnitude Code from Agresso to Pulse from the Branch Sync.