Microsoft InfoPath — XML-based form design and filling tool

Key components and characteristics

InfoPath typically splits work into two modes: a form designer and a form-filling runtime. The designer environment lets authors place controls (text boxes, choice lists, date pickers, repeating sections) and bind them to an underlying XML data source. The runtime provides a user-friendly interface for filling the form, applying rules, and saving or submitting the XML payload.

• XML-based storage: form data is saved as XML, enabling interoperability and automated processing.
• Data connections: forms can submit to or retrieve data from web services, databases, or SharePoint lists.
• Rules and logic: authors can add declarative rules or embed script/code (for example C# or Visual Basic) for validation and calculations.

History and development

Introduced by Microsoft in the early 2000s as part of an effort to bring XML and structured data capture to business users, InfoPath evolved across several releases to improve design features, data connections and SharePoint integration. Over time Microsoft shifted strategy toward web-based forms and Power Platform components, but InfoPath influenced later form and workflow tools by popularizing XML forms bound to back-end services.

Uses, examples and integrations

Organizations used InfoPath for business forms such as expense reports, timesheets, surveys, and HR onboarding documents. Common deployment scenarios included:

1. Filling forms locally and saving them as files for archiving or printing (file formats).
2. Publishing forms to SharePoint libraries so users can open and complete them from a browser or client (web-enabled forms).
3. Connecting forms to external data sources—databases, web services, or other enterprise systems—to read or write data (database integration).

Notable facts and distinctions

InfoPath emphasized declarative form design: many validations and actions can be implemented without code, using rules or XPath expressions (XPath) to select and manipulate XML nodes. It offered programmability when needed, allowing developers to extend behavior with managed code. Documentation, templates and community examples were hosted on Microsoft channels and third-party sites (official product page, support resources).

Although newer cloud-first tools have superseded InfoPath in many organizations, it remains a useful case study in how structured XML forms were used to bridge end-user form design with enterprise data systems, and it helped shape modern approaches to electronic forms and workflow automation (developer guidance, file and template details, programming extensions).