composer_mixin: Odoo itgen_odoo_composer_mixin
read only per partition
- Catalog:
Odoo - Schema:
mail - Label: itgen_odoo_composer_mixin
Mail Composer Mixin
Can only retrieve data.
Summary
Mixin used to edit and render some fields used when sending emails or notifications based on a mail template.
Main current purpose is to hide details related to subject and body computation
and rendering based on a mail.template. It also give the base tools to control
who is allowed to edit body, notably when dealing with templating language
like inline_template or qweb.
It is meant to evolve in a near future with upcoming support of qweb and fine
grain control of rendering access.
Table Columns
The columns of the table composer_mixin are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.
| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|---|---|---|
body |
varchar2 |
Contents | |||
can_ |
boolean |
Can Edit Body | |||
is_ |
boolean |
Is Editor | |||
lang |
varchar2 |
Language | Optional translation language (ISO code) to select when sending out an email. If not set, the english version will be used. This should usually be a placeholder expression that provides the appropriate language, e.g. {{ object.partner_id.lang }}. | ||
render_ |
varchar2 |
Rendering Model | |||
subject |
varchar2 |
Subject | |||
template_ |
varchar2 |
||||
template_ |
varchar2 |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver: