|
|
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
|
|
|
69.
|
|
|
Configuration wizards of business applications.
|
|
|
|
|
业务应用的配置向导
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
865624d928484f1cb2524a9411f31ee9
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:14
|
|
|
70.
|
|
|
Each application must create an entry in the main base_setup wizard that shows all the possible business applications defined in quality certified modules only.
|
|
|
|
|
每个应用必须在基本的主安装向导中创建创建实例（entry, 对象），这些向导展示了只有在质量认证过的模块中才定义可能的业务应用。
|
|
Translated and reviewed by
Victor Yu
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:16
|
|
|
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
|
|
|
72.
|
|
|
Business Applications must be complete
|
|
|
|
|
业务应用必须完整
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
3b5aa3dbc78d4dd2a6ad0e9a7015c1c1
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:29
|
|
|
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
|
|
|
74.
|
|
|
Transversal features, used by all applications
|
|
|
|
|
横向功能，能够被所有应用使用
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
932d8098e4de44109a2736365b585543
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:34
|
|
|
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
|
|
|
76.
|
|
|
Access Rights must define groups per application.
|
|
|
|
|
每个应用必须为用户组定义权限
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
5544798d0a1e4f27bad7824f6b8734a5
|
|
Located in
../../source/usability_book/7.Guidelines/1business applications.rst:40
|
