Explore topic-wise InterviewSolutions in .

It WOULD REQUIRE the INFOPATH Client Application to be INSTALLED.

It would require the InfoPath Client Application to be installed.

The FEATURE called OFFICE SHAREPOINT Server Enterprise Site Collection Features must be activated WITHIN the site collection.

The feature called Office SharePoint Server Enterprise Site Collection Features must be activated within the site collection.

Session State Service mode [SQL Server database] is recommended for low bandwidth users, as the form view states hamper the performance for low bandwidth. Whereas, Form View can be used for environments with small groups of users.

The ADMINISTRATOR can also enter a VALUE for the session DATA size allowed for Form View State. InfoPath Form SERVICES will AUTOMATICALLY revert to Session State Service when session data size exceeds the value associated with the form view mode.

Session State Service mode [SQL Server database] is recommended for low bandwidth users, as the form view states hamper the performance for low bandwidth. Whereas, Form View can be used for environments with small groups of users.

The administrator can also enter a value for the session data size allowed for Form View State. InfoPath Form Services will automatically revert to Session State Service when session data size exceeds the value associated with the form view mode.

The InfoPath Form SERVICES can maintain DATA in TWO modes:

1. SQL Server database: This approach is TERMED as using Session State Services.
2. ASP.NET view states stored in the client side: Termed form view.

Points to be noted: The application needs to be associated with the SHARED Service Provider.

The InfoPath Form Services can maintain data in two modes:

Points to be noted: The application needs to be associated with the Shared Service Provider.

This page allows an Administrator to configure some of the BASIC settings for the InfoPath Form Services.

There are so many sections in the page, but the important of them are following:

1. User Browser-enabled form TEMPLATES
2. Data CONNECTION time out
3. HTTP data connections
4. Cross domain access for User Form Templates
5. Form session STATES
6. Etc…

This page allows an Administrator to configure some of the basic settings for the InfoPath Form Services.

There are so many sections in the page, but the important of them are following:

Quiescing is a process that TAKES the form templates offline gradually and PREVENTS new sessions from being created. It allows existing sessions to be completed, THEREBY PREVENTING data loss. When a form template is quiesced by the ADMINISTRATOR, the form templates from all the site collections are taken offline.

Quiescing is a process that takes the form templates offline gradually and prevents new sessions from being created. It allows existing sessions to be completed, thereby preventing data loss. When a form template is quiesced by the administrator, the form templates from all the site collections are taken offline.

This section allows the ADMINISTRATOR to perform the following ACTIONS:

1. Activate a form template to a SITE COLLECTION.
2. De-activate a form template from a site collection.
3. Quiesce a form template.
4. Remove a form template.

This section allows the administrator to perform the following actions:

There are five sections:

1. Manage Form TEMPLATES
2. Configure InfoPath Services
3. UPLOAD form templates
4. Manage DATA Connection FILES
5. Manage the Web Service PROXY

There are five sections:

The INFOPATH form services server-level configuration ELEMENTS are located in SHAREPOINT CENTRAL Administration.

The InfoPath form services server-level configuration elements are located in SharePoint Central Administration.

Logic INSPECTOR is a tool in InfoPath 2007 that shows all of the code DEPENDENCIES for the FORM in a single dialog. Depending on how you ACCESS the Logic Inspector, you initially SEE either the overview pane or both the overview pane and the details pane.

Logic Inspector is a tool in InfoPath 2007 that shows all of the code dependencies for the form in a single dialog. Depending on how you access the Logic Inspector, you initially see either the overview pane or both the overview pane and the details pane.

The InfoPath Form SERVICES consists of four components that are responsible for RENDERING the .xsn file on browsers:

1. ASP.NET MODULES: RETURN HTML to the browser.
2. Infopath Form Services HTTP Handlers: Forward requests from IIS to the page generator.
3. Converter: Responsible for converting the .xsn file into .aspx pages.
4. Page generator: Communicates with internal data sources, and is responsible for processing postback data from the browser and maintaining SESSION states.

The InfoPath Form Services consists of four components that are responsible for rendering the .xsn file on browsers:

An InfoPath form template is actually a CAB File containing different component files.

Below is a list of files which forms part of an InfoPath template.

• .xsf file: A manifest file that describes the basic definition of other form files.
• .xsl file: Defines the transformation for data into different views.
• .xsd file: Defines the data source schema.
• .dll file: Carries the custom logic built into .NET or COM.
• .htm and other RESOURCE files: Custom HTML resource files and other RESOURCES for the form.

When a form template is uploaded using Administrative deployment, the template is STORED in the content database of the SITE. Office Forms Services provide a server-runtime environment for InfoPath Forms Services. While running on the browser, all rules, validations, and calculations are executed in the browser using client-side script.

All business logic is executed on the server. So when a browser requests business logic execution, a post back is executed using low cost XMLHTTP. Formserver.aspx is an InfoPath Forms Services page that accesses the form’s data from the content database and renders it to the client.

An InfoPath form template is actually a CAB File containing different component files.

Below is a list of files which forms part of an InfoPath template.

When a form template is uploaded using Administrative deployment, the template is stored in the content database of the site. Office Forms Services provide a server-runtime environment for InfoPath Forms Services. While running on the browser, all rules, validations, and calculations are executed in the browser using client-side script.

All business logic is executed on the server. So when a browser requests business logic execution, a post back is executed using low cost XMLHTTP. Formserver.aspx is an InfoPath Forms Services page that accesses the form’s data from the content database and renders it to the client.

DATA is STORED in XML FILES.

Data is stored in XML files.

It is the FORM schema FILE of InfoPath. It determines the FORMAT of DATA that InfoPath recognizes.

It is the form schema file of InfoPath. It determines the format of data that InfoPath recognizes.

The .xsl file is the form view file that provides a way to REPRESENT different information, depending upon the runtime environment and other factors, including the security profile of end users. They are based on XML STYLESHEETS that can be formatted depending upon the condition. [CONDITIONAL formatting is itself an INBUILT property of XSL.]

The .xsl file is the form view file that provides a way to represent different information, depending upon the runtime environment and other factors, including the security profile of end users. They are based on XML stylesheets that can be formatted depending upon the condition. [Conditional formatting is itself an inbuilt property of XSL.]

The InfoPath form template (.xsn FILE) is actually a CAB file [can also be CONSIDERED a zip file] containing the DIFFERENT COMPONENT files of which InfoPath is built.

Following are some of the important files contained inside that CAB file:

1. ..XSF
2. ..xsl
3. ..xsd
4. ..dll
5. ..htm and other resource files.

The InfoPath form template (.xsn file) is actually a CAB file [can also be considered a zip file] containing the different component files of which InfoPath is built.

Following are some of the important files contained inside that CAB file:

Prior to the introduction of Office 2007, the InfoPath client application, like other Office products, had to be INSTALLED on every user’s computer.

In order to develop and use a form:

1. The form had to be designed using InfoPath.
2. The resulting form template should be hosted in a network file share, or installed in individual user machines, or uploaded into a form library in SharePoint, from where users could fill the forms.
3. Filling up forms required InfoPath to be installed on the client machine.
4. Developing a connected InfoPath was complicated for end users.
5. Developers did not have an integrated development platform.
6. The product did not integrate with other Office products such as Word and Excel.

Benefits of Office 2007

This introduced a new server-side runtime to host InfoPath forms known as InfoPath Form Services.

The new capabilities include:

1. Ability to convert Word and Excel documents into InfoPath form templates.
2. With the help of InfoPath form services, a InfoPath form can be browser ENABLED.
3. The new InfoPath forms can be embedded in Outlook.
4. The form can be built once and rendered in different modes and devices, .i.e., Design Once.
5. Introduction of the DOCUMENT information panel. I.e., an InfoPath form that is hosted INSIDE Word 2007 or PowerPoint 2007 can be used to edit document properties.
6. Introduction of logic inspector. The components which provide visual view of all the rules embedded in the form.
7. The new InfoPath forms can be published to content types.
8. Introduction of template parts, i.e., reusable code sections.
9. Introduction of an integrated development environment inside Visual Studio 2005 using Visual Studio TOOLS for Office.
10. The information right management can be used to protect sensitive data in the form.

Prior to the introduction of Office 2007, the InfoPath client application, like other Office products, had to be installed on every user’s computer.

In order to develop and use a form:

Benefits of Office 2007

This introduced a new server-side runtime to host InfoPath forms known as InfoPath Form Services.

The new capabilities include:

InfoPath is an XML BASED electronic FORMS DEVELOPMENT PRODUCT.

InfoPath is an XML based electronic forms development product.