659   2 use cases are not considered in the setting group model

Created: 20 Apr 2010

Status: Not Applicable

Part: Part 7-2 (2003)

Links:

Page: 67

Clause: 13.2.1

Paragraph:

Category: Issue for edition 2 of this part

Issue

2 use cases are not considered in the setting group model
UC1, when SG1 is in editing states, the client want to cancel all modification.
UC2, when SG1 is in editing states, the client request a "SelectEditSG(SG2)" service (without ConfirmEditSGValues).
In either cases, the standard doesn't specify the correct response of the server.

Proposal

In principle the server shall not save any SG value changes unless the client explicitly request so by "ConfirmEditSGValues" service.

Proposal:
In addition to "ConfirmEditSGValue", add service "SelectEditSG(0 or AnyOtherValidSG)" between SG initial states and editing states. And the server shall give a warning/indication that the unsaved values had lost. So that both the above use cases are covered.