2
.. i18n: =====================
3
.. i18n: Business Applications
4
.. i18n: =====================
11
.. i18n: Defining new applications or completing existing ones
12
.. i18n: +++++++++++++++++++++++++++++++++++++++++++++++++++++
15
Defining new applications or completing existing ones
16
+++++++++++++++++++++++++++++++++++++++++++++++++++++
18
.. i18n: We usually try to define new business applications related to job positions in the enterprise. These are good examples of applications : Purchase, Sales, Accounting, Project, etc. Don't create business application by features. These are wrong examples of business applications : lunch orders management, expenses sheets, etc.
21
We usually try to define new business applications related to job positions in the enterprise. These are good examples of applications : Purchase, Sales, Accounting, Project, etc. Don't create business application by features. These are wrong examples of business applications : lunch orders management, expenses sheets, etc.
23
.. i18n: If you have specific features that do not belong the existing business applications, you can put them in the “Miscelleanous Tools” application.
26
If you have specific features that do not belong the existing business applications, you can put them in the “Miscelleanous Tools” application.
28
.. i18n: Configuration wizards of business applications.
29
.. i18n: +++++++++++++++++++++++++++++++++++++++++++++++
32
Configuration wizards of business applications.
33
+++++++++++++++++++++++++++++++++++++++++++++++
35
.. i18n: 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.
38
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.
40
.. i18n: .. figure:: Pictures/1.2.Installation_of_modules.png
41
.. i18n: :align: center
44
.. figure:: Pictures/1.2.Installation_of_modules.png
47
.. i18n: You can also create one configuration wizard dedicated to your business application. Example, when you install the project management, you get this wizard:
50
You can also create one configuration wizard dedicated to your business application. Example, when you install the project management, you get this wizard:
52
.. i18n: .. figure:: Pictures/1.3.Project_management.png
53
.. i18n: :align: center
56
.. figure:: Pictures/1.3.Project_management.png
59
.. i18n: Business Applications must be complete
60
.. i18n: ++++++++++++++++++++++++++++++++++++++
63
Business Applications must be complete
64
++++++++++++++++++++++++++++++++++++++
66
.. i18n: 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.
69
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.
71
.. i18n: Transversal features, used by all applications
72
.. i18n: ++++++++++++++++++++++++++++++++++++++++++++++
75
Transversal features, used by all applications
76
++++++++++++++++++++++++++++++++++++++++++++++
78
.. i18n: Some features should be accessible by all users, not depending on the application they usually works in. As an example, most of the users should have an 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)
79
.. i18n: And, these features must be set as shortcuts for every user in the system by default, at the creation of the user.
82
Some features should be accessible by all users, not depending on the application they usually works in. As an example, most of the users should have an 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)
83
And, these features must be set as shortcuts for every user in the system by default, at the creation of the user.
85
.. i18n: Access Rights must define groups per application.
86
.. i18n: +++++++++++++++++++++++++++++++++++++++++++++++++
89
Access Rights must define groups per application.
90
+++++++++++++++++++++++++++++++++++++++++++++++++
92
.. i18n: The groups defined by each module must be directly related to business application. So, if you have an application which is “Accounting”. All groups within this application must be like: “Accounting / Accountant”, “Accounting / Financial Manager”, etc.
95
The groups defined by each module must be directly related to business application. So, if you have an application which is “Accounting”. All groups within this application must be like: “Accounting / Accountant”, “Accounting / Financial Manager”, etc.
97
.. i18n: One dashboard defined per application
98
.. i18n: +++++++++++++++++++++++++++++++++++++
101
One dashboard defined per application
102
+++++++++++++++++++++++++++++++++++++
104
.. i18n: Each business application must have one dashboard attached to his root menuitem. When a user enters in a business application, he should see the dashboard related to this application.
107
Each business application must have one dashboard attached to his root menuitem. When a user enters in a business application, he should see the dashboard related to this application.