First to Site
Release 3.1

Manage Delays - Expected Date Logic

Fixed resubmitted expected date handling

Problem

The Manage Delays function was not correctly handling resubmitted expected dates. When used, it would blank out the old expected date without linking to the resubmission date.

From the Chatlogs

Reported as day-one feedback from users on Feb 6:

"Manage Delays button does not change the resubmitted expected date. (blanks out old expected date. Doesn't appear to be linked to resub date)" - User feedback

The issue persisted beyond the initial project fix - Matt flagged on Feb 8:

"Manage delays function is fixed for the original project but not for the rest of the platform regarding resubmitted projects/dates."

Root Cause

Jayrex identified the root cause as an incomplete implementation in the resubmission logic:

"There are separate paths for customer resubmissions and FTS/admin resubmissions. However, part of that split was only partially completed. As a result, some customer-resubmitted orders were hiding the resubmitted expected date in the UI, even though the correct value was already stored in the database."

Fix

  • Corrected the Orders tab display so delay indicators appear in the correct context
  • Removed the condition that hid resubmitted expected dates for customer resubmissions
  • Standardised that both customer and admin resubmissions consistently reflect the active resubmitted timeline

Impact

Restored reporting and tracking accuracy for delayed and resubmitted orders.