SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is SharePoint 2007. I created a custom workflow activity in Visual Studio 2008 (using this and a few other blogs as a reference). I deployed it properly, I think. I can go into SharePoint Designer 2007 and see my action in the list of available actions. But when I click it and press Add, nothing happens.

I've used samples I've found as well as simplifying the code in my activity as much as possible. It doesn't change anything. So I don't think it's my code there, but it's hard to say.

share|improve this question
I would love to see an answer to this. I am having the same issue with SPD 2010 – Mike T Jun 28 '11 at 23:54

Do you have multiple web front ends? Did you do an iisreset? I've seen similar behavior when it wasn't installed on all WFEs with a farm wide reset.

share|improve this answer
No, just one front end. I have done iisresets. That doesn't seem to help. I've also changed the name of the assembly in the .actions file and am able to break it - SPD will tell me that the assembly wasn't found. So I know it's at least seeing the assembly. But I found it won't error if I use a class name that I know doesn't exist. – Anonymous Sep 21 '10 at 14:47

Side note: the following steps working (for me) in test enviroment.

The steps that I follow for get custom activity working (selectable) are:

-> Check web.config changes and integrity structure of custom activity files (.action, .cs, etc):

 <SafeControl Assembly="TestCWA1, Version=, Culture=neutral, PublicKeyToken=7b0c1cea1fea1132" Namespace="TestCWA1" TypeName="*" Safe="True" SafeAgainstScript="False" />

 <authorizedType Assembly="TestCWA1, Version=, Culture=neutral, PublicKeyToken=7b0c1cea1fea1132" Namespace="TestCWA1" TypeName="*" Authorized="True" />

Source of the code given for this answer

  • Clear SharePoint Designer cache.

  • In my case, I create a .actions file, but I didn't added the WSS.ACTIONS schema file. The .actions file must be also contained in a SharePoint mapped folder as is described in this source.

  • Execute iisreset command.

  • Open SharePoint Designer and create a new Workflow and select the custom activity.

In your question, you didn't mention how you created the custom activity and (since the link of your question is broken) it's hard to continue debugging.

I followed this same steps in production enviroment, but my custom activity doesn't working for me (i.e selectable), but if anyone else have more information to add, please try expand this answer.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.