Daily updates from Odoo
Thursday, April 26, 2018
2 changes · master
Code cleanup and technical improvements
User access rights are now managed through clearer, fixed fields instead of a dynamically generated technical view. This makes user permissions easier to organize, especially by separating public, portal, and internal users into exclusive user types.
Original PR description
This is a POC for how to replace the reified view with hardcoded fields. The idea is to add the corresponding fields in res_users when adding groups. These fields should have the special methods _compute_groups and _compute_groups_inverse respectively for parameters compute and inverse. It is also necessary to inherit the res_users view to add the fields. A category "user_type" has been created to replace the extra and human_resources categories, which has child groups portal, public and employee. Task id: 32258 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change updates how user access groups are managed by defining them directly on user records instead of relying on an older generated view approach. It should make permissions configuration easier to maintain across several business apps, with limited immediate impact for end users.
Original PR description
This is a POC for how to replace the reified view with hardcoded fields. The idea is to add the corresponding fields in res_users when adding groups. These fields should have the special methods _compute_groups and _compute_groups_inverse respectively for parameters compute and inverse. It is also necessary to inherit the res_users view to add the fields. A category "user_type" has been created to replace the extra and human_resources categories, which has child groups portal, public and employee. Task id: 32258