Symptoms
When environments are changed the Smartobject connection string in the Infopath Form integration does not update for some connection strings in smart object integration wizard.
Diagnoses
I am looking for the help to resolve the issue that occurred when the environment is changed from staging to production. Process does not get connected to production k2 server at all places. (When environments are changed the connection string does not update for some connection strings in smart object integration wizard.)
Background of Project: I have k2 process developed using InfoPath and SharePoint. After completing successful testing in development environment, I have deployed the process in the Production. I imported all smart objects. Made sure all the SharePoint links are changed to the production etc.
Issue:
Some of my smart object integration methods are still connected to K2stg (Staging environment).
Resolution
This behavior was reproducible with the attached process, but only seem to occur with some of the Smartobjects/Infopath data connection integrations. When integrating an Infopath form with a Smartobject, if you use the "Integrator" (Right Clicking on an Infopath form andgt Integrate with SmartObject) instead of using the Integration wizard within the process a andltSmartobjectServer /andgt XML node in the process definition (.kprx) file and ultimately in the Infopath form (.xsn) file does not get generated/updated correctly which results in the data connections not updating correctly when deploying between environment. A TFS item has been logged to be investigated and to be addressed in a future release.
In the .kprx file, the XML node usually looks like :
andltSmartObjectServer Type="SourceCode.Workflow.Authoring.K2Field" Assembly="SourceCode.Workflow.Authoring, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d"andgt
andltPartsandgt
andltArtifactLibraryFieldPart Type="SourceCode.Workflow.Design.ArtifactLibraryFieldPart" Assembly="SourceCode.Workflow.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d"andgt
andltGuidandgt68ede11684bc4e379d64c7d224e67c10andlt/Guidandgt
andltValueTypeandgtSystem.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089andlt/ValueTypeandgt
andltFieldNameandgtSmartObject Serverandlt/FieldNameandgt
andlt/ArtifactLibraryFieldPartandgt
andlt/Partsandgt
andltGuidandgt15d4e250705b4a39a5c6470c753a9a27andlt/Guidandgt
andltValueTypeandgtSystem.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089andlt/ValueTypeandgt
andlt/SmartObjectServerandgt
A possible fix would be editing the .kprx file for the smartobject methods that are experiencing the update issue when changing environment, and then adding the andltSmartobjectServer /andgt node from a working smartobject integration to the none-working one. It is always recommended to make a backup of the whole project's directory when these steps are needed. Using an XML editing tool with a pretty-print option will assist with pin-pointing and editing the xml.
Once the .kprx is fixed, usually the steps to deploying between environment will just involve the following:
1. Changing the object browser to the serverenvironment that you wish to deploy to
2. Re-running the Infopath Integration Wizard and performing the "Refresh" for the Infopath Form
3. Running the "Edit" option to confirm if all SmartobjectServer data connection string is pointing toward the correct environment
4. If so, build and deploy the project (both the Smartobject Server connection strings from within the Infopath integration wizard and within the .xsn file should now be updated correctly)
5. Test
For the time being, we also recommend that the Infopath Integration wizard within a process be used to integrate an Infopath Form with a Smartobject instead of using the Right click andgt Integrate with Smartobject option outside of a designer.
