Delivery Comment
From UG
(→Business Needs and Requirements) |
(→Technical Specifications) |
||
| Line 9: | Line 9: | ||
== Technical Specifications == | == Technical Specifications == | ||
| + | |||
| + | === Summary === | ||
| + | |||
| + | In CT1 solution was to add Delivery Comment text box. If this text box was non-empty then system would "move" CT from Live Tab to Delivered Tab. | ||
| + | |||
| + | In CT2 it was required to satisfy this need but design has been changed. | ||
| + | |||
| + | System now does not look at delivery comment at the moment of deciding if CT is Live or Delivered. Instead it looks only at delivered date. To make sure delivery date is not empty Delivery Comment was supplemented by check box and additional logic that would "on check" display ''delivery comment'' text box plus copy some other dates into delivered date to make it non empty. | ||
== Dev and History == | == Dev and History == | ||
* Old link: http://mantis.jaguarfreight.com/wiki/Ops_Misc#Delivery_Comment_Check_Box | * Old link: http://mantis.jaguarfreight.com/wiki/Ops_Misc#Delivery_Comment_Check_Box | ||
Revision as of 21:51, 8 December 2009
Contents |
Mantis
Business Needs and Requirements
For some CTs delivery is managed by other company than Jaguar therefore exact delivery date is unknown. In this case we need another mechanism to change status of CT to "delivered" even though there is no date.
Technical Specifications
Summary
In CT1 solution was to add Delivery Comment text box. If this text box was non-empty then system would "move" CT from Live Tab to Delivered Tab.
In CT2 it was required to satisfy this need but design has been changed.
System now does not look at delivery comment at the moment of deciding if CT is Live or Delivered. Instead it looks only at delivered date. To make sure delivery date is not empty Delivery Comment was supplemented by check box and additional logic that would "on check" display delivery comment text box plus copy some other dates into delivered date to make it non empty.
