When change InfoPath form and then publish it to the SharePoint library,
how does the InfoPath control the versions?
For those K2 workflows that are in progress, it will pick up this new version of InfoPath. How to prevent this and keep the workflows in progress using the older version of InfoPath?
Now the projects I am working on, the InfoPath form will be published to the SharePoint library, and all the forms(Archived, in-progress) will link to this newer version of InfoPath.
So how do we make sure that backward compatibility works in InfoPath-Change the JavaScript(that is a pain!).
How to link the different version of InfoPath to the right version of K2 Workflow?
Thanks
coenw
+4
How to make an updated InfoPath form published to SharePoint library to work with older version of K2 workflow in progress?
When an updated InfoPath form is published to the SharePoint library, the older version of the form is overwritten.
This newer version is supposed to work with newer version of K2 workflow.
So how to make sure this newer version of form can work with the older version of K2 workflows(the XML schema in it is old) without causing conflicts
Thanks,
coenw
When an updated InfoPath form is published to the SharePoint library, the older version of the form is overwritten.
This newer version is supposed to work with newer version of K2 workflow.
So how to make sure this newer version of form can work with the older version of K2 workflows(the XML schema in it is old) without causing conflicts
Thanks,
coenw
Reply
View our Community Site Map
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.