[MIG] base_comment_template: Migration to 15.0

TT35696
This commit is contained in:
Víctor Martínez
2022-09-13 16:43:26 +02:00
committed by Jesús Alan Ramos Rodríguez
parent 61973247ec
commit 1a9d3178f1
23 changed files with 106 additions and 330 deletions

View File

@@ -12,7 +12,7 @@
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:
@@ -32,7 +32,7 @@ You should always use t-if since the method returns False if no template is foun
If you want to use Qweb templates, or different context, you can specify it just like in
mail.render.mixin with parameters:
- engine: "jinja" or "qweb",
- engine: "inline_template", "qweb" or "qweb_view",
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result