Constraints on Estimated Dates

From UG

Revision as of 20:41, 23 November 2011 by Denise (Talk | contribs)
Jump to: navigation, search


Contents

Info

Parent Mantis

Scope of this wiki

Add constraints and validations for estimated dates. Not allowing updates out of specified chronological order and for them to work in conjunction with the actual date validations that are already in place.

SOW 1

Mantis: 3185 (CT2 Misc) Add Estimated Date Validation

Core requirements:

  • Task type: Tweak.
  • Where: Estimated CT Dates.
  • What: System should validate the chronological order in the specific sequence for all estimated dates.
    • The system must allow each of the dates to be the same as the previous date or more.
    • If an attempt is made to confirm a date out of order an error message should be generated and the date should not be saved.
      • Generalized example of error message: <Next date> cannot be confirmed until <previous date> has been confirmed in <CT #XXXXXX>.
      • Specific example of error message: Estimated arrival date cannot be confirmed until Estimated departure date has been confirmed.
      • CT # should be indicated in the error message:
      1) If CT is a part of Group and date field what out of order is selected for "Group save".
      2) If CT is a part of Master.
    • NOTE: Validations of estimated dates are not subject to Actual Date validations.

Specific sequence of validating dates

  • Specific sequence of validating dates is conditioned on the set of events for the shipment.
  • Each event corresponds to the date of shipment depending on the mode of transport:

FCL shipments

LCL shipments

Air shipments

Trucking shipments

NOTE: Validations of Trucking CT dates will be specified later in separate mantis.

Personal tools