summaryrefslogtreecommitdiff
path: root/addons/maintenance/data/mail_data.xml
diff options
context:
space:
mode:
authorThibault Delavallée <tde@odoo.com>2017-12-01 12:48:41 +0100
committerThibault Delavallée <tde@odoo.com>2018-02-21 16:52:28 +0100
commit1aa0f9a4dbb0721c76c0dbe6a009e937418bffc5 (patch)
tree8d24a847898b9ed6acd268a3681b537ce2ccf4c0 /addons/maintenance/data/mail_data.xml
parent12ef8b63120f09bbd24cae57ccaaf1292fc4a9dd (diff)
[MOV] maintenance: split data to separate mail data from other data
It is simpler to have data split by main model or application like we already do for models and views. It allows to easily have an overview of data a module holds. As we will work on mail related data like adding activities or tweaking subtypes and templates, having them all in a single file and not lost between other data helps finding and working with it. This commit only moves code. No functional change should occur.
Diffstat (limited to 'addons/maintenance/data/mail_data.xml')
-rw-r--r--addons/maintenance/data/mail_data.xml51
1 files changed, 51 insertions, 0 deletions
diff --git a/addons/maintenance/data/mail_data.xml b/addons/maintenance/data/mail_data.xml
new file mode 100644
index 00000000000..74a3a6abe9d
--- /dev/null
+++ b/addons/maintenance/data/mail_data.xml
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="utf-8"?>
+<odoo>
+<data>
+ <!-- email alias for maintenance requests -->
+ <record id="mail_alias_equipment" model="mail.alias">
+ <field name="alias_name">helpdesk</field>
+ <field name="alias_model_id" ref="model_maintenance_request"/>
+ <field name="alias_user_id" ref="base.user_root"/>
+ </record>
+
+ <!-- Maintenance Request-related subtypes for messaging / Chatter -->
+ <record id="mt_req_created" model="mail.message.subtype">
+ <field name="name">Request Created</field>
+ <field name="res_model">maintenance.request</field>
+ <field name="hidden" eval="True"/>
+ <field name="description">Maintenance Request created</field>
+ </record>
+ <record id="mt_req_status" model="mail.message.subtype">
+ <field name="name">Status Changed</field>
+ <field name="res_model">maintenance.request</field>
+ <field name="default" eval="True"/>
+ <field name="description">Status changed</field>
+ </record>
+
+ <!-- Equipment-related subtypes for messaging / Chatter -->
+ <record id="mt_mat_assign" model="mail.message.subtype">
+ <field name="name">Equipment Assigned</field>
+ <field name="res_model">maintenance.equipment</field>
+ <field name="description">Equipment Assigned</field>
+ </record>
+
+ <!-- Equipment Category-related subtypes for messaging / Chatter -->
+ <record id="mt_cat_req_created" model="mail.message.subtype">
+ <field name="name">Maintenance Request Created</field>
+ <field name="res_model">maintenance.equipment.category</field>
+ <field name="default" eval="True"/>
+ <field name="parent_id" eval="ref('mt_req_created')"/>
+ <field name="relation_field">category_id</field>
+ </record>
+ <record id="mt_cat_mat_assign" model="mail.message.subtype">
+ <field name="name">Equipment Assigned</field>
+ <field name="res_model">maintenance.equipment.category</field>
+ <field name="default" eval="True"/>
+ <field name="parent_id" eval="ref('mt_mat_assign')"/>
+ <field name="relation_field">category_id</field>
+ </record>
+ <record id="equipment_team_maintenance" model="maintenance.team">
+ <field name="name">Internal Maintenance</field>
+ </record>
+</data>
+</odoo> \ No newline at end of file