[IMP] hr_recruitment, project: better access rules for categories

[odoo/odoo.git] / addons / hr_recruitment / hr_recruitment_data.xml

diff --git a/addons/hr_recruitment/hr_recruitment_data.xml b/addons/hr_recruitment/hr_recruitment_data.xml
index aed3fe1..d90f5ab 100644 (file)
--- a/addons/hr_recruitment/hr_recruitment_data.xml
+++ b/addons/hr_recruitment/hr_recruitment_data.xml
@@ -1,15 +1,19 @@
 <?xml version="1.0"?>
 <openerp>
-<!--
 <data noupdate="1">
--->
-<data>
+        <!-- notify all employees of module installation -->
+        <function model="mail.group" name="message_append_note">
+            <!-- ids, subject, body, parent_id=False, type='notification', content_subtype='html' -->
+            <value eval="[ref('mail.group_all_employees')]"/>
+            <value>Module Recruitment Process has been installed</value>
+            <value>Manage job positions and the recruitment process in your company.  This module is integrated with the module Survey to help you to define interviews for different jobs.
 
-    <!-- Case category (for interview meetings) -->
-    <record model="crm.case.categ" id="categ_meet_interview">
+You can automatically create application records from an email gateway, that you can configure in the Human Resources Settings.</value>
+        </function>
+
+    <!-- Meeting Types (for interview meetings) -->
+    <record model="crm.meeting.type" id="categ_meet_interview">
         <field name="name">Interview</field>
-        <field name="section_id" ref="crm.section_sales_department"/>
-        <field name="object_id" search="[('model','=','crm.meeting')]" model="ir.model"/>
     </record>
 
         <!--    HR Recruitment Source        -->
@@ -451,10 +455,9 @@
     </record>
    
     <record id="mail_alias_jobs" model="mail.alias">
-        <field name="alias_name">Jobs</field>
+        <field name="alias_name">jobs</field>
         <field name="alias_model_id" ref="model_hr_applicant"/>
         <field name="alias_user_id" ref="base.user_root"/>
-        <field name="alias_defaults">{}</field>
     </record>
     
 </data>