diff options
| author | Rohan Patel <rop@odoo.com> | 2018-02-09 17:40:53 +0530 |
|---|---|---|
| committer | Thibault Delavallée <tde@odoo.com> | 2018-03-21 10:44:20 +0100 |
| commit | 57e457c524b9d624e2a34a1c1cb36472f2e68b00 (patch) | |
| tree | bf1d276547a776dd29dbd92b374503138176935c /addons/web/static/src/js/views/basic/basic_view.js | |
| parent | 60793a8a48bddb59eb50b562fbff8646e82f0d3a (diff) | |
[IMP] hr: check employees only alias restriction independently of record existence
Commit 78ac6de52d690d278fd0cde5476bbeaec86cb124 refactored methods checking alias security on the
routing found for a given destination address. Indeed if a routing is found
linked to an alias a security check is performed according to the restriction
defined on the alias itself.
HR module adds the 'employees only' restriction. A bug has been introduced
in the mentioned commit concerning employees-based aliases. Indeed a condition
on having a recordset has been added (self.ids, changed to record.ids at
20d8025036eed9dc30365e3b5ccc5cd1b4b01c77). This condition is actually not necessary as checking the
email author is linked to an existing employee has nothing to do with the
alias being linked to a record or creating new record.
This may causes issues notably using employees-restricted aliases in
expense application. Indeed you could use aliases to create new expenses
for employees and you could have issues with this condition.
This commit is linked to task ID 1829860 and ID 35093. Closes #22960 .
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_view.js')
0 files changed, 0 insertions, 0 deletions
