Constraints On Dates (feature)

From UG

Revision as of 17:31, 11 January 2010 (edit) Alex (Talk | contribs) (→User Interface and Functionality) ← Older edit		Revision as of 17:32, 11 January 2010 (edit) (undo) Alex (Talk | contribs) (→Should not be able to set ANY actual date beyond the current date) Newer edit →
Line 24:		Line 24:
	=== User Interface and Functionality ===		=== User Interface and Functionality ===
-	==== Should not be able to set ANY actual date beyond the current date ====	+	==== Actual Date can not be a future date ====
	=== Entities and Attributes ===		=== Entities and Attributes ===

---

Revision as of 17:32, 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 Actual Date can not be a future date 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.

Requirements

All detailed requirements have been translated into specifications - see below.

Technical Specification

Summary

List of constraints on dates:

• # Dates order based on shipment path
• # Dates order based on shipment milestones
• # Actual Date can not be a future date

User Interface and Functionality

Actual Date can not be a future date

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure: XXX

History

Non Critical Bugs and RFC

DB