Version 1.25
Improvements:
- Accurate Planned Hours for Long-Duration Tasks: Resolved an issue where Planned Hours could appear as negative when effort was distributed across long-duration Tasks. Planned Hours now remain consistent with the Task estimate, avoiding over-allocation or negative adjustments.
- Example: Previously, spreading 6 Planned Hours across 26 working days rounded daily effort to 0.24 hours, pushing the total to 6.24 hours. The system then subtracted the extra from the first day, sometimes resulting in a negative value.
New Behaviour: Daily effort rounds down (e.g., to 0.23 hours), keeping the total within the 6-hour estimate. Any remaining time is applied to the first day without creating negative values.
- Planned Hours Move Correctly When Rescheduling Tasks: Rescheduling a Task now updates Planned Hours as expected. If a Task is moved to a new date, Planned Hours shift with it—avoiding duplicates and keeping totals consistent with the Task estimate.
- Example: Previously, logging time on a Task and then rescheduling it caused Planned Hours to stay on the original date and also appear on the new date, doubling the Planned Hours total (e.g., from 8 to 16 hours).
New Behaviour: Planned Hours now move to the new date with the Task, provided no Actual Hours exist on the original date. The total always matches the Task estimate
Version 1.24
Improvements:
- Managed Mode Improvements: Scenarios were identified where effort for a single Resource on a Phase across consecutive days with different levels of effort per day were being blended into a single Booking.
- Example: John was assigned to a Task on Monday for 4 Hours, and a Task on Tuesday for 8 Hours would result in a two day booking totalling 12 hours.
- New behaviour: Distinct Bookings will be created when effort across multiple days is different. The above example will now result in one 4 hour Booking for Monday and a second 8 hour Booking for Tuesday.
Version 1.23
Improvements:
- New Lookup field from the Phase to Board: when a Board is created related to a Phase a Lookup will be populated from the Phase to the Board. This allows Fields and Related Lists to be referenced from the Phase. Create new Phase Lightning Layouts to include fields and related lists from the Board.
- Resolved issue with Rounding issue with Hours on Bookings in Managed Mode when transforming Tasks into Bookings.
- Resolved issue with Precrusive 2.0 Task Template validation failing when Precursive OBX Licenses are Suspended.
Version 1.22
Improvements:
- Improved performance of BuildBookingsFromBoardsBatch background process.
Version 1.21
Improvements:
- Improved performance of BuildBookingsFromBoardsBatch background process.
Version 1.20
Improvements:
- Improved Visibility & Calculation of Resources Availability on the Precursive Plan: we are changing the approach to creating Bookings that overlap non-working days when Projects are resources in Managed Mode (Task-based resourcing). Tasks scheduled for a period that overlap a Resource non-working days are now split into multiple Bookings to reflect the Resource actual capacity on their working days. Unless a Task is specifically scheduled for their non-working days, Bookings are created for their working ones.
In the picture below you can compare a Project that has been updated after installing version 1.20 and one that is yet to be updated.
If we change the Capacity Mode to show Bookings as 'Hours per Day', you can see that the calculations are correct in the updated Project as the capacity is showed over 5 days instead of 7.
Note: To prevent Bookings to be created for your Resources non-working days, please make sure you review your Application Settings in Precursive OBX.
- Navigate to the Precursive OBX tab
- Click on the wrench icon on the bottom left to access 'Application Settings'
- Go to the 'Scheduling' tab
- Under 'Business Days' either enter 'MONFRI' to setup your org default working days from Mon to Fri or enter a customer Business Hours ID (previously setup in your Salesforce org)
Version 1.18
Improvements:
- Resolved issue with BuildBookingsFromBoardsBatch background process when receiving an error: "ENTITY_IS_DELETED".
- Resolved issue with error when updating Activity Category without a Task.
Version 1.17
Improvements:
- Resolved issue with Template Import failing.
Version 1.16
Improvements:
- Resolved issue with adding multiple Time Logs there is an exception: Row with duplicate Id at index: x
Version 1.15
Please see Precursive Winter Release '22 for more information.
New Features of the Precursive Connect Package
- Two ways synchronization between Time logs on Tasks and Timesheets: from the Winter '22 Release, the time that you log against Precursive Tasks is not only synchronized from your Time logs on Tasks onto the Timesheet but also from your Timesheet back to your Time Logs on Tasks. That means that whenever you miss logging your time against a task, you will still be able to do it from your timesheet before submitting it. Note - if you have overridden your time logs data on your current timesheets before the upgrade and then edit it after the upgrade, these entries will not synchronize back to Time Logs. All Timesheet Entries that were not overridden from the Timesheet page will synchronize accordingly to your edits. Please see Time Logs Synch between Tasks and Timesheet Entries for more information.
Related Resources
How to upgrade to the latest Precursive Platform version?
