Want to Turn Email to SharePoint Documents?

The company is releasing a solution today that it claims can transform email to searchable documents that can be managed in SharePoint.

Breaking Silos

It's a simple solution, David Lavenda, product manager at Harmon.ie told CMSWire. Instead of separate repositories for email and document management  – in this case Exchange and SharePoint — you turn email into documents and store them in SharePoint. That makes them easier to find and better for collaboration, he said.
“We've made it super easy to upload those Exchange email messages to SharePoint, automate the classification by taking the information in the headers and converting the messages into SharePoint columns,” he continued.

The single, central document repository makes it easier for organizations to manage both records and clients, as well as retaining critical knowledge.
It turns email into a more effective business tool, he said.
“Historically email was this almost real time communication tool that was different from documents. Over the years document creation applications and email applications have grown in parallel. Today it makes no sense to ask people who are already struggling across many different business initiatives to manage email as separate elements,” he said.

Where Microsoft Left Off

While Office 365 pulled together multiple Microsoft applications, including Exchange and SharePoint, it stopped short of connection the applications.
Office 365 offers a unified browser with tiles that allow you to switch between windows (like Exchange and SharePoint). But Lavenda contended, "At a very basic level you still have two user experiences. You have one product for email, you have one product for documents."
"There’s no way of searching, there’s no metadata and it doesn’t do anything to solve that problem of finding your information quickly.”
Harmon.ie's solution lets users drag and drop email from their Outlook window to a corporate SharePoint or Office 365 site, without exiting their email client.

How We Love to Hate Email

Despite what seems like nonstop complaints about email, it's use keeps growing, studies show.
"Email is certainly not going away in the Microsoft world. And IBM is talking about another generation of Verse and Google has its new Inbox,” Lavenda noted.
“The debate has changed. Now it is about whether email is the center of the universe with other things getting pulled in — which I think is the Microsoft, IBM and Google view of the world — or whether email is part of something larger. I think the latter is harder to do, but I think that’s the solution.”

Interview Questions and FAQ For InfoPath

Q.	What is InfoPath
A.	Office InfoPath 2007 is office Toll that help to design User Interface Form for Submitting and accessing data It can help you efficiently gather information through rich, dynamic forms. The information collected can easily be reused throughout organizations and across business processes because Office InfoPath 2007 supports industry-standard XML using any customer-defined schema. Office InfoPath 2007 customers who share information across their organizations and business processes can have greater business impact. Processed
Q.	What does Office InfoPath 2007 provide?
A.	Office InfoPath 2007 provides you with an easy and efficient way to create rich, flexible forms. In addition, Office InfoPath 2007 provides a user-friendly interface for entering information into these forms and automatically updates the data in XML format. Ready-to-use sample forms in Office InfoPath 2007 provide templates for common usage scenarios. Extend the power of Office InfoPath 2007 to browser-based environments by integrating it with Microsoft Office Forms Services. Q.Who is Office nfoPath 2007 designed for?
	Office InfoPath 2007 was developed for teams and organizations that need to collect and use information. Office InfoPath 2007 is valuable to any business, IT professional, or organization that needs an efficient and flexible way to collect information that can be standardized, validated, and integrated with an organization’s server systems.

• Take advantage of existing IT investments and knowledge to ease deployment costs.
What are some of the typical ways teams and organizations might use Office InfoPath 2007?
A. Office InfoPath 2007 can be applied to many different scenarios, either within organizations and workgroups, or across suppliers and partners. Using Office InfoPath 2007:
• A division manager can design and implement a performance appraisal system.
• A company can implement a timecard or expense reporting system.
• A health insurance company can create and implement its forms, and then integrate them into its database system and with the business processes of member hospitals.
• A team or workgroup can submit weekly status reports.
Pricing and Ordering

Q.	How much does Office InfoPath 2007 cost?
A.	Find pricing and licensing information on the 2007 Microsoft Office System Pricing page.

Will Office InfoPath 2007 be included with the 2007 Microsoft Office release?

A.

Yes. Office Infopath 2007 comes with EnterPrise Edition of Microsoft Office, Find packaging information on the 2007 Microsoft Office Packaging page. . How does Office InfoPath 2007 fit in with other Microsoft Office system programs? A. The Microsoft Office system provides customers with a set of programs that they can choose from to best address their business needs. Office InfoPath 2007 can be used as the interface to help gather information more effectively. Microsoft Office Excel 2007 is a spreadsheet program that can help you analyze numerical data. Microsoft Office Word 2007 provides word-processing capabilities for documents. Microsoft Office Access 2007 is a database management program for storing information and creating reports. Use Microsoft Office PowerPoint 2007 to graphically present information. Integration and Compatibility Q. What are the system requirements for Office InfoPath 2007? A. See the system requirements for Office InfoPath 2007. Q. How does Office InfoPath 2007 work with existing servers and databases? A. Office InfoPath 2007 works with any XML-enabled database or server by providing support for Web services and database interoperability. Q. What is XML and what does it have to do with Office InfoPath 2007? A. XML is an open, industry-standard language for organizing and storing data. Having data in XML means that the information is transportable and can be easily shared and reused.The default file format for Office InfoPath 2007 is XML, and InfoPath 2007 supports any customer-defined schema, which means that information gathered using InfoPath forms more easily integrates with server systems. Using Office InfoPath 2007 to gather information can improve the flow of information throughout the organization. Office InfoPath 2007 is a great example of how Microsoft Office system programs take advantage of XML technology to help people, teams, and organizations manage and use information more productively. Q. How does Office InfoPath 2007 relate to Microsoft .NET connection software? A. Microsoft .NET is a set of software technologies for connecting people, systems, information, and devices. It is built on a foundation of XML Web services, so that new and existing applications can connect with software and services across operating systems, programs, and programming languages. Office InfoPath 2007 works well as a client for Web services because it was built to work with XML and can help customers connect information with business processes and solutions. Q. What are the advantages of having Office InfoPath 2007 as a rich client application? A. Office InfoPath 2007 provides powerful functionality such as business logic validation, rich text formatting, AutoCorrect, and spelling checker.

What are browser-compatible forms?
Browser-Compatible forms are open in Browser, there is no need of InfoPath Installed on Client machine if your InfoPath form is designed as Browser Compatible design InfoPath 2007 introduced the possibility to fill out InfoPath forms by using a browser such as Internet Explorer, Firefox, Netscape, or Safari. These types of forms are called InfoPath 2007 browser-compatible forms. For a complete list of browsers that can be used to fill out InfoPath form.
Can I use browser-compatible forms without installing Microsoft Office SharePoint Server 2007 (MOSS)?
Yes, you can, but you will have to install Forms Server to be able to run browser-compatible forms. On your SharePoint site, there must be feature Office Publishing Infrastructure activated.
What is Forms Server?
Forms Server is the extracted version of Forms Services that comes with Microsoft Office SharePoint Server 2007 (MOSS). It is sold and can be used separately from MOSS to run and fill out InfoPath 2007 browser-compatible forms.
How do I make InfoPath 2007 forms compatible with InfoPath 2003?
Open the form template that you want to save in InfoPath 2003 format.
On the File menu, click Save As.
In the Save as type list, click InfoPath 2003 Form Template.
Click Save.
In C# code:
XPathNavigator nav = MainDataSource.CreateNavigator(); // xPathNavigator is Class is used to walk in DataSource of your Infopath Form
string fieldValue = nav.SelectSingleNode(“//my:field1″, NamespaceManager).Value; // Here “//my:field1″ is the XPath of your Field in Infopath Form you can get by Tool Pane – DataSource , select Field, RightClick and Choose CopyXPath.
In VB.NET code:
Dim nav As XPathNavigator = MainDataSource.CreateNavigator()
Dim fieldValue As String = nav.SelectSingleNode(“//my:field1″, NamespaceManager).Value
How do I set the value of an InfoPath field through code?
In C# code:
XPathNavigator nav = MainDataSource.CreateNavigator();
nav.SelectSingleNode(“//my:field1″, NamespaceManager).SetValue(“myValue”);
In VB.NET code:
Dim nav As XPathNavigator = MainDataSource.CreateNavigator()
nav.SelectSingleNode(“//my:field1″, NamespaceManager).SetValue(“myValue”)
How do I call a web service through code?
In C# code:
First we need to create the Connection with Given web Service then we write the following Code here I take the example of HelloWorld Name of our DataConnection with our Given webService.
// Create an XPathNavigator object to navigate the secondary data source of the web service
XPathNavigator nav = DataSources["HelloWorld"].CreateNavigator();
// Set the value of the parameter to pass to the web service
nav.SelectSingleNode(“//dfs:queryFields/tns:HelloWorld/tns:name”, NamespaceManager).SetValue(“myValue”);
// Call the web service
DataSources["HelloWorld"].QueryConnection.Execute();
// Retrieve the results returned by the web service
string results = nav.SelectSingleNode(“//dfs:dataFields/tns:HelloWorldResponse/tns:HelloWorldResult”, NamespaceManager).Value;
where HelloWorld is the name of a data connection to a web service.
In VB.NET code:
‘ Create an XPathNavigator object to navigate the data source of the web service
Dim nav As XPathNavigator = DataSources(“HelloWorld”).CreateNavigator()
‘ Set the value of the parameter to pass to the web service
nav.SelectSingleNode(“//dfs:queryFields/tns:HelloWorld/tns:name”, NamespaceManager).SetValue(“myValue”)
‘ Call the web service
DataSources(“HelloWorld”).QueryConnection.Execute()
‘ Retrieve the results returned by the web service
Dim results As String = nav.SelectSingleNode(“//dfs:dataFields/tns:HelloWorldResponse/tns:HelloWorldResult”, NamespaceManager).Value
Where HelloWorld is the name of a data connection to a web service.
Date and time basics in Microsoft Office InfoPath
Problem with date Field in InfoPath Form
You want to filter data on the current month, display the date in a way that is not available in Microsoft Office InfoPath, or perform calculations with dates.
Solution
Use the fact that Microsoft Office InfoPath represents dates and times internally as YYYY-MM-DDThh:mm:ss to be able to filter, display, and perform calculations with dates and times within InfoPath.
Discussion
InfoPath comes with 3 date/time data types:
1. Date (date)
2. Time (time)
3. Date and Time (dateTime)
The following table lists the corresponding internal representations InfoPath uses for each data type:
Data Type Internal InfoPath Representation
Date (date) YYYY-MM-DD
Time (time) hh:mm:ss
Date and Time (dateTime) YYYY-MM-DDThh:mm:ss
InfoPath uses the format you set on a date/time field through the Properties dialog box of the field and the Format… button to display dates and times. InfoPath will show dates/times in any way you have indicated, like e.g. 9:46 P.M., 21:46, 2/19/2006, or 19-02-2006. Keep in mind that this is only a visual display. When InfoPath performs validation on date and time fields, it still uses its own internal date and time representations.

Interview Questions in SharePoint InfoPath

Interview Questions in SharePoint InfoPath

>What is an InfoPath?InfoPath is an XML based electronic forms development product.

What are the benefits of InfoPath 2007?
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 didn’t have an integrated development platform.
6.The product didn’t 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.

>What is the structure of an InfoPath form template?
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.

>What is a .xsf file? Or what is the Form Definition file [XSF file]? Or what is a manifest.xsf file?
It’s a manifest file that provides the basic definition of other form files. This file contains XML code that describes all aspects of a form. The .xsf file is automatically created by InfoPath when a new form template is created and saved in Design mode. As form designers and developers change the form template or add new features to it, InfoPath updates the .xsf file to reflect those changes.

Note: The .xsf file can also be modified directly by using any text or XML editor, such as Microsoft Notepad. However, care should be taken when making modifications to the .xsf file: if an invalid entry is made, the form that the file is associated with may be left in an unusable state. However, some customizations can be made to the .xsf file that cannot be generated in Design mode.

The .xsf file is the core file of an InfoPath form because it contains information about the form as a whole. Some of the data it contains includes processing metadata, user interface customizations, schema definitions, views, business logic declarations, event handlers, and deployment information.

The following are some of the items that the .xsf file contains:

•A unique identifier for the form
•Global metadata information about the form, including deployment and publishing information
•The XML schema definitions for the XML document that the form produces
•Definition of views and their associated user interface components (menus, toolbars, and buttons)
•Definition of editing actions that are made available using user interface components, and how their availability will be determined contextually
•Workflow and routing information
•Event handlers, data validation, and business logic that is associated with individual XML nodes of the form’s underlying XML document, or with the XML document itself
•Event handlers associated with the form as a whole
•Packaging information about all of the files contained within the form template
The .xsf file is based on the xsf namespace. Its root element is the xDocumentClass element.

 
<?xml version=”1.0″ encoding=”UTF-8″?>
<!–
This file is automatically created and modified by Microsoft Office InfoPath.
Changes made to the file outside of InfoPath might be lost if the form template
is modified in InfoPath.
–>
<xsf:xDocumentClass trustSetting=”automatic” solutionFormatVersion=”2.0.0.0″ 
   dataFormSolution=”yes” solutionVersion=”1.0.0.6″ productVersion=”12.0.0″
   publishUrl=”" 
   name=”urn:schemas-microsoft-com:office:infopath:Unpacked:-dataFormSolution”
   xmlns:xsf=”http://schemas.microsoft.com/office/infopath/2003/solutionDefinition“ 
       xmlns:xsf2=”http://schemas.microsoft.com/office/
                   infopath/2006/solutionDefinition/extensions” 
       xmlns:msxsl=”urn:schemas-microsoft-com:xslt” 
       xmlns:xd=”http://schemas.microsoft.com/office/infopath/2003“ 
       xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“ 
       xmlns:xdUtil=”http://schemas.microsoft.com/office/infopath/2003/xslt/Util“ 
       xmlns:xdXDocument=”http://schemas.microsoft.com/office/infopath/2003/xslt/xDocument“ 
       xmlns:xdMath=”http://schemas.microsoft.com/office/infopath/2003/xslt/Math“ 
       xmlns:xdDate=”http://schemas.microsoft.com/office/infopath/2003/xslt/Date“ 
       xmlns:xdExtension= xmlns:xdEnvironment= 
          “http://schemas.microsoft.com/office/infopath/2006/xslt/environment“ 
       xmlns:xdUser=”http://schemas.microsoft.com/office/infopath/2006/xslt/User“ 
       xmlns:q=”http://schemas.microsoft.com/office/infopath/2003/ado/queryFields“ 
       xmlns:d=”http://schemas.microsoft.com/office/infopath/2003/ado/dataFields“ 
       xmlns:dfs=”http://schemas.microsoft.com/office/infopath/2003/dataFormSolution“ 
       xmlns:my=”http://schemas.microsoft.com/office/infopath/2003/myXSD/2007-03-19T15:02:59“ 
       xmlns:xdado=”http://schemas.microsoft.com/office/infopath/2003/adomapping“>
  <xsf:package>
    <xsf:files>
      <xsf:file name=”schema.xsd”>
        <xsf:fileProperties>
          <xsf:property name=”editability” 
             type=”string” value=”none”></xsf:property>
          <xsf:property name=”namespace” type=”string” 
             value=”http://schemas.microsoft.com/office/infopath/
                    2003/dataFormSolution”></xsf:property>
          <xsf:property name=”rootElement” type=”string” 
                value=”myFields”></xsf:property>
          <xsf:property name=”useOnDemandAlgorithm” 
             type=”string” value=”yes”></xsf:property>
        </xsf:fileProperties>
      </xsf:file>
      <xsf:file name=”schema1.xsd”>
        <xsf:fileProperties>
          <xsf:property name=”namespace” type=”string” 
             value=”http://schemas.microsoft.com/office/infopath/2003/ado/dataFields“>
          </xsf:property>
          <xsf:property name=”editability” type=”string” 
                  value=”none”></xsf:property>
        </xsf:fileProperties>
      </xsf:file>
      <xsf:file name=”schema2.xsd”>
        <xsf:fileProperties>
          <xsf:property name=”namespace” type=”string” 
             value=”http://schemas.microsoft.com/office/infopath/2003/ado/queryFields“>
          </xsf:property>
          <xsf:property name=”editability” type=”string” 
             value=”none”></xsf:property>
        </xsf:fileProperties>
      </xsf:file>
      <xsf:file name=”template.xml”></xsf:file>
      <xsf:file name=”sampledata.xml”>
        <xsf:fileProperties>
          <xsf:property name=”fileType” type=”string” 
                      value=”sampleData”></xsf:property>
        </xsf:fileProperties>
      </xsf:file>
      <xsf:file name=”view1.xsl”>
        <xsf:fileProperties>
          <xsf:property name=”lang” type=”string” value=”1033″></xsf:property>
          <xsf:property name=”queryView” type=”string” value=”yes”></xsf:property>
          <xsf:property name=”componentId” type=”string” value=”12″></xsf:property>
          <xsf:property name=”xmlToEditName” type=”string” value=”12″></xsf:property>
          <xsf:property name=”mode” type=”string” value=”1″></xsf:property>
        </xsf:fileProperties>
      </xsf:file>
    </xsf:files>
  </xsf:package>
  <xsf:importParameters enabled=”yes”></xsf:importParameters>
  <xsf:extensions>
    <xsf:extension name=”SolutionDefinitionExtensions”>
      <xsf2:solutionDefinition runtimeCompatibility=”client server” 
                   allowClientOnlyCode=”no”>
        <xsf2:offline openIfQueryFails=”yes” cacheQueries=”yes”></xsf2:offline>
        <xsf2:server isPreSubmitPostBackEnabled=”no” isMobileEnabled=”no” 
                   formLocale=”en-US”></xsf2:server>
      </xsf2:solutionDefinition>
    </xsf:extension>
  </xsf:extensions>
  <xsf:views default=”View 1″>
    <xsf:view name=”View 1″ caption=”View 1″>
      <xsf:mainpane transform=”view1.xsl”></xsf:mainpane>
      <xsf:editing>
        <xsf:xmlToEdit name=”DimCustomer_7″ 
              item=”/dfs:myFields/dfs:dataFields/d:DimCustomer” 
              container=”/dfs:myFields”>
          <xsf:editWith caption=”DimCustomer” 
                  xd:autogeneration=”template” component=”xCollection”>
            <xsf:fragmentToInsert>
              <xsf:chooseFragment parent=”dfs:dataFields” innerFragment=”d:DimCustomer”>
                <d:DimCustomer CustomerKey=”" Title=”" 
                     FirstName=”" MiddleName=”" LastName=”" 
                     BirthDate=”" MaritalStatus=”" 
                     Suffix=”" Gender=”" EmailAddress=”" 
                     AddressLine1=”" AddressLine2=”"></d:DimCustomer>
              </xsf:chooseFragment>
            </xsf:fragmentToInsert>
          </xsf:editWith>
        </xsf:xmlToEdit>
      </xsf:editing>
      <xsf:menuArea name=”msoInsertMenu”>
        <xsf:menu caption=”&amp;Section”>
          <xsf:button action=”xCollection::insert” 
             xmlToEdit=”DimCustomer_7″ caption=”DimCustomer”></xsf:button>
        </xsf:menu>
      </xsf:menuArea>
      <xsf:menuArea name=”msoStructuralEditingContextMenu”>
        <xsf:button action=”xCollection::insertBefore” xmlToEdit=”DimCustomer_7″ 
              caption=”Insert DimCustomer before” showIf=”immediate”></xsf:button>
        <xsf:button action=”xCollection::insertAfter” xmlToEdit=”DimCustomer_7″ 
              caption=”Insert DimCustomer after” showIf=”immediate”></xsf:button>
        <xsf:button action=”xCollection::remove” xmlToEdit=”DimCustomer_7″ 
              caption=”Remove DimCustomer” showIf=”immediate”></xsf:button>
        <xsf:button action=”xCollection::insert” xmlToEdit=”DimCustomer_7″ 
              caption=”Insert DimCustomer” showIf=”immediate”></xsf:button>
      </xsf:menuArea>
    </xsf:view>
  </xsf:views>
  <xsf:applicationParameters application=”InfoPath Design Mode”>
    <xsf:solutionProperties 
      fullyEditableNamespace=”http://schemas.microsoft.com/office/
                              infopath/2003/myXSD/2007-03-19T15:02:59″ 
      lastOpenView=”view1.xsl” 
      lastVersionNeedingTransform=”1.0.0.3″></xsf:solutionProperties>
  </xsf:applicationParameters>
  <xsf:documentSchemas>
    <xsf:documentSchema rootSchema=”yes” 
       location=”http://schemas.microsoft.com/office/infopath/2003/
                 dataFormSolution schema.xsd”></xsf:documentSchema>
    <xsf:documentSchema 
       location=”http://schemas.microsoft.com/office/infopath/2003/ado/
                 dataFields schema1.xsd”></xsf:documentSchema>
    <xsf:documentSchema 
       location=”http://schemas.microsoft.com/office/infopath/2003/ado/
                 queryFields schema2.xsd”></xsf:documentSchema>
  </xsf:documentSchemas>
  <xsf:fileNew>
    <xsf:initialXmlDocument caption=”Unpacked” 
       href=”template.xml”></xsf:initialXmlDocument>
  </xsf:fileNew>
  <xsf:query>
    <xsf:adoAdapter connectionString=”Provider=SQLOLEDB.1;Integrated Security=SSPI;
                           Persist Security Info=True;Initial Catalog=AdventureWorksDW;
                           Data Source=[Source];Use Procedure for Prepare=1;
                           Auto Translate=True;Packet Size=4096;Workstation ID=[ID];
                           Use Encryption for Data=False;
                           Tag with column collation when possible=False” 
           commandText=”select &quot;CustomerKey&quot;,&quot;Title&quot;, 
                        &quot;FirstName&quot;,&quot;MiddleName&quot;,
                        &quot;LastName&quot;,&quot;BirthDate&quot;,
                        &quot;MaritalStatus&quot;,&quot;Suffix&quot;,
                        &quot;Gender&quot;,&quot;EmailAddress&quot;,
                        &quot;AddressLine1&quot;,&quot;AddressLine2&quot; 
                        from &quot;dbo&quot;.&quot;DimCustomer&quot; 
                        as &quot;DimCustomer&quot;” 
           queryAllowed=”yes” name=”Main connection” 
           submitAllowed=”no”></xsf:adoAdapter>
  </xsf:query>
</xsf:xDocumentClass>

The xsf:extensions element is used to bind the form to other platforms, like SharePoint.

>What are the Form View files in InfoPath? Or XSL files?
The .xsl file is the form view file that provide 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.]

>What is an .XSD file in InfoPath?
It is the form schema file of InfoPath. It determines the format of data that InfoPath recognizes.

>Where does data get stored in an InfoPath form?
Data is stored in XML files.

>Explain in brief the architecture of InfoPath forms?
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 postback is executed using low cost XMLHTTP. FormsServer.aspx is an Infopath Forms Services page that accesses the form’s data from the content database and renders it to the client.

>What are the main components of InfoPath Form Services that are responsible for rendering the .xsn file on browsers?
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 HTTPHandlers: 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.

>What are the steps to create a Template Part?
In the Design a Form dialog box, you can choose to design a template part instead of a form template. If you do this, InfoPath features that aren’t supported in template parts are either hidden or disabled so that you aren’t tempted to use them in your template part.

1.On the File menu, click Design a Form Template.
2.In the Design a Form Template dialog box, click Template Part.
3.In the Based on gallery, do one of the following:
?To define the data source (Data source: the collection of fields and groups that define and store the data for an InfoPath form. Controls in the form are bound to the fields and groups in the data source.), as you design the template part, click Blank.
?To use an XML document (.xml) file or an XML schema (XML schema: A formal specification, written in XML, that defines the structure of an XML document, including element names and rich data types, which elements can appear in combination, and which attributes are available for each element.) (.xsd) file as the data source for the template part, click XML or Schema.
Note: If you base your template part on an XML document or XML schema, InfoPath populates the Data Source task pane with fields (field: an element or attribute in the data source that can contain data; if the field is an element, it can contain attribute fields; fields store data that is entered into controls) and groups (group: an element in the data source that can contain fields and other groups; controls that contain other controls, such as repeating tables and sections, are bound to groups) that map to XML elements (XML element: an XML structure that consists of a start tag, an end tag, and the information between the tags; elements can have attributes and can contain other elements) in the document or schema. The data source is locked. Depending on the document or schema, you might not be able to add new fields or groups to part or all of the data source, or to change certain aspects of existing fields and groups.

?To make your template part compatible with InfoPath Forms Services, select the Enable browser-compatible features only check box.
?Click OK.
A new template part opens in InfoPath.

?Design your template part.
?When you finish designing the template part, on the File menu, click Save.
How to reuse Template Parts
If you want to base the design of a new template part on an existing template part, you must open the existing template part, change its name in the Template Part Properties dialog box, and then save the new template part with another, distinguishing file name. When you change the template part name in the Template Part Properties dialog box, the template part ID is updated automatically. This ID further distinguishes one template part from another.

1.On the File menu, click Design a Form Template.
2.Under Open a form template in the Design a Form Template dialog box, click On My Computer.
3.In the Files of type list, click InfoPath Template Parts.
4.Browse to and click the template part that you want to open, and then click Open.
5.On the File menu, click Properties.
6.In the Template Part Properties dialog box, enter a new name in the Template part name box.
When you do this, the identifying text in the Template part ID box reflects the new name. The template part ID is generated automatically by InfoPath. It must be unique for each new template part that you create.

7.On the File menu, click Save As, and enter a new file name for the template part.
What is Document Information Panel?
When you create a document with Office Word 2007, Office Excel 2007, or Office PowerPoint 2007, a Document Information Panel is created for you automatically. This default Document Information Panel includes standard properties, such as Author, Title, and Subject. Alternatively, you can add custom properties by designing a Document Information Panel from scratch and then associating it with a document, or by customizing an existing Document Information Panel.

A document information panel is a form that is displayed within the client application, and which contains fields for the document metadata. Document information panels enable users to enter important metadata about a file anytime they want, without having to leave the Microsoft Office system client application.

>How many sections are there inside the InfoPath Form Services element?
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

>How is form session state maintained?
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.

>When to use which session state 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.

Using List Templates in SharePoint 2013

Summary : Using List Templates in SharePoint 2013,Create List Templates in SharePoint 2013, Save List as Template in SharePoint 2013,How to Save List as Template in SharePoint 2013
There is a lot of confusion about “Add an App for SharePoint” and Creating a new Conventional Custom List.Its the same thing! Last week one of my colleagues asked me that how do they create a new Custom List in SharePoint 2013. I replied Simply select “Add an App” in “View all Site Content” or in the Settings menu.He immediately popped another question about how to then create a List form a List Template.The answer is simple again using “Add an App”.A lot of new users has this confusion so I am writing this post about how to Create a new List from a List Template (Custom List template and User Saved list template)

How to Create a new List using “Custom List Template ” or “a manually saved List Template” in SharePoint 2013 –

Quick Steps –
1. Navigate to Site and Click on “Settings” wheel.Click on “Add an app” or go to “View All site Content” and then click “Add an App”.


or


Select “Custom List” from the “Your Apps” page.



Give the name of the List in the Popup and click Create.



and here is the new list in the Site Contents page



Next we will look at how to Create list from List Template
Save List as Template
So lets see how to save a list as a Template.Navigate to the List and under “List” tab in Ribbon click “List settings”.



I have a “New Custom List” which we will save as a Template.



Next it will take you to Confirmation page with a link to List Template Gallery.You can verify if the template is in the list template gallery but not required.



Once this is done go back to the Step 1 of “Add an App” or go to “View all site content” where you will find this new template.Click the Template and give it a name to create a list out of it.

CREATE AND CUSTOMIZE PAGES ON YOUR PUBLIC WEBSITE

Your public website in Office 365 includes web pages that you can customize by adding your own
page content, including text, images, videos, and apps. This course teaches you how to add and
customize pages, manage pages, and create and manage blog posts.
ADD A PAGE
1. From anywhere within your public website click
Page!New.

Give the page a name and click Create.
Click Format Text ! Save to save the draft.
EDIT A PAGE
1. Navigate to the page on your public website that
you want to edit.
2. Click the Page tab and choose Edit.

 

UPLOAD AN IMAGE FROM YOUR COMPUTER
1. Navigate to the page on your public website where
you want to add an image.
2. Click Insert!Picture!From Computer!Browse.
3. Select the desired picture and click Open.
HIDE LINKS IN THE NAVIGATION
1. From within the navigation on your public website,
click Edit Links.
2. Click the Hide icon.
3. Click Save.
DELETE A PAGE
1. Navigate to the page on your public website that
you want to delete.
2. Click Page ! Delete Page.
3. Click OK to confirm.

 CREATE NEW BLOG POSTS USING THE BLOG
POST EDITOR
1. Click the BLOG link on your website.
2. Under Blog tools, click Create a post.
3. Enter a title and body content, including text,
images, videos, etc.
4. Select a category and publishing date.
5. Click Publish.

 

CREATE NEW BLOG POSTS WITH MICROSOFT
WORD
1. Click the Blog link on your website.
2. Under Blog tools, click Launch blogging app.
Register the blog account if prompted.
3. Click the Blog Post tab and choose Publish.