CT Dates
From UG
(Difference between revisions)
(→Ver 1.1) |
(→Ver 1.2) |
||
| Line 9: | Line 9: | ||
== Ver 1.2 == | == Ver 1.2 == | ||
* ss1 // Error pop-up we have now "Invalid ordering of dates" must clearly state what dates and in what CTs/Master have conflict. Right now it is very hard to find out when you get this error while changing date in Master Details Tab and that master have 10 CTs. | * ss1 // Error pop-up we have now "Invalid ordering of dates" must clearly state what dates and in what CTs/Master have conflict. Right now it is very hard to find out when you get this error while changing date in Master Details Tab and that master have 10 CTs. | ||
| + | |||
| + | == Ver 1.3 == | ||
| + | * ss1 // Block user from changing actual delivered date from empty to something for ANY container on container panel if there is at least one line in commodity table unassigned. | ||
| + | |||
| + | (This is done because it every commodity must be part of some container before it is delivered) | ||
[[Category:Ops]] | [[Category:Ops]] | ||
Revision as of 17:15, 12 October 2009
Contents |
Intro
This article covers:
- Common CT dates logic
- CT Dates Tab in CT profile
Ver 1.1
- ss1 // p3low // add validation to all delivery dates: Actual delivery date(s) cannot be in the future. They can only be “today” or “in the past”. (If today is jan 2 2009 and I set this date today I can not set it to any date before that)
Ver 1.2
- ss1 // Error pop-up we have now "Invalid ordering of dates" must clearly state what dates and in what CTs/Master have conflict. Right now it is very hard to find out when you get this error while changing date in Master Details Tab and that master have 10 CTs.
Ver 1.3
- ss1 // Block user from changing actual delivered date from empty to something for ANY container on container panel if there is at least one line in commodity table unassigned.
(This is done because it every commodity must be part of some container before it is delivered)
