Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
My friend Doug is having some problems with SharePoint workflows and using the OnTaskCreated activity. He says it doesn't work, but I haven't had problems with this. Hoping that this video helps him as well as shows some of my readers how to quickly create a workflow for SharePoint 2007 with Visual Studio 2008.
The whole video is only 8:44, starting from creating a project from scratch all the way to creating a simple workflow.
Doug - if you see any variation between what I did and what you did, please let me know. I'd be glad to look up the hotfixes that are installed on the VPC if that helps as well.
Double-click the video to watch full screen.
Comments
Anonymous
August 30, 2008
PingBack from http://blog.a-foton.ru/2008/08/creating-sharepoint-workflows-with-visual-studio-2008/Anonymous
August 30, 2008
Thanks Kirk! As you know that's pretty much the same as the demo I sent you with a difference that I am setting task properties. I am getting the same error effect on a couple of environments, but I'm going to drop it onto a client's dev environment Tuesday to see if I can repro it there as well. It's worth noting that this often works for me as well. If I create 10 items in a row, a number of them will complete, but some won't and the path is indeterminate. In other words, sometimes only task1 is handled, sometimes 1 and 2, 2 and 3, 1 and 3, etc. I really appreciate you looking at this (on a Saturday morning no less) and I look forward to finding a fix. This problem in my opinion is extremely serious because once the event fails to fire, the workflow is in an unrecoverable, but non-error, state. Have fun at Tech-Ed!Anonymous
August 30, 2008
P.S. I'll put up a screen shot soon that shows what I am seeing.Anonymous
August 30, 2008
Robert Shelton has an entire series of "How To" SharePoint Workflow videos, including revised How To's leveraging VS 2008. Worth taking a look. http://www.sheltonblog.com/archive/2007/11/04/series-of-sharepoint-workflow-how-to-videos.aspxAnonymous
August 30, 2008
I believe I found the root cause. You can read about it here: http://www.elumenotion.com/Blog/Lists/Posts/Post.aspx?ID=69 I also included a possible work around for those affected. --DougAnonymous
August 30, 2008
@Lamont - ABSOLUTELY agreed, I leverage Robert's material frequently. For anyone wanting to see how to build real-world workflows with SharePoint and Visual Studio, check out Robert's fantastic work.Anonymous
August 30, 2008
@Lamont - ABSOLUTELY agreed, I leverage Robert's material frequently. For anyone wanting to see how to build real-world workflows with SharePoint and Visual Studio, check out Robert's fantastic work.Anonymous
August 30, 2008
@Lamont - ABSOLUTELY agreed, I leverage Robert's material frequently. For anyone wanting to see how to build real-world workflows with SharePoint and Visual Studio, check out Robert's fantastic work.Anonymous
August 30, 2008
@Doug - hoping that it is as simple as finding a missing hotfix, because I have customers running this same scenario in production under significant load without similar symptoms.