Widget Copy Yes / No (feature)

From UG

(Difference between revisions)
Jump to: navigation, search
(Functionality / Use Cases)
(Questions and RFC)
Line 94: Line 94:
[[File:Terminal Yes No (feature) UI.JPG]]
[[File:Terminal Yes No (feature) UI.JPG]]
-
== Questions and RFC ==
+
== Questions ==
 +
 
 +
== Suggestions ==
 +
 
 +
=== One outsider opinion about Y / N label ===
 +
 
 +
-- What does it mean "Yes / No"? What is "Yes"? What is "No"?
 +
 
 +
1) Maybe it will be useful to arrange this in the following way: simply to write a label
 +
"Copy data from Port of Loading" (Yes / No)"
 +
It will be understandable and no need to read help.
 +
 
 +
2) Why when "No", the Child is non-editable, and when "Yes", they are editable? Maybe, we should add to the radio-button a text field "Editable"? "Editable" Yes / No?
 +
 
 +
Or we should to change places between "Yes" and "No" and make "Yes, copy data from Port of Loading" / "No"?
 +
It's said only for discussion, but I prefer the last variant.
== Known Non Critical Bugs ==
== Known Non Critical Bugs ==

Revision as of 23:03, 7 February 2010


Contents

Classified As and Parent Mantis

Business Needs and Requirements

Application of this feature to Port / Terminal on Exp Tab (Ocean)

  • [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.

Application of this feature to Shipper Consignee (Truck modes)

For Truck modes only:

  • pair a)
    • Gen_Tab#Shipper; Gen_Tab#Shipper_Address - "master" ( has Y/N)
    • Gen_Tab#Pick_up; Gen_Tab#Pick_up_Address
  • pair b)
    • Gen_Tab#Consegnee; Gen_Tab#Consignee_Address - "master" ( has Y/N)
    • Gen_Tab#Delivery_to; Gen_Tab#Gen_Tab#Delivery_to_Address

Application of this feature to 2 pairs of Port / Terminal on Master Details Tab (Ocean)

same as #Application of this feature to Port / Terminal on Exp Tab (Ocean)

Comments from Systems Architect

  1. This feature is already implemented for #Application of this feature to 2 pairs of Port / Terminal on Exp Tab (Ocean)
  2. Now we need to describe existing behavior
  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
  5. Describe abstractly: talk about parent / child realation between 2 groups of widgets

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

Preliminary Design / Prototype

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

Detailed Design (Technical Specification)

Summary

The property "Widget Copy Yes / No" is created to provide in the specified pairs Parent / Child of an automatic filling in of the Child fields with data from corresponding Parent fields, depending on a state of "Yes / No" switch.

User Interface

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


  • every Parent, as well as a Child, for which the "Widget Copy Yes / No" is implemented, has several fields.
    • Quantity of those fields in pairs is equal and here exists a strict correspondence between Child fields and Parent fields. For example, on the Exp Tab the "Widget Copy Yes / No" property is implemented for two pairs Port / Terminal and, correspondingly, for their fields Port Name, Estimated Date, Actual Date - See #Figure 1: UI
    • default value: empty
  • also, every Child has switch field "Yes / No" in a form of a Radiogroup with two radio buttons: Yes or No
    • default value: No

Functionality / Use Cases

In the pair "Parent / Child" the following pairs of fields are used for automatic filling in:

  1. from Parent#Field1 to Child#Field1
  2. ...
  3. from Parent#FieldN to Child#FieldN

The list and correspondence of the fields see in the section Business Needs and Requirements или #Temp.

UC1: editing (switch is set to No)

UC2: editing (switch is set to Yes)

when data in a Parent field is edited, data in corresponding Child fields would not been changed

UC3: setting from No to Yes

all Child fields will be cleared and become editable

UC4: setting from Yes to No

all Child fields will be immediately set to corresponding Parent field values and become non-editable

Quality Assurance

Look And Feel

Figures

Figure 1: UI

File:Terminal Yes No (feature) UI.JPG

Questions

Suggestions

One outsider opinion about Y / N label

-- What does it mean "Yes / No"? What is "Yes"? What is "No"?

1) Maybe it will be useful to arrange this in the following way: simply to write a label "Copy data from Port of Loading" (Yes / No)" It will be understandable and no need to read help.

2) Why when "No", the Child is non-editable, and when "Yes", they are editable? Maybe, we should add to the radio-button a text field "Editable"? "Editable" Yes / No?

Or we should to change places between "Yes" and "No" and make "Yes, copy data from Port of Loading" / "No"? It's said only for discussion, but I prefer the last variant.

Known Non Critical Bugs

Links to Archived / Old specs

History

This doc has been created

--Alex 19:54, 19 January 2010 (UTC)

Spec Update:(Widget Copy Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest) and Shipper / Consignee

--Alex 19:54, 19 January 2010 (UTC)

Personal tools