TIP: You can type at any time to perform a new search.
Sale Orders Terms and conditions Templates
sale_order_note_template · OCA/sale-workflow
- Repository
- OCA/sale-workflow · module folder · Try on Runboat
- Module version
- 1.0.0
- Category
- Sales/Sales
- Folder size
- 0.05 MB
- License
- AGPL-3
- Application
- No
- Auto-installable
- No
- Website
- https://github.com/OCA/sale-workflow
- Last tracking update
- 2026-08-07 09:06:23
- Authors
- Odoo Community Association (OCA), Pierre Verkest
- Maintainers
- Odoo Community Association (OCA), Pierre Verkest
- Committers
- OCA-git-bot, oca-ci, Bhavesh Heliconia
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- None
- Description
This module add sale terms and conditions templates and change existing terms and conditions (sale_order.note) field type from Text to Html. Users will be able to select *terms and conditions template* to fulfill *terms and conditions* likes in mail composer users can configure their template using jinja2. ## How this module differ from [sale_comment_template](https://github.com/OCA/sale-reporting/tree/14.0/sale_comment_template)? - [base_comment_template](https://github.com/OCA/reporting-engine/tree/14.0/base_comment_template) is for managing comments not terms, it would probably see as mess for users to mixed terms and comments. - [sale_comment_template](https://github.com/OCA/sale-reporting/tree/14.0/sale_comment_template) depends on [account_comment_template](https://github.com/OCA/account-invoice-reporting/tree/14.0/account_comment_template) comments are forwards to generated invoices, here we don't really display sales terms on final invoices - [base_comment_template](https://github.com/OCA/reporting-engine/tree/14.0/base_comment_template) at the time writing do not support template engine
Code Analysis ⓘ
Views touched (4)
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
view_order_form_terms_template |
sale_order_note_templatesale.order.form | sale.order | form | Inherits sale.view_order_form |
view_sale_terms_template_form |
sale.terms_template.form | sale.terms_template | form | New |
view_sale_terms_template_search |
sale.terms_template.search | sale.terms_template | search | New |
view_sale_terms_template_tree |
sale.terms_template.list | sale.terms_template | list | New |
HTTP endpoints (0)
No HTTP endpoints found for this module.
Models touched (2)
New fields (2)
-
noteHtml -
terms_template_idMany2one → sale.terms_templatestring='Terms and conditions template' args: 'sale.terms_template'
No public methods.
New fields (3)
-
activeBooleandefault=True -
nameCharrequired=True -
textHtmlstring='Terms template'translate=True
-
get_value(self, sale_order, add_context=None, post_process=True)Get sales terms from template. Like in mail composer `text` template can use jinja or qweb syntax. if `partner_id` is provide, it will retreive it's lang to use the right translation. Then template is populated with model/res_id attributes according jinja/qweb instructions. :param sale_order: recordset (browsed) sale order :param add_context: context forwarded to the templating engine :param post_process: what ever to use `post_process` from the templating engine. If `True` urls are transform to absolute urls
Loading…
Loading…
Loading…