Widget Copy Yes / No (feature)

From UG

(Difference between revisions)
Jump to: navigation, search
(User Interface)
(User Interface)
Line 64: Line 64:
''No need to define [[widget]]s here, it is to be defind in [[Imp Tab]] component.--[[User:Alex|Alex]] 13:58, 28 January 2010 (UTC)''
''No need to define [[widget]]s here, it is to be defind in [[Imp Tab]] component.--[[User:Alex|Alex]] 13:58, 28 January 2010 (UTC)''
-
-See Figure 1
+
* See Figure 1
-
-каждый Порт, как и Терминал имеет три поля: Name, Estimated Date, Actual Date
+
* каждый Порт, как и Терминал имеет три поля: Name, Estimated Date, Actual Date
-
-значение по умолчанию: пустое
+
* значение по умолчанию: пустое
-
-также каждый Терминал имеет поле переключателя "Terminal Yes / No" в виде 2-х элементов radiobutton: Yes, No
+
* также каждый Терминал имеет поле переключателя "Terminal Yes / No" в виде 2-х элементов radiobutton: Yes, No
-
-значение по умолчанию: No
+
* значение по умолчанию: No
=== Functionality / Use Cases ===
=== Functionality / Use Cases ===

Revision as of 20:53, 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:
    1. Exp Tab#Origin Terminal Yes No
    2. Exp Tab#Origin Terminal
    3. Exp Tab#Origin Terminal Estimated Date
    4. Exp Tab#Origin Terminal Actual Date
    5. Exp Tab#Port Of Loading
    6. Exp Tab#Port Of Loading Estimated Date
    7. Exp Tab#Port Of Loading Actual Date
    8. Exp Tab#Port Of Trans shipment
    9. Exp Tab#Port Of Trans shipment Estimated Date
    10. Exp Tab#Port Of Trans shipment Actual Date
    11. Exp Tab#Port Of Discharge
    12. Exp Tab#Port Of Discharge Estimated Date
    13. Exp Tab#Port Of Discharge Actual Date
    14. Exp Tab#Destination Terminal Yes No
    15. Exp Tab#Destination Terminal
    16. Exp Tab#Destination Terminal Esimated Date
    17. Exp Tab#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)

Summary

Свойство "Terminal Yes / No" создается для обеспечения в указанных парах Порт/Терминал автоматического заполнения полей Терминала данными из полей соответствующего Порту в зависимости от состояния переключателя "Yes / No".

User Interface

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

  • See Figure 1
  • каждый Порт, как и Терминал имеет три поля: Name, Estimated Date, Actual Date
  • значение по умолчанию: пустое
  • также каждый Терминал имеет поле переключателя "Terminal Yes / No" в виде 2-х элементов radiobutton: Yes, No
  • значение по умолчанию: No

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

Personal tools