Widget Copy Yes / No (feature)

From UG

Revision as of 15:08, 7 February 2010

Classified As and Parent Mantis

• Classified As: common feature
• Parent Mantis: 1692

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.

• [r3] See possible UI design here: #Figure 1: UI

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)

• when the data in the Parent field is edited, the corresponding Child fields immediately possess equal value.
  • for example, after setting data into the field Exp Tab#Port Of Loading, they will copy Exp Tab#Port Of Loading value into Exp Tab#Origin Terminal.
• when a Parent field is emptied, a corresponding Child field will be cleared immediately.
  • for example, after clearing of data in the field Exp Tab#Port Of Discharge Estimated Date (or ExpTab.14b.ETA) (adjacent button "C" is used) it is necessary to clear Exp Tab#Destination Terminal Esimated Date (or ExpTab.15b.ETA).

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

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:(Widget Copy Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest) and Shipper / Consignee

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

• mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1692
• see #Application of this feature to Shipper Consignee (Truck modes)
• see #Application of this feature to 2 pairs of Port / Terminal on Master Details Tab (Ocean)
• Biz Req updated? Y
• Tech Spec updated? N