Constraints On Dates (feature)
From UG
Contents |
Parent Mantis
Business Need
We have a number of constraints / validation rules that we need to enforce for dates.
Requirements
All detailed requirements have been translated into specifications - see below.
Technical Specification
Summary
List of constraints on dates:
- # Order Constraint Based On Shipment's Path
- # Order Constraint Based On Pre-conditions
- # Actual Date Can Not Be A Future Date Constraint
User Interface and Functionality
List of dates in their Natural Order
AIR:
[no1] [I] [----------------] ( Act) Created on Date [no2] [I] [----------------] ( Act) Notification Date [no3] [I] [----------------] ( Act) Authorized on [no4] [I] [COLLECTION EVENT] (Est / Act) Pick-up date [no5] [M] [DEPARTURE EVENT ] (Est / Act) Airport of Departure [no6] [M] [----------------] (Est / Act) Trans-shipment Airport [no7] [M] [ARRIVAL EVENT ] (Est / Act) Airport of Discharge [no8] [I] [----------------] ( Act) Customs Status Date [no9] [I] [----------------] ( Act) FDA Status Date [no10][I] [DELIVERY EVENT ] (Est / Act) Delivery Date
LCL/FCL:
[I] [----------------] ( Act) Created on Date [I] [----------------] ( Act) Notification Date [I] [----------------] ( Act) Authorized on [I] [COLLECTION EVENT] (Est / Act) Pick-up date, Container 1 [I] [COLLECTION EVENT] (Est / Act) Pick-up date, Container 2 (FCL only) ... [I] [COLLECTION EVENT] (Est / Act) Pick-up date, Container N (FCL only) [I] [DEPARTURE EVENT ] (Est / Act) Origin Terminal [M] [--------------- ] (Est / Act) Port Of Loading [M] [----------------] (Est / Act) Port Of Trans-shipment [M] [----------------] (Est / Act) Port Of Discharge [I] [ARRIVAL EVENT ] (Est / Act) Destination Terminal [I] [----------------] ( Act) Customs Status Date [I] [----------------] ( Act) FDA Status Date [I] [DELIVERY EVENT ] (Est / Act) Delivery Date, Container 1 [I] [DELIVERY EVENT ] (Est / Act) Delivery Date, Container 2 (FCL only) ... [I] [DELIVERY EVENT ] (Est / Act) Delivery Date, Container N (FCL only)
Order Constraint Based On Shipment's Path
"On save" check the following order. See #List of dates in their Natural Order.
no1 <= no2 <= no3 <= ...
If order is incorrect the show pop-up: "In CT#XXX, date <date name> can not be <earlier/later> than date <date name>" [OK].
Actual Date Can Not Be A Future Date Constraint
If user is trying to set any actual dates (see below) to the future date system must issue pop up: "Error while saving: <name of the date> can not be in the future [OK]".
List of actual dates in the system
UNDEF:
- Gentab.Actual export pickup
Truck-Dom:
- Gentab.Actual export pickup
- Gentab.Actual Delivery
Truck-Air:
- Gentab.Actual export pickup
- Gentab.Actual Delivery
Truck-Ocn:
- Conttab.Containers.ContainerX.Actual collection
- Conttab.Containers.ContainerX.Actual Delivery
AIR:
Gentab:
- Actual export pickup
Exptab:
- Airport of Departure. ATD
- Trans-shipment Airport.ATD
- Airport Of Destination. ATD
ImpTab:
- Actual Delivery Date
LCL:
Gentab:
- Actual export pickup
Exptab:
- Origin Terminal ATD
- Port Of Loading ATD
- Port Of Trans-shipment ATA
- Port Of Discharge ATA
- Destination Terminal ATA
ImpTab:
- Actual Delivery Date
FCL:
Conttab.Containers:
- ContainerX.Actual collection
- ContainerX.Actual Delivery
Exptab:
- Origin Terminal ATD
- Port Of Loading ATD
- Port Of Trans-shipment ATA
- Port Of Discharge ATA
- Destination Terminal ATA
Entities and Attributes
Special Cases and Misc
Look And Feel
Figures
Figure: XXX
History
Non Critical Bugs and RFC
bug1) error is not specific to what date in what CT there is a problem
bug2) even if problem with ordering of actual dates system complains about "estimated"
