Our typical development process is to create a SharePoint Site and List on a devlopment server to test and create K2 workflows and ASP.NET forms and webparts. I recently moved a K2 Workflow from development to our production server and it seemed easy enough with the SharePoint Integration Client. I discovered some fields weren't updating between the workflow and SharePoint as I had planned so I went to SharePoint List Items step to check on them. I saw that the Design Time Value was pointing to the dev site, and not production. To check I archived and deleted my development site and then discovered the Metadata list was blank back in K2!
I then changed the SharePoint Site URL to my production site and the Metadata re-appeared. I will now have to open each SharePoint List Items event and change the Design Time Value! There are probably close to 50 in this workflow so it will take me some time to double check them all.
1. Is this normal behavior? Is K2 designed so that when you switch lists you have to change the Design Time Values individually?
2. How is it possible to work on a development SharePoint environment to test changes, and then push it to production environment? This would seem to be hours of work each time.