|
|
66.
|
|
|
Configuration wizards are launched automatically at the creation of a new database. You must develop configuration wizards per application in order to:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:6
|
|
|
67.
|
|
|
1.Help the user choose the features (=modules) he wants to install or not
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:8
|
|
|
68.
|
|
|
2.Help the user to configure the system
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:10
|
|
|
69.
|
|
|
For the point (1), the less the user install modules, the easier it is to understand the system. So, most of the features are proposed as extra in the configuration wizards.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:12
|
|
|
70.
|
|
|
For the point (2), whenever it's possible, it's better to provide a default configuration that works for most companies as data created by default instead of developing a configuration wizard to ask questions to configure the system.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:14
|
|
|
71.
|
|
|
Don't forget that configuration wizards are here to help users to configure the system tailored to their need, not to ask complex questions for very specific configurations.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:16
|
|
|
72.
|
|
|
OpenERP allows user configure his OpenERP following his business's needs. When user creates a database, he can choose one or more application(s). Following application(s) chosen, he can see some configuration wizards to add modules related to his chosen application(s) and so, his needs. For example: user has chosen “Project”. He will have another wizard to configure Project Management.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/4.Configuration/Configuration_wizards.rst:18
|
|
|
84.
|
|
|
One user/role must be able to perform most of his tasks from one business application. He should not be forced to swtich to another application to perform the tasks of the same role. Example, a salesman should see in his menu: Leads, Opportunities, Meetings, Sales Orders, Sales to Invoice, etc. He should not be forced to go to the accounting application to invoice the sales.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:31
|
|
|
124.
|
|
|
If there is a current button, it is generally selected by default. This button filters all draft and open documents. This is usually selected by default to avoid seeing canceled and closed documents.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:36
|
|
|
131.
|
|
|
Near “section_id” we can find buttons generally used in views related to sale's applications.This button shows documents linked with current user's department(sales/marketing/HR,etc.).
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:49
|
