Community mailing list archives
Re: Product maintenance independent of other modulesby
2015-03-18 14:17 GMT-06:00 Jordi Ballester Alomar <email@example.com>:
Well, rather than defining a manager for a product I was referring more generally to making it possible for a group (perhaps to be called 'Product maintainer') to be able to maintain all company products.
Agreed, but using the field "Product Manager" in the product iself will allow you do 2 kind of elements.
Type 1: (Segmented product editors)
1.- I can edit "only" product which I am responsible for, for example, products for expenses are generally managed by Accountant users.
2.- Products that require deeper nanalysis are not managed by accountants they are a mix between correct default values (in categoories) and ACL on product istelf (Produc Manager comes up again).
Type 2: (Super Product Administrators)
3.- Super Product Editors (these are the ones you are mentioning).
With your approach you will have a "All in all out" which in not wrong but is incomplete, at least we solved manually in that way.
Be care about 2 things.
1.- With website enabled, portal user will nee write access to write messages, test that also.
2.- You can "disable" some ACL to base groups which you mentioned, then you module with demo data should add "admin" as user to not brake some tests.
I hope it clearfy my points a little better.