Widget Copy Yes / No (feature)
From UG
Contents |
Classified As and Parent Mantis
Business Needs
Terminals (Origin and Dest) are additional optional CT milestones. We need to automate updating this fields to save time.
Business Requirements
- [r0] There are 2 pairs of Port /Terminal. They should behave identically:
- Origin Terminal / Port Of Loading
- Port Of Discharge / Destination Terminal
- [r1] By default any edits from Port should propagate into Terminal.
- [r2] System should provide option to make Terminal fields "independent from" Port fields. This could be done by adding Yes/No radio.
- [r3] See possible UI design here: #Figure 1: UI
So far there are 2 places where these fields appear:
- ocean CT profile
- Master ocean profile
Comments from Systems Analyst
Not all details are captured in above requirements. For example, should system clear Terminal fields after user selects from Y to N? Same question for change of state from N to Y, etc.
Technical Specification
Summary
User Interface and Functionality
Entities and Attributes
Special Cases and Misc
Look And Feel
Figures
Figure 1: UI
_UI.JPG)
Questions and RFC
Known Non Critical Bugs
Links to Archived / Old specs
History
This doc has been created
--Alex 19:54, 19 January 2010 (UTC)
Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest)
--Alex 19:54, 19 January 2010 (UTC)
- mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1692
- Biz Req updated? Y
- Tech Spec updated? N
