Precursive Connect 1.25 – Extended Release Notes and Enablement Guidance

This article provides a deeper look at the key improvements delivered in Precursive Connect 1.25. It is intended for customers, admins, and power users who want to understand what changed, how new capabilities work, and enablement guidance on how to successfully rollout these changes. Version 1.25 introduces fixes to Planned Hours accuracy when distributing effort across long-duration Tasks and Bookings, ensuring totals always match Task estimates and eliminating negative or inflated hour values.

  • 20-Feb-2026
  • Knowledge
Available forOBXPSXLearn more

Title
Precursive Connect 1.25 – Extended Release Notes and Enablement Guidance
URL Name
Precursive-Connect-1-25-Extended-Release-Notes
Body

Accurate Planned Hours for Long-Duration Tasks and Bookings

Highlights

Planned Hours now remain consistent with Task estimates when effort is distributed across long-duration Tasks and Bookings, eliminating negative values and rounding overages that previously caused incorrect totals.

What Changed

When Task effort was distributed across a large number of Bookings or Timesheet Entries, rounding could cause the total distributed hours to slightly exceed or fall short of the Task estimate — resulting in negative Planned Hours on the first entry, or small discrepancies in totals. Both Booking Mode and Task Mode are now corrected so that the sum of distributed hours always matches the Task's Estimated Hours exactly.

How It Works

  • For example: spreading 6 Estimated Hours across 229 working days previously rounded each day up to 0.03 hours, giving a total of 6.87 hours — and corrected by setting the first entry to a negative value
  • Daily hours now round down (e.g. 0.02 hours/day), and any positive remainder is applied to the first Booking or Timesheet Entry — so the first entry may be slightly higher than the others, but the total always matches the Task estimate
  • Similarly, in Task Mode, where two Bookings of 3.75 hours each could previously sum to 7.44 hours due to rounding, the system now explicitly calculates and applies the remainder so the total is always 7.50

Enablement Guidance

No manual steps necessary.

Data Model

No changes in the Data Model in 1.25 release.

Review all Release Notes.

Was this article helpful?
Upload Files