MitDesk — Purchase
| Answer procurement questions. Confirming a purchase order always asks. |
Technical name minddesk_purchase.
Edition: Pro and above. See Editions and how the modules fit together.
This bridge connects MitDesk to Purchase. It adds a fixed set of named tools. It is not a way to call any method on any model. Every call runs as the person who asks.
Odoo app it needs: Purchase (purchase).
Tools
| Tool | What happens | What it does |
|---|---|---|
purchase_order_search |
Reads | Search purchase orders. |
purchase_orders_to_confirm |
Reads | List requests for quotation that wait for confirmation. |
purchase_order_counts_by_state |
Reads | Count purchase orders by state. |
purchase_order_match_for_bill |
Reads | Compare a vendor bill proposal with purchase orders you can see. |
purchase_order_confirm |
Always asks first | Confirm requests for quotation into purchase orders. |
Why some steps always ask
Confirming a purchase order is on the permanent floor of state changes that always need a person.
On the 360 board
Card: Purchase.
Job roles it ships
A job role is a blueprint you hire a digital employee from. This needs MitDesk — Digital Employees. Without it the bridge still works.
- Procurement Coordinator: watches open requests for quotation. Confirmation stays behind approval.
Requirements
Needs minddesk, purchase.
Related
- Domain bridges: all bridges side by side.
- How consent works: when an action runs, asks or is refused.
- The modules: every module and what it needs.