Deploying K2.net InfoPath processes between environments

  • 24 February 2022
  • 0 replies
  • 3 views
C
Userlevel 3
Badge +8
 

Deploying K2.net InfoPath processes between environments

KB000111

PRODUCT
K2.net 2003
TAGS
Microsoft InfoPath
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

This article describes the deployment issues with the K2.net InfoPath process settings that are stored in process data fields. It also provides a step-by-step guide to follow when deploying K2.net InfoPath solutions between environments.

 

The K2.net® 2003 InfoPath Process stores the integration settings in process level data fields. As the integration settings often differ as the process progresses through the development, staging and production environments, it is advisable to verify the settings (e.g. K2DWSPath, K2SharePointLibURL, K2WorklistURL, etc.)  
 
Note: It is possible to update the integration settings by re-running the InfoPath Process Template from K2.net® Studio. However, in scenarios where the Development environment is isolated - having no connection to the staging and production environments - the InfoPath Process Template wizard cannot be used as K2.net Studio verifies the server connections by establishing a connection to them, and fails as they are unreachable.
 
These values are not stored in String Tables to avoid compatibility issues between previous and existing process and template code versions.
 
The steps below illustrate how to deploy a K2.net InfoPath process solution between two environments (e.g. development and staging):
1)  Create a copy of the process, the development settings remain as they are
2)  Change the process data field values to represent the values in the staging environment. Change both the Value and the Metadata for each field
 
Field Name Example Description
K2DWSName Sites/mySite/ Virtual path to the SharePoint folder where the temporary InfoPath files will be stored.
K2DWSPath http://stagingserver:121/sites/mySite Server name of the SharePoint server where the temporary InfoPath files will be stored
K2IgnoreErrors False Ignores any errors, possibly caused by locking, during the deletion of the temporary InfoPath file.
K2SharePointURL http://stagingserver:121 SharePoint Virtual Server URL used in the Initialize event to create or prepare a work space for the temporary InfoPath file.
 
3)  Run the Document Settings of the process. Go to Process>Properties>Process General and on the drop down box under InfoPath Document Actions, click on Update Document Settings
4)  On the "InfoPath Source File" form of the wizard, provide the location of the InfoPath document in the staging environment. (Must have access to this document)

  
5)  On the InfoPath Document Settings form, change the name of the K2.net Server Name and K2.net InfoPath Web Service URL for the staging environment

  
6)  If a message pops up stating that the InfoPath Web service could not be found, click on Yes to ignore

  
7)  If a message pops up stating that the K2.net server could not be found, click on Yes to ignore

  
😎  Complete the wizard and export the process to the staging environment

 

0 replies

Be the first to reply!

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings