Designers > K2 Designer for Visual Studio > Design Tools > Toolbox > Process Wizards > InfoPath Process - Orientation | Send feedback |
The K2 InfoPath Process Wizard allows custom InfoPath form templates to be incorporated in a process that enables users to perform workflow tasks. InfoPath form templates are added using either the InfoPath Integration Process wizard or the InfoPath Client Event wizard, which will display the InfoPath Integration Process wizard if not already configured.
A specific 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 security must be tightly controlled.
Microsoft InfoPath and the Microsoft Office Forms Server are two very powerful technologies that organizations can take advantage of to deliver rich forms to their end users to facilitate business processes.
With the advent of the Microsoft Office Forms Server, InfoPath forms may now be opened with or without the InfoPath client. The Microsoft Office Forms Server renders InfoPath forms inside a web browser, 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.
Although the Microsoft Office Forms Server makes it easier for end users to interact with InfoPath forms, the developer side of the equation remains extremely complicated. Writing all the managed code necessary to pull data from disparate systems and integrate the InfoPath forms with workflows inside SharePoint is a complex process and can take several days to complete, for just one InfoPath form. K2 blackpearl automates the authoring of this code via the wizards to integrate InfoPath forms with SharePoint and the Windows Workflow Foundation. K2 blackpearl lets business analysts and other non-developers create these InfoPath forms and workflow interactions with just a few clicks, instead of needing a developer skill set and spending days writing code. This empowers users and also reduces the time and effort associated with developing and deploying InfoPath forms inside a SharePoint environment.
- A network location on a local drive
- A shared network location over a network
- A published SharePoint Site
FTP locations cannot be used as a shared location |
It is possible to have certain sections of the InfoPath form digitally signed |