2413 rfd

From UG

(Difference between revisions)
Jump to: navigation, search
(Requirements and Solutions: updated example of error message)
(Details: renamed "Details" section to "Specific sequence of validating dates")
 
(One intermediate revision not shown)
Line 13: Line 13:
*** ''Generalized example of error message:'' '''<Next date>''' cannot be confirmed until '''<previous date>''' has been confirmed in '''<CT #XXXXXX>'''.
*** ''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.
*** ''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:
+
*** CT # should be indicated in the error message:
-
**** If it is part of Group and selected for Group saving.
+
**: 1) If CT is a part of Group and date field what out of order is selected for "Group save".
-
**** If it is part of Master.
+
**: 2) If CT is a part of Master.
** NOTE: Validations of estimated dates are no longer required.
** NOTE: Validations of estimated dates are no longer required.
-
=== Details ===
+
=== Specific sequence of validating dates ===
* Specific sequence of validating dates is conditioned on the set of events the shipment.
* 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:
* Each event corresponds to the date of shipment depending on the mode of transport:

Current revision as of 10:42, 1 February 2011


Contents

[edit] Info

  • mantis 0002413: [Ops Misc Dates] Date Validation

[edit] 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 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 no longer required.

[edit] Specific sequence of validating dates

  • 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:

[edit] FCL shipments

[edit] LCL shipments

[edit] Air shipments

[edit] Trucking shipments

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

[edit] Architect Review

[edit] Implementation Notes

[edit] QA Plan

[edit] History

Personal tools