Menu Security

[jde1]

Hi List,

Could you please let me know how to secure menus from the users.
For ex there is a group called TP which has many users within it.
The group TP can access a customised menu TP1 which has many sub
menus. I want only 3 users to view one sub menu called RP1 & want
to block it from all other users.

Your help would be appreciated.

Bye
Sneh

 

[KSmithCPA]

I beleive you will need to set-up two groups (And two menus). One group with access to the TP1 menu, and the other group without access.

 

[fat_elvis]

You could work around this by using "Exclusive Application" Security at the individual user profile level but I'd say away from that if possible.

I'd reccommend creating another group for the 3 users and grant them security to the application(s) in the RP1 menu and remove it for everyone else. This would allow both groups use the same menus but they'll only see the applications they've been granted access to.

 

[peterfourie]

There are a lot of ways for doing this but World menu security was replaced
with Oneworld Row security. I remember reading a document on the KG
detailing how to apply menu security using the row security function.

Peter Fourie

----- Original Message -----
From: "fat_elvis" <[email protected]>
To: <[email protected]>
Sent: Friday, April 19, 2002 11:17 AM
Subject: Re: Menu Security


the individual user profile level but I'd say away from that if possible.I'd
reccommend creating another group for the 3 users and grant them security to
the application(s) in the RP1 menu and remove it for everyone else. This
would allow both groups use the same menus but they'll only see the
applications they've been granted access to.

 

[pjones75]

OneWorld does not easliy have menu security. As suggested you may be able to setup through Row Security, I know you get around Version Security this way.

The New JDE solution is to use Solutions Explorer. This has the facility for Views and Tasks and you can secure users by Roles. In this they do not see menus that they are not meant to. You then only need one View with the tasks secured according to user role.

Paul J