Widget Copy Yes / No (feature)

From UG

(Difference between revisions)

Revision as of 20:41, 19 January 2010

1 Classified As and Parent Mantis
2 Business Needs
3 Business Requirements
- 3.1 Comments from Systems Analyst
4 Technical Specification
5 Questions and RFC
6 Known Non Critical Bugs
7 Links to Archived / Old specs
8 History
- 8.1 This doc has been created
- 8.2 Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest)
9 DB

Classified As and Parent Mantis

Classified As: common feature
Parent Mantis: 1692

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

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)