CustomActions allow you to provide an easy way for an end user to perform some sort of action on or with a specific list item that is not available in a standard SharePoint installation.
Let’s go through a simple demo of using a CustomAction. In this demo, we will create a CustomAction which will redirect to a custom ASPX page and display some information about the list item. To start, let’s create a new WSPBuilder project named “CustomActionsDemo” and add a new Blank Feature called “DemoCustomAction”. (If you have never used WSPBuilder before, please check out my Intro to WSPBuilder post.) Use the following in the feature settings dialog:
Next, we’ll need to add a LAYOUTS folder to the folder that represents the 12 hive in our project. Beneath that, add a “DemoCustomAction” folder. Once we have these folders added, WSPBuilder will automatically knows how to push these files out to the 12 hive. At this point, your project folder structure should look like this:
Now we can go ahead and add a new web form without code behind to the LAYOUTS/DemoCustomAction folder. Name it ViewListItem.aspx and put the following code into it:
<%@ Page Language="C#" %>
<%@ Import Namespace="Microsoft.SharePoint" %>
The code above uses two parameters which are generated and passed in via the URL from our CustomAction. It then uses these two parameters, ListId and ItemId, to find the specific SPListItem and display it’s Title field.
Now all that is left to do is write the CustomAction specification for our feature. The following code should be placed into the elements.xml file that was generated for you when you added the blank feature to the project:
This is the XML that specifies your CustomAction. Here is a quick run-through of the attributes used (Note that there is a full page on MSDN explaining all of the attributes here: http://msdn.microsoft.com/en-us/library/ms460194.aspx):
- Id – This is an optional field to identify this CustomAction. You can make it whatever you would like.
- RegistrationType – How we will specify what items get this CustomAction. In our case, we have stated that a specific content type will get it.
- RegistrationId – The identifier of what will get this CustomAction attached to it. Since we have chosen to attach by content type and our RegistrationId is 0x01, we are attaching this CustomAction to the Item content type and all that inherit from it.
- Title – This is the text to display for this CustomAction.
- Description – This is a description of the CustomAction. It will be displayed as a tooltip when the user hovers over the link for the CustomAction.
- Location – The location attribute specifies where to place the CustomAction. In our case, we have chosen DisplayFormToolbar which will display on the details page of the item.
- UrlAction Url – This is the URL that we will send the user to when the CustomAction is clicked. The items in curly braces are variables provided by SharePoint that contain the current List ID and the current Item ID.
Now that our coding is complete, we can deploy this feature out to SharePoint using WSPBuilder. After deploying the feature, we should see the feature available in Site Collection Features.
Go ahead and activate the feature. After activation, create a custom list and add a new list item to it:
Now if you view the item, you should see a new item in the top of the toolbar called “Invoke Demo Custom Action”.
Go ahead and click it. This will invoke the CustomAction we just wrote and re-direct you to the custom page that we wrote earlier. If all went well, you should see something like this:
That’s about it for CustomAction basics. Obviously you can use this technique to link to a page that does much more than just display some information about the list item. Stay tuned for more on CustomActions in the future.