Sharepoint Designer İş Akışını Taşıma

Selam, hocalar daha iyi bilirler bu konuyu ama araştırdım, şöyle bir şey buldum  : http://spwflmigrator.codeplex.com/

Sharepoint Designer ile oluşturduğumuz bir iş akışını bir başka sharepoint servera taşımak için workflows klasöründen ilgili akışa ait klasörü  kopyalayıp yapıştırdğımızda iş akışı çalışmıyor.(farklı 2 moss olarak düşünelim).Designer da oluşturduğumuz iş akışlarını nasıl bir başka server yada siteye taşıyabiliriz.

... 

So you've got a workflow and now you want to either move it to another list or attach it to another list at the same time.  The list you want to attach it to is in the same site.  You would think there was a way of associated a workflow with more than one list but in fact there isn't and to some degree it's understandable.  A lot of the actions you define in the workflow are specific to the library you are working with, even if you were to abstract your logic away from the list then SharePoint Designer links actions such as "Current Item" properties to the underlying list.

So, unfortunately it's not as easy as just editing the configuration XML file:

[workflow name].xoml.wfconfig.xml

and pointing it at the XOML and RULES files for your existing workflow.  Your workflow will almost certainly contain references to the original library or list, so just pointing the config file at you existing workflow will have some pretty uncertain outcomes!

The good news is that you can use a lot of what you've already created and apply it to a new workflow, as per…

1. Make sure the new list your working with is set up correctly (content types, columns, approval, check in /out…)
   
2. In SharePoint Designer, create a blank workflow with a dummy step defined
   
3. Copy the contents of your original XOML file named, [workflow name].xoml to the new XOML file that was created when you created the new workflow (use notepad)  NOTE: The XOML contains all the variables and activity definitions for your workflow, but not the logic
   
4. Copy the rules [workflow name].xoml.rules file contents to the new rules file  NOTE: The rules file contains the login for if, then…else comparisons
   
5. Compare your config [workflow name].xoml.wfconfig.xml file with the original config file and make relevant changes (probably just need to reference the content types created when requesting data from users)
   
6. Check through the workflow and change any fields linked back to the original document library – THIS IS THE MOST LABORIOUS JOB!

• UPDATE…ACTUALLY IT'S QUICKER AND EASIER TO OPEN THE XOML AND DO A GLOBAL SEARCH AND REPLACE LOOKING FOR THE GUID OF THE ORIGINAL LIBRARY AND REPLACING THAT WITH THE GUID OF YOUR NEW LIBRARY (GET THE GUID FROM THE URL LINKS ON THE SETTINGS PAGES, THE "AUDIENCE TARGETING SETTING' LINK IS PARTICULARLY HELPFUL!)

To a different site:

Your workflow is great and now everyone wants a go!  You need to deploy not just within the same site but to another location in your farm

The steps here are similar to the above, with the exception that you will have to copy all the files that are required to run the original workflow to the new location.  These files are usually just the ASPX pages that are run when you collect data from a user, you'll need to change the config file to associate the workflow with the files in the new location.  Better still copy the files to a central location and reference them this location in both workflow's.  That way you only have one set of files to keep up to date. 

After you've done this you can follow the steps above to make the necessary changes.

Kaynak: http://vspug.com/andynoon/2007/09/18/reparenting-a-workflow-to-a-different-list/

Alper ve Mert Bey teşekkür ederim.Her iki yöntemde başarı ile çalıştı.Alper Bey'in sunduğu çözümle 2 moss sunucusuna erişilebiliyorsa akışlar birbirlerine aktarılabiliyor.Mert Bey'in sunduğu çözümle de moss lardan birine erişilemiyorsa ama akışlar yedeklenmişse akışlar ayağa kaldırlabiliyor.Özellikle çok adımlı ve çok rule içeren akışlarda büyük yardımı olucaktır.2 yöntemi de denedim ikisindede akışları başarı ile aldım.

Alper ve Mert Bey teşekkür ederim.Her iki yöntemde başarı ile çalıştı.Alper Bey'in sunduğu çözümle 2 moss sunucusuna erişilebiliyorsa akışlar birbirlerine aktarılabiliyor.Mert Bey'in sunduğu çözümle de moss lardan birine erişilemiyorsa ama akışlar yedeklenmişse akışlar ayağa kaldırlabiliyor.Özellikle çok adımlı ve çok rule içeren akışlarda büyük yardımı olucaktır.2 yöntemi de denedim ikisindede akışları başarı ile aldım.

Faydalı olduğuna sevindim.

İyi çalışmalar.