“Creating a SharePoint application that uses InfoPath 2010 involves many steps, many of which are performed in the designer.
To become skilled in using InfoPath 2010, consider joining MS InfoPath 2010 Essentials Training Course from pdtraining in Brisbane, Melbourne and other cities in Australia.
Regardless of the form template you select, you must build the main data source of the form. Additionally, depending on the scenario, you might add views for different user roles, include connections to external data sources, integrate with a SharePoint workflow, or even filter list controls that are based on certain user selections.
This kind of functionality affects both the usability and performance of your form template: therefore, you should follow best practices whenever possible.
This section will provide guidance with regard to creating a SharePoint application by using InfoPath 2010.
Obviously, this subject has many permutations. Therefore, this documentation cannot cover every aspect of a given scenario. Instead, this section is intended to draw attention to certain features, tips, and tricks that will optimise the SharePoint application.
As a general guideline in form template design, when you increase complexity, runtime performance may worsen. Complexity comes in different ways, such as declarative rules, conditional formatting, external data connections, and custom code. All of that logic must be processed at runtime, which affects how the form is rendered. This section offers several simple techniques that will help improve performance in your forms.
InfoPath 2010 uses XSLT to transform the form’s XML data source into editable HTML. Each form view in a template has its own associated .xsl file. From a performance perspective, it is better to have many form views (each with a small amount of business logic, such as conditional formatting) than a single view that contains all of the template’s business logic. The XSLT transformation engine is taxed less if your .xsl file is not too complex.
SharePoint applications typically have multiple user roles. For example, in the hardware request scenario described in Building SharePoint Applications with InfoPath 2010 (Part 2 of 2), any employee can start a hardware request.
In turn, any approver, such as a manager, can approve or reject the request. In that scenario, there are at least two user roles: a requestor and an approver. ”
source – http://msdn.microsoft.com/en-us/library/ff961896.aspx
Learning new skills should be an absolute requirement for any professional.
Pdtraining delivers 1000’s of professional development courses each year in Brisbane, Sydney, Parramatta, Melbourne, Adelaide, Canberra and Perth, so you can be assured your training will be delivered by a qualified and experienced trainer.
All public MS InfoPath 2010 Essentials Training courses include am/pm tea, lunch, printed courseware and a certificate of completion. Customised courses are available upon request so please contact pdtraining on 1300 121 400 to learn more.