Widget Copy Yes / No (feature)

From UG

Revision as of 15:26, 28 January 2010 (edit) Alex (Talk | contribs) (→Comments from Systems Architect) ← Older edit		Revision as of 15:27, 28 January 2010 (edit) (undo) Alex (Talk | contribs) (→Comments from Systems Architect) Newer edit →
Line 33:		Line 33:
	# Please refer to related fields as:		# Please refer to related fields as:
-	##[[ Exp Tab #Origin Terminal Yes N]]	+	* [[ Exp Tab#Origin Terminal Yes N]]
-	##[[ Exp Tab # Origin Terminal]]	+	##[[ Exp Tab#Origin Terminal]]
	##[[ Exp Tab#Origin Terminal Estimated Date]]		##[[ Exp Tab#Origin Terminal Estimated Date]]
	##[[ Exp Tab#Origin Terminal Actual Date]]		##[[ Exp Tab#Origin Terminal Actual Date]]

---

Revision as of 15:27, 28 January 2010

Contents 1 Classified As and Parent Mantis 2 Business Needs 3 Business Requirements 4 Comments from Systems Architect 5 Preliminary Design / Prototype 6 Detailed Design (Technical Specification) 6.1 User Interface 6.2 Functionality / Use Cases 7 Quality Assurance 8 Look And Feel 9 Figures 9.1 Figure 1: UI 10 Questions and RFC 11 Known Non Critical Bugs 12 Links to Archived / Old specs 13 History 13.1 This doc has been created 13.2 Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest) 14 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 Architect

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

1. Please refer to related fields as:

• Exp Tab#Origin Terminal Yes N

1. 1. Exp Tab#Origin Terminal
   2. Exp Tab#Origin Terminal Estimated Date
   3. Exp Tab#Origin Terminal Actual Date
2. 18 Port Of Loading
3. 19 Port Of Loading Estimated Date
4. 20 Port Of Loading Actual Date
5. 21 Port Of Trans shipment
6. 22 Port Of Trans shipment Estimated Date
7. 23 Port Of Trans shipment Actual Date
8. 24 Port Of Discharge
9. 25 Port Of Discharge Estimated Date
10. 26 Port Of Discharge Actual Date
11. 27 Destination Terminal Yes No
12. 28 Destination Terminal
13. 29 Destination Terminal Esimated Date
14. 30 Destination Terminal Actual Date

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

Preliminary Design / Prototype

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

Detailed Design (Technical Specification)

User Interface

No need to define widgets here, it is to be defind in Imp Tab component.--Alex 13:58, 28 January 2010 (UTC)

Functionality / Use Cases

Quality Assurance

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)

--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

DB