SharePoint / ASP.Net Development
Experiences from the field...
Navigation
   RSS 2.0
Categories
Entries by Month

# Wednesday, June 07, 2006

How would you address this scenario:

I have a web part that displays information from a legacy system. The information is very important to that system's user community -- so much so that it deserves to be displayed on the home page (WSS, not SPS). However, the legacy system user community is about 25% of the organizations employees. This 25% is influential, and mostly technology averse.

If the information applied to 100% (or somthing close to it) of the employees, then I would update the Shared View. But I would rather not subject 75% to an empty web part. And forcing the 25% to manually add the web part to their Personal View is a nonstarter.

I encourage comments/questions on my blog site.

Wednesday, June 07, 2006 1:11:29 PM (Central Daylight Time, UTC-05:00)  #    Comments [2]  | 
Friday, June 09, 2006 6:46:27 AM (Central Daylight Time, UTC-05:00)
If this is a "home grown" web part, then you could host the web part with no frame. The web part, itself, could then see if the active user were a member of the 25% and, if not, render nothing. In this way, the web part could be conditionally 'absent'.

If this is not home grown, then you could create a web part that looks up the active user to see whether they should see the webpart or not and, if not, this webpart could emit CSS to set the style of the legacy system webpart to "display:none".

Kevin Buchan
Thursday, April 05, 2007 12:50:10 AM (Central Daylight Time, UTC-05:00)
This is a classic case to use Audiences to set up who sees the web part and who doesn't. I just hope there is a way for you to identify who are the 25% of the users (security group? user property?) and that you have MOSS and not just WSS.
Comments are closed.
Search

Further Reading...

Powered by: newtelligence dasBlog 2.2.8279.16125

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2008, Paul Schaeflein

Send mail to the author(s) E-mail