Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Problem summary: Given 2 content types and a different workflow associated with each CT, one workflow works properly for it's CT but when the other CT is uploaded the wrong workflow is invoked. I have checked all settings carefully and I am stumped.

Background: I have a site collection which contains a document library (SP 2010 Server service pack 1). The library has been enabled for multiple content types and I have 2 custom content types which are defined on my content type hub. Re-publishing and running the timer jobs for the hub and subscribers have been done after changes.

Content Type TeleworkAgreement is associated with a reusable workflow named FlexiplaceApproval as shown here:

this workflow works OK

Content Type FlexiplaceArchive is associated with a reusable workflow also named FlexiplaceArchive as shown here:

this is NOT getting invoked

The workflow settings for the library seem correct. There is NO workflow associated with ALL content types per the dropdown box. The following shows how the FlexiplaceArchive workflow is configured to run on items of type FlexiplaceArchive:

workflow Settings

Strangely, there is an Approval Form shown in the Forms section of the designer when examining the FlexiplaceArchive workflow. There should not be because there is no Approval Task in that workflow.

I hope you can help me figure this out. Would there be a Powershell script(s) to ensure that each workflow gets invoked for its proper content type. The UI appears correct to me.

share|improve this question
    
It might benefit you to work on your accept rate. It would probably incentivize more answers. Also, Atlas Shrugged is garbage propaganda. –  RJ Cuthbertson Oct 12 '12 at 2:34
    
At Stackoverflow.com, I think my "accept rate", reputation and badges are "pretty good" but since directing more questions to Sharepoint.stackexchange I am getting little useful help. I am sure you are a sharp young man and when you get a little older and pay a LOT more taxes you may think differently about the ideas behind Atlas Shrugged. –  John Adams Oct 16 '12 at 17:43

1 Answer 1

I believe I understand this problem now and I created a workaround which is an acceptable resolution. In short, associating a workflow with a content type does not behave as one would think. If the default content type for the document library has a workflow associated with it, then that workflow will always be invoked - even if the user selects a different content type in the Document Information Panel when supplying metadata.

I posted a more complete explanation in the Technet forum for Sharepoint: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010customization/thread/ce672930-0876-45b5-995e-da9dbe330f95

share|improve this answer

Your Answer

 
discard

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.