audrius/reporting-engine
1
0
Fork 1
mirror of https://github.com/OCA/reporting-engine.git synced 2025-02-16 16:30:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

[IMP] base_comment_template: pre-commit auto fixes

Browse Source
This commit is contained in:
Jesús Alan Ramos Rodríguez
2024-05-03 10:00:37 -06:00
parent e1e49f8b34
commit 7234782c24
11 changed files with 257 additions and 213 deletions
Download Patch File Download Diff File Expand all files Collapse all files

161
base_comment_template/README.rst
View File

@@ -17,40 +17,44 @@ Base Comments Templates
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Freporting--engine-lightgray.png?logo=github
:target: https://github.com/OCA/reporting-engine/tree/16.0/base_comment_template
:target: https://github.com/OCA/reporting-engine/tree/17.0/base_comment_template
:alt: OCA/reporting-engine
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
:target: https://translation.odoo-community.org/projects/reporting-engine-16-0/reporting-engine-16-0-base_comment_template
:target: https://translation.odoo-community.org/projects/reporting-engine-17-0/reporting-engine-17-0-base_comment_template
:alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
:target: https://runboat.odoo-community.org/builds?repo=OCA/reporting-engine&target_branch=16.0
:target: https://runboat.odoo-community.org/builds?repo=OCA/reporting-engine&target_branch=17.0
:alt: Try me on Runboat
|badge1| |badge2| |badge3| |badge4| |badge5|
Add a new mixin class to define templates of comments to print on documents.
The comment templates can be defined like make templates, so you can use variables from linked models.
Add a new mixin class to define templates of comments to print on
documents. The comment templates can be defined like make templates, so
you can use variables from linked models.
Two positions are available for the comments:
* above document lines (before_lines)
* below document lines (after_lines)
- above document lines (before_lines)
- below document lines (after_lines)
The template are general, and can be attached to any Model and based on some domain defined in the template.
You can define one default template per Model and domain, which can be overwritten for any company and partners.
It has a priority field (smaller number = higher priority)
The template are general, and can be attached to any Model and based on
some domain defined in the template. You can define one default template
per Model and domain, which can be overwritten for any company and
partners. It has a priority field (smaller number = higher priority)
In existing reports, if you add this line will get the comment template if you created one like
* <span t-out="o.get_comment_template('position',company_id=o.company_id, partner_id=o.parnter_id )"/> ( or without any parameter)
In existing reports, if you add this line will get the comment template
if you created one like
- <span
t-out="o.get_comment_template('position',company_id=o.company_id,
partner_id=o.parnter_id )"/> ( or without any parameter)
This module is the base module for following modules:
* sale_comment_template
* purchase_comment_template
* account_comment_template
* stock_picking_comment_template
- sale_comment_template
- purchase_comment_template
- account_comment_template
- stock_picking_comment_template
**Table of contents**
@@ -60,60 +64,73 @@ This module is the base module for following modules:
Configuration
=============
Go to *Settings > Technical > Reporting > Comment Templates* and start designing you comment templates.
Go to *Settings > Technical > Reporting > Comment Templates* and start
designing you comment templates.
This module is the base module for following modules:
* sale_comment_template
* purchase_comment_template
* invoice_comment_template
* stock_picking_comment_template
- sale_comment_template
- purchase_comment_template
- invoice_comment_template
- stock_picking_comment_template
Usage
=====
#. Go to *Settings* and activate the developer mode.
#. Go to *Settings > Technical > Reporting > Comment Templates*.
#. Create a new record.
#. Define the Company the template is linked or leave default for all companies.
#. Define the Partner the template is linked or leave default for all partners.
#. Define the Model, Domain the template is linked.
#. Define the Position where the template will be printed:
1. Go to *Settings* and activate the developer mode.
2. Go to *Settings > Technical > Reporting > Comment Templates*.
3. Create a new record.
4. Define the Company the template is linked or leave default for all
companies.
5. Define the Partner the template is linked or leave default for all
partners.
6. Define the Model, Domain the template is linked.
7. Define the Position where the template will be printed:
* above document lines
* below document lines
- above document lines
- below document lines
You should have at least one template with Default field set, if you choose a Partner the template is deselected as a Default one.
If you create a new template with the same configuration (Model, Domain, Position) and set it as Default, the previous one will be deselected as a default one.
You should have at least one template with Default field set, if you
choose a Partner the template is deselected as a Default one. If you
create a new template with the same configuration (Model, Domain,
Position) and set it as Default, the previous one will be deselected as
a default one.
The template is a html field which will be rendered just like a mail template, so you can use variables like {{object}}, {{user}}, {{ctx}} to add dynamic content.
The template is a html field which will be rendered just like a mail
template, so you can use variables like {{object}}, {{user}}, {{ctx}} to
add dynamic content.
Change the report related to the model from configuration and add a statement like:
Change the report related to the model from configuration and add a
statement like:
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top">
<div t-out="o.render_comment(comment_template_top)" />
| <t t-foreach="o.comment_template_ids.filtered(lambda x: x.position ==
'before_lines')" t-as="comment_template_top">
| <div t-out="o.render_comment(comment_template_top)" />
</t>
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'after_lines')" t-as="comment_template_bottom">
<div t-out="o.render_comment(comment_template_bottom)" />
| <t t-foreach="o.comment_template_ids.filtered(lambda x: x.position ==
'after_lines')" t-as="comment_template_bottom">
| <div t-out="o.render_comment(comment_template_bottom)" />
</t>
You should always use t-if since the method returns False if no template is found.
You should always use t-if since the method returns False if no template
is found.
If you want to use Qweb templates, or different context, you can specify it just like in
mail.render.mixin with parameters:
If you want to use Qweb templates, or different context, you can specify
it just like in mail.render.mixin with parameters:
- engine: "inline_template", "qweb" or "qweb_view",
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result
- engine: "inline_template", "qweb" or "qweb_view",
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result
so you could use it :
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top">
<div t-out="o.render_comment(comment_template_top, engine='qweb', add_context={my dict}, postprocess=True)" />
| <t t-foreach="o.comment_template_ids.filtered(lambda x: x.position ==
'before_lines')" t-as="comment_template_top">
| <div t-out="o.render_comment(comment_template_top, engine='qweb',
add_context={my dict}, postprocess=True)" />
</t>
@@ -123,7 +140,7 @@ Bug Tracker
Bugs are tracked on `GitHub Issues <https://github.com/OCA/reporting-engine/issues>`_.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
`feedback <https://github.com/OCA/reporting-engine/issues/new?body=module:%20base_comment_template%0Aversion:%2016.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
`feedback <https://github.com/OCA/reporting-engine/issues/new?body=module:%20base_comment_template%0Aversion:%2017.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
Do not contact contributors directly about support or help with technical issues.
@@ -131,46 +148,46 @@ Credits
=======
Authors
~~~~~~~
-------
* Camptocamp
Contributors
~~~~~~~~~~~~
------------
* Xavier Jimenez <xavier.jimenez@qubiq.es>
* Nicolas Bessi <nicolas.bessi@camptocamp.com>
* Yannick Vaucher <yannick.vaucher@camptocamp.com>
* Guewen Baconnier <guewen.baconnier@camptocamp.com>
* Simone Rubino <simone.rubino@agilebg.com>
* `DynApps <https://www.dynapps.be>`_:
- Xavier Jimenez <xavier.jimenez@qubiq.es>
- Nicolas Bessi <nicolas.bessi@camptocamp.com>
- Yannick Vaucher <yannick.vaucher@camptocamp.com>
- Guewen Baconnier <guewen.baconnier@camptocamp.com>
- Simone Rubino <simone.rubino@agilebg.com>
- `DynApps <https://www.dynapps.be>`__:
* Raf Ven <raf.ven@dynapps.be>
- Raf Ven <raf.ven@dynapps.be>
* `Druidoo <https://www.druidoo.io>`_:
- `Druidoo <https://www.druidoo.io>`__:
* Iván Todorovich <ivan.todorovich@druidoo.io>
* Pierre Verkest <pierreverkest84@gmail.com>
- Iván Todorovich <ivan.todorovich@druidoo.io>
* `NextERP Romania <https://www.nexterp.ro>`_:
- Pierre Verkest <pierreverkest84@gmail.com>
- `NextERP Romania <https://www.nexterp.ro>`__:
* Fekete Mihai <feketemihai@nexterp.ro>
- Fekete Mihai <feketemihai@nexterp.ro>
* `Tecnativa <https://www.tecnativa.com>`_:
- `Tecnativa <https://www.tecnativa.com>`__:
* Carlos Roca
* Víctor Martínez
- Carlos Roca
- Víctor Martínez
* `Jarsa <https://www.jarsa.com>`_:
- `Jarsa <https://www.jarsa.com>`__:
* Alan Ramos <alan.ramos@jarsa.com>
- Alan Ramos <alan.ramos@jarsa.com>
* `Bloopark systems <https://www.bloopark.de/>`_:
- `Bloopark systems <https://www.bloopark.de/>`__:
* Achraf Mhadhbi <machraf@bloopark.de>
- Achraf Mhadhbi <machraf@bloopark.de>
Maintainers
~~~~~~~~~~~
-----------
This module is maintained by the OCA.
@@ -182,6 +199,6 @@ OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.
This module is part of the `OCA/reporting-engine <https://github.com/OCA/reporting-engine/tree/16.0/base_comment_template>`_ project on GitHub.
This module is part of the `OCA/reporting-engine <https://github.com/OCA/reporting-engine/tree/17.0/base_comment_template>`_ project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

3
base_comment_template/pyproject.toml Normal file
View File

@@ -0,0 +1,3 @@
[build-system]
requires = ["whool"]
build-backend = "whool.buildapi"

9
base_comment_template/readme/CONFIGURE.md Normal file
View File

@@ -0,0 +1,9 @@
Go to *Settings \> Technical \> Reporting \> Comment Templates* and
start designing you comment templates.
This module is the base module for following modules:
- sale_comment_template
- purchase_comment_template
- invoice_comment_template
- stock_picking_comment_template

8
base_comment_template/readme/CONFIGURE.rst
View File

@@ -1,8 +0,0 @@
Go to *Settings > Technical > Reporting > Comment Templates* and start designing you comment templates.
This module is the base module for following modules:
* sale_comment_template
* purchase_comment_template
* invoice_comment_template
* stock_picking_comment_template

19
base_comment_template/readme/CONTRIBUTORS.md Normal file
View File

@@ -0,0 +1,19 @@
- Xavier Jimenez \<<xavier.jimenez@qubiq.es>\>
- Nicolas Bessi \<<nicolas.bessi@camptocamp.com>\>
- Yannick Vaucher \<<yannick.vaucher@camptocamp.com>\>
- Guewen Baconnier \<<guewen.baconnier@camptocamp.com>\>
- Simone Rubino \<<simone.rubino@agilebg.com>\>
- [DynApps](https://www.dynapps.be):
- Raf Ven \<<raf.ven@dynapps.be>\>
- [Druidoo](https://www.druidoo.io):
- Iván Todorovich \<<ivan.todorovich@druidoo.io>\>
- Pierre Verkest \<<pierreverkest84@gmail.com>\>
- [NextERP Romania](https://www.nexterp.ro):
- Fekete Mihai \<<feketemihai@nexterp.ro>\>
- [Tecnativa](https://www.tecnativa.com):
- Carlos Roca
- Víctor Martínez
- [Jarsa](https://www.jarsa.com):
- Alan Ramos \<<alan.ramos@jarsa.com>\>
- [Bloopark systems](https://www.bloopark.de/):
- Achraf Mhadhbi \<<machraf@bloopark.de>\>

30
base_comment_template/readme/CONTRIBUTORS.rst
View File

@@ -1,30 +0,0 @@
* Xavier Jimenez <xavier.jimenez@qubiq.es>
* Nicolas Bessi <nicolas.bessi@camptocamp.com>
* Yannick Vaucher <yannick.vaucher@camptocamp.com>
* Guewen Baconnier <guewen.baconnier@camptocamp.com>
* Simone Rubino <simone.rubino@agilebg.com>
* `DynApps <https://www.dynapps.be>`_:
* Raf Ven <raf.ven@dynapps.be>
* `Druidoo <https://www.druidoo.io>`_:
* Iván Todorovich <ivan.todorovich@druidoo.io>
* Pierre Verkest <pierreverkest84@gmail.com>
* `NextERP Romania <https://www.nexterp.ro>`_:
* Fekete Mihai <feketemihai@nexterp.ro>
* `Tecnativa <https://www.tecnativa.com>`_:
* Carlos Roca
* Víctor Martínez
* `Jarsa <https://www.jarsa.com>`_:
* Alan Ramos <alan.ramos@jarsa.com>
* `Bloopark systems <https://www.bloopark.de/>`_:
* Achraf Mhadhbi <machraf@bloopark.de>

27
base_comment_template/readme/DESCRIPTION.md Normal file
View File

@@ -0,0 +1,27 @@
Add a new mixin class to define templates of comments to print on
documents. The comment templates can be defined like make templates, so
you can use variables from linked models.
Two positions are available for the comments:
- above document lines (before_lines)
- below document lines (after_lines)
The template are general, and can be attached to any Model and based on
some domain defined in the template. You can define one default template
per Model and domain, which can be overwritten for any company and
partners. It has a priority field (smaller number = higher priority)
In existing reports, if you add this line will get the comment template
if you created one like
- \<span
t-out="o.get_comment_template('position',company_id=o.company_id,
partner_id=o.parnter_id )"/\> ( or without any parameter)
This module is the base module for following modules:
- sale_comment_template
- purchase_comment_template
- account_comment_template
- stock_picking_comment_template

23
base_comment_template/readme/DESCRIPTION.rst
View File

@@ -1,23 +0,0 @@
Add a new mixin class to define templates of comments to print on documents.
The comment templates can be defined like make templates, so you can use variables from linked models.
Two positions are available for the comments:
* above document lines (before_lines)
* below document lines (after_lines)
The template are general, and can be attached to any Model and based on some domain defined in the template.
You can define one default template per Model and domain, which can be overwritten for any company and partners.
It has a priority field (smaller number = higher priority)
In existing reports, if you add this line will get the comment template if you created one like
* <span t-out="o.get_comment_template('position',company_id=o.company_id, partner_id=o.parnter_id )"/> ( or without any parameter)
This module is the base module for following modules:
* sale_comment_template
* purchase_comment_template
* account_comment_template
* stock_picking_comment_template

52
base_comment_template/readme/USAGE.md Normal file
View File

@@ -0,0 +1,52 @@
1. Go to *Settings* and activate the developer mode.
2. Go to *Settings \> Technical \> Reporting \> Comment Templates*.
3. Create a new record.
4. Define the Company the template is linked or leave default for all
companies.
5. Define the Partner the template is linked or leave default for all
partners.
6. Define the Model, Domain the template is linked.
7. Define the Position where the template will be printed:
- above document lines
- below document lines
You should have at least one template with Default field set, if you
choose a Partner the template is deselected as a Default one. If you
create a new template with the same configuration (Model, Domain,
Position) and set it as Default, the previous one will be deselected as
a default one.
The template is a html field which will be rendered just like a mail
template, so you can use variables like {{object}}, {{user}}, {{ctx}} to
add dynamic content.
Change the report related to the model from configuration and add a
statement like:
\<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top"\>
\<div t-out="o.render_comment(comment_template_top)" /\>
\</t\>
\<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'after_lines')" t-as="comment_template_bottom"\>
\<div t-out="o.render_comment(comment_template_bottom)" /\>
\</t\>
You should always use t-if since the method returns False if no template
is found.
If you want to use Qweb templates, or different context, you can specify
it just like in mail.render.mixin with parameters:
- engine: "inline_template", "qweb" or "qweb_view",
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result
so you could use it :
\<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top"\>
\<div t-out="o.render_comment(comment_template_top, engine='qweb',
add_context={my dict}, postprocess=True)" /\>
\</t\>

44
base_comment_template/readme/USAGE.rst
View File

@@ -1,44 +0,0 @@
#. Go to *Settings* and activate the developer mode.
#. Go to *Settings > Technical > Reporting > Comment Templates*.
#. Create a new record.
#. Define the Company the template is linked or leave default for all companies.
#. Define the Partner the template is linked or leave default for all partners.
#. Define the Model, Domain the template is linked.
#. Define the Position where the template will be printed:
* above document lines
* below document lines
You should have at least one template with Default field set, if you choose a Partner the template is deselected as a Default one.
If you create a new template with the same configuration (Model, Domain, Position) and set it as Default, the previous one will be deselected as a default one.
The template is a html field which will be rendered just like a mail template, so you can use variables like {{object}}, {{user}}, {{ctx}} to add dynamic content.
Change the report related to the model from configuration and add a statement like:
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top">
<div t-out="o.render_comment(comment_template_top)" />
</t>
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'after_lines')" t-as="comment_template_bottom">
<div t-out="o.render_comment(comment_template_bottom)" />
</t>
You should always use t-if since the method returns False if no template is found.
If you want to use Qweb templates, or different context, you can specify it just like in
mail.render.mixin with parameters:
- engine: "inline_template", "qweb" or "qweb_view",
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result
so you could use it :
<t t-foreach="o.comment_template_ids.filtered(lambda x: x.position == 'before_lines')" t-as="comment_template_top">
<div t-out="o.render_comment(comment_template_top, engine='qweb', add_context={my dict}, postprocess=True)" />
</t>

94
base_comment_template/static/description/index.html
View File

@@ -8,10 +8,11 @@
/*
:Author: David Goodger (goodger@python.org)
:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $
:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
Despite the name, some widely supported CSS2 features are used.
See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to
customize this style sheet.
@@ -274,7 +275,7 @@ pre.literal-block, pre.doctest-block, pre.math, pre.code {
margin-left: 2em ;
margin-right: 2em }
pre.code .ln { color: grey; } /* line numbers */
pre.code .ln { color: gray; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
@@ -300,7 +301,7 @@ span.option {
span.pre {
white-space: pre }
span.problematic {
span.problematic, pre.problematic {
color: red }
span.section-subtitle {
@@ -368,20 +369,25 @@ ul.auto-toc {
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:72251979ce578742037aa71ca933ba9c4ed9951b7e3f68951ca232766f72d000
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/reporting-engine/tree/16.0/base_comment_template"><img alt="OCA/reporting-engine" src="https://img.shields.io/badge/github-OCA%2Freporting--engine-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/reporting-engine-16-0/reporting-engine-16-0-base_comment_template"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/reporting-engine&amp;target_branch=16.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
<p>Add a new mixin class to define templates of comments to print on documents.
The comment templates can be defined like make templates, so you can use variables from linked models.</p>
<p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/reporting-engine/tree/17.0/base_comment_template"><img alt="OCA/reporting-engine" src="https://img.shields.io/badge/github-OCA%2Freporting--engine-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/reporting-engine-17-0/reporting-engine-17-0-base_comment_template"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/reporting-engine&amp;target_branch=17.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
<p>Add a new mixin class to define templates of comments to print on
documents. The comment templates can be defined like make templates, so
you can use variables from linked models.</p>
<p>Two positions are available for the comments:</p>
<ul class="simple">
<li>above document lines (before_lines)</li>
<li>below document lines (after_lines)</li>
</ul>
<p>The template are general, and can be attached to any Model and based on some domain defined in the template.
You can define one default template per Model and domain, which can be overwritten for any company and partners.
It has a priority field (smaller number = higher priority)</p>
<p>In existing reports, if you add this line will get the comment template if you created one like</p>
<p>The template are general, and can be attached to any Model and based on
some domain defined in the template. You can define one default template
per Model and domain, which can be overwritten for any company and
partners. It has a priority field (smaller number = higher priority)</p>
<p>In existing reports, if you add this line will get the comment template
if you created one like</p>
<ul class="simple">
<li>&lt;span t-out=”o.get_comment_template(‘position’,company_id=o.company_id, partner_id=o.parnter_id )”/&gt; ( or without any parameter)</li>
<li>&lt;span
t-out=”o.get_comment_template(‘position’,company_id=o.company_id,
partner_id=o.parnter_id )”/&gt; ( or without any parameter)</li>
</ul>
<p>This module is the base module for following modules:</p>
<ul class="simple">
@@ -406,7 +412,8 @@ It has a priority field (smaller number = higher priority)</p>
</div>
<div class="section" id="configuration">
<h1><a class="toc-backref" href="#toc-entry-1">Configuration</a></h1>
<p>Go to <em>Settings &gt; Technical &gt; Reporting &gt; Comment Templates</em> and start designing you comment templates.</p>
<p>Go to <em>Settings &gt; Technical &gt; Reporting &gt; Comment Templates</em> and start
designing you comment templates.</p>
<p>This module is the base module for following modules:</p>
<ul class="simple">
<li>sale_comment_template</li>
@@ -421,8 +428,10 @@ It has a priority field (smaller number = higher priority)</p>
<li>Go to <em>Settings</em> and activate the developer mode.</li>
<li>Go to <em>Settings &gt; Technical &gt; Reporting &gt; Comment Templates</em>.</li>
<li>Create a new record.</li>
<li>Define the Company the template is linked or leave default for all companies.</li>
<li>Define the Partner the template is linked or leave default for all partners.</li>
<li>Define the Company the template is linked or leave default for all
companies.</li>
<li>Define the Partner the template is linked or leave default for all
partners.</li>
<li>Define the Model, Domain the template is linked.</li>
<li>Define the Position where the template will be printed:<ul>
<li>above document lines</li>
@@ -430,33 +439,44 @@ It has a priority field (smaller number = higher priority)</p>
</ul>
</li>
</ol>
<p>You should have at least one template with Default field set, if you choose a Partner the template is deselected as a Default one.
If you create a new template with the same configuration (Model, Domain, Position) and set it as Default, the previous one will be deselected as a default one.</p>
<p>The template is a html field which will be rendered just like a mail template, so you can use variables like {{object}}, {{user}}, {{ctx}} to add dynamic content.</p>
<p>Change the report related to the model from configuration and add a statement like:</p>
<dl class="docutils">
<dt>&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”&gt;</dt>
<dd>&lt;div t-out=”o.render_comment(comment_template_top)” /&gt;</dd>
</dl>
<p>You should have at least one template with Default field set, if you
choose a Partner the template is deselected as a Default one. If you
create a new template with the same configuration (Model, Domain,
Position) and set it as Default, the previous one will be deselected as
a default one.</p>
<p>The template is a html field which will be rendered just like a mail
template, so you can use variables like {{object}}, {{user}}, {{ctx}} to
add dynamic content.</p>
<p>Change the report related to the model from configuration and add a
statement like:</p>
<div class="line-block">
<div class="line">&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
‘before_lines’)” t-as=”comment_template_top”&gt;</div>
<div class="line">&lt;div t-out=”o.render_comment(comment_template_top)” /&gt;</div>
</div>
<p>&lt;/t&gt;</p>
<dl class="docutils">
<dt>&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘after_lines’)” t-as=”comment_template_bottom”&gt;</dt>
<dd>&lt;div t-out=”o.render_comment(comment_template_bottom)” /&gt;</dd>
</dl>
<div class="line-block">
<div class="line">&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
‘after_lines’)” t-as=”comment_template_bottom”&gt;</div>
<div class="line">&lt;div t-out=”o.render_comment(comment_template_bottom)” /&gt;</div>
</div>
<p>&lt;/t&gt;</p>
<p>You should always use t-if since the method returns False if no template is found.</p>
<p>If you want to use Qweb templates, or different context, you can specify it just like in
mail.render.mixin with parameters:</p>
<p>You should always use t-if since the method returns False if no template
is found.</p>
<p>If you want to use Qweb templates, or different context, you can specify
it just like in mail.render.mixin with parameters:</p>
<ul class="simple">
<li>engine: “inline_template”, “qweb” or “qweb_view”,</li>
<li>add_context: dict with your own context,</li>
<li>post_process: perform a post processing on rendered result</li>
</ul>
<p>so you could use it :</p>
<dl class="docutils">
<dt>&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”&gt;</dt>
<dd>&lt;div t-out=”o.render_comment(comment_template_top, engine=’qweb’, add_context={my dict}, postprocess=True)” /&gt;</dd>
</dl>
<div class="line-block">
<div class="line">&lt;t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
‘before_lines’)” t-as=”comment_template_top”&gt;</div>
<div class="line">&lt;div t-out=”o.render_comment(comment_template_top, engine=’qweb’,
add_context={my dict}, postprocess=True)” /&gt;</div>
</div>
<p>&lt;/t&gt;</p>
</div>
<div class="section" id="bug-tracker">
@@ -464,7 +484,7 @@ mail.render.mixin with parameters:</p>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/reporting-engine/issues">GitHub Issues</a>.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
<a class="reference external" href="https://github.com/OCA/reporting-engine/issues/new?body=module:%20base_comment_template%0Aversion:%2016.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
<a class="reference external" href="https://github.com/OCA/reporting-engine/issues/new?body=module:%20base_comment_template%0Aversion:%2017.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
<p>Do not contact contributors directly about support or help with technical issues.</p>
</div>
<div class="section" id="credits">
@@ -514,11 +534,13 @@ If you spotted it first, help us to smash it by providing a detailed and welcome
<div class="section" id="maintainers">
<h2><a class="toc-backref" href="#toc-entry-7">Maintainers</a></h2>
<p>This module is maintained by the OCA.</p>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<a class="reference external image-reference" href="https://odoo-community.org">
<img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" />
</a>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>
<p>This module is part of the <a class="reference external" href="https://github.com/OCA/reporting-engine/tree/16.0/base_comment_template">OCA/reporting-engine</a> project on GitHub.</p>
<p>This module is part of the <a class="reference external" href="https://github.com/OCA/reporting-engine/tree/17.0/base_comment_template">OCA/reporting-engine</a> project on GitHub.</p>
<p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>
</div>
</div>