Widget Copy Yes / No (feature)

From UG

Revision as of 13:51, 28 January 2010 by Alex (Talk | contribs)

(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

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 Architect

This feature is already implemented for CT ocean
Now we need to describe existing behaviour
Describe in details. For example - what happens with state of every field on change from Y to N? From N to Y?
Above description could be done in style similar as in Delivery Comment

--Alex 13:46, 28 January 2010 (UTC)

Preliminary Design / Prototype

Not needed. --Alex 13:51, 28 January 2010 (UTC)

Detailed Design (Technical Specification)

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)