[REM] hr_recruitment: removed some dead code and unnecessary
features : - [REM] removed unnecessary action about stages and installer and the file containing it. - [REM] hr_recruitment: removed useless doc directory, containing only crap and useless notes. - [REM] hr_recruitment: removed unused wizard creating a partner from an applicant. As we have all the necessary stuff in the form view this wizard does not seem necessary. As it is not used, let us drop it.
This commit is contained in:
@@ -3,5 +3,4 @@
|
||||
import hr_department
|
||||
import hr_recruitment
|
||||
import report
|
||||
import wizard
|
||||
import res_config
|
||||
|
||||
@@ -28,12 +28,10 @@ You can define the different phases of interviews and easily rate the applicant
|
||||
'utm',
|
||||
],
|
||||
'data': [
|
||||
'wizard/hr_recruitment_create_partner_job_view.xml',
|
||||
'hr_recruitment_view.xml',
|
||||
'security/hr_recruitment_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'report/hr_recruitment_report_view.xml',
|
||||
'hr_recruitment_installer_view.xml',
|
||||
'res_config_view.xml',
|
||||
'survey_data_recruitment.xml',
|
||||
'hr_recruitment_data.xml',
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
.. _changelog:
|
||||
|
||||
Changelog
|
||||
=========
|
||||
|
||||
`trunk (saas-3)`
|
||||
----------------
|
||||
|
||||
- ``hr.recruitment.stage``: added template_id field. If an email template is linked
|
||||
to the stage, it is used to render and post a message on the applicant. This
|
||||
allows for example to have template for accepted or refused applicants.
|
||||
|
||||
`trunk (saas-2)`
|
||||
----------------
|
||||
|
||||
- Stage/state update
|
||||
|
||||
- ``hr.applicant``: removed inheritance from ``base_stage`` class and removed
|
||||
``state`` field. Added ``date_last_stage_update`` field holding last stage_id
|
||||
modification. Removed ``date`` field not used anywhere. Updated reports.
|
||||
- ``hr.recruitment.stage``: removed ``state`` field.
|
||||
|
||||
- Removed ``hired.employee`` wizard.
|
||||
@@ -1,22 +0,0 @@
|
||||
=====================
|
||||
HR Recruitment DevDoc
|
||||
=====================
|
||||
|
||||
Hr Recruitment module documentation
|
||||
===================================
|
||||
|
||||
Documentation topics
|
||||
''''''''''''''''''''
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
stage_status.rst
|
||||
|
||||
Changelog
|
||||
'''''''''
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
changelog.rst
|
||||
@@ -1,54 +0,0 @@
|
||||
.. _stage_status:
|
||||
|
||||
Stage and Status
|
||||
================
|
||||
|
||||
.. versionchanged:: 8.0 saas-2 state/stage cleaning
|
||||
|
||||
Stage
|
||||
+++++
|
||||
|
||||
This revision removed the concept of state on hr.applicant objects. The ``state``
|
||||
field has been totally removed and replaced by stages, using ``stage_id``. The
|
||||
following models are impacted:
|
||||
|
||||
- ``hr.applicant`` now use only stages. However a convention still exists about
|
||||
'New' stage. An applicant is consdered as ``new`` when it has the following
|
||||
properties:
|
||||
|
||||
- ``stage_id and stage_id.sequence = 1``
|
||||
|
||||
- ``hr.recruitment.stage`` do not have any ``state`` field anymore.
|
||||
- ``hr.recruitment.report`` do not have any ``state`` field anymore.
|
||||
|
||||
By default a newly created applicant be in a new stage. It means that it will
|
||||
fetch the stage having ``sequence = 1``. Stage mangement is done using the
|
||||
kanban view or the clikable statusbar. It is not done using buttons anymore.
|
||||
Employee creation is still feasible directly from a link button in the form view.
|
||||
|
||||
Stage analysis
|
||||
++++++++++++++
|
||||
|
||||
Stage analysis can be performed using the newly introduced ``date_last_stage_update``
|
||||
datetime field. This field is updated everytime ``stage_id`` is updated.
|
||||
|
||||
``hr.recruitment.report`` model also uses the ``date_last_stage_update`` field.
|
||||
This allows to group and analyse the time spend in the various stages.
|
||||
|
||||
Open / Assignation date
|
||||
+++++++++++++++++++++++
|
||||
|
||||
The ``date_open`` field meaning has been updated. It is now set when the ``user_id``
|
||||
(responsible) is set. It is therefore the assignation date.
|
||||
|
||||
Subtypes
|
||||
++++++++
|
||||
|
||||
The following subtypes are triggered on ``hr.applicant``:
|
||||
|
||||
- ``mt_applicant_new``: new applicants. Condition: ``obj.stage_id and obj.stage_id.sequence == 1``
|
||||
- ``mt_applicant_stage_changed``: stage changed. Condition: ``obj.stage_id and obj.stage_id.sequence != 1``
|
||||
|
||||
The following subtype is trigerred on ``hr.job``:
|
||||
|
||||
- ``mt_job_new_applicant``: new applicant in the job.
|
||||
@@ -1,13 +0,0 @@
|
||||
<openerp>
|
||||
<data>
|
||||
<record model="ir.actions.act_window" id="hr_recruitment_stage_form_installer">
|
||||
<field name="name">Review Recruitment Stages</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="res_model">hr.recruitment.stage</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Check if the following stages are matching your recruitment process. Don't forget to specify the department if your recruitment process is different according to the job position.</field>
|
||||
<field name="view_id" ref="hr_recruitment.hr_recruitment_stage_tree"/>
|
||||
</record>
|
||||
</data>
|
||||
</openerp>
|
||||
@@ -1,4 +0,0 @@
|
||||
# -*- coding: utf-8 -*-
|
||||
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
||||
|
||||
import hr_recruitment_create_partner_job
|
||||
@@ -1,60 +0,0 @@
|
||||
# -*- coding: utf-8 -*-
|
||||
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
||||
from openerp.osv import fields, osv
|
||||
from openerp.tools.translate import _
|
||||
from openerp.exceptions import UserError
|
||||
|
||||
class hr_recruitment_partner_create(osv.osv_memory):
|
||||
_name = 'hr.recruitment.partner.create'
|
||||
_description = 'Create Partner from job application'
|
||||
_columns = {
|
||||
'close': fields.boolean('Close job request'),
|
||||
}
|
||||
|
||||
def view_init(self, cr, uid, fields_list, context=None):
|
||||
case_obj = self.pool.get('hr.applicant')
|
||||
if context is None:
|
||||
context = {}
|
||||
for case in case_obj.browse(cr, uid, context['active_ids'], context=context):
|
||||
if case.partner_id:
|
||||
raise UserError(_('A contact is already defined on this job request.'))
|
||||
pass
|
||||
|
||||
def make_order(self, cr, uid, ids, context=None):
|
||||
mod_obj = self.pool.get('ir.model.data')
|
||||
partner_obj = self.pool.get('res.partner')
|
||||
case_obj = self.pool.get('hr.applicant')
|
||||
|
||||
if context is None:
|
||||
context = {}
|
||||
data = self.read(cr, uid, ids, context=context)[0]
|
||||
result = mod_obj._get_id(cr, uid, 'base', 'view_res_partner_filter')
|
||||
res = mod_obj.read(cr, uid, result, ['res_id'], context=context)
|
||||
|
||||
for case in case_obj.browse(cr, uid, context['active_ids'], context=context):
|
||||
partner_id = partner_obj.search(cr, uid, [('name', '=', case.partner_name or case.name)], context=context)
|
||||
if partner_id:
|
||||
raise UserError(_('A contact is already existing with the same name.'))
|
||||
partner_id = partner_obj.create(cr, uid, {
|
||||
'name': case.partner_name or case.name,
|
||||
'user_id': case.user_id.id,
|
||||
'comment': case.description,
|
||||
'phone': case.partner_phone,
|
||||
'mobile': case.partner_mobile,
|
||||
'email': case.email_from
|
||||
}, context=context)
|
||||
|
||||
case_obj.write(cr, uid, [case.id], {
|
||||
'partner_id': partner_id,
|
||||
}, context=context)
|
||||
|
||||
return {
|
||||
'domain': "[]",
|
||||
'view_type': 'form',
|
||||
'view_mode': 'form,tree',
|
||||
'res_model': 'res.partner',
|
||||
'res_id': int(partner_id),
|
||||
'view_id': False,
|
||||
'type': 'ir.actions.act_window',
|
||||
'search_view_id': res['res_id']
|
||||
}
|
||||
@@ -1,30 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<openerp>
|
||||
<data>
|
||||
|
||||
<record id="view_hr_recruitment_partner_create" model="ir.ui.view">
|
||||
<field name="name">hr.recruitment.partner.create.form</field>
|
||||
<field name="model">hr.recruitment.partner.create</field>
|
||||
<field name="arch" type="xml">
|
||||
<form string="Convert To Partner">
|
||||
<label string="Are you sure you want to create a contact based on this job request ?"/>
|
||||
<footer>
|
||||
<button name="make_order" string="Create Contact" type="object" groups="base.group_partner_manager" class="oe_highlight"/>
|
||||
<label string="or" groups="base.group_partner_manager"/>
|
||||
<button string="Cancel" class="oe_link" special="cancel" />
|
||||
</footer>
|
||||
</form>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_hr_recruitment_partner_create" model="ir.actions.act_window">
|
||||
<field name="name">Create Contact</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="res_model">hr.recruitment.partner.create</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">form</field>
|
||||
<field name="target">new</field>
|
||||
</record>
|
||||
|
||||
</data>
|
||||
</openerp>
|
||||
Reference in New Issue
Block a user