I have a case where we have a set of pages where each of them belongs to a s
pecific department. If you belong to department A, when you log on to the po
rtal you should only see "Department A" in the top navigation of the portal.
 Quite easy to implement us
ing visibility rules I assume.

But the tricky part is, it should be possible on another page called "All de
partments" to open for instance "Department B" even if you belong to A. I'm 
having trouble figuring out how to do this, because with the visibility rule
 I have said "If A --> Show
A", so if you are B you will never see A...but I want to say "If A --> Show 
B only if not in top navigation"...

Have anyone done something like this. The only thing that comes to my mind i
s to make a portlet with all the links hard coded (uniquenames) or as config
 properties, but anyhow...not as dynamic as it could be :-)

R.

[ Post a follow-up to this message ]

You'll have to have 2 copies of the content item, one in each site area and 
then personalize them separately.

[ Post a follow-up to this message ]

I was guided to a working solution: Create each page, then for each page cre
ate a visibility rule (with profile) saying "hide the page unless the user i
s from dep. A OR request parameter is set to true". Then I create a portal u
rl, and add a parameter sho
w=true. Then users from dep. B will be able to see dep. A page, but still hi
de it from the level 1 navigation.

[ Post a follow-up to this message ]

Hi,

Can you please show us with some sample how you are using "request parameter
 is set to true" in the rules. I am trying to implement a visibilty rule whe
re the portlet will be shown or hidden depending on a request parameter or r
equest attribute.

Could you please share the code if you have for this?The problem is , i am s
ettig request param in the portlet on a click but the Rules are not recogniz
ing this portlet attribute.
How come the rules know that there is a request attribute which should be ac
cessed from the portlet code??

[ Post a follow-up to this message ]

When creating your rule in the Personalization Navigator, add a request prop
erty that matches the parameter the portlet puts in the request. This is don
e using the Manage Properties menu option.

Brian

[ Post a follow-up to this message ]

Brian,

I did the same thing using 'Manage properties' option but i do not know why 
the portlet is still showing up when the request attribute property in the j
sf is present.
I tried printing the Request attribute value and its not null but the portle
t which has to hide when the request attribute is not empty.., is still show
s up.

does your code working , if so, can u just send me the rule and the portlet.
.

[ Post a follow-up to this message ]

Hi

I started my holiday on the 11'th of July, so have not been checking this po
sting since then. If it is still an issue for you, I can try to look back on
 what I did and maybe provide you with some more info.

R.

[ Post a follow-up to this message ]