Merge lp://qastaging/~akretion-team/partner-contact-management/add-partner_relation into lp://qastaging/~partner-contact-core-editors/partner-contact-management/7.0
Status: | Needs review |
---|---|
Proposed branch: | lp://qastaging/~akretion-team/partner-contact-management/add-partner_relation |
Merge into: | lp://qastaging/~partner-contact-core-editors/partner-contact-management/7.0 |
Diff against target: |
914 lines (+866/-0) 8 files modified
partner_relation/__init__.py (+23/-0) partner_relation/__openerp__.py (+57/-0) partner_relation/i18n/fr.po (+171/-0) partner_relation/i18n/partner_relation.pot (+171/-0) partner_relation/partner_relation.py (+217/-0) partner_relation/partner_relation_demo.xml (+104/-0) partner_relation/partner_relation_view.xml (+118/-0) partner_relation/security/ir.model.access.csv (+5/-0) |
To merge this branch: | bzr merge lp://qastaging/~akretion-team/partner-contact-management/add-partner_relation |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lorenzo Battistini (community) | Needs Resubmitting | ||
Frère Bernard (community) | functionnal tests | Approve | |
Partner and Contact Core Editors | Pending | ||
Review via email: mp+220726@code.qastaging.launchpad.net |
Description of the change
This merge proposal adds a new module partner_relation. Here is the description :
===========
This module adds relations between partners. The type of relation is configurable ; it supports symetric and asymetric relations.
For example, you will be able to define on the form view of partner A that :
* Partner A is a competitor of Partner B (symetric relation : B is a competitor of A),
* Partner A has been recommended by Partner C (asymetric relation : C recommands A),
* Partner A is the editor of Partner D (asymetric relation : D is the integrator of A).
The relations that you define on Partner A towards Partner B will automatically be visible on the form view of Partner B.
============
Technically, it is not easy to implement in OpenERP. This implementation inherit the create() of the relation object to automatically generate a reverse relation (src_partner_id and dest_partner_id are swapped and the type of relation is the reverse if the relation is asymetric).
I have tried other implementations that would avoid to create a double entry for each relation, but all the other implementations were not good enough because I wanted relations to be simple and easy-to-use inside the partner form view.
This module is flake8 compliant, has demo data, ACLs, POT file and even an icon ! :)
Unmerged revisions
- 41. By Alexis de Lattre
-
Sort relation types by alphabetical order.
- 40. By Alexis de Lattre
-
Initial check-in of the module partner_relation.
as we discussed before, here my take to the same problem: https:/ /code.launchpad .net/~hbrunn/ +junk/partner_ relations
maybe we can throw that together