InfoPath Form Custom Code

SharePoint 2007

Specifies custom code that is included within a Microsoft Office InfoPath form that is uploaded and hosted server-side by InfoPath Forms Services.

Real World Example

A business process development team needs to perform some complex custom business logic processing within a server-side InfoPath form. They develop a form that includes several managed code assemblies that will be installed on the server.

Technical Details

There are two different categories of browser-compatible InfoPath form templates:

  • Those that contain code.

  • Those containing only declarative business logic (such as rules, calculations, and conditional formatting) only.

Deploying InfoPath form templates that contain managed code involves more steps and requires a server administrator to perform them.

Custom business logic is supported in a browser-enabled form template if it uses the supported types and members of the new managed code object model that is included in Microsoft Office InfoPath 2007. It can use assemblies or code modules defined within the form.

The process of deploying InfoPath form templates that contain form code to a server running InfoPath Forms Services occurs in three distinct steps:

  1. Get the form template ready. This step creates a new .xsn file that contains information about the server it will be deployed to.

  2. Upload the form template to the server. This step requires a farm administrator to add the form template to the server and includes the optional step of verifying that the form template can be uploaded.

  3. Activate the form template to a site collection. This makes the form template available on a site collection so that it can be filled out in the browser or in InfoPath, depending on whether users have Office InfoPath 2007 installed.

Support Details

Business logic assemblies from all browser-enabled form templates on servers running InfoPath Forms Services are loaded, as necessary, into the single Application Domain that SharePoint Products and Technologies use and control. When the Application Domain is recycled, business logic assemblies are not reloaded until they are requested again.

See Also

Community Additions

ADD
Show: