Skip to content
Health
32/100
poor
  • Security22/25
    1 minor finding
  • Activity0/25
    Last human commit 98 months ago
  • Required by5/25
    0 modules depend on it
  • Maturity5/25
    In 1 Odoo series since 10.0

Heuristic over the facts below, not an audit · How it's computed

Security findings
Grave / minor (static analysis)
Required by
0
Modules depending on it
External deps
0 pip · 0 bin
Python packages / system binaries
License
AGPL-3
No conflicts with its dependencies
Folder size
0.04 MB
Module directory on disk
Code analysis 2 migration notes 4 models 2 views 0 HTTP endpoints

Description

Dependencies

Odoo dependencies
OCA/partner-contact:
odoo/odoo:
- web
- bus
Python dependencies
None
System dependencies
None
Required by
None

Code analysis

Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.

Views touched 2

XML IDNameModelTypeStatus
form_res_partner_relation_type res.partner.relation.type form Inherits partner_multi_relation.form_res_partner_relation_type
view_partner_form view.partner.form res.partner form Inherits base.view_partner_form

HTTP endpoints 0

No HTTP endpoints found for this module.

Models touched 4

New fields (3)
  • has_partner_above Boolean
    compute='_compute_partners_above' readonly=True
  • partner_above_hierarchy Char
    compute='_compute_partners_above' readonly=True string='Upper level partners'
  • partner_above_ids One2many → res.partner.relation.hierarchy
    comodel_name='res.partner.relation.hierarchy' inverse_name='partner_id' readonly=True string='Partners above in hierarchy'
Public methods (1)
  • is_above(self, other_partner)
    @api.multi
    Check whether this partner is above other_partner.

New fields (0)

No new fields.

Public methods (1)
  • create(self, vals)
    @api.model
    Prevent contradictory links in hierarchy. We should not do this in a constraint, as those are only checked after creation has already been done, and other modules might fail when they process in invalid hierarchy when triggered on create. TODO: Prevent this also on write.

New fields (5)
  • hierarchy_display Char
    help='Compact representation of hierarchy' readonly=True required=True string='Hierarchy'
  • level Integer
    help='Number of levels that partner above is higher up' readonly=True required=True string='Level'
  • partner_above_id Many2one → res.partner
    comodel_name='res.partner' help='Partner somewhere above in the hierarchy' readonly=True required=True string='Partner above'
  • partner_below_id Many2one → res.partner
    comodel_name='res.partner' help='Partner immediately below partner above in the hierarchy' readonly=True required=True string='Partner below'
  • partner_id Many2one → res.partner
    comodel_name='res.partner' help='The partner at the base of the hierarchy' readonly=True required=True string='Partner'
Public methods (0)

No public methods.

New fields (1)
  • hierarchy Selection
    default='equal' help="Select wether the relation between the partners can be considered hierarchical. And if so which side is considered 'above'." selection=HIERARCHY_SELECTION string='Partners equal, right above, or left above'
Public methods (0)

No public methods.