& with InfoPath 2007 Business case Our consultant tracking solution implements a number of business processes for one or more stakeholders to submit or process requests. To support these processes, several forms had to be created. These forms would have to: Implement complex business logic. Some form sections must be shown or hidden dynamically based on underlying data Integrate easily with a data repository in our case a number of SharePoint and forms – libraries Integrate with web services without any need for custom code Work seamlessly with SharePoint workflows We selected InfoPath forms as the best option for the following reasons: The integration with SharePoint Server is delivered simply through wizards. Once your form is ready, it can be published as a template to a SharePoint form library. Any field in the form data structure can be promoted to a SharePoint column to the destination form library. As a result, data entered in an InfoPath form is readily available like any other SharePoint list item for search, sorting or displaying. The tool is intuitive to many business users. As a consequence we were able to design the form literally sitting next to a business user, receiving immediate feedback on the form design Here is the form as it looks in design mode, when every control is visible: Form data sources Internal data source Every form you create in InfoPath has an underlying Data Source. This is essentially an XML document that stores values as they are entered in fields throughout the form. Here is the data source for our Resource Request form:
& with InfoPath 2007 Business case Our consultant tracking solution implements a number of business processes for one or more stakeholders to submit or process requests. To support these processes, several forms had to be created. These forms would have to: Implement complex business logic. Some form sections must be shown or hidden dynamically based on underlying data Integrate easily with a data repository – in our case a number of SharePoint and forms libraries Integrate with web services without any need for custom code Work seamlessly with SharePoint workflows We selected InfoPath forms as the best option for the following reasons: The integration with SharePoint Server is delivered simply through wizards. Once your form is ready, it can be published as a template to a SharePoint form library. Any field in the form data structure can be promoted to a SharePoint column to the destination form library. As a result, data entered in an InfoPath form is readily available like any other SharePoint list item for search, sorting or displaying. The tool is intuitive to many business users. As a consequence we were able to design the form literally sitting next to a business user, receiving immediate feedback on the form design Here is the form as it looks in design mode, when every control is visible: Form data sources Internal data source Every form you create in InfoPath has an underlying Data Source. This is essentially an XML document that stores values as they are entered in fields throughout the form. Here is the data source for our Resource Request form:
Developing%20Custom%20Applications%20with%20SharePoint%20Server%202007.docx