INFOPATH FORMS in MOSS CUSTOM WORKFLOWS

Using InfoPath forms in Custom Workflows for MOSS
1) Never clone an InfoPath form it is not a good practice. InfoPath has a unique internal ID that will also copy over to new form and can create issues when both forms are used in a WF set up.
2) Always ensure that "
network" published InfoPath forms (*.xsn) listed under Metadata section of "workflow.xml" (part of WF solution) exists and are under the correct folder location. Delete the references of forms not being used from "workflow.xml" which otherwise will lead to errors like "Form is closed".
3) Ensure that with every change done to the InfoPath form is acknowledged by publishing the InfoPath form to the network.
4) Ensure that every change made to the project will be accounted by redeploying the *.dll in GAC.
5) Uninstall/Install the feature. Workflows that are already in progress will be updated with the new changes. Keep this is mind before applying the changes. Accordingly wait for "In Progress" workflows to finish.6) There is no need to redeploy the workflow project library if only InfoPath forms are changed. 7) Restart the IIS after deploying. Restart ensures that the new changes come in effect.

Comments

Popular posts from this blog

Better manage customer relationships using Outlook Customer Manager

Understanding the Cloud Spectrum

Multi-Factor Authentication for Office 365