When an employee submits an expense, no mail is sent to the manager. This should be the case, since it works this way on holidays. The trick, however, is that the expense is created as submitted, but the followers are only added afterwards. We need to make sure to add the followers at creation. opw-751085
77 lines
3.8 KiB
XML
77 lines
3.8 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<!-- notify all employees of module installation -->
|
|
<record id="module_install_notification" model="mail.message">
|
|
<field name="model">mail.channel</field>
|
|
<field name="res_id" ref="mail.channel_all_employees"/>
|
|
<field name="message_type">notification</field>
|
|
<field name="subtype_id" ref="mail.mt_comment"/>
|
|
<field name="subject">Expense Management application installed!</field>
|
|
<field name="body"><![CDATA[<p>Manage your employees' expenses, after due validation by their manager and the accountant, then generate and pay the corresponding invoices.</p>
|
|
<p>This feature is also linked to analytic accounting and compatible with timesheet invoices, so you will be able to automatically re-invoice project-related expenses to your customers.</p>]]></field>
|
|
</record>
|
|
|
|
<!--default alias for leads-->
|
|
<record id="mail_alias_expense" model="mail.alias">
|
|
<field name="alias_name">expense</field>
|
|
<field name="alias_model_id" ref="model_hr_expense"/>
|
|
<field name="alias_user_id" ref="base.user_root"/>
|
|
<field name="alias_contact">employees</field>
|
|
</record>
|
|
|
|
|
|
<!-- Resource: product.uom.categ -->
|
|
<record id="cat_expense" model="product.category">
|
|
<field name="parent_id" ref="product.product_category_all"/>
|
|
<field name="name">Expenses</field>
|
|
</record>
|
|
|
|
<record id="product_product_fixed_cost" model="product.product">
|
|
<field name="name">Expenses</field>
|
|
<field name="list_price">0.0</field>
|
|
<field name="standard_price">1.0</field>
|
|
<field name="type">service</field>
|
|
<field name="default_code">EXP</field>
|
|
<field name="categ_id" ref="hr_expense.cat_expense"/>
|
|
<field name="can_be_expensed" eval="True"/>
|
|
</record>
|
|
|
|
<!-- Expense-related subtypes for messaging / Chatter -->
|
|
<record id="mt_expense_approved" model="mail.message.subtype">
|
|
<field name="name">Approved</field>
|
|
<field name="res_model">hr.expense.sheet</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="description">Expense report approved</field>
|
|
</record>
|
|
<record id="mt_expense_refused" model="mail.message.subtype">
|
|
<field name="name">Refused</field>
|
|
<field name="res_model">hr.expense.sheet</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="description">Expense report refused</field>
|
|
</record>
|
|
<record id="mt_expense_confirmed" model="mail.message.subtype">
|
|
<field name="name">Submitted</field>
|
|
<field name="res_model">hr.expense.sheet</field>
|
|
<field name="description">Expense report submitted, waiting approval</field>
|
|
<field name="default" eval="True"/>
|
|
</record>
|
|
<record id="mt_expense_paid" model="mail.message.subtype">
|
|
<field name="name">Paid</field>
|
|
<field name="res_model">hr.expense.sheet</field>
|
|
<field name="description">Expense report paid</field>
|
|
<field name="default" eval="False"/>
|
|
</record>
|
|
<!-- Department (Parent) related subtypes for messaging / Chatter -->
|
|
<record id="mt_department_expense_confirmed" model="mail.message.subtype">
|
|
<field name="name">Expenses To Approve</field>
|
|
<field name="res_model">hr.department</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="parent_id" eval="ref('mt_expense_confirmed')"/>
|
|
<field name="relation_field">department_id</field>
|
|
<field name="sequence" eval="10"/>
|
|
</record>
|
|
|
|
</data>
|
|
</odoo>
|