PURPOSE
Clean organization of templates in odoo apps: mail.template records in data,
qweb templates (views) used directly in code, notably using post with view.
Purpose is to ease future improvements in posting based on templates.
SPECIFICATIONS
* move those templates in their own file to ease their discovering and
maintenance;
* put them into data (as those are not views even if it contains qweb)
* guidelines are now :
-> Qweb templates should be in data/mail_templates.xml;
-> mail.template records should be in data/mail_template_data.xml;
* put their declaration in no update when not done if template has no
technical code or complex dependency on underlying code;
* move found mail data (mail.message.subtype or mail.activity.type) records
in a mail_data file that should contain only "core" records linked to mail;
LINKS
Task ID-2375767
COM PR odoo/odoo#61814
ENT PR odoo/enterprise#14775
UPG PR odoo/upgrade#1936
27 lines
1.1 KiB
XML
27 lines
1.1 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo><data noupdate="1">
|
|
<!-- Event-related subtypes for new track / Chatter -->
|
|
<record id="mt_event_track" model="mail.message.subtype">
|
|
<field name="name">New Track</field>
|
|
<field name="res_model">event.event</field>
|
|
<field name="description">New Track Created</field>
|
|
<field name="default" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Track subtypes -->
|
|
<record id="mt_track_blocked" model="mail.message.subtype">
|
|
<field name="name">Track Blocked</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track blocked</field>
|
|
</record>
|
|
<record id="mt_track_ready" model="mail.message.subtype">
|
|
<field name="name">Track Ready</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track Ready for Next Stage</field>
|
|
</record>
|
|
</data></odoo>
|