MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

WorkFlow & ContentType

  Asked By: Kamal    Date: Feb 04    Category: MOSS    Views: 811

We have 10-20 sub-sites w custom lists built w content types in a MOSS
site collection. These ss are "stamped out" with a template we built
and update as needed. There are SPD WFs on these lists.

However, when we change our WFs, we are currently going to each ss and
modifying the WF therein with SPD. Retro-fitting is a pain.

I think we are doing something wrong. Can we "attach" a WF to a
content type, so that when we change the WF, it automatically updates
each sub-site's lists WFs?

Is it as obivious as some checkbox somewhere?



5 Answers Found

Answer #1    Answered By: Dwight Becker     Answered On: Feb 04

The problem is that you are using SPD designed workflows which are tied to a
specific list or library. If you want to make these workflows more generic and
use them in multiple locations then repackage them as features using Visual

Answer #2    Answered By: Amar Kumbar     Answered On: Feb 04

Yep, just figured that out. Unfortunately, we do not have access to

Answer #3    Answered By: Marc Dixon     Answered On: Feb 04

You can only attach  workflows built  in Visual Studio to a Content Type. SPD
workflows are attached to a single list or library and will need to be updated
manually each time you want to incorporate a change. That's one of the primary
limitations of SPD workflows.

Answer #4    Answered By: Latanya Nieves     Answered On: Feb 04

Just to be completely clear...when you create a workflow  in VS and attach  it
to a Content Type, you can update  it once and the changes are reflected

Answer #5    Answered By: Georgia Barr     Answered On: Feb 04

The answer is Yes and No. Visual studio workflows are compiled as DLLs, and as
such they aren't as automatic to update  as SPD workflows. Having said that. If
you Instantiate a workflow  on a content  Type it will be available wherever that
content type  is used in a document library or list. If you swap it out for a
newer version of the workflow then the new version is also automatically
available in all those locations. From a practical point of view the answer is
yes. But the process for updating isn't just modifying the existing workflow
and re-deploying. You have to create a new version of the workflow, add it to
the content type and then in the content type set the old one to accept no new
instances and the new one to create new instances.

I hope that doesn't confuse things more. You will have ONE instance of the
workflow that is managed in the content type its just that updating it is a
little different than SPD workflows. You still only need to deploy one new
instance to update it.

Didn't find what you were looking for? Find more on WorkFlow & ContentType Or get search suggestion and latest updates.