Hi All,
I'm working on a State Machine workflow, using VS 2008, and all is going OK, but I am a bit concerned about the default handling I'm seeing of Workflow History. If I deploy a new version of my workflow (with an incremented build number), the currently enabled workflow on the list gets set to "No New Instances". But when I associate the new version of the workflow with my list, and remove the old one, all of the Workflow History for items handled under that older version of the workflow appear to be removed. If however I try to use the same name for the Workflow when I associate with the list without removing the old one, I get told a workflow with the same name exists. All of this behaviour sort of makes sense, but I want to retain the workflow history for items handled under earlier versions of the workflow. Am I missing something here? It's going to be a fact of life that subsequent versions of a workflow need to be deployed into a live environment as changes are made, but surely you don't have to pay the penalty of losing all of the workflow history for the previous versions of the workflow? Kind Regards, Trevor Andrew ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
