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
64 lines
2.7 KiB
XML
64 lines
2.7 KiB
XML
<?xml version="1.0"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
|
|
<record id="mail_alias_jobs" model="mail.alias">
|
|
<field name="alias_name">jobs</field>
|
|
<field name="alias_model_id" ref="model_hr_applicant"/>
|
|
<field name="alias_user_id" ref="base.user_admin"/>
|
|
<field name="alias_parent_model_id" ref="model_hr_job"/>
|
|
</record>
|
|
|
|
<!-- Applicant-related subtypes for messaging / Chatter -->
|
|
<record id="mt_applicant_new" model="mail.message.subtype">
|
|
<field name="name">New Applicant</field>
|
|
<field name="res_model">hr.applicant</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="hidden" eval="True"/>
|
|
</record>
|
|
<record id="mt_applicant_stage_changed" model="mail.message.subtype">
|
|
<field name="name">Stage Changed</field>
|
|
<field name="res_model">hr.applicant</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="description">Stage changed</field>
|
|
</record>
|
|
<record id="mt_applicant_hired" model="mail.message.subtype">
|
|
<field name="name">Applicant Hired</field>
|
|
<field name="res_model">hr.applicant</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="description">Applicant hired</field>
|
|
</record>
|
|
|
|
<!-- Job-related subtypes for messaging / Chatter -->
|
|
<record id="mt_job_new" model="mail.message.subtype">
|
|
<field name="name">Job Position created</field>
|
|
<field name="res_model">hr.job</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="hidden" eval="True"/>
|
|
</record>
|
|
<record id="mt_job_applicant_stage_changed" model="mail.message.subtype">
|
|
<field name="name">Applicant Stage Changed</field>
|
|
<field name="res_model">hr.job</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="parent_id" ref="mt_applicant_stage_changed"/>
|
|
<field name="relation_field">job_id</field>
|
|
</record>
|
|
<record id="mt_job_applicant_hired" model="mail.message.subtype">
|
|
<field name="name">Applicant Hired</field>
|
|
<field name="res_model">hr.job</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="parent_id" ref="mt_applicant_hired"/>
|
|
<field name="relation_field">job_id</field>
|
|
</record>
|
|
|
|
<!-- Department-related (parent) subtypes for messaging / Chatter -->
|
|
<record id="mt_department_new" model="mail.message.subtype">
|
|
<field name="name">Job Position Created</field>
|
|
<field name="res_model">hr.department</field>
|
|
<field name="sequence" eval="1"/>
|
|
<field name="parent_id" ref="mt_job_new"/>
|
|
<field name="relation_field">department_id</field>
|
|
</record>
|
|
|
|
</data></odoo>
|