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
Improve usability of employee form. It is confusing for end users
to create another record to encode the employee address.
Move all the private information on the hr.employee record itself.
Remove the M2O address_home_id.
TaskID: 3101400
PURPOSE:
Companies want to have a better integration, we need to focus on the On/Offboarding process,
to find automation and something to show to our customers.
In this commit, we add the "Fleet Manager" in the responsible list of the activities
generated from a plan.
Case 1:
If employee is not linked with fleet, `Employee XXX is not linked to a vehicle`
this warning will be appeared.
Case 2:
If employee linked with fleet but doesn't fleet manager set on fleet,
`Employee's vehicle XXX is not linked to a fleet manager.` this warning will be appeared.
task-3081261
closesodoo/odoo#108892
Signed-off-by: Kevin Baptiste <kba@odoo.com>
The demo data were assigning random res.partner as home_address_id for
some employees, this is no longer required since #98027.
closesodoo/odoo#107767
Signed-off-by: Kevin Baptiste <kba@odoo.com>
In the demo data from hr_fleet, we add address_home_id's to some employees in
order to create the correct vehicle assignation logs. However, as the driver_id
is already set at that moment, the _compute_driver_employee_id is not called
again as no dependency was changed, resulting in an empty driver_employee_id
for some logs. This commit fixes this by calling the compute method on the demo
data with the assignation logs that have no driver_employee_id set and have a
driver_id.
task-2742923
Part-of: odoo/odoo#83755
Pierre-Yves Dufays