Actually workflows CAN be created and deployed to various locations. Jim is correct that the WF is tied to the list for which it is created, but only if the WF was created using SP Designer.

Create the WF using Visual Studio and package it for deployment, then you can simply activate it on whatever lists you would like. Using VS with SharePoint Extensions to design and build your workflows is a little more advanced, but will allow you the flexibility you are looking for. This method also allows for code reuse so that you don’t have to recreate common functionality from scrath.

I use this method for nearly all of the workflows that I create.

I am enjoying these tutorials very much!

No, Workflows are not “deployable.” At least not easily. They’re tied to the specific list for which they were created.

I have had limited success copying them and reconfiguring them. I’ll work on a demo to post to EUSP.

Bjørn,

Great information. I look forward to seeing more. You’re doing a great job.

Blessings,
Jim Bob

Top News Stories Five Truths You Must Know About SharePoint and Exchange (Search Win IT) IT managers…

You’ve got me 95% of the way there! I probably learned 3 or 4 things in this simple webcast that didn’t come clear to me in lots of time looking over stuff on microsoft.com…!

Here’s a potential topic for a future video:

How can we easily redeploy workflows? I’m wondering if we can develop a workflow for “routing approvals” and then save that document library as a template. If we redeploy it does the workflow come along for the ride? Just a thought..