Skip to content
Health
63/100
fair
  • Security25/25
    No findings
  • Activity0/25
    Last human commit 101 months ago
  • Required by20/25
    3 modules depend on it
  • Maturity18/25
    In 3 Odoo series since 8.0

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

Security findings
Grave / minor (static analysis)
Required by
3
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.02 MB
Module directory on disk
Code analysis 2 migration notes 1 model 1 view 0 HTTP endpoints

Description

Dependencies

Code analysis

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

Views touched 1

XML IDNameModelTypeStatus
view_purchase_requisition_form purchase.requisition.form.inherit purchase.requisition form Inherits purchase_requisition.view_purchase_requisition_form

HTTP endpoints 0

No HTTP endpoints found for this module.

Models touched 1

New fields (2)
  • consignee_id Many2one → res.partner
    domain=[('is_consignee', '=', True)] help='The person to whom the shipment is to be delivered.' args: 'res.partner', 'Consignee'
  • dest_address_id Many2one → res.partner
    args: 'res.partner', 'Delivery Address'
Public methods (2)
  • onchange_dest_address_id(self)
    @api.onchange('dest_address_id')
    Find a picking type from the address. There is a similar onchange in the module purchase_requisition_delivery_address. A similar logic to choose the picking type is used in the module framework_agreement_sourcing in github.com/OCA/vertical-ngo.
  • onchange_picking_type_id(self)
    @api.onchange('picking_type_id')
    If the picking type has an address, use it. We cannot empty the address if one is not found, because that gives a short circuit with the onchange of the address.

Loading…

Loading…