odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[DOC] hr_recruitment: added some documentation 

bzr revid: tde@openerp.com-20130709113439-twm0zw2d5dwa14jx
This commit is contained in:
Thibault Delavallée 2013-07-09 13:34:39 +02:00
parent 66e4f06035
commit 1d6ba9a813
3 changed files with 49 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
addons/hr_recruitment/doc/changelog.rst
View File

@ -6,5 +6,9 @@ Changelog
`trunk (saas-2)`
----------------
- ``hr_recruitment``: removed inheritance from ``base_stage`` class and removed
``state`` field.
- 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. Updated reports.
- ``hr.recruitment.stage``: removed ``state`` field.

4
addons/hr_recruitment/doc/index.rst
View File

@ -5,8 +5,8 @@ HR Recruitment DevDoc
Hr Recruitment module documentation
===================================
Hr Recruitment documentation topics
'''''''''''''''''''''''''''''''''''
Documentation topics
''''''''''''''''''''
.. toctree::
:maxdepth: 1

48
addons/hr_recruitment/doc/stage_status.rst
View File

@ -3,18 +3,52 @@
Stage and Status
================
.. versionchanged:: 8.0 saas-2 state/stage cleaning
Stage
+++++
.. versionchanged:: 8.0 saas-2 state/stage cleaning
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``.
field has been totally removed and replaced by stages, using ``stage_id``. The
following models are impacted:
Convention
++++++++++
- ``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:
A ``hr.recruitment.stage`` is ``new`` when it has the following properties:
- ``stage_id and stage_id.sequence = 1``
- ``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.