Constraints On Dates (feature)

From UG

Revision as of 21:31, 11 January 2010 (edit) Alex (Talk | contribs) (→Non Critical Bugs and RFC) ← Older edit		Revision as of 21:35, 11 January 2010 (edit) (undo) Alex (Talk | contribs) (→Order Constraint Based On Shipment's Path) Newer edit →
Line 81:		Line 81:
	==== Order Constraint Based On Shipment's Path ====		==== Order Constraint Based On Shipment's Path ====
-	"On save" check the following rules. See [[#List of dates in their Natural Order]].	+	"On save" check the following order. See [[#List of dates in their Natural Order]].
-	1) Starting from the top of the list. Dates can be “same day” moving down, but a date cannot be “before” a date located “above”.	+	no1 <= no2 <= no3 <= ...
-	2) On the same level (actual and estimated) ther is no rule"	+	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 ====		==== Actual Date Can Not Be A Future Date Constraint ====

---

Revision as of 21:35, 11 January 2010

Contents 1 Parent Mantis 2 Business Need 3 Requirements 4 Technical Specification 4.1 Summary 4.2 User Interface and Functionality 4.2.1 List of dates in their Natural Order 4.2.2 Order Constraint Based On Shipment's Path 4.2.3 Actual Date Can Not Be A Future Date Constraint 4.2.3.1 List of actual dates in the system 4.3 Entities and Attributes 4.4 Special Cases and Misc 4.5 Look And Feel 4.6 Figures 4.6.1 Figure: XXX 5 History 6 Non Critical Bugs and RFC 7 DB

Parent Mantis

tbd

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"

DB