Amal Nagm

The design experience

• The form template contains managed code.
• The form template requires a Full Trust security level, which allows the resulting forms to have full access to the system resources on users' computers, such as files and settings.
• The form template uses a data connection that is managed by an administrator.
• The form template is enabled to be displayed on a mobile device.

The user experience

Users submit data to external data sources by clicking a Submit button on the toolbar.

Users switch between views by clicking an item in the View list on the toolbar.

Reach customers, partners, and suppliers with user-friendly forms

• The form opens in a browser If users don't have InfoPath installed on their computer, the form opens in a browser, where they can fill it out just as they would any other Web-based form.
• The form opens in InfoPath If users have InfoPath installed on their computer, the form opens in InfoPath, where they can fill it out just as they would any other InfoPath form. Because they are filling out the form in InfoPath, these users will have the added benefit of being able to use the full range of InfoPath features for filling out forms, some of which are not available in browser forms.
  Note It you prefer, you can customize the settings for your form template so that it always opens in a browser, even if users have InfoPath installed on their computer. This can be useful when you want the experience of filling out a form to be identical for everyone, or when you don't want the form to be opened in InfoPath, because you want to discourage users from opening or modifying the underlying form template in design mode.

Streamline forms-driven business processes

• Submit data to existing business systems When you design a browser-compatible form template, you can create data connections (data connection: The connection between an InfoPath form and an external data source, such as a database, Web service, SharePoint library, or XML file. Data connections are used to query and submit data.) to Web services or other external data sources. This allows you to submit data to existing business systems, enterprise applications, or corporate databases. For example, a sales department can design a form that can submit sales leads and customer information to an existing Customer Relationship Management (CRM) system.
• Query data from existing business systems It is also possible to query data in existing business systems, enterprise applications, or corporate databases. For example, when users open a form based on your form template, you might want data from an external data source to appear in the name and address fields on the form. This enables you to take advantage of existing organizational data and simplifies the process of filling out a form.
• Add workflow to forms You can add a workflow to the form template that is stored in a library. This enables you to consistently manage common business processes. For example, as a manager, you can use an approval workflow to route an expense report form through a list of approvers. Approvers can approve or reject the expense report form, reassign the approval task, or request changes to the form. In InfoPath, users click commands on the File menu to participate in the workflow. On the server, they can point to the name of the form in the library, click the arrow that appears, and then click Workflows to participate in the workflow.
  

Manage forms and form templates in a centralized location

• Store forms and form templates in a centralized location You can associate a form template with a library, which is a location on a SharePoint site where you can create, collect, update, and manage files with other people in your organization. When users fill out forms based on the form template in that library, the completed forms appear in the library along with key information from the forms themselves. Depending on how the SharePoint library is designed, users can fill out forms that are based on your form template, export the data from completed forms to Microsoft Office Excel, or merge the data from several forms into one form. The following example shows expense reports stored in a library.
  
• Use content types to manage form templates You can use the InfoPath Publishing Wizard to publish a form template as a site content type (content type: A reusable group of settings for a category of content. Use content types to manage the metadata, templates, and behaviors of items and documents consistently. Content types are defined at the site level and used on lists and libraries.). A content type defines a form template, a set of columns, and document management settings on the server, such as workflow or policy settings.
  By creating content types, you can reuse form templates and settings across a site collection (site collection: A set of Web sites on a virtual server that have the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more subsites.). In the past, if you wanted to use a form template in multiple SharePoint libraries, you had to publish two distinct copies of the form template, one for each library. If you wanted to update the form template, you had to change the form template in both places. However, now you can publish a form template as a site content type. When you update the content type, your change is automatically applied wherever that content type is used.
  You can assign a single content type to multiple libraries across a site collection or assign multiple content types to a single library. For example, you can add a content type for status report forms to all of the libraries that are used by the sales department in your company, so that each sales team is collecting and reporting the same type of information to management. Alternatively, suppose that your department uses different form templates for travel request, trip report, and expense report forms. You can publish the three form templates as site content types and add them to a single library used for storing team travel-related information. When people create a new form from the library, they can then select which of these form templates they want to use.
• Manage forms and form templates Server farm administrators can control how form templates are accessed by users and deployed throughout the organization. For example, they can control who can publish form templates throughout the site or decide how to upgrade form templates on the server with minimal impact to form users.
• Manage data connections in a central location If multiple form templates will use the same data connections (data connection: The connection between an InfoPath form and an external data source, such as a database, Web service, SharePoint library, or XML file. Data connections are used to query and submit data.), you can store the settings for that data connection in a data connection file (data connection file: A file that stores information about a connection to a data source, such as an Access database, a spreadsheet, or a text file, and that facilitates data source administration.) in a data connection library (data connection library: A document library, located on a site running Microsoft Office SharePoint Server 2007, that contains a collection of universal data connection (.udcx) and Office data connection (.odc) files.). When a user opens a form that connects to a data connection file, InfoPath uses the settings in that file to connect to the external data source. In this way, multiple form templates can use the same data connection file, so there is no need to manually create the same data connection for each form template. Moreover, if the location or connection settings for an external data source change, you don't need to update each form template that uses the data connection. Instead, you simply update the data connection file once, and all form templates continue to work as expected.