Update to this article with SharePoint Solution (.wsp) file is available here!
A past customer called me today, frantically going nuts because they have a large MOSS deployment (~ 15,000 users) that was planned for production push out tomorrow, and needed a redirection strategy.
Eh, what? What the hell does a redirection strategy mean?
The problem with their sandboxed / user acceptance SharePoint environment was that although there were intuitive navigation controls, and a good navigation strategy supplemented by intuitive custom WebParts, some users were somewhat resisting the adaption of SharePoint, complaining it was over 2 clicks to get to what they wanted. Although I think that this is a rather stringent benchmark to get to the information that you require in an enterprise EIM system, he really needed a way to cut down on the clicks. The only real good part of the requirements is that a majority of users only went to certain site collections, rarely crossing collections, so it should be easy to redirect the users on entry to the portal to certain site collections, right?
It turns out, yes, it really wasn’t that difficult. Since I owed him a favor, I got started developing the SharePoint Redirector WebPart, which after gets tested tomorrow in production, I am going to release for free!
It works pretty simply. Basically, it takes an Active Directory operator (pretty much whatever you want since is a freeform text box property), something that exists in the user profile, and redirects based on whether that condition is met. Like if in my user profile I have the field squadron and in the squadron field, I met condition 101st SharePoint Squadron, I can be redirected immediately to http://www.sharepointsecurity.com/101squad or any other URL of my choosing. There is the provisioning in the WebPart properties to handle up to 10 redirections, and once I get the chance I will expand this to hold any number of redirections.
Administrators and general users don’t see the same thing, as administrators shouldn’t immediately be redirected if they met that profile operator, they still have to manage the root of the SharePoint implementation. Rather, they should see a small dashboard saying whether there are redirections conditions that have been setup, and the appropriate redirection parameters that are bound to those conditions.
The exception handling is pretty good, and will create a new event source in the event log, to a local .log file, and will output major errors to the screen. I use a standard exception handling class that I use for all WebPart development with it.
The Redirector WebPart Properties Toolpane
Global WebPart Settings
Condition Activation Management