2413 rfd

From UG

(Difference between revisions)
Jump to: navigation, search
(Requirements and Solutions: added links to CT bo)
(Requirements and Solutions: updated example of error message)
Line 11: Line 11:
** The system must allow each of the dates to be the same as the previous date or more.
** 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.  
** 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.  
-
*** ''Text of message:'' '''<Next date>''' cannot be confirmed until '''<previous date>''' has been confirmed.
+
*** ''Generalized example of error message:'' '''<Next date>''' cannot be confirmed until '''<previous date>''' has been confirmed in '''<CT #XXXXXX>'''.
-
*** ''Example:'' Actual arrival date cannot be confirmed until actual departure date has been confirmed.
+
*** ''Specific example of error message:'' '''Actual arrival date''' cannot be confirmed until '''actual departure date''' has been confirmed.
 +
*** CT # should be specified in error message:
 +
**** If it is part of Group and selected for Group saving.
 +
**** If it is part of Master.
** NOTE: Validations of estimated dates are no longer required.
** NOTE: Validations of estimated dates are no longer required.

Revision as of 01:29, 1 February 2011


Contents

Info

  • mantis 0002413: [Ops Misc Dates] Date Validation

Requirements and Solutions

  • Task type: Tweak.
  • Where: Actual CT Dates.
  • What: System should validate the chronological order in the specific sequence for all actual 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: Actual arrival date cannot be confirmed until actual departure date has been confirmed.
      • CT # should be specified in error message:
        • If it is part of Group and selected for Group saving.
        • If it is part of Master.
    • NOTE: Validations of estimated dates are no longer required.

Details

  • Specific sequence of validating dates is conditioned on the set of events 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.

Architect Review

Implementation Notes

QA Plan

History

Personal tools