After migrating SharePoint 2007 portal to 2010, I noticed that the workflows associated with lists were not available and after researching a bit, I found something interesting on TechNet.
If you had disabled the Workflow Auto Cleanup timer job in your Office SharePoint Server 2007 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job, see Disable preservation of workflow history (SharePoint Server 2010).
I checked the timer job and it was running on both machines so something else was at play here so later I found out here that
“In SharePoint 2010 the 2007 workflows are there to allow any running workflows to complete, but by default creating new instances of the workflows is disabled as the expectations are that you will want to move forward to the SharePoint 2010 workflows.”
And to allow creation of SharePoint 2007 workflows instances, I followed Vinit’s solution which was
- Activate SharePoint 2007 workflows feature in Site Collection Features
-
Remove ‘none’ from <AssociationCategories>none</AssociationCategories>
14\template\features\ReviewWorkflows\Reviewapproval.xml
14\template\features\ReviewWorkflows\ReviewFeedback.xml
14\template\features\SignatureWorkflow\Signatures.xml
Don’t’ forget take backup of these files before modifying them.
I hope you find this post useful, thanks for reading.
October 1st, 2012 at 4:34 pm
Reblogged this on Sutoprise Avenue, A SutoCom Source.
October 24th, 2012 at 10:20 pm
[...] SharePoint 2007 workflows missing after migrating to SharePoint 2010. [...]
November 29th, 2012 at 9:09 pm
Interesting post, in fact i came across this post and your profile while searching on how to migrate a Sharepoint 2007 app to Sharepoint 2010 (or 2013 is a better idea??) – basically i am having a complete re-engineering and i’ve been asked to do that using agile methodologies. You think TFS would help? Project involves Sharepoint and Project Server.
Will be helpful if you can share your thoughts on this.
November 30th, 2012 at 9:55 pm
Thanks for reading and commenting Bhavin. Now regarding your queries, please review my comments below:
1. You can easily migrate from SharePoint 2007 to 2010, I haven’t found any supported way from Microsoft to migrate to SharePoint 2013 from 2007 directly. There is a product called ShareGate which you can use for migration and it also supports migration from 2007 to 2013 directly (http://en.share-gate.com/blog/sharepoint-2013-migration-free).
2. For using agile, list down what you are required to migrate and plan it in iterations like in first release you can target migrating sites and document libraries and then in second iteration you can target my site.
3. If you are doing any custom development like writing web parts or workflows using Visual Studio then integrating TFS with SharePoint would give you some nice features, check out this article on how to do so http://blog.cloudshare.com/2012/06/11/how-to-integrate-team-foundation-server-with-sharepoint/
Please let me know if you need anything else. Thanks