We convert the custom plan implementation to use the generic one. As the generic one can define plans for multiple model. We use the check dedicated_to_res_model == 'hr.employee' to activate the specific feature for hr.employee. Indeed, that field contains the model name when the plan is applicable only for one model. We also remove the 'launch plan' button as we can now launch a plan directly from the activities button in the chatter. Technical notes: For the activity schedule wizard, we add the support for active_ids and active_model as default values for res_ids and res_model because it is used as link in the chatter to launch the wizard and we want to avoid a big migration by keeping the link identical (and there are probably no simple solution to keep the same behavior). HR CONTRACT Before the first contract date of the first selected element was chosen to determine the planned due date if all first contract date were different otherwise the minimum was chosen. So if the selection included 2 different date among 3, the minimum was chosen but the first if the 3 were different. With this change, the minimum is always used to determine the default planned due date. Task-3390865 Part-of: odoo/odoo#137969
24 lines
679 B
Python
24 lines
679 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from . import hr_contract_type
|
|
from . import hr_employee_base
|
|
from . import hr_employee
|
|
from . import hr_employee_category
|
|
from . import hr_employee_public
|
|
from . import hr_department
|
|
from . import hr_departure_reason
|
|
from . import hr_job
|
|
from . import hr_work_location
|
|
from . import mail_activity_plan
|
|
from . import mail_activity_plan_template
|
|
from . import mail_alias
|
|
from . import discuss_channel
|
|
from . import models
|
|
from . import res_config_settings
|
|
from . import res_users
|
|
from . import res_company
|
|
from . import res_partner
|
|
from . import resource
|
|
from . import ir_ui_menu
|