|
|
67.
|
|
|
We usually try to define new business applications related to job positions in the enterprise. These are good examples of applications: Purchase, Sales, Accounting and Project. Don't create business application by features. These are bad examples of business applications: lunch orders management, expenses sheets, etc.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/1business applications.rst:9
|
|
|
68.
|
|
|
If you have specific features that don't belong in the existing business applications, you can put them in the “Miscelleanous Tools” application.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/1business applications.rst:11
|
|
|
71.
|
|
|
You can also create one configuration wizard dedicated to your business application. For example, when you install project management, you get this wizard:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/1business applications.rst:22
|
|
|
73.
|
|
|
Each user/role must be able to perform most of their tasks from one business application. For 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/Guidelines/1business applications.rst:31
|
|
|
75.
|
|
|
Some features should be accessible by all users, regardless of which application they usually work in. For example, most users should have access to: Partners, Agenda of Meetings, Products. In that case, you put the menu in the applications that needs these features more. (Example: the address book is in the sales, purchases and accounting application) And, these features must be set as shortcuts for every user in the system by default, at the creation of the user.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/1business applications.rst:36
|
|
|
79.
|
|
|
Each business application must have one dashboard attached to its root menu item. When a user enters a business application, they should see the dashboard related to this application.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/1business applications.rst:48
|
|
|
83.
|
|
|
The first items of the main menu (application management) must be the most useful documents of the application. There are 2 reasons for this:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/menus.rst:9
|
|
|
84.
|
|
|
users must have direct and easy access to their documents, usually, most important features which correspond to daily operations.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/menus.rst:11
|
|
|
86.
|
|
|
If the application contains the object “res.partner” it is always after the main menu. Because, it is important to have easy access to the suppliers in “purchases” or the customers in “sales”.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/menus.rst:17
|
|
|
87.
|
|
|
“Configuration” is always the last menu item in an application. By default, only “admin / configuration” has access to this menu.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/menus.rst:18
|
