2
.. i18n: To connect to Open ERP
3
.. i18n: =======================
6
=======================
8
.. i18n: Since this is the first time you've connected to it you'll have to
9
.. i18n: go through the Setup wizard in steps:
11
Since this is the first time you've connected to it you'll have to
12
go through the Setup wizard in steps:
14
.. i18n: #. :guilabel:`Select a profile` : select ``Minimal Profile`` and click :guilabel:`Next`.
16
.. i18n: #. At the :guilabel:`Define Main Company` step you should select your own :guilabel:`Company Name` and
17
.. i18n: :guilabel:`Currency`, and address details on the first tab :guilabel:`General Information`;
18
.. i18n: and add more details on the second tab :guilabel:`Report Information` including a logo,
19
.. i18n: if you have one, that appears on reports. Click :guilabel:`Next`.
21
.. i18n: #. At the :guilabel:`Summary` page you can go back to change details if you need.
22
.. i18n: Click the :guilabel:`Install` button.
24
.. i18n: #. Finally, at the :guilabel:`Installation done` page, click :guilabel:`Start Configuration`.
26
.. i18n: Configuration consists of a set of wizards that help you through options for the installed modules.
27
.. i18n: Hardly anything is installed so this is a very simple process at the moment.
29
.. i18n: #. At the first screen click :guilabel:`Continue` to go into the first wizard.
30
.. i18n: Choose :guilabel:`View Mode` : :guilabel:`Simplified Interface`
31
.. i18n: and then click :guilabel:`Set` to save it.
33
.. i18n: #. Click :guilabel:`Skip Step` to step over the next wizard, which would enable you to add other users.
35
.. i18n: #. You've now reached the end of the configuration so click :guilabel:`Continue` to start using the
36
.. i18n: system as the Administrator.
38
#. :guilabel:`Select a profile` : select ``Minimal Profile`` and click :guilabel:`Next`.
40
#. At the :guilabel:`Define Main Company` step you should select your own :guilabel:`Company Name` and
41
:guilabel:`Currency`, and address details on the first tab :guilabel:`General Information`;
42
and add more details on the second tab :guilabel:`Report Information` including a logo,
43
if you have one, that appears on reports. Click :guilabel:`Next`.
45
#. At the :guilabel:`Summary` page you can go back to change details if you need.
46
Click the :guilabel:`Install` button.
48
#. Finally, at the :guilabel:`Installation done` page, click :guilabel:`Start Configuration`.
50
Configuration consists of a set of wizards that help you through options for the installed modules.
51
Hardly anything is installed so this is a very simple process at the moment.
53
#. At the first screen click :guilabel:`Continue` to go into the first wizard.
54
Choose :guilabel:`View Mode` : :guilabel:`Simplified Interface`
55
and then click :guilabel:`Set` to save it.
57
#. Click :guilabel:`Skip Step` to step over the next wizard, which would enable you to add other users.
59
#. You've now reached the end of the configuration so click :guilabel:`Continue` to start using the
60
system as the Administrator.
63
.. i18n: single: administrator
68
.. i18n: Once you're displaying the main menu you're able to see the following screen items,
69
.. i18n: as shown in screenshot :ref:`fig-oech2-main`:
71
Once you're displaying the main menu you're able to see the following screen items,
72
as shown in screenshot :ref:`fig-oech2-main`:
74
.. i18n: * the :guilabel:`Preferences` toolbar to the top right, showing the user name, links to the :guilabel:`Home` page,
75
.. i18n: :guilabel:`Preferences`, :guilabel:`About` and :guilabel:`Logout`,
77
.. i18n: * just below you'll find information about the :guilabel:`Request` system,
79
.. i18n: * links to the :guilabel:`MAIN MENU` and the :guilabel:`SHORTCUTS`,
81
.. i18n: * information about copyright and the database you're logged into at the bottom of the page,
83
.. i18n: * the main contents of the window with by the menu toolbar to the left: links generally line up on
84
.. i18n: the right but there are none to show at the moment.
86
* the :guilabel:`Preferences` toolbar to the top right, showing the user name, links to the :guilabel:`Home` page,
87
:guilabel:`Preferences`, :guilabel:`About` and :guilabel:`Logout`,
89
* just below you'll find information about the :guilabel:`Request` system,
91
* links to the :guilabel:`MAIN MENU` and the :guilabel:`SHORTCUTS`,
93
* information about copyright and the database you're logged into at the bottom of the page,
95
* the main contents of the window with by the menu toolbar to the left: links generally line up on
96
the right but there are none to show at the moment.
98
.. i18n: .. _fig-oech2-main:
100
.. i18n: .. figure:: images/main_window_openerp_ch02.png
102
.. i18n: :align: center
104
.. i18n: *The Main Menu of the openerp_ch02 database*
108
.. figure:: images/main_window_openerp_ch02.png
112
*The Main Menu of the openerp_ch02 database*
114
.. i18n: Two menus are available on the left:
116
Two menus are available on the left:
118
.. i18n: * :menuselection:`Partners`,
120
.. i18n: * :menuselection:`Administration`.
122
* :menuselection:`Partners`,
124
* :menuselection:`Administration`.
127
.. i18n: single: Preferences
132
.. i18n: Preferences toolbar
133
.. i18n: ---------------------
136
---------------------
138
.. i18n: When you're connected to Open ERP the Preferences toolbar indicates which user you're connected as.
139
.. i18n: So it should currently be showing :guilabel:`Welcome Administrator` (unless you logged in as another
140
.. i18n: user and it's reflecting the name of that user instead).
142
When you're connected to Open ERP the Preferences toolbar indicates which user you're connected as.
143
So it should currently be showing :guilabel:`Welcome Administrator` (unless you logged in as another
144
user and it's reflecting the name of that user instead).
146
.. i18n: You'll find a link to the :guilabel:`Home` page to its right. This takes you to either the
147
.. i18n: dashboard or the available menus, depending on the user configuration. In the case of the \
148
.. i18n: ``openerp_ch02``\ database so far the Home page is the Main Menu. But in general each user of the
149
.. i18n: system is presented with a dashboard that's designed to show performance indicators and urgent
150
.. i18n: documents that are most useful to someone of the user's position in the company. You'll see how to
151
.. i18n: assign dashboards to different users in a later chapter, :ref:`ch-config`.
153
You'll find a link to the :guilabel:`Home` page to its right. This takes you to either the
154
dashboard or the available menus, depending on the user configuration. In the case of the \
155
``openerp_ch02``\ database so far the Home page is the Main Menu. But in general each user of the
156
system is presented with a dashboard that's designed to show performance indicators and urgent
157
documents that are most useful to someone of the user's position in the company. You'll see how to
158
assign dashboards to different users in a later chapter, :ref:`ch-config`.
161
.. i18n: single: timezone
166
.. i18n: .. tip:: Multi-nationals and time zones
168
.. i18n: If you have users in different countries, they can configure their own timezone. Timestamp displays
169
.. i18n: are then adjusted by reference to the user's own localization setting.
171
.. i18n: So if you have a team in India and a team in England, the times will automatically be converted. If
172
.. i18n: an Indian employee sets her working hours from 9 to 6 that will be converted and saved in the
173
.. i18n: server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
174
.. i18n: user's available time will be converted to English time.
176
.. tip:: Multi-nationals and time zones
178
If you have users in different countries, they can configure their own timezone. Timestamp displays
179
are then adjusted by reference to the user's own localization setting.
181
So if you have a team in India and a team in England, the times will automatically be converted. If
182
an Indian employee sets her working hours from 9 to 6 that will be converted and saved in the
183
server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
184
user's available time will be converted to English time.
186
.. i18n: The next element in the Toolbar is a link to :guilabel:`Preferences`. By clicking that link you
187
.. i18n: reach a page where the current user can set their password, a timezone, a working language, and
188
.. i18n: a signature:
190
The next element in the Toolbar is a link to :guilabel:`Preferences`. By clicking that link you
191
reach a page where the current user can set their password, a timezone, a working language, and
194
.. i18n: * The :guilabel:`Password` field gives the user the opportunity to change their own password.
195
.. i18n: You should take steps (perhaps written policies) to prevent users making these too trivial.
197
.. i18n: * The :guilabel:`Language` field enables the user's working language to be changed. But first the
198
.. i18n: system must be loaded with other languages for the user to be able to choose an alternative, which
199
.. i18n: is described in the next subsection of this chapter. This is a mandatory field, although might
200
.. i18n: initially be set as blank.
202
.. i18n: * The :guilabel:`Timezone` setting indicates the user's location to Open ERP. This can be different
203
.. i18n: from that of the server. All of the dates in the system are converted to the user's timezone
204
.. i18n: automatically.
206
.. i18n: * The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
207
.. i18n: from within Open ERP.
209
* The :guilabel:`Password` field gives the user the opportunity to change their own password.
210
You should take steps (perhaps written policies) to prevent users making these too trivial.
212
* The :guilabel:`Language` field enables the user's working language to be changed. But first the
213
system must be loaded with other languages for the user to be able to choose an alternative, which
214
is described in the next subsection of this chapter. This is a mandatory field, although might
215
initially be set as blank.
217
* The :guilabel:`Timezone` setting indicates the user's location to Open ERP. This can be different
218
from that of the server. All of the dates in the system are converted to the user's timezone
221
* The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
222
from within Open ERP.
224
.. i18n: The :guilabel:`About` link gives information about the development of the Open ERP software and
225
.. i18n: various links to other information.
227
The :guilabel:`About` link gives information about the development of the Open ERP software and
228
various links to other information.
230
.. i18n: The :guilabel:`Logout` link enables you to logout and return to the original login page. You can
231
.. i18n: then login to another database, or to the same database as another user. This page also gives you
232
.. i18n: access to the super-administrator functions for managing databases on this server.
234
The :guilabel:`Logout` link enables you to logout and return to the original login page. You can
235
then login to another database, or to the same database as another user. This page also gives you
236
access to the super-administrator functions for managing databases on this server.
238
.. i18n: The :guilabel:`Requests` link sits just below this toolbar. It is only visible if you're logged into
239
.. i18n: a database. If your database is new it will say :guilabel:`No request`. You can click on that link
240
.. i18n: to look at requests that have been sent to you at any time.
242
The :guilabel:`Requests` link sits just below this toolbar. It is only visible if you're logged into
243
a database. If your database is new it will say :guilabel:`No request`. You can click on that link
244
to look at requests that have been sent to you at any time.
247
.. i18n: single: installation; language
250
single: installation; language
252
.. i18n: Installing a new language
253
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
255
Installing a new language
256
^^^^^^^^^^^^^^^^^^^^^^^^^^^
258
.. i18n: Each user of the system can work in his or her own language. More than twenty languages are
259
.. i18n: currently available besides English. Users select their working language using the Preferences link.
260
.. i18n: You can also assign a language to a partner (customer or supplier), in which case all the documents
261
.. i18n: sent to that partner will be automatically translated into that language.
263
Each user of the system can work in his or her own language. More than twenty languages are
264
currently available besides English. Users select their working language using the Preferences link.
265
You can also assign a language to a partner (customer or supplier), in which case all the documents
266
sent to that partner will be automatically translated into that language.
268
.. i18n: .. attention:: More information about languages
270
.. i18n: The base version of Open ERP is translated into the following languages: English, German, Chinese,
271
.. i18n: Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
273
.. i18n: But other languages are also available: Arabic, Afghan,
274
.. i18n: Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
276
.. attention:: More information about languages
278
The base version of Open ERP is translated into the following languages: English, German, Chinese,
279
Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
281
But other languages are also available: Arabic, Afghan,
282
Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
284
.. i18n: As administrator you can install a new main working language into the system.
286
As administrator you can install a new main working language into the system.
288
.. i18n: #. Select :menuselection:`Administration` in the Menu Toolbar and click
289
.. i18n: :menuselection:`Translations --> Load an Official Translation` in the main menu window,
291
.. i18n: #. Select the language to install, \ ``French``\ for example, and click on :guilabel:`Start
292
.. i18n: Installation`,
294
.. i18n: #. When the message :guilabel:`Installation done` appears in the :guilabel:`Language file loaded` window,
295
.. i18n: click :guilabel:`OK` to return to the menu. (Your system will actually need the French locale loaded
296
.. i18n: to be able to do this, so you may not be successful here.)
298
#. Select :menuselection:`Administration` in the Menu Toolbar and click
299
:menuselection:`Translations --> Load an Official Translation` in the main menu window,
301
#. Select the language to install, \ ``French``\ for example, and click on :guilabel:`Start
304
#. When the message :guilabel:`Installation done` appears in the :guilabel:`Language file loaded` window,
305
click :guilabel:`OK` to return to the menu. (Your system will actually need the French locale loaded
306
to be able to do this, so you may not be successful here.)
308
.. i18n: To see the effects of this installation change the preferences of your user to change the working
309
.. i18n: language (you may first need to ensure that you have explicitly selected English as your language,
310
.. i18n: rather than keep the default, before you're given the French option).
311
.. i18n: The main menu is immediately translated in the selected language. If you're using the GTK
312
.. i18n: client you'll first have to close the menu then open a new main menu to start seeing things in the
313
.. i18n: new language.
315
To see the effects of this installation change the preferences of your user to change the working
316
language (you may first need to ensure that you have explicitly selected English as your language,
317
rather than keep the default, before you're given the French option).
318
The main menu is immediately translated in the selected language. If you're using the GTK
319
client you'll first have to close the menu then open a new main menu to start seeing things in the
322
.. i18n: .. note:: Navigating the menu
324
.. i18n: From this point in the book navigation from the main menu is written as a series of menu entries
325
.. i18n: connected by the :menuselection:`-->` character. Instead of seeing “ Select Administration in
326
.. i18n: the Menu toolbar then click Translations > Load an Official Translation ” you'll just get “ use menu
327
.. i18n: :menuselection:`Administration --> Translations --> Load an Official Translation` ”.
329
.. note:: Navigating the menu
331
From this point in the book navigation from the main menu is written as a series of menu entries
332
connected by the :menuselection:`-->` character. Instead of seeing “ Select Administration in
333
the Menu toolbar then click Translations > Load an Official Translation ” you'll just get “ use menu
334
:menuselection:`Administration --> Translations --> Load an Official Translation` ”.
336
.. i18n: .. index:: requests
340
.. i18n: Requests as a mechanism for internal communication
341
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
343
Requests as a mechanism for internal communication
344
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
346
.. i18n: Requests are a powerful communication mechanism between users of the system. They're also used by
347
.. i18n: Open ERP itself to send system messages to users.
349
Requests are a powerful communication mechanism between users of the system. They're also used by
350
Open ERP itself to send system messages to users.
352
.. i18n: They have distinct advantages over traditional emails:
354
They have distinct advantages over traditional emails:
356
.. i18n: * requests are linked to other Open ERP documents,
358
.. i18n: * an event's history is attached to the request,
360
.. i18n: * you can monitor events effectively from the messages they've sent.
362
* requests are linked to other Open ERP documents,
364
* an event's history is attached to the request,
366
* you can monitor events effectively from the messages they've sent.
368
.. i18n: Open ERP uses this mechanism to inform users about certain system events. For example if there's a
369
.. i18n: problem concerning the procurement of a product a request is sent by Open ERP to the production
372
Open ERP uses this mechanism to inform users about certain system events. For example if there's a
373
problem concerning the procurement of a product a request is sent by Open ERP to the production
376
.. i18n: Send a request to get an understanding of its functionality:
378
Send a request to get an understanding of its functionality:
380
.. i18n: #. Click on the :guilabel:`Requests` link that should currently be showing :guilabel:`No Requests`.
381
.. i18n: This opens a window that lists all of your waiting requests.
383
.. i18n: #. Click :guilabel:`New` to create and send a new request.
385
.. i18n: #. Complete the subject of the request, such as \ ``How are things?``\ then give a description of the
386
.. i18n: enquiry in the field.
388
.. i18n: #. Click the :guilabel:`Search` button to the right of the :guilabel:`To` field and select
389
.. i18n: :guilabel:`Administrator` in the window that opens (that's the user that you're already connected
392
.. i18n: #. You can then link this request to other system documents using the :guilabel:`References` field,
393
.. i18n: which could, for example, be a partner or a quotation or a disputed invoice.
395
.. i18n: #. Click :guilabel:`Send` to send the request to the intended recipient – that's yourself in this
396
.. i18n: case. Then click :guilabel:`MAIN MENU` to return to the original screen.
398
#. Click on the :guilabel:`Requests` link that should currently be showing :guilabel:`No Requests`.
399
This opens a window that lists all of your waiting requests.
401
#. Click :guilabel:`New` to create and send a new request.
403
#. Complete the subject of the request, such as \ ``How are things?``\ then give a description of the
404
enquiry in the field.
406
#. Click the :guilabel:`Search` button to the right of the :guilabel:`To` field and select
407
:guilabel:`Administrator` in the window that opens (that's the user that you're already connected
410
#. You can then link this request to other system documents using the :guilabel:`References` field,
411
which could, for example, be a partner or a quotation or a disputed invoice.
413
#. Click :guilabel:`Send` to send the request to the intended recipient – that's yourself in this
414
case. Then click :guilabel:`MAIN MENU` to return to the original screen.
416
.. i18n: .. figure:: images/request_tab.png
417
.. i18n: :align: center
420
.. i18n: *Creating a new request*
422
.. figure:: images/request_tab.png
426
*Creating a new request*
428
.. i18n: To check your requests:
430
To check your requests:
432
.. i18n: #. Click on the link to the right of the :guilabel:`Requests` label to open a list of your
433
.. i18n: requests. (It's possible that you'll still see the statement :guilabel:`No Requests` because this
434
.. i18n: information is updated periodically ather than instantly.) The list of requests then opens and you
435
.. i18n: can see the requests you've been sent there.
437
.. i18n: #. Click the :guilabel:`Edit` icon, represented by a pencil, at the right hand end of the request
438
.. i18n: line. That opens the request in edit mode.
440
.. i18n: #. You can then click the :guilabel:`Reply` button and make your response in the
441
.. i18n: :guilabel:`Request` field that appears in place of the original message.
443
.. i18n: #. Click :guilabel:`Send` to save your response and send it to the original sender.
445
#. Click on the link to the right of the :guilabel:`Requests` label to open a list of your
446
requests. (It's possible that you'll still see the statement :guilabel:`No Requests` because this
447
information is updated periodically ather than instantly.) The list of requests then opens and you
448
can see the requests you've been sent there.
450
#. Click the :guilabel:`Edit` icon, represented by a pencil, at the right hand end of the request
451
line. That opens the request in edit mode.
453
#. You can then click the :guilabel:`Reply` button and make your response in the
454
:guilabel:`Request` field that appears in place of the original message.
456
#. Click :guilabel:`Send` to save your response and send it to the original sender.
458
.. i18n: .. note:: Requests vs. email
460
.. i18n: The advantage of an Open ERP request compared with a set of emails about one thread of discussion
461
.. i18n: is that a request contains all of the conversation in one place. You can easily monitor a whole
462
.. i18n: discussion with the appropriate documents attached, and quickly review a list of incomplete
463
.. i18n: discussions with the history within each request.
465
.. note:: Requests vs. email
467
The advantage of an Open ERP request compared with a set of emails about one thread of discussion
468
is that a request contains all of the conversation in one place. You can easily monitor a whole
469
discussion with the appropriate documents attached, and quickly review a list of incomplete
470
discussions with the history within each request.
472
.. i18n: Look at the request and its history, then close it.
474
Look at the request and its history, then close it.
476
.. i18n: #. Click on the :guilabel:`History` tab in the :guilabel:`Request` form to see the
477
.. i18n: original request and all of the responses. By clicking on each line you could get more information
478
.. i18n: on each element.
480
.. i18n: #. Return to the first tab, :guilabel:`Request` and click :guilabel:`End of Request` to set it to \
481
.. i18n: ``closed``\. This then appears greyed out.
483
#. Click on the :guilabel:`History` tab in the :guilabel:`Request` form to see the
484
original request and all of the responses. By clicking on each line you could get more information
487
#. Return to the first tab, :guilabel:`Request` and click :guilabel:`End of Request` to set it to \
488
``closed``\. This then appears greyed out.
490
.. i18n: The request is no longer active. It's not visible to searches and won't appear in your list of
491
.. i18n: waiting requests.
493
The request is no longer active. It's not visible to searches and won't appear in your list of
496
.. i18n: .. tip:: Trigger dates
498
.. i18n: You can send a request with a future date. This request won't appear in the recipient's waiting
499
.. i18n: list until the indicated date. This mechanism is very useful for setting up alerts before an
500
.. i18n: important event.
502
.. tip:: Trigger dates
504
You can send a request with a future date. This request won't appear in the recipient's waiting
505
list until the indicated date. This mechanism is very useful for setting up alerts before an
509
.. i18n: single: user; configuration
512
single: user; configuration
514
.. i18n: Configuring Users
515
.. i18n: -------------------
520
.. i18n: The database you created contains minimal functionality but can be extended to include all of the
521
.. i18n: potential functionality available to Open ERP. About the only functions actually available in this
522
.. i18n: minimal database are Partners and Currencies – and these only because the definition of your main
523
.. i18n: company required this. And because you chose to include demonstration data, both Partners and
524
.. i18n: Currencies were installed with some samples.
526
The database you created contains minimal functionality but can be extended to include all of the
527
potential functionality available to Open ERP. About the only functions actually available in this
528
minimal database are Partners and Currencies – and these only because the definition of your main
529
company required this. And because you chose to include demonstration data, both Partners and
530
Currencies were installed with some samples.
533
.. i18n: single: administrator
536
single: administrator
538
.. i18n: Because you logged in as Administrator, you have all the access you need to configure users. Click
539
.. i18n: :menuselection:`Administration --> Users --> Users` to display the list of users defined in the
540
.. i18n: system. A second user, \ ``Demo User``\ , is also present in the system as part of the
541
.. i18n: demonstration data. Click the \ ``Demo User``\ name to open a non-editable form on that user.
543
Because you logged in as Administrator, you have all the access you need to configure users. Click
544
:menuselection:`Administration --> Users --> Users` to display the list of users defined in the
545
system. A second user, \ ``Demo User``\ , is also present in the system as part of the
546
demonstration data. Click the \ ``Demo User``\ name to open a non-editable form on that user.
548
.. i18n: Click the :guilabel:`Security` tab to see that the demo user is a member of only the ``Employee`` group,
549
.. i18n: has no roles
550
.. i18n: and is subject to no specialized rules. The \ ``admin``\ user is different, as you can see if you
551
.. i18n: follow the same sequence to review the its definition. It's a member of the \ ``admin``\ group,
552
.. i18n: which gives it more advanced rights to configure new users.
554
Click the :guilabel:`Security` tab to see that the demo user is a member of only the ``Employee`` group,
556
and is subject to no specialized rules. The \ ``admin``\ user is different, as you can see if you
557
follow the same sequence to review the its definition. It's a member of the \ ``admin``\ group,
558
which gives it more advanced rights to configure new users.
561
.. i18n: single: user; access
562
.. i18n: single: user; role
563
.. i18n: single: user; group
570
.. i18n: .. tip:: Roles, Groups and Users
572
.. i18n: Users and groups provide the structure for specifying access rights to different documents. Their
573
.. i18n: setup answers the question “Who has access to what?”
575
.. i18n: Roles are used in business processes for permitting or blocking certain steps in the workflow of a
576
.. i18n: given document. For example you can assign the role of approving an invoice. Roles answer the
577
.. i18n: question “Who should do what?”
579
.. tip:: Roles, Groups and Users
581
Users and groups provide the structure for specifying access rights to different documents. Their
582
setup answers the question “Who has access to what?”
584
Roles are used in business processes for permitting or blocking certain steps in the workflow of a
585
given document. For example you can assign the role of approving an invoice. Roles answer the
586
question “Who should do what?”
588
.. i18n: Click :menuselection:`Administration --> Users --> Groups` below the main menu to open the list of
589
.. i18n: groups defined in the system. If you open the form view of the \ ``admin``\ group by clicking its
590
.. i18n: name in the list, the first tab give you the list of all the users who belong to this group.
592
Click :menuselection:`Administration --> Users --> Groups` below the main menu to open the list of
593
groups defined in the system. If you open the form view of the \ ``admin``\ group by clicking its
594
name in the list, the first tab give you the list of all the users who belong to this group.
596
.. i18n: Click the Security tab and it gives you details of the access rights for that group. These are
597
.. i18n: detailed later in :ref:`ch-config`, but you can already see there further up in the window, the list of menus
598
.. i18n: reserved for the admin group. By convention, the \ ``admin``\ in Open ERP has rights of access to
599
.. i18n: the :menuselection:`Configuration` menu in each section. So \ ``Partners / Configuration``\ is
600
.. i18n: found in the list of access rights but \ ``Partners``\ isn't found there because it's accessible
601
.. i18n: to all users.
603
Click the Security tab and it gives you details of the access rights for that group. These are
604
detailed later in :ref:`ch-config`, but you can already see there further up in the window, the list of menus
605
reserved for the admin group. By convention, the \ ``admin``\ in Open ERP has rights of access to
606
the :menuselection:`Configuration` menu in each section. So \ ``Partners / Configuration``\ is
607
found in the list of access rights but \ ``Partners``\ isn't found there because it's accessible
610
.. i18n: You can create some new users to integrate them into the system. Assign them to predefined groups to
611
.. i18n: grant them certain access rights. Then try their access rights when you login as these users.
612
.. i18n: Management defines these access rights as described in :ref:`ch-config`.
614
You can create some new users to integrate them into the system. Assign them to predefined groups to
615
grant them certain access rights. Then try their access rights when you login as these users.
616
Management defines these access rights as described in :ref:`ch-config`.
618
.. i18n: .. note:: Changes to default access rights
620
.. i18n: New versions of Open ERP differ from earlier versions of Open ERP and Tiny ERP in this area:
621
.. i18n: many groups have been predefined and access to many of the menus and objects are keyed to these
622
.. i18n: groups by default.
623
.. i18n: This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
624
.. i18n: could be defined but were not activated by default.
626
.. note:: Changes to default access rights
628
New versions of Open ERP differ from earlier versions of Open ERP and Tiny ERP in this area:
629
many groups have been predefined and access to many of the menus and objects are keyed to these
631
This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
632
could be defined but were not activated by default.
635
.. i18n: single: partner; managing
638
single: partner; managing
640
.. i18n: Managing partners
641
.. i18n: -------------------
646
.. i18n: In Open ERP, a partner represents an entity that you do business with. That can be a prospect, a
647
.. i18n: customer, a supplier, or even an employee of your company.
649
In Open ERP, a partner represents an entity that you do business with. That can be a prospect, a
650
customer, a supplier, or even an employee of your company.
652
.. i18n: List of partners
653
.. i18n: ^^^^^^^^^^^^^^^^^
658
.. i18n: Click :menuselection:`Partners --> Partners` in the main menu to open the list of partners. Then
659
.. i18n: click the name of the first partner to get hold of the details – a form appears with several tabs
662
Click :menuselection:`Partners --> Partners` in the main menu to open the list of partners. Then
663
click the name of the first partner to get hold of the details – a form appears with several tabs
666
.. i18n: * the :guilabel:`General` tab contains the main information about the company, such as its corporate
667
.. i18n: name, its primary language, your different contacts at that partner and the categories it belongs
670
.. i18n: * the :guilabel:`Sales & Purchases` tab contains information that's slightly less immediate.
672
.. i18n: * the :menuselection:`History` tab contains the history of all the events that the partner has
673
.. i18n: been involved in. These events are created automatically by different system documents: invoices,
674
.. i18n: orders, support requests and so on, from a list that can be configured in the system.
675
.. i18n: These give you a rapid view of the partner's history on a single
678
.. i18n: * the :menuselection:`Notes` tab is an area for free text notes.
680
* the :guilabel:`General` tab contains the main information about the company, such as its corporate
681
name, its primary language, your different contacts at that partner and the categories it belongs
684
* the :guilabel:`Sales & Purchases` tab contains information that's slightly less immediate.
686
* the :menuselection:`History` tab contains the history of all the events that the partner has
687
been involved in. These events are created automatically by different system documents: invoices,
688
orders, support requests and so on, from a list that can be configured in the system.
689
These give you a rapid view of the partner's history on a single
692
* the :menuselection:`Notes` tab is an area for free text notes.
694
.. i18n: To the right of the form is a list of Reports, Actions and Links related to a partner. Click some of
695
.. i18n: them to get a feel for their use.
697
To the right of the form is a list of Reports, Actions and Links related to a partner. Click some of
698
them to get a feel for their use.
700
.. i18n: .. figure:: images/partner.png
701
.. i18n: :align: center
704
.. i18n: *Partner form*
706
.. figure:: images/partner.png
713
.. i18n: single: partner; category
716
single: partner; category
718
.. i18n: .. tip:: Partner Categories
720
.. i18n: Partner Categories enable you to segment different partners according to their relation with you
721
.. i18n: (client, prospect, supplier, and so on). A partner can belong to several categories – for example
722
.. i18n: it may be both a customer and supplier at the same time.
724
.. i18n: But there are also Customer, Supplier and Rental checkboxes on the partner form, which are different.
725
.. i18n: These checkboxes are designed to enable Open ERP to quickly select what should appear on some of the
726
.. i18n: system drop-down selection boxes. They, too, need to be set correctly.
728
.. tip:: Partner Categories
730
Partner Categories enable you to segment different partners according to their relation with you
731
(client, prospect, supplier, and so on). A partner can belong to several categories – for example
732
it may be both a customer and supplier at the same time.
734
But there are also Customer, Supplier and Rental checkboxes on the partner form, which are different.
735
These checkboxes are designed to enable Open ERP to quickly select what should appear on some of the
736
system drop-down selection boxes. They, too, need to be set correctly.
738
.. i18n: Partner Categories
739
.. i18n: ^^^^^^^^^^^^^^^^^^^
744
.. i18n: You can list your partners by category using the menu :menuselection:`Partners --> Partners by
745
.. i18n: category` . This opens a hierarchical structure of categories where each category can be divided
746
.. i18n: into sub-categories. Click a category to obtain a list of partners in that category. For example,
747
.. i18n: click all of the partners in the category :menuselection:`Supplier` or :menuselection:`Supplier -->
748
.. i18n: Components Supplier`. You'll see that if a company is in a subcategory (such as
749
.. i18n: :guilabel:`Components Supplier` ) then it will also show up when you click the parent category (such
750
.. i18n: as :guilabel:`Supplier`).
752
You can list your partners by category using the menu :menuselection:`Partners --> Partners by
753
category` . This opens a hierarchical structure of categories where each category can be divided
754
into sub-categories. Click a category to obtain a list of partners in that category. For example,
755
click all of the partners in the category :menuselection:`Supplier` or :menuselection:`Supplier -->
756
Components Supplier`. You'll see that if a company is in a subcategory (such as
757
:guilabel:`Components Supplier` ) then it will also show up when you click the parent category (such
758
as :guilabel:`Supplier`).
760
.. i18n: .. figure:: images/main_window_partner_menu_config.png
762
.. i18n: :align: center
764
.. i18n: *Categories of partner in a hierarchical structure, for example Customer, Prospect, Supplier*
766
.. figure:: images/main_window_partner_menu_config.png
770
*Categories of partner in a hierarchical structure, for example Customer, Prospect, Supplier*
772
.. i18n: The administrator can define new categories. So you'll create a new category and link it to a
775
The administrator can define new categories. So you'll create a new category and link it to a
778
.. i18n: #. Use :menuselection:`Partners --> Configuration --> Partner Categories` to reach a list
779
.. i18n: of the same categories as above but in a list view rather than a hierarchical tree structure.
781
.. i18n: #. Click :guilabel:`New` to open an empty form for creating a new category
783
.. i18n: #. Enter \ ``My Prospects``\ in the field :guilabel:`Name of Category`. Then click on the
784
.. i18n: :guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
785
.. i18n: \ ``Prospect``\ in the list that appears.
787
.. i18n: #. Then save your new category using the :guilabel:`Save` button.
789
#. Use :menuselection:`Partners --> Configuration --> Partner Categories` to reach a list
790
of the same categories as above but in a list view rather than a hierarchical tree structure.
792
#. Click :guilabel:`New` to open an empty form for creating a new category
794
#. Enter \ ``My Prospects``\ in the field :guilabel:`Name of Category`. Then click on the
795
:guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
796
\ ``Prospect``\ in the list that appears.
798
#. Then save your new category using the :guilabel:`Save` button.
800
.. i18n: .. tip:: Required Fields
802
.. i18n: Fields colored blue are required. If you try to save the form while any of these fields are empty
803
.. i18n: the field turns red to indicate that there's a problem. It's impossible to save the form until
804
.. i18n: you've completed every required field.
806
.. tip:: Required Fields
808
Fields colored blue are required. If you try to save the form while any of these fields are empty
809
the field turns red to indicate that there's a problem. It's impossible to save the form until
810
you've completed every required field.
812
.. i18n: You can review your new category structure using :menuselection:`Partners --> Partners by category`.
813
.. i18n: You should see the new structure of \ ``Prospects / My Prospects``\ there.
815
You can review your new category structure using :menuselection:`Partners --> Partners by category`.
816
You should see the new structure of \ ``Prospects / My Prospects``\ there.
818
.. i18n: .. figure:: images/main_window_partner_tab.png
820
.. i18n: :align: center
822
.. i18n: *Creating a new partner category*
824
.. figure:: images/main_window_partner_tab.png
828
*Creating a new partner category*
830
.. i18n: To create a new partner and link it to this new category open a new partner form to modify it.
832
To create a new partner and link it to this new category open a new partner form to modify it.
834
.. i18n: #. In the :guilabel:`General` tab, type \ ``New Partner``\ into the :guilabel:`Name` field.
836
.. i18n: #. Then click on the search icon to the right of the :guilabel:`Categories` field and select your
837
.. i18n: new category from the list that appears: \ ``Prospect / My Prospects``\
839
.. i18n: #. Then save your partner by clicking :guilabel:`Save` The partner now belongs in the category
840
.. i18n: \ ``Prospect / My prospects.``\
842
.. i18n: #. Monitor your modification in the menu :menuselection:`Partners --> Partners by category`. Select
843
.. i18n: the category :guilabel:`My Prospect`. The list of partners opens and you'll find your new partner
844
.. i18n: there in that list.
846
#. In the :guilabel:`General` tab, type \ ``New Partner``\ into the :guilabel:`Name` field.
848
#. Then click on the search icon to the right of the :guilabel:`Categories` field and select your
849
new category from the list that appears: \ ``Prospect / My Prospects``\
851
#. Then save your partner by clicking :guilabel:`Save` The partner now belongs in the category
852
\ ``Prospect / My prospects.``\
854
#. Monitor your modification in the menu :menuselection:`Partners --> Partners by category`. Select
855
the category :guilabel:`My Prospect`. The list of partners opens and you'll find your new partner
858
.. i18n: .. tip:: Searching for documents
860
.. i18n: If you need to search through a long list of partners it's best to use the available search
861
.. i18n: criteria rather than scroll through the whole partner list. It's a habit that'll save you a lot of
862
.. i18n: time in the long run as you search for all kinds of documents.
864
.. tip:: Searching for documents
866
If you need to search through a long list of partners it's best to use the available search
867
criteria rather than scroll through the whole partner list. It's a habit that'll save you a lot of
868
time in the long run as you search for all kinds of documents.
870
.. i18n: .. note:: Example Categories of partners
872
.. i18n: A partner can be assigned to several categories. These enable you to create alternative
873
.. i18n: classifications as necessary, usually in a hierarchical form.
875
.. i18n: Here are some structures that are often used:
877
.. i18n: * geographical locations,
879
.. i18n: * interest in certain product lines,
881
.. i18n: * subscriptions to newsletters,
883
.. i18n: * type of industry.
885
.. note:: Example Categories of partners
887
A partner can be assigned to several categories. These enable you to create alternative
888
classifications as necessary, usually in a hierarchical form.
890
Here are some structures that are often used:
892
* geographical locations,
894
* interest in certain product lines,
896
* subscriptions to newsletters,
900
.. i18n: .. Copyright © Open Object Press. All rights reserved.
902
.. Copyright © Open Object Press. All rights reserved.
904
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
905
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
907
.. You may take electronic copy of this publication and distribute it if you don't
908
.. change the content. You can also print a copy to be read by yourself only.
910
.. i18n: .. We have contracts with different publishers in different countries to sell and
911
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
912
.. i18n: .. in bookstores. This helps to distribute and promote the Open ERP product. It
913
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
914
.. i18n: .. rights of these sales.
916
.. We have contracts with different publishers in different countries to sell and
917
.. distribute paper or electronic based versions of this book (translated or not)
918
.. in bookstores. This helps to distribute and promote the Open ERP product. It
919
.. also helps us to create incentives to pay contributors and authors using author
920
.. rights of these sales.
922
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
923
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
924
.. i18n: .. written authorisation for this.
926
.. Due to this, grants to translate, modify or sell this book are strictly
927
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
928
.. written authorisation for this.
930
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
931
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
932
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
933
.. i18n: .. printed in initial capitals.
935
.. Many of the designations used by manufacturers and suppliers to distinguish their
936
.. products are claimed as trademarks. Where those designations appear in this book,
937
.. and Open Object Press was aware of a trademark claim, the designations have been
938
.. printed in initial capitals.
940
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
941
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
942
.. i18n: .. resulting from the use of the information contained herein.
944
.. While every precaution has been taken in the preparation of this book, the publisher
945
.. and the authors assume no responsibility for errors or omissions, or for damages
946
.. resulting from the use of the information contained herein.
948
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
950
.. Published by Open Object Press, Grand Rosière, Belgium