InfoPath?
InfoPath is based on industry-standard Extensible Markup Language (XML). Extensible Markup Language (XML) is a condensed form of Standard Generalized Markup Language (SGML) that enables developers to create customized tags that offer flexibility in organizing and presenting information. When you design a form, InfoPath creates a form template (.xsn) file, with an .xsn extension. When someone fills out a form in InfoPath, the data in that form is saved in XML format. This makes it easy for organizations to reuse the data elsewhere, perhaps in an existing process that relies on XML, such as an expense reporting process.
However, you don't need to understand XML in order to design or fill out an InfoPath form. The important point is that the form's XML format makes it easy to repurpose and share the data you collect.
In InfoPath, you can do two things:
Design forms:
You can design and publish interactive, user-friendly forms in design mode. In addition to inserting standard controls into a form, InfoPath lets you insert controls that offer users the flexibility to add, remove, or hide sections of a form. The forms you design can range from simple forms for collecting data to complex forms that are part of a larger business process. You don't need programming or scripting expertise to design an effective form. However, if you know how to write script, you can use Microsoft JScript or Microsoft Visual Basic Scripting Edition (VBScript) in your forms by accessing the Microsoft Script Editor (MSE) from within design mode.
Fill out forms:
Users who have InfoPath installed on their computer can fill out forms using familiar, document-like features, such as the spelling checker and rich text formatting. Depending on the form's design, users may also be able to merge data from multiple forms into a single form, or export data to other programs. Users can also save forms to their computer, work on them offline, and then submit them to the corporate network when they are reconnected. This is especially useful for people who have intermittent or limited access to network resources, such as employees who travel frequently.
Why to Use InfoPath?
InfoPath forms can be straightforward, simple forms that are used by a few people in a small workgroup For example, a 10-person sales team can use InfoPath to fill out and share information in sales call forms. These forms can be published to and accessed from a common location on the company network, such as a form library located on a Microsoft Windows® SharePoint™ Services site. Alternatively, the sales call form can be designed so that data is submitted directly to an existing database of customer information.
InfoPath forms can also be more sophisticated forms that are integrated into the existing business processes of a large organization. For example, if a company uses Microsoft BizTalk Server to manage the process of expense claim reporting, developers in the company's IT department might design an InfoPath expense claim form that submits data to BizTalk, which then routes that data to the appropriate department for approval or processing.
The following lists are some of the most important benefits of using InfoPath:
Reusable data: The data stored in an InfoPath form doesn't have to remain locked in the form forever; it can be easily separated from the form and reformatted or reused in a variety of ways. This enables form designers to integrate form data into existing business processes.
Accurate data: As a user fills out an InfoPath form, the data they enter can be checked for data validation errors. If your form is connected to a database or Web service, users won't be able to submit data until they fix these errors. This helps you ensure that the data you collect is accurate and error-free, and that it conforms to whatever standards you specify.
Offline support: Unlike Web-based forms, InfoPath forms don't have to be filled out while a user is connected to a network. Users can fill out forms offline, and then submit them later, when they are reconnected.
Flexible controls: In addition to standard controls, such as text boxes and list boxes, InfoPath also includes a number of new controls, such as repeating tables and optional sections these types of controls let you create a flexible form that is designed to accommodate your users. For example, in an expense report form, you can use a repeating table to allow users to enter only as many expense items as necessary.
Tablet PC support: InfoPath allows you to design forms for Tablet PC users. In particular, you can include special controls, called ink picture controls, in your form. Tablet PC users can then add handwritten words or drawings inside these controls.
SharePoint?
Microsoft Office SharePoint Portal Server 2003 connects people, teams, and knowledge across business processes. It unifies disparate information, facilitates easy collaboration on documents, projects, and other efforts, and presents specific applications and customized content based on a user’s functional group and organizational role. SharePoint Portal Server works with Microsoft Windows Explorer, Microsoft Office applications, and Web browsers to help you create, manage and share content throughout your organization.
Integration
Form Library
The InfoPath form library is the primary integration point between Windows SharePoint Services and InfoPath. An InfoPath form library is a special type of document library that can contain and promote any information from any XML file. All documents stored within it are based on a specified InfoPath form template.
The form library is the main distribution point for a specified InfoPath form template; it allows the form to be maintained, deployed, and shared for use by the members of an organization. The form library can display columns of information extracted from the forms. With these columns, the user can create custom views to organize the forms and their content, called property promotion.
The form library also makes the extracted information available for searching as part of the SharePoint site. A form designer can use InfoPath to publish a form template directly to the form library and to define custom views for the forms.
Scenario
You can use SharePoint Products and Technologies in combination with InfoPath to improve status reporting with a project team.
Members of a project team compose and submit project status reports on a weekly basis. The status report covers topics such as tasks, progress, issues, hours logged, and budget expended. The project manager reviews the status report submission for each team member and consolidates relevant information from all team members into a single report, which is then specified to the project sponsor.
Existing Process
Project teams use a generic status report document and store all status reports on a file share. The status report process typically operates as follows:
· Team Member Creates a Status Report The team member opens a local, possibly outdated, copy of the generic status report document. The team member types new information for the current reporting period.
· Team Member Submits a Status Report The team member posts the completed status report to a file share and sends an e-mail message to the project manager; alternately, the team member mails the status report to the project manager.
· Project Manager Collects Individual Status Reports The project manager checks both the file share and e-mail periodically, looking for new status reports.
· Project Manager Browses Status Reports The project manager must open a specific report to examine its contents, even if the project manager wants only a quick summary of the status report.
· Project Manager Searches Status Reports The file share is not included in an index by a search engine, so searches against the contents of the status reports are not possible.
· Project Manager Creates the Consolidated Status Report Once all reports are submitted, the project manager goes through a time-consuming, manual process to generate the consolidated status report for the project sponsor.
· Project Manager Submits the Consolidated Status Report The project manager posts the completed status report to a file share and sends an e-mail message to the project sponsor; alternately, the project manager mails the status report to the project sponsor.
