InfoPath Integration Process Wizard

This content applies to legacy design tools (such as K2 Studio, K2 for Visual Studio, or the Silverlight-based K2 workflow design tool). If you have upgraded from K2 blackpearl 4.7 to K2 Five, these tools may still be available in your environment. These legacy tools may not be available in new installations of K2 Five. These legacy tools may also not be available, supported, or behave as described, in future updates or versions of K2. Please see the legacy component support policy for more information about support for these components.

What does it do?

The InfoPath Integration process wizard allows you to use InfoPath form templates in a process to start workflows and action workflow tasks. Add InfoPath form templates using either the InfoPath Integration process wizard or the InfoPath Client Event wizard, the latter of which displays the InfoPath Integration Process wizard if not already configured.

A view in an InfoPath form template is chosen for each event, which means that one InfoPath form template that contains multiple views can be used for multiple events. Conversely, multiple InfoPath form templates, each with one or more views, can be used in the process for multiple events. This option is useful when a process contains sensitive data or when access to data must be tightly controlled.

Why Use the InfoPath Process Wizard?

Microsoft InfoPath and the Microsoft Office Forms Server are two technologies that organizations can take advantage of to deliver rich forms to their end users to facilitate business processes.

With the Microsoft Office Forms Server, InfoPath forms may be opened with or without the InfoPath client. The Microsoft Office Forms Server renders InfoPath forms inside SharePoint, thus eliminating the need for the InfoPath client for simple forms. The InfoPath client is still required to open InfoPath forms that have complex controls on them and to design forms.

K2 automates the authoring of code behind InfoPath forms via the wizards to integrate InfoPath forms with K2. K2 lets business analysts and other non-developers create these InfoPath forms and workflow interactions with a few clicks, instead of needing a developer skill set and writing code. This empowers users and also reduces the time and effort associated with developing and deploying InfoPath forms inside a SharePoint environment.

Note: InfoPath is a deprecated technology from Microsoft and is not supported with SharePoint 2013 and later. The K2 integration continues to work but there are no new investments in this integration technology.

Information required to make use of this wizard:

  • An InfoPath form saved on a shared location

Important considerations when making use of the InfoPath Process Wizard

  • A shared location is described as the following:
    • A network location on a local drive

    • A shared network location over a network

    • A SharePoint site

  • FTP locations cannot be used as a shared location

  • The InfoPath form used during the wizard configuration is downloaded from the specified shared location and is stored as a local copy in the project location. The wizard configuration makes use of the local project copy of the InfoPath form and does not perform any actions on the original InfoPath form.
  • Any changes made in the InfoPath Integration process wizard are applied to the InfoPath Client Event Wizard.
  • All the InfoPath project information is saved under the main data source in a _K2 node. It is highly recommended that this folder not be modified.
  • When using Forms Server with InfoPath forms, cross-domain access for form templates needs to be enabled.

It is possible to have certain sections of the InfoPath form digitally signed