Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | "Cannot proceed in Mail Merge at "Insert address block" until all fields matched" | ||
---|---|---|---|
Product: | Writer | Reporter: | integrafin <psimpson> |
Component: | ui | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, os_ooo |
Version: | OOo 2.3.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
integrafin
2008-01-02 12:47:26 UTC
Reassigned to HI. The current behavior is nasty if you are an expert. But usability studies showed that desaster happens when a user has a database where the fields do not match. So the workflow was changed in issue http://www.openoffice.org/issues/show_bug.cgi?id=51947 to always demand a matching of fields. With current spec http://specs.openoffice.org/writer/mail_merge/mailmerge_specification_pp1.sxw this works as designed. Hello. Many thanks for your speedy response. I accept that there may be problems subsequently if the user has not matched fields, but the problem is that the user is not informed that s/he has to match fields: All they know is that the "Next button" is disabled and there is no clue as to why. Can a message be placed on the screen so that they know why it is disabled ? Many thanks, Peter Issue type changed from defect to enhancement. Summary also changed from: Take the user by hand and show why Next button is disabled. *** Issue 85019 has been marked as a duplicate of this issue. *** UI relevant -> 3.1 ->fl: I propose not to disable the "Next" button but to show a QueryBox in that case. This box informs the user about possibly unassigned fields. Something like: Not all database fields are assigned correctly. Do you want to assign them now? Assign now Ignore Cancel While "Assign now" calls the related dialog, "Ignore" continues to the next page (or any other page selected in the list of pages) and "Cancel" goes back to the current page. Any other idea? move target to 3.2. Branche date (feature- and code-freeze) for OOo 3.2 is nearly done. Therefore I change the target of this issue to OOo 3.x. If you think it is a stopper for OOo 3.2 please change the target back. |