RedLining: Add comment if rejection could not restore the old state

OpenOffice.org 2.0

Document - ID	Specification Owner	Last Change	Status
	Eike Rathke	2004-07-07	Final
Conforms to	StarOffice Specification Workflow v0.1, Aug 2003
Applies to	Calc
Task ID(s)	112261
Category	Feature

Abstract

If a recorded change is rejected for an OpenOffice.org Calc document, a comment for the rejecting action is inserted if dependencies to other actions indicate that at least one of them couldn't be properly restored.

i-Team Members (The specification owner is part of the i-Team)

	Name	E-mail Address
User Experience	Matthias Müller-Prove	mmp@openoffice.org
Development	Eike Rathke	er@openoffice.org
Quality Assurance	Oliver Crämer	oc@openoffice.org
Documentation	Uwe Fischer	ufi@openoffice.org

Approved for Implementation

	Approved by	Date
User Experience	Matthias Müller-Prove	06/01/04
Development	Eike Rathke	2004-06-30
Quality Assurance	Oliver Craemer	06/01/04
Documentation	Uwe Fischer	2004-07-06
String Review	Elizabeth Matthis/Paul Compton	06/09/04 / 2004-07-02

Document Change History

Rev. Level	Change	Initials	Date
1.0	initial version	ER	2004-05-27
	approved by User Experience	MMP	06/01/04
	added second user scenario "row or column deleted"	ER	2004-07-02
	Added comment for future task OC-1	OC	07/07/04

Contents

Glossary	1

2	Motivation	1

3	User Scenarios	1

3.1	Range moved	1

3.2	Row or column deleted	1

4	Goals	2

5	Requirements and Dependencies	2

5.1	Requirements	2

5.2	Technical Dependencies	2

6	Competitive Analyses	2

7	Detailed Specification	2

7.1	G11n	3

7.2	Error Conditions	3

7.3	Migration	3

8	Future Tasks	3

9	Notes	4

10	References	4

Glossary

Term	Description
RedLining, ChangeTracking	recording modifications for a document

Motivation

If a recorded change (AKA RedLining, ChangeTracking) is rejected, it may happen that the change or it's dependants can not be properly restored. This is a limitation of how the change is stored and the amount of data that is stored for each change, and the behavior can not be easily modified without quite some effort. The comment added will inform the user about potential data mismatch.

User Scenarios

Range moved

	A	B
1	one	
2	two	=A2

Cell B2 contains the formula =A2 that displays the content of cell A2, "two".

Menu Edit.Changes.Record is activated.

Cell A1 is moved (via drag&drop or cut&paste) to cell A2. Cell B2 still displays the content of cell A2, this time "one".

Under menu Edit.Changes.AcceptOrReject in the dialog the "Range moved" action is rejected. This leads to a reverse move where due to the rules how references pointing to moved cells are updated the formula in B2 is modified to follow the move.

Now cell B2 contains the formula =A1 that displays the content of cell A1, "one", and not the content of cell A2 "two" like it did before the original move.

The reverse move is displayed as an accepted rejecting action in the dialog.

Row or column deleted

	A	B
1		=A1

If column A is deleted, cell B1 becomes cell A1 and displays #REF!. The formula's reference displays =#REF!1

Rejecting the action will entirely restore the previous state.

If the document is stored and reloaded, information about where the formula originally pointed to is lost. The formula's reference is still displayed as =#REF!1 but the cell displays #NAME! because the formula couldn't be compiled during load.

If the deletion is rejected now the formula will not be restored.

The reverse action of the deletion is displayed as an accepted insertion in the dialog.

Goals

To inform the user about this scenario a comment will be displayed for the accepted rejecting move, stating that data mismatch might have resulted from this action.

Requirements and Dependencies

Requirements

<State the requirement(s) of this feature here.>

Technical Dependencies

<Are there any technical dependencies for this feature? Does the implementation of this feature create any technical dependencies to other program parts? Or very important any issues for automatedd GUI Testing?>

Competitive Analyses

<Describe or reference to solutions which are already on the market. Describe what is done well or what is done bad.>

Detailed Specification

Illustration 1Dialog with highlighted rejecting action

The comment field of the rejecting action will have a string prepended, specified below.

String list

Item	English	German	Comments
String	WARNING: This action may have resulted in unintended changes to cell references in formulas.	ACHTUNG: Diese Aktion kann zu unbeabsichtigten Änderungen von Zellreferenzen in Formeln geführt haben!	ER: scenario "range moved". EM: I removed the word "ablehnend" from the message to avoid confusing users as the message appears after the "accepted" entry. The real matter is the possible data inconsistency.
String	WARNING: This action may have resulted in references to the deleted area not being restored.	ACHTUNG: Diese Aktion kann dazu geführt haben, dass Referenzen auf den gelöschten Bereich nicht wieder hergestellt wurden.	ER: scenario "row or column deleted".

Tab Order

<If necessary Describe or visualize the tabbing order. The description of the tab order has to contain which control has the initial focus.>

Key Board Shortcuts

<Key Board shortcuts used in dialogs have to be listed in a table with a small description.>

G11n

n/a

Error Conditions

n/a

Migration

n/a

Future Tasks

Eliminate the root cause for this notification. Provide robust roll-back for rejection actions.

cf. Notes: OC-1

Notes

OC-1: The warning is only visible if the treelistbox for accepted changes is opened. This should be enhanced in future versions for better visibility.

References

n/a

RedLining: Add comment if rejection could not restore the old state

Page 4

http://specs.openoffice.org/calc/ease-of-use/redlining_comment.sxw

RedLining: Add comment if rejection could not restore the old state

Eike Rathke

2004-05-27T19:02:02

Matthias Müller-Prove