A while back I whipped together some web parts for assisting in troubleshooting and managing some elements in SharePoint 2007 which wasn’t easy to do then. I’ve since converted them to SharePoint 2010. They’re available for download on http://sp2010adminpack.codeplex.com.
Workflow Manager
The Workflow Manager web part allows an admin to view all active and attached workflows in the site collection. This is a web part, so you can add it to any page you want within your site collection. I find this exceptionally helpful in larger deployments when you want to know where exactly your workflow is being used.
Features
- View the workflow template, and the actual name used by the list. Click the Workflow Name to go to the settings page.
- View whether or not it’s enabled, and how it runs.
- View the number of currently running instanced.
- View the site and list it’s attached to. Click the list to go to that list.
- Each column is filterable and sortable for easy analysis.
Workflow Organizer
The Workflow Organizer allows an admin to specify the order in which multiple workflows will be run. The feature adds a new link to the Workflow Settings page of your list called Workflow Organizer.
Features
- Fire a workflow for any event on your list, ItemAdded, ItemAdding, ItemDeleted and more!
- Specify the firing order of your workflows, you control what runs when.
- Use the delay to give your workflows a little more time to process.
Site Columns
The Site Columns web part was originally designed to handle the missing site columns we experienced with promoting InfoPath fields in MOSS. I don’t know as if this is still an issue with SharePoint 2010, however the web part also allows you to view all content types which rely on a site column.
Features
- View all or a select group of site columns.
- View the field name, ID and internal name.
- Click the field name to edit its properties.
- Click Find to display all content types this site column is used by.
Server Name
The Server Name web part simply displays what the current server name is. Why? Because when you’re working with network load balancers, you need to know what actual web front end you’re on for troubleshooting certain things. Drop this web part on a page or in your master page footer and you’ll always know where you’re at.
Features
- Not much, just shows the actual host name of the server you’re on.