Constraints on Estimated Dates

From UG

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Category:Ops Common == Info == === Parent Mantis === * mantis [http://ct.jaguarfreight.com/mantis/view.php?id=0100 0100] === Scope of this wiki === Add constraints and vā€¦')
(ā†’SOW 1)
Line 16: Line 16:
Core requirements:
Core requirements:
 +
 +
* '''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.
 +
 +
=== 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:
 +
 +
==== FCL shipments ====
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Notification_Date Notification date].
 +
* [http://ct.jaguarfreight.com/wiki/Container#Actual_Export_Pick_Up_Date Actual collection date]. ''Only required to be filled in if an estimated collection date is filled in.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Origin_Terminal_Actual_Date Origin terminal actual date]. ''Only required if radio button is set to yes indicating the origin terminal is different from the port of loading.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Port_Of_Loading_Actual_Date Port of loading actual date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Trans_Shipment_Actual_Date Port of trans-ship actual date]. ''Only if check box is checked indicating this record has a trans-shipment point.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Port_Of_Discharge_Actual_Date Port of discharge actual date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Destination_Terminal_Actual_Date Destination terminal actual date]. ''Only if radio button is set to yes indicating the destination terminal is different than the port of discharge.''
 +
* [http://ct.jaguarfreight.com/wiki/Container#Actual_Delivery_Date Actual delivery date] or [http://ct.jaguarfreight.com/wiki/CT_bo#Delivery_Comment delivery comment].
 +
 +
==== LCL shipments ====
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Notification_Date Notification date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Actual_Export_Pick_Up_Date Actual export pickup date]. ''Only if the estimated export pickup date is entered.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Origin_Terminal_Actual_Date Origin terminal actual date]. ''Only if radio button is set to yes indicating it would differ from Port of Loading actual date.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Port_Of_Loading_Actual_Date Port of loading actual date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Trans_Shipment_Actual_Date Port of trans-ship actual date]. ''Only if check box is checked indicating this record has a trans-shipment point.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Port_Of_Discharge_Actual_Date Port of discharge actual date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Destination_Terminal_Actual_Date Destination terminal actual date]. ''Only if radio button is set to yes indicating the destination terminal is different than the port of discharge.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Actual_Delivery_Date Actual delivery date] or [http://ct.jaguarfreight.com/wiki/CT_bo#Delivery_Comment delivery comment].
 +
 +
==== Air shipments ====
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Notification_Date Notification date].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Actual_Export_Pick_Up_Date Actual export pickup date]. ''Only if the estimated export pickup date is entered.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Airport_Of_Departure_Actual_Date Airport of departure actual time of departure].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Trans_Shipment_Actual_Date Trans-shipment airport actual time of departure]. ''Only if check box is checked indicating this record has a trans-shipment point.''
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Airport_Of_Destination_Actual_Date Airport of destination actual time of arrival].
 +
* [http://ct.jaguarfreight.com/wiki/CT_bo#Actual_Delivery_Date Actual delivery date] or [http://ct.jaguarfreight.com/wiki/CT_bo#Delivery_Comment delivery comment].
 +
 +
==== Trucking shipments ====
 +
''NOTE: Validations of Trucking CT dates will be specified later in separate mantis.''

Revision as of 20:17, 23 November 2011


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

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:

FCL shipments

LCL shipments

Air shipments

Trucking shipments

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

Retrieved from "https://wiki.jaguarfreight.com/Constraints_on_Estimated_Dates"
Personal tools