ad
KERRAY
ještě že mám dneska jedno univerzální workflow, který akorát pouští ironpython skripty, takže není potřeba kvůli každé změně a opravě všechno předělávat... nicméně teď bych potřeboval udělat úpravu toho společnýho základu, takže nás to asi čeká...
Julie's Office Dev Blog : Sharepoint Workflow Versioning
http://blogs.officezealot.com/jkremer/archive/2007/05/02/20330.aspx
Deploying an update to a workflow does require a bit of work. This is covered in the Microsoft patterns and practices SharePoint Guidance (
http://www.microsoft.com/spg).
If you don't change the serialization (properties, activites, or order of the workflow) you can just redeploy overtop. Bascially, anything that's a quick bug fix. If you change the serialization you have to deploy a new workflow.
https://blogs.pointbridge.com/Blogs/herzog_daniel/Pages/Post.aspx?_ID=4
Instead you’re going to have to deploy the subsequent version it as if it were a completely new workflow. It gets its own GUID in the workflow.xml, and has to be associated with the lists and libraries all over again. You’ll want to set the version 1 workflow to “No New Instances.” To do this, go to the list’s settings screen and go to Workflow Settings -> Remove Workflows. Here you’ll find a radio button to set the workflow to “No New Instances.” When version 2 is deployed and associated, only version 2 will be allowed to start on an item. At the same time, any currently running version 1 workflows will continue to operate normally.