infopath

Wednesday, 23 February 2011

Sequential approval workflow in infopath 2007?

I designed a infopath form with 6 approvars based on dropdown selelection.if you select 2 approvers i shows 2 approvers only,After selecting approvers, form is submitted. then the form will be read only and approve ,reject buttons will appear based on user login .If the user is not a approver 1 the approve, reject buttons are disable.if the login user is approver 1 then buttons are visible to him then only he able approve or reject the form evary time the approval and rejected status is changes in the list and also mail will goes to requestor.anybody want this type of form design i will help you to design.

how to use infopath forms as a office documents?

This article discusses the benefits of using electronic forms instead of paper-based forms to collect data. It also contains some best practices for converting paper-based forms into Microsoft Office InfoPath form templates.

Note If your paper-based form was designed in Microsoft Office Word or Microsoft Office Excel, you can use the InfoPath Import Wizard to quickly convert the document or workbook into an InfoPath form template. If the form was created in another program, or if you can't access the original source file for the form, you will need to recreate the paper form from scratch in InfoPath.

In this article

Benefits of using electronic forms

There are many benefits to using electronic forms instead of paper-based forms. These benefits include the following:
Accurate, consistent data    With paper forms, people often write information in the wrong place or misinterpret instructions for filling out the form. Errors can also occur when an employee manually reenters the form data into a database or other program. Finding and fixing these types of data-entry errors can be costly and time-consuming. InfoPath includes a number of automated ways to help users avoid data-entry errors. For example, you can use formulas (formula: An XPath expression made up of values, fields or groups, functions, and operators. Formulas can be used to calculate mathematical values, display dates and times, and reference fields.) to automatically calculate mathematical values for users. You can also use conditional formatting (conditional formatting: The process of changing the appearance of a control, including its visibility and read-write state, based on values entered into the form.) to draw the user's attention to data, or enable the spelling checker so that users can check for spelling errors before submitting their forms. It is also possible to automatically fill in fields for users by using existing data from a database or other data storage system. For example, you can design a sales form that fills in employee information fields automatically after users enter their identification number in an Employee ID box.
Easy updates    If you need to update an existing form template, you can change it, republish it, and redistribute it to users. The update happens automatically the next time that users open a form that is based on your form template. If users are working offline when you publish an updated form template, the update occurs the next time that they connect to the network. Users typically won't notice that an update is occurring, although you can design your form template to alert users.
Workflow options    By taking advantage of the workflow features in InfoPath, you can increase the overall efficiency of common business processes in which the data is routed from one person to another. Workflows can reduce the cost and time required to coordinate business processes, such as project approval or document review, by managing and tracking the human tasks involved with these processes. For example, imagine a paper-based expense reporting process in which an employee fills out a printed expense report form, attaches a paper routing slip to the form, and then sends it through interoffice mail to his manager. After approving the report, the manager checks the box next to her name on the routing slip, and then sends the report to the accounting department through interoffice mail. If the accounting manager approves the report, then reimbursement checks are issued. Weeks could pass between the time that the initial report was submitted and when the employee received his reimbursement check. If you use InfoPath in conjunction with Microsoft Office SharePoint Server 2007, you can automate this type of workflow, which can save you substantial time and expense.
Integration with other systems    You can integrate form data from InfoPath with other products or technologies. For example, you can store form data in a Microsoft SQL Server database, or decide to base the design of your form template on a Web service so that you can submit data to a database that isn't directly supported by InfoPath. InfoPath works with many other programs and servers in the Microsoft Office system, including Microsoft Office Outlook, Microsoft Office Excel, and Microsoft Office Access. Among other things, you can design and fill out InfoPath forms in Outlook e-mail messages, export InfoPath data to Excel workbooks, submit InfoPath data to an Access database, or query data from a SharePoint list. In addition, developers can embed InfoPath controls into the custom business applications that are used in your company.
Added security    Paper forms are not necessarily secure. They can get misrouted or lost, which introduces a potential for the disclosure of sensitive information. The security model for InfoPath is related to the security zone and level settings in Windows Internet Explorer. These security features are designed to help protect users' forms and computers from unsafe operations, such as accessing or sending data to a source that is not trusted. InfoPath offers additional security measures, including protecting the design of a form template, using digital signatures (digital signature: An electronic, encryption-based stamp of authentication on a form or a section of a form. This signature confirms that the form or section originated from the signer and has not been altered.), managing certain form operations such as merging and submission, and trusting forms that are installed on user computers.

Top of Page

Best practices for converting paper forms

The following list describes some considerations to keep in mind when you convert paper forms to InfoPath form templates.

Use layout tables to organize sections of the form As with a paper form, you should organize an electronic form so that people who fill it out can move through the form in a logical manner. In InfoPath, you can use layout tables to organize controls, to separate one section from another, and to hold logos and other graphics. In addition, using layout tables gives you the added benefit of being able to easily align text boxes, check boxes, and other elements so that your form template looks professional and polished. In the following example, a layout table is used to organize text boxes inside a section (section: A control on a form that contains other controls.) on a form template.

Layout table inside section on form template

This layout table has two rows.

There are three columns in the second row. The center column is used only for spacing purposes.

Consider solutions for optional information Paper forms often contain sections that are reserved for specific categories of users. For example, at a hospital, a patient information form can contain a "For administrative use only" section that is intended to be filled out by nurses or other medical personnel and not by the patient. In InfoPath, there are a number of ways to accommodate this type of optional information. One of the best ways is to use an optional section, which is a control that contains other controls but does not appear on the form unless the user chooses to add it. For example, on a status report form template, you can include an optional Notes section. Users who want to add supplementary notes can insert and fill out this optional section. Everybody else can leave the section hidden.

You can also use conditional formatting (conditional formatting: The process of changing the appearance of a control, including its visibility and read-write state, based on values entered into the form.) to hide certain fields unless a specific condition is met in the form — for example, in an application form template, you can hide a certain set of fields until the user selects an 18 or older check box.

Use repeating tables instead of regular tables You can use repeating tables to save space and offer your users an extra degree of flexibility when they fill out your form. When you use repeating tables, your form template doesn't need to show numerous blank rows when the user first opens it. Instead, users typically see just one row and only add more when and if they need them.

Repeating table used to collect line items in expense report

Determine data needs Before you convert your paper form, you should decide what ultimately needs to happen to the data that users will enter into the electronic form. By thinking through your data needs up-front, before you convert your paper form, you can determine whether you possess the infrastructure necessary to create your form template. For example, if users need to be able to quickly send form data back and forth, and you don't need to reuse the data, then you may want to publish your form template as an e-mail message. You can then store user forms in an InfoPath Forms folder (InfoPath Forms folder: A folder in Outlook 2007 that stores a collection of related InfoPath 2007 forms. In the InfoPath Forms folder, you can use columns to group, filter, and sort data from multiple forms.) in your Inbox. If other people need to access and share the form data, then you may want to store collections of related InfoPath forms in libraries on a server running Microsoft Windows SharePoint Services. If users need to access the form data in other business applications or systems, such as expense reporting or accounting applications, then you may want to store the data in corporate databases. This is often accomplished by connecting the form template to a Web service, which serves as an intermediary between the form template and the database or business system.
Determine how many views that you need In InfoPath, you can create different views of the same form template. A view is an alternative way to present data in a form template. For example, if you are designing a permit application form template, you can use one view for the electrical contractor to fill out, another view for the receiving agent, and a third view for the investigator who approves or denies the application. By using views, you eliminate the need to design and maintain multiple forms for the same business process.
Determine what type of controls that you need If you created a paper form in a program such as Word, which really isn't intended for designing forms, you probably used text boxes, check boxes, buttons, and perhaps a few other controls. InfoPath offers more than 30 different controls that you can add to your form template. In addition to standard controls, such as text boxes and list boxes, InfoPath includes a number of new controls, such as repeating tables (repeating table: A control on a form that contains other controls in a table format and that repeats as needed. Users can insert multiple rows when filling out the form.), choice groups (choice group: A control that is used to present a set of mutually exclusive choices. By default, a choice group contains two choice sections, one of which appears to the user as the default choice in the form.), and optional sections. These types of controls let you design a flexible form template that accommodates your users. For example, in an expense report form template, you can use a repeating table to allow users to enter only as many expense items as they need.
Consider using template parts for common sets of controls If you have large numbers of paper forms to convert, you can look for common sections and sets of fields that can be turned into InfoPath template parts. A template part is a portion of a form template that can be saved for reuse in multiple form templates. A typical template part consists of controls and a 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.), and can also include features such as data connections, data validation, and rules (rule: A condition or action, or a set of conditions or actions, that automatically performs tasks based on events and values in the form.). By creating and using template parts, you can help ensure that the form templates in your organization are consistent in tone, structure, and behavior. For example, a human resources department can use a single Contact Information template part in all of its form templates.

Template part appearing in multiple forms

Enable digital signatures In InfoPath, you can configure your form template so that users can sign certain parts of a form or the entire form. Signing a form helps authenticate a user as the person who filled out the form and also helps ensure that the contents of the form were not altered.
Use features that help users fill out forms In InfoPath, you can assign default values to controls in order to help users fill out your forms faster. For example, in an expense report, you can assign today's date as the default value for a date picker control. You can assign formulas to Subtotal and Total fields so that expenses are automatically calculated as the user enters expense items. You can also enable spell checking so that users can check the text that they enter for spelling problems, just as they would in any other Microsoft Office document. And if you want to provide form-specific commands or Help content, you can create a custom task pane (custom task pane: An .html file whose content is displayed in a window next to a form. Custom task panes can provide form-specific commands and Help content.) that displays next to the form.

Office Marketplace options for converting paper forms

If your company has an especially large number of paper forms, you may want to consider using a third-party solution for converting your forms. You can search for these solutions on the Microsoft Office Marketplace, which lists products and services from third-party providers. Find links to more information about Office Marketplace in the See Also section.

how to backup and restore a sharepoint site collection?

BACKUP/RESTORE COMMANDS
For site collection backup
stsadm -o backup -url "URL name" -filename "file name" [-overwrite]
url -----A valid URL, such as http://server_name ------ URL of the site collection that you want to back up
filename ------ A valid file name for the site collection restore file, such as "Siteres.bak" ------- Name of the restore file (with path)
For site collection restore
stsadm -o restore -url <URL name> -filename <file name> [-hostheaderwebapplicationurl] <Web application URL> [-overwrite]
url -----A valid URL, such as http://server_name ------ URL of the site collection where you want to restore (should already exist)
filename ------ A valid file name for the site collection restore file, such as "Siteres.bak" ------- Name of the restore file (complete path of file created during backup)

How to create and deploy a basic Site Definition ?

How to create and deploy a basic Site Definition

A Site Definition provides the underlying structure of a site. It defines the site navigation, available features, document and list templates, initial lists and libraries, webparts available to a site when first created. Site Definitions provide a template for creating sites and can be re-used. Any change to the site definition is reflected across all the sites that are already created and those that shall be created in the future.
Site Definitions differ from site templates that are created by saving a site (non-publishing) as a site template using site settings menu options. Sites created using Site Definitions are ghosted or uncustomized while those created Site templates are un-ghosted or customized. Hence changes to site templates are not reflected in the site already created using them.
Let's have a look at the structural elements of a site definition.
Site definitions are located under 12\Template\SiteTemplates\ folder. It MAY contain following files: -

ONET.XML - located under Site Templates\xml or 2\TEMPLATE\GLOBAL\XML folder. This is the manifest file for the site definition. It is a required file and is used to specify available configurations for a site.
Default.aspx - located under SiteTemplates folder. This file defines the structure of the home page of site created using the site definition.
Default.master - located under 12\Template\Global. It is used by all site definitions.
Schema.xml - located under 12\TEMPLATE\GLOBAL\Lists. It is used to define the schema (fields) for lists and libraries.
STDVIEW.xml - located under 12\TEMPLATE\GLOBAL\XML. It defines view information for a site.
VWSTYLES.xml - located under 2\TEMPLATE\GLOBAL\XML. It defines view information for lists/libraries.

Now that we've had an overview of various files that constitute a site definition, let's create one basic Site Definition.

Go to 12\Template\Site Templates\ folder. Copy the folder named - STS and paste in a different work folder for custom-projects on your system.
Go to 12\TEMPLATE\1033\XML. Copy WEBTEMP.XML and paste it to the projects work folder created in step1.
Open Visual Studio 2005/2008. Create a new C# class library project named - SoftwareSiteDefinition. We'll create the following structure.
Create above folder structure without creating files. Once done, let's start adding files to them. Go to the folder copied in step 1. open the XML folder within it. Cut-paste ONET.XML file from it to Template\SiteTemplates\SoftwareSiteDefinition\xml\. Cut-paste default.aspx from copied folder in step 1 and paste under Template\SiteTemplates\SoftwareSiteDefinition\.
Now go to the work folder created in step 1. Rename the WEBTEMP.XML file to Webtemp_SoftwareSiteDefinition.xml. Cut-paste this file to Template\1033\XML\ folder in above solution (step 3).
Add a new xml file named - manifest.xml and a text file named- cab.ddf to DeploymentFiles folder. Once we've the files ready, let's start working on them.
Open the Webtemp_SoftwareSiteDefinition.xml file.
paste the below text: - <?xml version="1.0" encoding="utf-8"?>


<Templates xmlns:ows="Microsoft SharePoint">
<Template Name="SoftwareSiteDefinition" ID="11000">
    <Configuration ID="0"
      Title="Software Development Project Site" Hidden="FALSE" ImageUrl="/_layouts/images/stsprev.png"
      Description="A site for managing Software Development projects."
      DisplayCategory="My Custom Templates" >
    </Configuration>
</Template>
</Templates>
The name of the template is SoftwareSiteDefinition which should be unique in the 12\template\SiteTemplates folder. This would be the name of the Site definition folder created in above project. They should be identical and this is how the template file associates itself with its site definition.
The configuration element specifies the available configurations/variations within a site definition. There can be multiple configuration elements within Template element. Title attribute specifies the name of configuration as it appears on create new site page. DisplayCategory specifies the tab under which the configuration would be available. Specify a new unique name to create a new tab. Template ID specifies the unique id of site definition. Use values > 10000.
Now open the file - onet.xml from the solution project. We'll make some changes to this definition.
NavBars element is used to specify initial navigation as it appears on the site. One can specify the quick launch navigation as well as top navigation. Paste the below code for navigation. <NavBars>
        <NavBar Name="$Resources:core,category_Top;" Separator="&nbsp;&nbsp;&nbsp;" Body="<a ID='onettopnavbar#LABEL_ID#' href='#URL#' accesskey='J'>#LABEL#</a>" ID="1002"/>
        <NavBar Name="$Resources:core,category_Documents;" Prefix="<table border=0 cellpadding=4 cellspacing=0>" Body="<tr><td><table border=0 cellpadding=0 cellspacing=0><tr><td><img src='/_layouts/images/blank.gif' ID='100' alt='' border=0>&nbsp;</td><td valign=top><a ID=onetleftnavbar#LABEL_ID# href='#URL#'>#LABEL#</td></tr></table></td></tr>" Suffix="</table>" ID="1004"/>
        <NavBar Name="$Resources:core,category_Lists;" Prefix="<table border=0 cellpadding=4 cellspacing=0>" Body="<tr><td><table border=0 cellpadding=0 cellspacing=0><tr><td><img src='/_layouts/images/blank.gif' ID='100' alt='' border=0>&nbsp;</td><td valign=top><a ID=onetleftnavbar#LABEL_ID# href='#URL#'>#LABEL#</td></tr></table></td></tr>" Suffix="</table>" ID="1003"/>
        
        <NavBar Name="$Resources:core,category_Sites;" Prefix="<table border=0 cellpadding=4 cellspacing=0>" Body="<tr><td><table border=0 cellpadding=0 cellspacing=0><tr><td><img src='/_layouts/images/blank.gif' ID='100' alt='' border=0>&nbsp;</td><td valign=top><a ID=onetleftnavbar#LABEL_ID# href='#URL#'>#LABEL#</td></tr></table></td></tr>" Suffix="</table>" ID="1026"/>
        <NavBar Name="$Resources:core,category_People;" Prefix="<table border=0 cellpadding=4 cellspacing=0>" Body="<tr><td><table border=0 cellpadding=0 cellspacing=0><tr><td><img src='/_layouts/images/blank.gif' ID='100' alt='' border=0>&nbsp;</td><td valign=top><a ID=onetleftnavbar#LABEL_ID# href='#URL#'>#LABEL#</td></tr></table></td></tr>" Suffix="</table>" ID="1027"/>
    <NavBar Name="Quick Links" Prefix="<table border=0 cellpadding=4 cellspacing=0>" Body="<tr><td><table border=0 cellpadding=0 cellspacing=0><tr><td><img src='/_layouts/images/blank.gif' ID='100' alt='' border=0>&nbsp;</td><td valign=top><a ID=onetleftnavbar#LABEL_ID# href='#URL#'>#LABEL#</td></tr></table></td></tr>" Suffix="</table>" ID="1028">
      <NavBarLink Name="Google Chart" Url="http://code.google.com/apis/chart/" />
      <NavBarLink Name="Heather Solomon" Url="http://www.heathersolomon.com/blog/articles/MOSS07DesignComponents.aspx"/>
    </NavBar>
As we can see, I have commented the discussions link from quick launch, since I don't want this list to appear. I also don't want this list to be create by default ( this'll be taken care of in later sections). I have also added a new navigation heading named - Quick Links which has two hyperlinks.
Now go to the configuration section, remove all configurations but the one with ID=0. <Lists>
                <List FeatureId="00BFEA71-E717-4E80-AA17-D0C71B360101" Type="101" Title="$Resources:core,shareddocuments_Title;" Url="$Resources:core,shareddocuments_Folder;" QuickLaunchUrl="$Resources:core,shareddocuments_Folder;/Forms/AllItems.aspx"/>
                
                
                <List FeatureId="00BFEA71-2062-426C-90BF-714C59600103" Type="103" Title="$Resources:core,linksList;" Url="$Resources:core,lists_Folder;/$Resources:core,links_Folder;"/>
                <List FeatureId="00BFEA71-EC85-4903-972D-EBE475780106" Type="106" Title="$Resources:core,calendarList;" Url="$Resources:core,lists_Folder;/$Resources:core,calendar_Folder;" QuickLaunchUrl="$Resources:core,lists_Folder;/$Resources:core,calendar_Folder;/Calendar.aspx" EmailAlias="$Resources:core,calendar_EmailAlias;"/>
                <List FeatureId="00BFEA71-A83E-497E-9BA0-7A5C597D0107" Type="107" Title="$Resources:core,taskList;" Url="$Resources:core,lists_Folder;/$Resources:core,tasks_Folder;" QuickLaunchUrl="$Resources:core,lists_Folder;/$Resources:core,tasks_Folder;/AllItems.aspx"/>
            </Lists>
I have commented the discussions and announcement list section, since I don't want it to appear in the pre-created lists. Remember that if a list is not created initially, it's references should also be removed from quick launch navigation.
Remove all modules child elements of configuration element except the one named - Default. Now go to the Modules element which is a child element of Project and not configuration element. remove all modules except- Default. <Module Name="Default" Url="" Path="">
            <File Url="default.aspx" NavBarHome="True">
        <View List="$Resources:core,shareddocuments_Folder;" BaseViewID="0" WebPartZoneID="Top" WebPartOrder="2"/>
                
                <View List="$Resources:core,lists_Folder;/$Resources:core,calendar_Folder;" BaseViewID="0" RecurrenceRowset="TRUE" WebPartZoneID="Left" WebPartOrder="2"/>
                <AllUsersWebPart WebPartZoneID="Right" WebPartOrder="1"><![CDATA[
                   <WebPart xmlns="http://schemas.microsoft.com/WebPart/v2" xmlns:iwp="http://schemas.microsoft.com/WebPart/v2/Image">
                        <Assembly>Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>
                        <TypeName>Microsoft.SharePoint.WebPartPages.ImageWebPart</TypeName>
                        <FrameType>None</FrameType>
                        <Title>$Resources:wp_SiteImage;</Title>
                        <iwp:ImageLink>/_layouts/images/homepage.gif</iwp:ImageLink>
                        <iwp:AlternativeText>$Resources:core,sitelogo_wss;</iwp:AlternativeText>
                   </WebPart>
                   ]]></AllUsersWebPart>
                <View List="$Resources:core,lists_Folder;/$Resources:core,links_Folder;" BaseViewID="0" WebPartZoneID="Right" WebPartOrder="2"/>
                <NavBarPage Name="$Resources:core,nav_Home;" ID="1002" Position="Start"/>
                <NavBarPage Name="$Resources:core,nav_Home;" ID="0" Position="Start"/>
            </File>
        </Module>
This element will specify the views appearing on the home page and the navigations. Add a new view for - Shared Documents list. Ensure that the list is created in advance (step 15). Comment the announcement list view. Save the file.
Now open default.aspx from the project.
Add a new data row for containing a webpart zone which will span all the rows below. <table width="100%" cellpadding=0 cellspacing=0 style="padding: 5px 10px 10px 10px;">
          <tr>
           <td valign="top" width="100%" colspan="3">
               <WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly" ID="Top" Title="loc:Top" />
                
           </td>
           </tr>           <tr>
           <td valign="top" width="70%">
               <WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly" ID="Left" Title="loc:Left" />
                
           </td>
           <td> </td>
           <td valign="top" width="30%">
               <WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly" ID="Right" Title="loc:Right" />
                
           </td>
           <td> </td>
          </tr>
         </table>
        </td>
      </tr>
    </table>
Save the file.

Once the site definition is created, we need to create a deploy package for it.
Creating the WSP/solution package for Site definition

open manifest.xml and make following entries. <?xml version="1.0" encoding="utf-8" ?>
<Solution xmlns="http://schemas.microsoft.com/sharepoint/" SolutionId="0C07DA61-1542-4d49-BA09-2587B4125A63"
           DeploymentServerType="WebFrontEnd"
           ResetWebServer="False">
<SiteDefinitionManifests>
    
    <SiteDefinitionManifest Location="SoftwareSiteDefinition">
      
      <WebTempFile Location="1033\XML\Webtemp_SoftwareSiteDefinition.xml"/>
    </SiteDefinitionManifest>
</SiteDefinitionManifests>
</Solution>
Rt. click the file, select properties. Select the schema which should be WSS.xsd (xmlns=http://schemas.microsoft.com/sharepoint/) located in 12\template\xml.
This file specifies the name of associated files. SiteDefinitionManifest Location specifies the name of the root folder of site definition within the WSP package. WebTempFile Location specifies the location and name of the webtemp files within the WSP package. hence the path is relative to WSP and not 12 hive.
save the file and open cab.ddf. This is a diamond directive file.
Paste the following. ;****** this file packages the files from solution to WSP
.OPTION Explicit
.Set Cabinet=On
.Set CabinetNameTemplate=SoftwareSiteDefinition.wsp;****name of the wsp file
.Set CompressionType=MSZIP
.Set DiskDirectory1=MYWSP
.Set DiskDirectoryTemplate=CDROM
.Set UniqueFiles=Off
;*** include location of WSP manifest from root of the solution
DeploymentFiles\manifest.xml
;*** include locations of onet,default.aspx and webtemp
;*** create subfolder within the WSP
.Set DestinationDir=SoftwareSiteDefinition
Template\SiteTemplates\SoftwareSiteDefinition\default.aspx
.Set DestinationDir=SoftwareSiteDefinition\xml
Template\SiteTemplates\SoftwareSiteDefinition\xml\onet.xml
.Set DestinationDir=1033\XML
Template\1033\XML\Webtemp_SoftwareSiteDefinition.xml
We need to place all the necessary files from the solution project to the package so that they could be picked up by manifest.xml.
The package will have following structure: - Two folders with following hierarchies.
SoftwareSiteDefinition
1. default.aspx
2. xml
  1. onet.xml
1033
1. XML
  1. Webtemp_SoftwareSiteDefinition.xml
DeploymentFiles\manifest.xml
DestinationDir allows us to create subfolders within the package. The locations below it specify the actual location of all four files within the project solution. save the file
Go to command prompt. Browse to the root folder e.g. C:\SharepointCustomProjects\SoftwareSiteDefinition\SoftwareSiteDefinition.
un makecab /f DeploymentFiles\manifest.xml. This will create a package named - MYWSP under the root of the project which will contain a WSP cabinet file named - SoftwareSiteDefinition.wsp.

self signing Digital Signatures in Infopath form templates

For internally developed applications, we would not want to buy digital certificates and sign the InfoPath form templates using them. Hence comes the concept of self signing the form templates. However this has to be used strictly for testing purposes only.
1) Download the Microsoft Platform SDK for Windows Server 2003 R2 from Microsoft site.
2) Use the makecert utility located in the C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin folder.
makecert -sk <key file store location name> -n "CN=TestCertificate for Himani" certificate1.cer -ss my -pe
3) Now the certificate will be available in the “personal folder. You can use signtool.exe’s signwizard to sign the form template with this certificate. You need to select the certificate from the personal store and select the private key store location.

Tuesday, 22 February 2011

how to get current sharepoint site username or user email on page load using web service?

Any body want this answer .then comment it .i will give the answer about it?

Ask me about infopath?

post yor questions about infopath. I will give answers immediatly

Wednesday, 23 February 2011

Benefits of using electronic forms

Best practices for converting paper forms

Office Marketplace options for converting paper forms

Tuesday, 22 February 2011

Total Pageviews