3. #SPSPhilly @PGBhoyar
What Will We Cover Today?
• InfoPath
• InfoPath and SharePoint
• Browser based Forms
• InfoPath Deployment
• Limitations of InfoPath
5. #SPSPhilly @PGBhoyar
LessComplexity
Why InfoPath in
SharePoint?
• InfoPath Forms Services
• Browser Support –
Local Installation is
not required
• Easy to create
• Out of the Box
Validation, Rules,
Calculations, Logic,
Formatting
6. #SPSPhilly @PGBhoyar
LessComplexity
Examples of InfoPath in SharePoint
• Leave System
• Time cards
• Performance reviews
• Collaborative budgeting
• Status reports
• Service requests
• Recruiting
• New project initiation
• New hires / terminations
7. #SPSPhilly @PGBhoyar
InfoPath 2010 Client Based
Technologies
• InfoPath Filler 2010
• Used by End Users to complete the forms
or “fill it in”
• Can’t be use to design form templates
• Need InfoPath client to use
• InfoPath Designer 2010
• Used by Designers to design and publish
form templates
9. #SPSPhilly @PGBhoyar
LessComplexity
InfoPath Forms in SharePoint
• Standard InfoPath Forms
• Usage Scenario : Users create new form, fill the
information and promote certain fields to forms library
(Property Promotion)
• List Forms
• Upgrade the List associated forms to InfoPath forms.
(add InfoPath capabilities of formatting, rules, logic,
calculations, and so on).
10. #SPSPhilly @PGBhoyar
LessComplexity
Browser Based Forms
• Users don’t need local installation of InfoPath client
• Any options that cannot be rendered in a browser is
hidden. For Example (Spell-Check, The Vertical Label, Ink Picture, Signature
Line, Scrolling).
Full list can be found here http://office.microsoft.com/en-gb/infopath-help/infopath-2010-features-
unavailable-in-web-browser-forms-HA101732796.aspx
• Available only with Enterprise Client Access License (eCAL)
for SharePoint. Not available in SharePoint Foundation or
SharePoint Standard Server
11. #SPSPhilly @PGBhoyar
LessComplexity
InfoPath List Forms in SharePoint
• Advantages
• Easy to customize
• Add validations, rules
• Drawbacks
• SharePoint adds additional information to list and content type
like hidden fields, absolute urls
• Deployment to other site collection, Web Application and Farms
• Resolution: Save list as template (.stp) and deploy
13. #SPSPhilly @PGBhoyar
LessComplexity
InfoPath XSN and XML Files
• XSN or Form Template is collection of several files
packaged into a cabinet (.cab) file
• Forms are stored in SharePoint in the form of XML
files
• Inherits core SharePoint functionalities (Versions,
Recycle Bin etc.)
15. #SPSPhilly @PGBhoyar
LessComplexity
Data Connection Library
• List designed to store data connection files for use in
InfoPath
• Details of system to which the form connects are not hard-
coded into the form
• If connection details change, only the data connection
must be updated. This avoids needing to update and
redeploy the form
• Data connection details are not stored in the form itself
17. #SPSPhilly @PGBhoyar
LessComplexity
Save and Submit
• Use InfoPath toolbar options Save and Save As
• No control over where the forms get saved, or what filenames are
used.
• Custom Submit Button
• Email
• Web Service
• Hosting Env
• Web Server
• Data Connection
• SharePoint Document Library
18. #SPSPhilly @PGBhoyar
InfoPath 2010
Forms Data
• Store in form itself
• Open the form to see the info
• Difficult to crawl the information
• Publish in Library/List –
“Property Promotion”
• Create list views
• Can be used by other Workflows
• Used as look up field
• Search
20. #SPSPhilly @PGBhoyar
LessComplexity
InfoPath Forms Web Part
SharePoint
• InfoPath Browsers Forms takes entire screen
area. This can be confusing for users
• Use of InfoPath Forms Web Part
• Provides a range of options for rendering
a form inside a web part that can be placed in any SharePoint web
part page
• Avoid if Form is complex and has multiple views
23. #SPSPhilly @PGBhoyar
InfoPath Deployment
LessComplexity
• Deploying to a Form Library
• InfoPath Designer requires direct access to SharePoint Server
• Form will be available in specific site/library
• Deploying to a Content Type
• Creates a new content type
• Available in List and Libraries of Site
• Cons:
• Need to deploy manually to all site collections
• Manually associate content type with list/library
24. #SPSPhilly @PGBhoyar
InfoPath Deployment
Administrator Approved Forms
Templates
• Allows InfoPath form to be reused
throughout the entire SharePoint farm
• Easy to maintain, as we need to do change
at one location only
• If Form has code behind in it, then this is
the only option for deployment
• To deploy:
• Save the Form template
• Upload to Central Admin
• Use the option “Activate to a site
collection” for each site collection
25. #SPSPhilly @PGBhoyar
InfoPath Deployment
LessComplexity
Deploy with Feature
• XsnFeatureReceiver class in namespace
Microsoft.Office.InfoPath.Server.Administration
• During activation/deactivation copy the
.XSN file to forms library
• Same as publishing the form using InfoPath
designer
• Deployment can be done per site collection
• Since it’s a feature more control via
PowerShell and Deployment/Retraction
• Cannot be used to deploy forms to Central
Administration
29. #SPSPhilly @PGBhoyar
LessComplexity
Alternatives to InfoPath
Alternative Advantages over InfoPath Disadvantages
over InfoPath
Ideal Usage When not to use
SharePoint
List Forms
-Very Quick to Design
-Can be upgraded to InfoPath
-No technical Skills Required
-No control over
Presentation
-When very simple
Info is required
-When time and
resource are
Limited
-Presentation is
important
-Time and
Resources are
available
Custom
SharePoint
Web Parts
- Can meet exact
requirements (Custom Code)
-Difficult to
maintain without
developer
-Need complete
control over UI
-Want to avoid
custom code
Custom
SharePoint
Application
Pages
(ASP.NET
Pages)
- Can meet exact
requirements (Custom Code)
-Difficult to
maintain without
developer
-Need complete
control over UI
-Want to avoid
custom code
30. #SPSPhilly @PGBhoyar
LessComplexity
Workflows using InfoPath and
SharePoint
• Use SharePoint Alerts when forms are submitted
• Send custom notification using SharePoint Designer
Workflow
• Custom Code
• Third Party Workflow Tools
31. #SPSPhilly @PGBhoyar
LessComplexity
Is InfoPath Right Choice?
• Yes if,
• Forms that must be designed by a non-technical user
(Power User)
• Custom Code is not allowed
• Forms that will benefit from rich conditional formatting
• Forms that must be designed rapidly
• Solution will be hosted in cloud vs on Premise
33. #SPSPhilly @PGBhoyar
Questions? Feedback? Contact me:
Twitter: @PGBhoyar
Blog: http://pgbhoyar.wordpress.com
Email: pgbhoyar@gmail.com
Thank You
Organizers, Sponsors and You for Making this Possible.
35. #SPSPhilly @PGBhoyar
SharePoint User Group
• SharePoint
• End Users
• Administrators
• Architects
• Developers
• IT Pros
• Meetings: 2nd Tuesday of the month, Microsoft Malvern, 5:30-8 pm
WEB: www.TriStateSharePoint.org
EMAIL: info@TriStateSharePoint.org
TWITTER: @tristateSP
36. #SPSPhilly @PGBhoyar
SharePoint Network
• Are you an independent consultant or remote worker
who deals with SharePoint, Office or Office365?
• Do you sometimes feel cut off from the rest of the
SharePoint world?
• Do you need help with technical or business issues, or
just want the chance to socialize with others?
If so, then the SharePoint Network might be for you!
www.SharePointNetwork.org
Notas do Editor
Please encourage folks to visit the sponsors in the lobby. Everyone should have a sponsor bingo card. If they get initials from each sponsor they can be entered in our drawings to win great prizes, including Kindles, and a Surface RT.
This is the local Philly SharePoint user group. We cover a range of topics for all audiences.
This is a local group that is just getting started as an adjunct to the user group. As the slide says, it is a support and social group for independent and remote workers in the Philly area. More information is available on the website.