2
.. i18n: To connect to Open ERP
3
.. i18n: =======================
7
=======================
9
.. i18n: Since this is the first time you've connected to it you'll have to
10
.. i18n: go through the Setup wizard in steps:
13
Since this is the first time you've connected to it you'll have to
14
go through the Setup wizard in steps:
16
.. i18n: #. :guilabel:`Select a profile` : select ``Minimal Profile`` and click :guilabel:`Next`.
18
.. i18n: #. At the :guilabel:`Define Main Company` step you should select your own :guilabel:`Company Name` and
19
.. i18n: :guilabel:`Currency`, and address details on the first tab :guilabel:`General Information`;
20
.. i18n: and add more details on the second tab :guilabel:`Report Information` including a logo,
21
.. i18n: if you have one, that appears on reports. Click :guilabel:`Next`.
23
.. i18n: #. At the :guilabel:`Summary` page you can go back to change details if you need.
24
.. i18n: Click the :guilabel:`Install` button.
26
.. i18n: #. Finally, at the :guilabel:`Installation done` page, click :guilabel:`Start Configuration`.
28
.. i18n: Configuration consists of a set of wizards that help you through options for the installed modules.
29
.. i18n: Hardly anything is installed so this is a very simple process at the moment.
31
.. i18n: #. At the first screen click :guilabel:`Continue` to go into the first wizard.
32
.. i18n: Choose :guilabel:`View Mode` : :guilabel:`Simplified Interface`
33
.. i18n: and then click :guilabel:`Set` to save it.
35
.. i18n: #. Click :guilabel:`Skip Step` to step over the next wizard, which would enable you to add other users.
37
.. i18n: #. You've now reached the end of the configuration so click :guilabel:`Continue` to start using the
38
.. i18n: system as the Administrator.
41
#. :guilabel:`Select a profile` : select ``Minimal Profile`` and click :guilabel:`Next`.
43
#. At the :guilabel:`Define Main Company` step you should select your own :guilabel:`Company Name` and
44
:guilabel:`Currency`, and address details on the first tab :guilabel:`General Information`;
45
and add more details on the second tab :guilabel:`Report Information` including a logo,
46
if you have one, that appears on reports. Click :guilabel:`Next`.
48
#. At the :guilabel:`Summary` page you can go back to change details if you need.
49
Click the :guilabel:`Install` button.
51
#. Finally, at the :guilabel:`Installation done` page, click :guilabel:`Start Configuration`.
53
Configuration consists of a set of wizards that help you through options for the installed modules.
54
Hardly anything is installed so this is a very simple process at the moment.
56
#. At the first screen click :guilabel:`Continue` to go into the first wizard.
57
Choose :guilabel:`View Mode` : :guilabel:`Simplified Interface`
58
and then click :guilabel:`Set` to save it.
60
#. Click :guilabel:`Skip Step` to step over the next wizard, which would enable you to add other users.
62
#. You've now reached the end of the configuration so click :guilabel:`Continue` to start using the
63
system as the Administrator.
66
.. i18n: single: administrator
72
.. i18n: Once you're displaying the main menu you're able to see the following screen items,
73
.. i18n: as shown in screenshot :ref:`fig-oech2-main`:
76
Once you're displaying the main menu you're able to see the following screen items,
77
as shown in screenshot :ref:`fig-oech2-main`:
79
.. i18n: * the :guilabel:`Preferences` toolbar to the top right, showing the user name, links to the :guilabel:`Home` page,
80
.. i18n: :guilabel:`Preferences`, :guilabel:`About` and :guilabel:`Logout`,
82
.. i18n: * just below you'll find information about the :guilabel:`Request` system,
84
.. i18n: * links to the :guilabel:`MAIN MENU` and the :guilabel:`SHORTCUTS`,
86
.. i18n: * information about copyright and the database you're logged into at the bottom of the page,
88
.. i18n: * the main contents of the window with by the menu toolbar to the left: links generally line up on
89
.. i18n: the right but there are none to show at the moment.
92
* the :guilabel:`Preferences` toolbar to the top right, showing the user name, links to the :guilabel:`Home` page,
93
:guilabel:`Preferences`, :guilabel:`About` and :guilabel:`Logout`,
95
* just below you'll find information about the :guilabel:`Request` system,
97
* links to the :guilabel:`MAIN MENU` and the :guilabel:`SHORTCUTS`,
99
* information about copyright and the database you're logged into at the bottom of the page,
101
* the main contents of the window with by the menu toolbar to the left: links generally line up on
102
the right but there are none to show at the moment.
104
.. i18n: .. _fig-oech2-main:
106
.. i18n: .. figure:: images/main_window_openerp_ch02.png
108
.. i18n: :align: center
110
.. i18n: *The Main Menu of the openerp_ch02 database*
115
.. figure:: images/main_window_openerp_ch02.png
119
*The Main Menu of the openerp_ch02 database*
121
.. i18n: Two menus are available on the left:
124
Two menus are available on the left:
126
.. i18n: * :menuselection:`Partners`,
128
.. i18n: * :menuselection:`Administration`.
131
* :menuselection:`Partners`,
133
* :menuselection:`Administration`.
136
.. i18n: single: Preferences
142
.. i18n: Preferences toolbar
143
.. i18n: ---------------------
147
---------------------
149
.. i18n: When you're connected to Open ERP the Preferences toolbar indicates which user you're connected as.
150
.. i18n: So it should currently be showing :guilabel:`Welcome Administrator` (unless you logged in as another
151
.. i18n: user and it's reflecting the name of that user instead).
154
When you're connected to Open ERP the Preferences toolbar indicates which user you're connected as.
155
So it should currently be showing :guilabel:`Welcome Administrator` (unless you logged in as another
156
user and it's reflecting the name of that user instead).
158
.. i18n: You'll find a link to the :guilabel:`Home` page to its right. This takes you to either the
159
.. i18n: dashboard or the available menus, depending on the user configuration. In the case of the \
160
.. i18n: ``openerp_ch02``\ database so far the Home page is the Main Menu. But in general each user of the
161
.. i18n: system is presented with a dashboard that's designed to show performance indicators and urgent
162
.. i18n: documents that are most useful to someone of the user's position in the company. You'll see how to
163
.. i18n: assign dashboards to different users in a later chapter, :ref:`ch-config`.
166
You'll find a link to the :guilabel:`Home` page to its right. This takes you to either the
167
dashboard or the available menus, depending on the user configuration. In the case of the \
168
``openerp_ch02``\ database so far the Home page is the Main Menu. But in general each user of the
169
system is presented with a dashboard that's designed to show performance indicators and urgent
170
documents that are most useful to someone of the user's position in the company. You'll see how to
171
assign dashboards to different users in a later chapter, :ref:`ch-config`.
174
.. i18n: single: timezone
180
.. i18n: .. tip:: Multi-nationals and time zones
182
.. i18n: If you have users in different countries, they can configure their own timezone. Timestamp displays
183
.. i18n: are then adjusted by reference to the user's own localization setting.
185
.. i18n: So if you have a team in India and a team in England, the times will automatically be converted. If
186
.. i18n: an Indian employee sets her working hours from 9 to 6 that will be converted and saved in the
187
.. i18n: server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
188
.. i18n: user's available time will be converted to English time.
191
.. tip:: Multi-nationals and time zones
193
If you have users in different countries, they can configure their own timezone. Timestamp displays
194
are then adjusted by reference to the user's own localization setting.
196
So if you have a team in India and a team in England, the times will automatically be converted. If
197
an Indian employee sets her working hours from 9 to 6 that will be converted and saved in the
198
server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
199
user's available time will be converted to English time.
201
.. i18n: The next element in the Toolbar is a link to :guilabel:`Preferences`. By clicking that link you
202
.. i18n: reach a page where the current user can set their password, a timezone, a working language, and
203
.. i18n: a signature:
206
The next element in the Toolbar is a link to :guilabel:`Preferences`. By clicking that link you
207
reach a page where the current user can set their password, a timezone, a working language, and
210
.. i18n: * The :guilabel:`Password` field gives the user the opportunity to change their own password.
211
.. i18n: You should take steps (perhaps written policies) to prevent users making these too trivial.
213
.. i18n: * The :guilabel:`Language` field enables the user's working language to be changed. But first the
214
.. i18n: system must be loaded with other languages for the user to be able to choose an alternative, which
215
.. i18n: is described in the next subsection of this chapter. This is a mandatory field, although might
216
.. i18n: initially be set as blank.
218
.. i18n: * The :guilabel:`Timezone` setting indicates the user's location to Open ERP. This can be different
219
.. i18n: from that of the server. All of the dates in the system are converted to the user's timezone
220
.. i18n: automatically.
222
.. i18n: * The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
223
.. i18n: from within OpenERP.
226
* The :guilabel:`Password` field gives the user the opportunity to change their own password.
227
You should take steps (perhaps written policies) to prevent users making these too trivial.
229
* The :guilabel:`Language` field enables the user's working language to be changed. But first the
230
system must be loaded with other languages for the user to be able to choose an alternative, which
231
is described in the next subsection of this chapter. This is a mandatory field, although might
232
initially be set as blank.
234
* The :guilabel:`Timezone` setting indicates the user's location to Open ERP. This can be different
235
from that of the server. All of the dates in the system are converted to the user's timezone
238
* The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
241
.. i18n: The :guilabel:`About` link gives information about the development of the Open ERP software and
242
.. i18n: various links to other information.
245
The :guilabel:`About` link gives information about the development of the Open ERP software and
246
various links to other information.
248
.. i18n: The :guilabel:`Logout` link enables you to logout and return to the original login page. You can
249
.. i18n: then login to another database, or to the same database as another user. This page also gives you
250
.. i18n: access to the super-administrator functions for managing databases on this server.
253
The :guilabel:`Logout` link enables you to logout and return to the original login page. You can
254
then login to another database, or to the same database as another user. This page also gives you
255
access to the super-administrator functions for managing databases on this server.
257
.. i18n: The :guilabel:`Requests` link sits just below this toolbar. It is only visible if you're logged into
258
.. i18n: a database. If your database is new it will say :guilabel:`No request`. You can click on that link
259
.. i18n: to look at requests that have been sent to you at any time.
262
The :guilabel:`Requests` link sits just below this toolbar. It is only visible if you're logged into
263
a database. If your database is new it will say :guilabel:`No request`. You can click on that link
264
to look at requests that have been sent to you at any time.
267
.. i18n: single: installation; language
271
single: installation; language
273
.. i18n: Installing a new language
274
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
277
Installing a new language
278
^^^^^^^^^^^^^^^^^^^^^^^^^^^
280
.. i18n: Each user of the system can work in his or her own language. More than twenty languages are
281
.. i18n: currently available besides English. Users select their working language using the Preferences link.
282
.. i18n: You can also assign a language to a partner (customer or supplier), in which case all the documents
283
.. i18n: sent to that partner will be automatically translated into that language.
286
Each user of the system can work in his or her own language. More than twenty languages are
287
currently available besides English. Users select their working language using the Preferences link.
288
You can also assign a language to a partner (customer or supplier), in which case all the documents
289
sent to that partner will be automatically translated into that language.
291
.. i18n: .. attention:: More information about languages
293
.. i18n: The base version of Open ERP is translated into the following languages: English, German, Chinese,
294
.. i18n: Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
296
.. i18n: But other languages are also available: Arabic, Afghan,
297
.. i18n: Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
300
.. attention:: More information about languages
302
The base version of Open ERP is translated into the following languages: English, German, Chinese,
303
Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
305
But other languages are also available: Arabic, Afghan,
306
Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
308
.. i18n: As administrator you can install a new main working language into the system.
311
As administrator you can install a new main working language into the system.
313
.. i18n: #. Select :menuselection:`Administration` in the Menu Toolbar and click
314
.. i18n: :menuselection:`Translations --> Load an Official Translation` in the main menu window,
316
.. i18n: #. Select the language to install, \ ``French``\ for example, and click on :guilabel:`Start
317
.. i18n: Installation`,
319
.. i18n: #. When the message :guilabel:`Installation done` appears in the :guilabel:`Language file loaded` window,
320
.. i18n: click :guilabel:`OK` to return to the menu. (Your system will actually need the French locale loaded
321
.. i18n: to be able to do this, so you may not be successful here.)
324
#. Select :menuselection:`Administration` in the Menu Toolbar and click
325
:menuselection:`Translations --> Load an Official Translation` in the main menu window,
327
#. Select the language to install, \ ``French``\ for example, and click on :guilabel:`Start
330
#. When the message :guilabel:`Installation done` appears in the :guilabel:`Language file loaded` window,
331
click :guilabel:`OK` to return to the menu. (Your system will actually need the French locale loaded
332
to be able to do this, so you may not be successful here.)
334
.. i18n: To see the effects of this installation change the preferences of your user to change the working
335
.. i18n: language (you may first need to ensure that you have explicitly selected English as your language,
336
.. i18n: rather than keep the default, before you're given the French option).
337
.. i18n: The main menu is immediately translated in the selected language. If you're using the GTK
338
.. i18n: client you'll first have to close the menu then open a new main menu to start seeing things in the
339
.. i18n: new language.
342
To see the effects of this installation change the preferences of your user to change the working
343
language (you may first need to ensure that you have explicitly selected English as your language,
344
rather than keep the default, before you're given the French option).
345
The main menu is immediately translated in the selected language. If you're using the GTK
346
client you'll first have to close the menu then open a new main menu to start seeing things in the
349
.. i18n: .. note:: Navigating the menu
351
.. i18n: From this point in the book navigation from the main menu is written as a series of menu entries
352
.. i18n: connected by the :menuselection:`-->` character. Instead of seeing “ Select Administration in
353
.. i18n: the Menu toolbar then click Translations > Load an Official Translation ” you'll just get “ use menu
354
.. i18n: :menuselection:`Administration --> Translations --> Load an Official Translation` ”.
357
.. note:: Navigating the menu
359
From this point in the book navigation from the main menu is written as a series of menu entries
360
connected by the :menuselection:`-->` character. Instead of seeing “ Select Administration in
361
the Menu toolbar then click Translations > Load an Official Translation ” you'll just get “ use menu
362
:menuselection:`Administration --> Translations --> Load an Official Translation` ”.
364
.. i18n: .. index:: requests
369
.. i18n: Requests as a mechanism for internal communication
370
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
373
Requests as a mechanism for internal communication
374
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
376
.. i18n: Requests are a powerful communication mechanism between users of the system. They're also used by
377
.. i18n: Open ERP itself to send system messages to users.
380
Requests are a powerful communication mechanism between users of the system. They're also used by
381
Open ERP itself to send system messages to users.
383
.. i18n: They have distinct advantages over traditional emails:
386
They have distinct advantages over traditional emails:
388
.. i18n: * requests are linked to other Open ERP documents,
390
.. i18n: * an event's history is attached to the request,
392
.. i18n: * you can monitor events effectively from the messages they've sent.
395
* requests are linked to other Open ERP documents,
397
* an event's history is attached to the request,
399
* you can monitor events effectively from the messages they've sent.
401
.. i18n: Open ERP uses this mechanism to inform users about certain system events. For example if there's a
402
.. i18n: problem concerning the procurement of a product a request is sent by Open ERP to the production
406
Open ERP uses this mechanism to inform users about certain system events. For example if there's a
407
problem concerning the procurement of a product a request is sent by Open ERP to the production
410
.. i18n: Send a request to get an understanding of its functionality:
413
Send a request to get an understanding of its functionality:
415
.. i18n: #. Click on the :guilabel:`Requests` link that should currently be showing :guilabel:`No Requests`.
416
.. i18n: This opens a window that lists all of your waiting requests.
418
.. i18n: #. Click :guilabel:`New` to create and send a new request.
420
.. i18n: #. Complete the subject of the request, such as \ ``How are things?``\ then give a description of the
421
.. i18n: enquiry in the field.
423
.. i18n: #. Click the :guilabel:`Search` button to the right of the :guilabel:`To` field and select
424
.. i18n: :guilabel:`Administrator` in the window that opens (that's the user that you're already connected
427
.. i18n: #. You can then link this request to other system documents using the :guilabel:`References` field,
428
.. i18n: which could, for example, be a partner or a quotation or a disputed invoice.
430
.. i18n: #. Click :guilabel:`Send` to send the request to the intended recipient – that's yourself in this
431
.. i18n: case. Then click :guilabel:`MAIN MENU` to return to the original screen.
434
#. Click on the :guilabel:`Requests` link that should currently be showing :guilabel:`No Requests`.
435
This opens a window that lists all of your waiting requests.
437
#. Click :guilabel:`New` to create and send a new request.
439
#. Complete the subject of the request, such as \ ``How are things?``\ then give a description of the
440
enquiry in the field.
442
#. Click the :guilabel:`Search` button to the right of the :guilabel:`To` field and select
443
:guilabel:`Administrator` in the window that opens (that's the user that you're already connected
446
#. You can then link this request to other system documents using the :guilabel:`References` field,
447
which could, for example, be a partner or a quotation or a disputed invoice.
449
#. Click :guilabel:`Send` to send the request to the intended recipient – that's yourself in this
450
case. Then click :guilabel:`MAIN MENU` to return to the original screen.
452
.. i18n: .. figure:: images/request_tab.png
453
.. i18n: :align: center
456
.. i18n: *Creating a new request*
459
.. figure:: images/request_tab.png
463
*Creating a new request*
465
.. i18n: To check your requests:
468
To check your requests:
470
.. i18n: #. Click on the link to the right of the :guilabel:`Requests` label to open a list of your
471
.. i18n: requests. (It's possible that you'll still see the statement :guilabel:`No Requests` because this
472
.. i18n: information is updated periodically rather than instantly.) The list of requests then opens and you
473
.. i18n: can see the requests you've been sent there.
475
.. i18n: #. Click the :guilabel:`Edit` icon, represented by a pencil, at the right hand end of the request
476
.. i18n: line. That opens the request in edit mode.
478
.. i18n: #. You can then click the :guilabel:`Reply` button and make your response in the
479
.. i18n: :guilabel:`Request` field that appears in place of the original message.
481
.. i18n: #. Click :guilabel:`Send` to save your response and send it to the original sender.
484
#. Click on the link to the right of the :guilabel:`Requests` label to open a list of your
485
requests. (It's possible that you'll still see the statement :guilabel:`No Requests` because this
486
information is updated periodically rather than instantly.) The list of requests then opens and you
487
can see the requests you've been sent there.
489
#. Click the :guilabel:`Edit` icon, represented by a pencil, at the right hand end of the request
490
line. That opens the request in edit mode.
492
#. You can then click the :guilabel:`Reply` button and make your response in the
493
:guilabel:`Request` field that appears in place of the original message.
495
#. Click :guilabel:`Send` to save your response and send it to the original sender.
497
.. i18n: .. note:: Requests vs. email
499
.. i18n: The advantage of an Open ERP request compared with a set of emails about one thread of discussion
500
.. i18n: is that a request contains all of the conversation in one place. You can easily monitor a whole
501
.. i18n: discussion with the appropriate documents attached, and quickly review a list of incomplete
502
.. i18n: discussions with the history within each request.
505
.. note:: Requests vs. email
507
The advantage of an Open ERP request compared with a set of emails about one thread of discussion
508
is that a request contains all of the conversation in one place. You can easily monitor a whole
509
discussion with the appropriate documents attached, and quickly review a list of incomplete
510
discussions with the history within each request.
512
.. i18n: Look at the request and its history, then close it.
515
Look at the request and its history, then close it.
517
.. i18n: #. Click on the :guilabel:`History` tab in the :guilabel:`Request` form to see the
518
.. i18n: original request and all of the responses. By clicking on each line you could get more information
519
.. i18n: on each element.
521
.. i18n: #. Return to the first tab, :guilabel:`Request` and click :guilabel:`End of Request` to set it to \
522
.. i18n: ``closed``\. This then appears greyed out.
525
#. Click on the :guilabel:`History` tab in the :guilabel:`Request` form to see the
526
original request and all of the responses. By clicking on each line you could get more information
529
#. Return to the first tab, :guilabel:`Request` and click :guilabel:`End of Request` to set it to \
530
``closed``\. This then appears greyed out.
532
.. i18n: The request is no longer active. It's not visible to searches and won't appear in your list of
533
.. i18n: waiting requests.
536
The request is no longer active. It's not visible to searches and won't appear in your list of
539
.. i18n: .. tip:: Trigger dates
541
.. i18n: You can send a request with a future date. This request won't appear in the recipient's waiting
542
.. i18n: list until the indicated date. This mechanism is very useful for setting up alerts before an
543
.. i18n: important event.
546
.. tip:: Trigger dates
548
You can send a request with a future date. This request won't appear in the recipient's waiting
549
list until the indicated date. This mechanism is very useful for setting up alerts before an
553
.. i18n: single: user; configuration
557
single: user; configuration
559
.. i18n: Configuring Users
560
.. i18n: -------------------
566
.. i18n: The database you created contains minimal functionality but can be extended to include all of the
567
.. i18n: potential functionality available to Open ERP. About the only functions actually available in this
568
.. i18n: minimal database are Partners and Currencies – and these only because the definition of your main
569
.. i18n: company required this. And because you chose to include demonstration data, both Partners and
570
.. i18n: Currencies were installed with some samples.
573
The database you created contains minimal functionality but can be extended to include all of the
574
potential functionality available to Open ERP. About the only functions actually available in this
575
minimal database are Partners and Currencies – and these only because the definition of your main
576
company required this. And because you chose to include demonstration data, both Partners and
577
Currencies were installed with some samples.
580
.. i18n: single: administrator
584
single: administrator
586
.. i18n: Because you logged in as Administrator, you have all the access you need to configure users. Click
587
.. i18n: :menuselection:`Administration --> Users --> Users` to display the list of users defined in the
588
.. i18n: system. A second user, \ ``Demo User``\ , is also present in the system as part of the
589
.. i18n: demonstration data. Click the \ ``Demo User``\ name to open a non-editable form on that user.
592
Because you logged in as Administrator, you have all the access you need to configure users. Click
593
:menuselection:`Administration --> Users --> Users` to display the list of users defined in the
594
system. A second user, \ ``Demo User``\ , is also present in the system as part of the
595
demonstration data. Click the \ ``Demo User``\ name to open a non-editable form on that user.
597
.. i18n: Click the :guilabel:`Groups` tab to see that the demo user is a member of only the ``Employee`` group,
598
.. i18n: has no roles
599
.. i18n: and is subject to no specialized rules. The \ ``admin``\ user is different, as you can see if you
600
.. i18n: follow the same sequence to review the its definition. It's a member of the \ ``admin``\ group,
601
.. i18n: which gives it more advanced rights to configure new users.
604
Click the :guilabel:`Groups` tab to see that the demo user is a member of only the ``Employee`` group,
606
and is subject to no specialized rules. The \ ``admin``\ user is different, as you can see if you
607
follow the same sequence to review the its definition. It's a member of the \ ``admin``\ group,
608
which gives it more advanced rights to configure new users.
611
.. i18n: single: user; access
612
.. i18n: single: user; role
613
.. i18n: single: user; group
621
.. i18n: .. tip:: Roles, Groups and Users
623
.. i18n: Users and groups provide the structure for specifying access rights to different documents. Their
624
.. i18n: setup answers the question “Who has access to what?”
626
.. i18n: Roles are used in business processes for permitting or blocking certain steps in the workflow of a
627
.. i18n: given document. For example you can assign the role of approving an invoice. Roles answer the
628
.. i18n: question “Who should do what?”
631
.. tip:: Roles, Groups and Users
633
Users and groups provide the structure for specifying access rights to different documents. Their
634
setup answers the question “Who has access to what?”
636
Roles are used in business processes for permitting or blocking certain steps in the workflow of a
637
given document. For example you can assign the role of approving an invoice. Roles answer the
638
question “Who should do what?”
640
.. i18n: Click :menuselection:`Administration --> Users --> Groups` below the main menu to open the list of
641
.. i18n: groups defined in the system. If you open the form view of the \ ``admin``\ group by clicking its
642
.. i18n: name in the list, the first tab give you the list of all the users who belong to this group.
645
Click :menuselection:`Administration --> Users --> Groups` below the main menu to open the list of
646
groups defined in the system. If you open the form view of the \ ``admin``\ group by clicking its
647
name in the list, the first tab give you the list of all the users who belong to this group.
649
.. i18n: Click the Security tab and it gives you details of the access rights for that group. These are
650
.. i18n: detailed later in :ref:`ch-config`, but you can already see there further up in the window, the list of menus
651
.. i18n: reserved for the admin group. By convention, the \ ``admin``\ in Open ERP has rights of access to
652
.. i18n: the :menuselection:`Configuration` menu in each section. So \ ``Partners / Configuration``\ is
653
.. i18n: found in the list of access rights but \ ``Partners``\ isn't found there because it's accessible
654
.. i18n: to all users.
657
Click the Security tab and it gives you details of the access rights for that group. These are
658
detailed later in :ref:`ch-config`, but you can already see there further up in the window, the list of menus
659
reserved for the admin group. By convention, the \ ``admin``\ in Open ERP has rights of access to
660
the :menuselection:`Configuration` menu in each section. So \ ``Partners / Configuration``\ is
661
found in the list of access rights but \ ``Partners``\ isn't found there because it's accessible
664
.. i18n: You can create some new users to integrate them into the system. Assign them to predefined groups to
665
.. i18n: grant them certain access rights. Then try their access rights when you login as these users.
666
.. i18n: Management defines these access rights as described in :ref:`ch-config`.
669
You can create some new users to integrate them into the system. Assign them to predefined groups to
670
grant them certain access rights. Then try their access rights when you login as these users.
671
Management defines these access rights as described in :ref:`ch-config`.
673
.. i18n: .. note:: Changes to default access rights
675
.. i18n: New versions of OpenERP differ from earlier versions of OpenERP and Tiny ERP in this area:
676
.. i18n: many groups have been predefined and access to many of the menus and objects are keyed to these
677
.. i18n: groups by default.
678
.. i18n: This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
679
.. i18n: could be defined but were not activated by default.
682
.. note:: Changes to default access rights
684
New versions of OpenERP differ from earlier versions of OpenERP and Tiny ERP in this area:
685
many groups have been predefined and access to many of the menus and objects are keyed to these
687
This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
688
could be defined but were not activated by default.
691
.. i18n: single: partner; managing
695
single: partner; managing
697
.. i18n: Managing partners
698
.. i18n: -------------------
704
.. i18n: In Open ERP, a partner represents an entity that you do business with. That can be a prospect, a
705
.. i18n: customer, a supplier, or even an employee of your company.
708
In Open ERP, a partner represents an entity that you do business with. That can be a prospect, a
709
customer, a supplier, or even an employee of your company.
711
.. i18n: List of partners
712
.. i18n: ^^^^^^^^^^^^^^^^^
718
.. i18n: Click :menuselection:`Partners --> Partners` in the main menu to open the list of partners. Then
719
.. i18n: click the name of the first partner to get hold of the details – a form appears with several tabs
723
Click :menuselection:`Partners --> Partners` in the main menu to open the list of partners. Then
724
click the name of the first partner to get hold of the details – a form appears with several tabs
727
.. i18n: * the :guilabel:`General` tab contains the main information about the company, such as its corporate
728
.. i18n: name, its primary language, your different contacts at that partner and the categories it belongs
731
.. i18n: * the :guilabel:`Sales & Purchases` tab contains information that's slightly less immediate.
733
.. i18n: * the :menuselection:`History` tab contains the history of all the events that the partner has
734
.. i18n: been involved in. These events are created automatically by different system documents: invoices,
735
.. i18n: orders, support requests and so on, from a list that can be configured in the system.
736
.. i18n: These give you a rapid view of the partner's history on a single
739
.. i18n: * the :menuselection:`Notes` tab is an area for free text notes.
742
* the :guilabel:`General` tab contains the main information about the company, such as its corporate
743
name, its primary language, your different contacts at that partner and the categories it belongs
746
* the :guilabel:`Sales & Purchases` tab contains information that's slightly less immediate.
748
* the :menuselection:`History` tab contains the history of all the events that the partner has
749
been involved in. These events are created automatically by different system documents: invoices,
750
orders, support requests and so on, from a list that can be configured in the system.
751
These give you a rapid view of the partner's history on a single
754
* the :menuselection:`Notes` tab is an area for free text notes.
756
.. i18n: To the right of the form is a list of Reports, Actions and Links related to a partner. Click some of
757
.. i18n: them to get a feel for their use.
760
To the right of the form is a list of Reports, Actions and Links related to a partner. Click some of
761
them to get a feel for their use.
763
.. i18n: .. figure:: images/partner.png
764
.. i18n: :align: center
767
.. i18n: *Partner form*
770
.. figure:: images/partner.png
777
.. i18n: single: partner; category
781
single: partner; category
783
.. i18n: .. tip:: Partner Categories
785
.. i18n: Partner Categories enable you to segment different partners according to their relation with you
786
.. i18n: (client, prospect, supplier, and so on). A partner can belong to several categories – for example
787
.. i18n: it may be both a customer and supplier at the same time.
789
.. i18n: But there are also Customer, Supplier and Rental checkboxes on the partner form, which are different.
790
.. i18n: These checkboxes are designed to enable OpenERP to quickly select what should appear on some of the
791
.. i18n: system drop-down selection boxes. They, too, need to be set correctly.
794
.. tip:: Partner Categories
796
Partner Categories enable you to segment different partners according to their relation with you
797
(client, prospect, supplier, and so on). A partner can belong to several categories – for example
798
it may be both a customer and supplier at the same time.
800
But there are also Customer, Supplier and Rental checkboxes on the partner form, which are different.
801
These checkboxes are designed to enable OpenERP to quickly select what should appear on some of the
802
system drop-down selection boxes. They, too, need to be set correctly.
804
.. i18n: Partner Categories
805
.. i18n: ^^^^^^^^^^^^^^^^^^^
811
.. i18n: You can list your partners by category using the menu :menuselection:`Partners --> Partners by
812
.. i18n: category` . This opens a hierarchical structure of categories where each category can be divided
813
.. i18n: into sub-categories. Click a category to obtain a list of partners in that category. For example,
814
.. i18n: click all of the partners in the category :menuselection:`Supplier` or :menuselection:`Supplier -->
815
.. i18n: Components Supplier`. You'll see that if a company is in a subcategory (such as
816
.. i18n: :guilabel:`Components Supplier` ) then it will also show up when you click the parent category (such
817
.. i18n: as :guilabel:`Supplier`).
820
You can list your partners by category using the menu :menuselection:`Partners --> Partners by
821
category` . This opens a hierarchical structure of categories where each category can be divided
822
into sub-categories. Click a category to obtain a list of partners in that category. For example,
823
click all of the partners in the category :menuselection:`Supplier` or :menuselection:`Supplier -->
824
Components Supplier`. You'll see that if a company is in a subcategory (such as
825
:guilabel:`Components Supplier` ) then it will also show up when you click the parent category (such
826
as :guilabel:`Supplier`).
828
.. i18n: .. figure:: images/main_window_partner_menu_config.png
830
.. i18n: :align: center
832
.. i18n: *Categories of partner in a hierarchical structure, for example Customer, Prospect, Supplier*
835
.. figure:: images/main_window_partner_menu_config.png
839
*Categories of partner in a hierarchical structure, for example Customer, Prospect, Supplier*
841
.. i18n: The administrator can define new categories. So you'll create a new category and link it to a
845
The administrator can define new categories. So you'll create a new category and link it to a
848
.. i18n: #. Use :menuselection:`Partners --> Configuration --> Partner Categories` to reach a list
849
.. i18n: of the same categories as above but in a list view rather than a hierarchical tree structure.
851
.. i18n: #. Click :guilabel:`New` to open an empty form for creating a new category
853
.. i18n: #. Enter \ ``My Prospects``\ in the field :guilabel:`Name of Category`. Then click on the
854
.. i18n: :guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
855
.. i18n: \ ``Prospect``\ in the list that appears.
857
.. i18n: #. Then save your new category using the :guilabel:`Save` button.
860
#. Use :menuselection:`Partners --> Configuration --> Partner Categories` to reach a list
861
of the same categories as above but in a list view rather than a hierarchical tree structure.
863
#. Click :guilabel:`New` to open an empty form for creating a new category
865
#. Enter \ ``My Prospects``\ in the field :guilabel:`Name of Category`. Then click on the
866
:guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
867
\ ``Prospect``\ in the list that appears.
869
#. Then save your new category using the :guilabel:`Save` button.
871
.. i18n: .. tip:: Required Fields
873
.. i18n: Fields colored blue are required. If you try to save the form while any of these fields are empty
874
.. i18n: the field turns red to indicate that there's a problem. It's impossible to save the form until
875
.. i18n: you've completed every required field.
878
.. tip:: Required Fields
880
Fields colored blue are required. If you try to save the form while any of these fields are empty
881
the field turns red to indicate that there's a problem. It's impossible to save the form until
882
you've completed every required field.
884
.. i18n: You can review your new category structure using :menuselection:`Partners --> Partners by category`.
885
.. i18n: You should see the new structure of \ ``Prospects / My Prospects``\ there.
888
You can review your new category structure using :menuselection:`Partners --> Partners by category`.
889
You should see the new structure of \ ``Prospects / My Prospects``\ there.
891
.. i18n: .. figure:: images/main_window_partner_tab.png
893
.. i18n: :align: center
895
.. i18n: *Creating a new partner category*
898
.. figure:: images/main_window_partner_tab.png
902
*Creating a new partner category*
904
.. i18n: To create a new partner and link it to this new category open a new partner form to modify it.
907
To create a new partner and link it to this new category open a new partner form to modify it.
909
.. i18n: #. In the :guilabel:`General` tab, type \ ``New Partner``\ into the :guilabel:`Name` field.
911
.. i18n: #. Then click on the search icon to the right of the :guilabel:`Categories` field and select your
912
.. i18n: new category from the list that appears: \ ``Prospect / My Prospects``\
914
.. i18n: #. Then save your partner by clicking :guilabel:`Save` The partner now belongs in the category
915
.. i18n: \ ``Prospect / My prospects.``\
917
.. i18n: #. Monitor your modification in the menu :menuselection:`Partners --> Partners by category`. Select
918
.. i18n: the category :guilabel:`My Prospect`. The list of partners opens and you'll find your new partner
919
.. i18n: there in that list.
922
#. In the :guilabel:`General` tab, type \ ``New Partner``\ into the :guilabel:`Name` field.
924
#. Then click on the search icon to the right of the :guilabel:`Categories` field and select your
925
new category from the list that appears: \ ``Prospect / My Prospects``\
927
#. Then save your partner by clicking :guilabel:`Save` The partner now belongs in the category
928
\ ``Prospect / My prospects.``\
930
#. Monitor your modification in the menu :menuselection:`Partners --> Partners by category`. Select
931
the category :guilabel:`My Prospect`. The list of partners opens and you'll find your new partner
934
.. i18n: .. tip:: Searching for documents
936
.. i18n: If you need to search through a long list of partners it's best to use the available search
937
.. i18n: criteria rather than scroll through the whole partner list. It's a habit that'll save you a lot of
938
.. i18n: time in the long run as you search for all kinds of documents.
941
.. tip:: Searching for documents
943
If you need to search through a long list of partners it's best to use the available search
944
criteria rather than scroll through the whole partner list. It's a habit that'll save you a lot of
945
time in the long run as you search for all kinds of documents.
947
.. i18n: .. note:: Example Categories of partners
949
.. i18n: A partner can be assigned to several categories. These enable you to create alternative
950
.. i18n: classifications as necessary, usually in a hierarchical form.
952
.. i18n: Here are some structures that are often used:
954
.. i18n: * geographical locations,
956
.. i18n: * interest in certain product lines,
958
.. i18n: * subscriptions to newsletters,
960
.. i18n: * type of industry.
963
.. note:: Example Categories of partners
965
A partner can be assigned to several categories. These enable you to create alternative
966
classifications as necessary, usually in a hierarchical form.
968
Here are some structures that are often used:
970
* geographical locations,
972
* interest in certain product lines,
974
* subscriptions to newsletters,
978
.. i18n: .. Copyright © Open Object Press. All rights reserved.
981
.. Copyright © Open Object Press. All rights reserved.
983
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
984
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
987
.. You may take electronic copy of this publication and distribute it if you don't
988
.. change the content. You can also print a copy to be read by yourself only.
990
.. i18n: .. We have contracts with different publishers in different countries to sell and
991
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
992
.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
993
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
994
.. i18n: .. rights of these sales.
997
.. We have contracts with different publishers in different countries to sell and
998
.. distribute paper or electronic based versions of this book (translated or not)
999
.. in bookstores. This helps to distribute and promote the OpenERP product. It
1000
.. also helps us to create incentives to pay contributors and authors using author
1001
.. rights of these sales.
1003
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
1004
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1005
.. i18n: .. written authorisation for this.
1008
.. Due to this, grants to translate, modify or sell this book are strictly
1009
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1010
.. written authorisation for this.
1012
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
1013
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
1014
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
1015
.. i18n: .. printed in initial capitals.
1018
.. Many of the designations used by manufacturers and suppliers to distinguish their
1019
.. products are claimed as trademarks. Where those designations appear in this book,
1020
.. and Open Object Press was aware of a trademark claim, the designations have been
1021
.. printed in initial capitals.
1023
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
1024
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
1025
.. i18n: .. resulting from the use of the information contained herein.
1028
.. While every precaution has been taken in the preparation of this book, the publisher
1029
.. and the authors assume no responsibility for errors or omissions, or for damages
1030
.. resulting from the use of the information contained herein.
1032
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
1035
.. Published by Open Object Press, Grand Rosière, Belgium
added
removed
i18n/ru/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.rst
