Hi Deepak,
Without extension, you may easily cut at different levels using widgets (more for backend side but can be used also on eCommerce UI
types)
* Applications
* Menus
* screens
* parts of screens
* forms
* possibly parts of forms (never tried that could be by using skip-start and skip-end and maybe hide-header , but become more
complicated and I just realise that those attributes are missing xsd doc :/)
Of course you can also filter in events or services (related to request-map)
Markus case is very specific and he wants to avoid mucking in templates.
I'm not quite sure how to do that without really thinking/trying, and I'm not
inclined to do so today :o)
Maybe Markus can pick your ideas...
Jacques
From: "Deepak Agarwal" <[email protected]>
Hello Jacques,
Just my opinion regarding role based restriction over ui parts, I see 2
possibilities to do it OOTB:
1) Each request-map is unique, so we can have an interface to link requests
with a particular role
2) We can also have role based selection of screens.
An example interface would be:
Select Screen (drop down) Restrict for Roles (drop down)
so hasPermission can be extended as isRestricted(screen, role) .
On Sat, Jul 14, 2012 at 5:49 PM, Jacques Le Roux <
[email protected]> wrote:
Roles are a part of it, see this page for rights organisation
https://demo-trunk.ofbiz.**apache.org/partymgr/control/**
ProfileEditUserLoginSecurityGr**oups?partyId=admin&**userLoginId=admin<https://demo-trunk.ofbiz.apache.org/partymgr/control/ProfileEditUserLoginSecurityGroups?partyId=admin&userLoginId=admin>
You get there from the user profil, look for Security Groups. From them
follow the code and data. Looking into OOTB related demo data is very good
way to understand stuff, often quicker than tracing code
Jacques
From: "MMA" <[email protected]>
Hi Jacques,
thanks for your fast response.
Im not sure if this is exactly what i was searching for...
My intention is to restrict the access to certain catalogues on the front
end (in the ecommerce shop).
For instance, i want a un-registered user to see just our empty front
page,
without any catalogues/products.
Signed-in users should see different catalogues based on new defined roles
e.g.
user 1
"role 1"
catalogue 1
catalogue 3
user 2
"role 2"
catalogue 1
catalogue 2
i hope that there is a possibility to do this in the backend, because i
want
to generate rules as dynamic as
possible, it would be much more effort to edit all template (or similar)
files.
Is there any hint you could give me, where to start to achieve this? i
already found the possibility to bind
certain parties with a defined role to a catalogue, but i don't see where
to define concrete rights for these
roles...
nevertheless, thank you and best regards,
Markus
--
View this message in context: http://ofbiz.135035.n4.nabble.**
com/Catalog-category-**privilegs-per-user-**tp4634786p4634815.html<http://ofbiz.135035.n4.nabble.com/Catalog-category-privilegs-per-user-tp4634786p4634815.html>
Sent from the OFBiz - User mailing list archive at Nabble.com.
--
Thanks,
Deepak Agarwal,
Paxcel Technologies Pvt Ltd.
Hartron Complex, Sector 18, Gurgaon, India.
E-Mail: [email protected]
Mobile: +91 9910322604
