Widget Copy Yes / No (feature)

From UG

(Difference between revisions)
Jump to: navigation, search
(→Detailed Design (Technical Specification))
(→Comments from Systems Architect)
Line 31: Line 31:
# Describe in details. For example - what happens with state of every field on change from Y to N? From N to Y?
# 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]]
# Above description could be done in style similar as in [[Delivery Comment]]
 +
 +
# Please refer to related fields as:
 +
 +
[[ Exp Tab#Origin Terminal Yes N]]
 +
[[ Exp Tab#Origin Terminal]]
 +
[[ Exp Tab#Origin Terminal Estimated Date]]
 +
[[ Exp Tab#Origin Terminal Actual Date]]
 +
# 18 Port Of Loading
 +
# 19 Port Of Loading Estimated Date
 +
# 20 Port Of Loading Actual Date
 +
# 21 Port Of Trans shipment
 +
# 22 Port Of Trans shipment Estimated Date
 +
# 23 Port Of Trans shipment Actual Date
 +
# 24 Port Of Discharge
 +
# 25 Port Of Discharge Estimated Date
 +
# 26 Port Of Discharge Actual Date
 +
# 27 Destination Terminal Yes No
 +
# 28 Destination Terminal
 +
# 29 Destination Terminal Esimated Date
 +
# 30 Destination Terminal Actual Date
 +
--[[User:Alex|Alex]] 13:46, 28 January 2010 (UTC)
--[[User:Alex|Alex]] 13:46, 28 January 2010 (UTC)

Revision as of 15:24, 28 January 2010


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.

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 Exp Tab#Origin Terminal Exp Tab#Origin Terminal Estimated Date Exp Tab#Origin Terminal Actual Date

  1. 18 Port Of Loading
  2. 19 Port Of Loading Estimated Date
  3. 20 Port Of Loading Actual Date
  4. 21 Port Of Trans shipment
  5. 22 Port Of Trans shipment Estimated Date
  6. 23 Port Of Trans shipment Actual Date
  7. 24 Port Of Discharge
  8. 25 Port Of Discharge Estimated Date
  9. 26 Port Of Discharge Actual Date
  10. 27 Destination Terminal Yes No
  11. 28 Destination Terminal
  12. 29 Destination Terminal Esimated Date
  13. 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

File:Terminal Yes No (feature) 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)

DB

Retrieved from "https://wiki.jaguarfreight.com/Widget_Copy_Yes_/_No_(feature)"
Personal tools