WorkshopErgonomy
From Wiki
Contents |
Ergonomy and Simplification Workshop
Terminology
Goals
- fast and full proof data handling (50% lots of demo data added, business game in process)
- self explaining forms (100% Tooltips on all fields, restructured layout of forms)
Ideas and Propositions
- replace text of OK and Cancel Buttons with "Action" text (731)
- Save, Discard, Close Window, Create New Record,...
- multi tabbed forms: move "name" (human identification attributes) above tab (100% all forms reviewed)
- GTK-Client: next/previous set of records (like WEB-Client) (195)
- also for one2many widget, restrict to 20-80 records
- default sort list by sequence (if defined), "name" 100% + D&D to reorder
- the sort criteria must be displayed (not for 5.0)
- optionally start with query mode for lists with very many rows (avoid transfer and dispatch of not used lines) (not for 5.0)
- Query on one2many widget (676)(630) (not for 5.0, sometimes a shortcut has been added)
- thousands separator (localisation of grouping numbers) (173) (100%)
- allow comma AND dot from numpad as decimal separator input (100%)
- keep order of displayed records AFTER save (705) (100% Use drag and drop to store order when sequence exists)
- search in menu (192)
- documents need page numbers and date (235) (100%)
- display all search criteria (268) (100% tab labels/titles improved with context, rest not for 5.0)
- form - notebook pages - fetch on demand (455) (not for 5.0)
- select file name should show filename instead of file size
- audit and logging of certain user actions (100% audit trail and game scenario implemented)
- optional: time relational data storage (100% print are saved in attchment)
- better error handling - better wording, more specific (record_id, field name) (100% exceptions reviewed)
- xml import - handling of null values (616,723)
- do not allow input in read only one2many widgets (639) (100%)
- importing boolean values (622)
- uniqueness of names (715) (100%)
- shortening fields during upgrade (631)
- do not allow to delete master records (687) (100%)
- tooltips / help text (translatable?) (100%)
- check matching client/server/database versions (100%)
- multicompany - singel db - single user (accountant) setup ? (100%)
- group/wrap server scripts (start/stop/status and init/update)
- hidden errors on multitabbed forms (633) (100% still exist but removed the most common error)
- accounting: universal move entry (100%)
- change the behaviour of the changing button "new" or "search" in many2one fields. (100%)
- add a "duplicate" button in one2many fields (not for 5.0)
- define color rules in openErp. Red means Error, for example, blue means mandatory but also draft...
(100% check guidelines)
Interrested Peoples
- Ferdinand Gassauer
Results
Guide lines
A guideline should be write in the wiki to help developers to build ergonomics forms. Those points should be included in it:
- Replace text of OK and Cancel Buttons with "Action" text (731)
- multi tabbed forms: move "name" (human identification attributes) above tab
- for all error messages, write a line to explain the error, and another one to explain what to do to avoid or correct it. (and optional technical details)
- change the behaviour of the changing button "new" or "search" in many2one fields. Try search for a country (for example 'bel') this will popup a window without context (mentioned elsewhere: where is the context), also, the popup window will not allow to create the country that is search for directly (using the searchphrase as a default value, preferably)
- define color rules in openErp. Red means Error, for example, blue means mandatory but also draft... These colors should be used consistently.
# alert (blue) # error (red) # ok (black or gray)
Tiny Todo
also see the page: [FR] https://tinyerp.saas-camptocamp.com/trac/tinyerp/wiki/OPENERP_IMPROVEMENT headings "Améliorations du client" and "usability" for a list of improvements already discussed between Tiny & Camptocamp
- go through the guide lines and apply those advices to existing forms. '(100% reviewed forms and menus)
- default sort list by sequence (if defined), "name" (never by id). (100%)
- the sort criteria must be displayed
- make it optional to display lists empty by default (without any records diplayed) because if the list is too long (let's say 30'000 records) it's useless to display the 80 first records as we'll perform a search in any case. (We prefer keeping always the same behaviour)
- add a "breadcrumb" at the top of the client window to list the previous places you visited. like "partner -> state -> country -> etc..." http://en.wikipedia.org/wiki/Breadcrumb_(navigation) (In the pipeline)
- thousands separator (localisation of grouping numbers) (173). There should be a way to define the format to be able to print a report with two different style if needed (100%, using locales)
- search in menu: A kind of filter on menus. For example, if you install a new module, you want to find where the new menu appeared.
- display all search criteria (268): For example, dbl click on an account in the chart of accounts. Then double click on another one. Then you have 2 tabs with an identical name and no way to say which tab belongs to which account. It maybe be solved by the breadcrumb or by the display of the search criteria at the top of the form.
- error messages: We need different levels or error to differentiate messages that goes to the log and messages that appear to the end user. A developer watching the log do not need to see what the user did wrong (like a end date defined before a start date) and the user need text messages and explanation on what to do instead of "constraint error field_id = value"
- do not allow input in read only one2many widgets (639)
- importing boolean values does not work(622)
- Please never shorten a field during an upgrade if there is data in that field that is longer than the new length. (this may have been fixed already)
- wizard to create and subscribe audit rules for all/selected objects at once (Checkboxes in a list: audit, dont audit, etc would be sufficient)
- tooltips / help text (translatable?) (80%)
# there is a new help system under discussion (according to tiny) # there are a lot of missing tooltips. (a lot of fields that have unknown undocumented meaning) # all text (not just help) should be translatable # It would be nice to have a glossary (which is automatically linked to
- There should be auto notification if any of the 3 layers is not the correct version (DB, Server, Client)
# And if the client is out of date, it should offer to upgrade itself
- All modules should check if they are compliant with the server & DB versions they are (being) installed in.
- hidden errors on multitabbed forms (633) If there is an error on tab #2, the form will show tab#, stating there is an error, but *not* stating on which tab that error has occured. Flagging the tab that contains the error (or navigating to it, if it is only 1 tab) would help.
- Optin to not print/show lines with 0 values (chart of accounts, stock location, ..) in tree views
To investigate further if it's possible or not
- keep order of displayed records AFTER save (705): when you go through a list in form view with next and previous buttons, if you create a new record, you loose your position in the list and restart at the first element.
- introduce time management for all objects. Either a temporal database or a log file of all changes or use the AuditTrail module. This way it would be possible to recreate records (and reports) as how they would have looked on a certain date in the past.
- multicompany - singel db - single user (accountant) setup ? If one person has a role in multiple companies that are in the same database, he can not perform a different role in these companies, as all his access rights are calculated from the parent company (@ parked for Fabian)
Already in the Tiny todo list
- GTK-Client: next/previous set of records (like WEB-Client) (195)
- also for one2many widget, restrict to 20-80 records
- or implement dynamic data loading when scrolling
- xml import - handling of null values (616,723)
- documents need page numbers and date (235) <-- already fully investigated by the report workshop
Post Dev Days Remarks
- do not allow to delete master records (687) - ref 22 from above
- it should not be possible to delete partners which are
referenced from projects
- it should not be possible to delete time sheets with
timesheet line details (although the lines are not deleted and show up in other apps - this confuses the user)
- do not delete menu tab (was discussed in plenary session)
- merge fields.selection and fields.one2many functionality (792) http://tinyforge.org/tracker/index.php?func=detail&aid=792&group_id=13&atid=132
- purchase workflow enhancements getting goods:
- create invoice button should only be visible if no invoice is created yet. (currently the functionality is called, but no invoice is created)
- open invoice (the one which was just created) to continue for validation and eventually payment.( I am thinking about small and medium companies where entering the data is done by the same person) for workflows where only the supplier invoice exists - but the OpenERP user has to start with a purchase order to get purchased goods in to stock.
- various lists in sales/purchase/stock management should be sorted "newest/latest on top" to avoid unnecessary scrolling
- and the sorting order should be the generally the same for all list currently:
- sales order: newest on top
- getting goods and invoices: newest at bottom
- and the sorting order should be the generally the same for all list currently:
- Products - product sales - should show customer in the list/tree view
- stock moves: list view should show sheet number( sales/packing/invoice ) and partner
- simple / extended view
- see: product forms - http://www.openerp.com/forum/post21666.html#21666
- for product of type "service" (and consumable - what ever this is ?) all stock related fields must be set to invisible (or read only) and must be set to their default values in case the user has already entered some "false" values (see discussion in the forum)
- see: product forms - http://www.openerp.com/forum/post21666.html#21666
- import csv data: manual reload is necessary to display the loaded data - usually the user wants to see the loaded data
- either automatic (not always a good idea) or hint or a second button "load and display"
- delete main record or record in one2many widget
- It happens to frequently to be ignored. The user (also myself) marks one or more record(s) of one2many widget and clicks "delete" on top of the screen instead of the delete button in the one2many widget. (see also top of the list - do not delete master). IMHO only in rare cases a complete deletion (cascade) of master/detail constructs is the desired behavior -- needs discussion. The issued question "do you want to delete ..." does not really help, because the user wants to delete -a- record - but in facts it's the wrong one.
- Windows XP - GTK-Client - Windows Title Bar no maximize icon
- while in Linux it is possible use an icon to maximize the pop-up window this is not the case in Windows - Example:
- Anylytic account -> Open Associate Partner: The resulting window is much to small to display the content of the partner FORM, especially the embedded contacts forms is not usable/readable in the small window inside.
- while in Linux it is possible use an icon to maximize the pop-up window this is not the case in Windows - Example:
- many2many widget should get New/Edit buttons (like many2one)
- one2many widget - close window issue
- open complete / part of a tree with one click
- http://tinyforge.org/tracker/index.php?group_id=13&atid=129
- or allow tree branches as bookmarks
- make (simple) lists editable (on top)
- csv - import - debugging
- better error messages
- option: import of valid records and saving invalid records to an error list for further processing.
- interactive error correction
- handling of blanks
- add http:// to website URL if not specified
- either for data entry
- or when calling the browser
- sort in sfd_report_designer
- because of the missing sort by name (see above) the strandard sort order of contacts and products (!) is by id of Partner and product_template. (print outs of some 100 records are for the trash because people do not find anything.)
- sort order work around
- text word wrap and LF (bug 819,820)
- pls make sure that this problem is solved for all reports
- print order (bug 821)
- pls make sure that this problem is solved for all TREE reports
- default selection for mandatory fileds can not be set to null
- Menu selection with "This Month"
- A lot of reports are run during the first days of the next month after finishing/closing all activities of the last month - IMHO we need a section "Last Month"
- editable tree views
- for users it is difficult to distinguish if the tree view is editable or not
- not editable -> switch view
- editable -> eventually open a field and edit the content (unwanted) - a special problem are the boolean fields which are changed "on click"
- I have no (good) idea how to solve this except to forbid editable tree views. but this is not a good solution neither.
- for users it is difficult to distinguish if the tree view is editable or not