Human Resources (Interview Evaluation)
hr_interview · OCA/hr
-
Security25/25No findings
-
Activity0/25Last human commit 140 months ago
-
Required by5/250 modules depend on it
-
Maturity5/25In 1 Odoo series since 6.1
Heuristic over the facts below, not an audit · How it's computed
Migration considerations
- Migrating to 11.0: the workflow engine (`trg_validate`) was removed: rewrite as state-field transitions. migration-workflow-call · source
- Migrating to 19.0: only `__manifest__.py` is recognized: a module with `__openerp__.py` is not detected at all. migration-openerp-manifest · source
candidate_category— Class 'candidate_category' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. (6 occurrences in this file) migration-old-api-base · sourcecandidate_category— Class 'candidate_category' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. (7 occurrences in this file) migration-old-style-fields · sourcecandidate_category_tree— Migrating to 18.0: the `tree` view type was renamed to `list` (`<list>` roots, `view_mode`). (6 occurrences in this file) migration-view-tree-tag · sourcehr_interview_form— Migrating to 17.0: `attrs=`/`states=` are rejected in views: convert them to Python expressions in `invisible`/`readonly`/`required`, keeping the original AND/OR logic. migration-view-attrs-states · sourcewiz_schedule— Class 'wiz_schedule' still inherits from the old-style `osv.osv_memory` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
This module stores all the educational as well as professional details of candidates who appears for interview. While taking an interview, the interviewers can evaluate the candidate's performance on the basis of categories. The Candidate is evaluated bases on different evaluations, which are related to categories.
Example: Candidate X to be evaluated for Y Category (Category reflects to the recruitment criteria). Category Y has several question types: DBMS questions, OOP questions, Communication skills, etc.
Dependencies
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 12
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
candidate_category_search |
cand.categ.search | candidate.category | form | New |
candidate_category_tree |
cand.categ.tree | candidate.category | tree | New |
candidate_experience_form |
candidate.experience.form | candidate.experience | form | New |
candidate_experience_tree |
candidate.experience.tree | candidate.experience | tree | New |
category_question_form |
category.question.form | category.question | form | New |
category_question_tree |
category.question.tree | category.question | tree | New |
hr_interview_form |
hr.interview.form | hr.interview | form | New |
hr_interview_log_form |
hr.interview.log.form | hr.interview.log | form | New |
hr_interview_log_tree |
hr.interview.log.tree | hr.interview.log | tree | New |
hr_interview_tree |
hr.interview.tree | hr.interview | tree | New |
technical_skill_form |
technical.skill.form | technical.skill | form | New |
technical_skill_tree |
technical.skill.tree | technical.skill | tree | New |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 0
No models found for this module.