Martin Trigaux 6286dc4809 [FIX] hr: force a name to employee creation ...

The name field is a stored related on the resource.resource record.
The name on the resource is required.

If no name (and no resource_id), the creation fails as trying to create a
resource without name (non-null constrain)

Force in the view to indicate to the user that a name is required but without
adding the constrain at the database level.
required=True on the fields adds a non-null constrain on the SQL column but the
related values are populated *after* the INSERT so it would fail depending on
the given values (e.g. a resource_id value but no name)

Fixes #20126
Closes #20128

2017-10-13 14:21:32 +02:00

..

hr_templates.xml

[MIGR] hr : migrate to new api

2016-04-13 12:28:34 +02:00

hr_views.xml

[FIX] hr: force a name to employee creation

2017-10-13 14:21:32 +02:00

res_config_settings_views.xml

[FIX] account, base_setup, crm, event, google_calendar, hr, hr_attendance, hr_expense, hr_payroll, hr_recruitment, l10n_be_hr_payroll_fleet, mass_mailing, mrp, project, purchase, sale, stock, website: rename the actions leading to settings to "settings", for breadcrumbs

2017-10-02 15:15:14 +02:00