Get documents about "InfoPath Forms Services - PowerPoint - PowerPoint
Shared by: undul853
Categories
Tags
infopath forms services, infopath 2007, microsoft office infopath, sharepoint server, forms services, office sharepoint server, office infopath, microsoft office sharepoint server 2007, windows sharepoint services, microsoft infopath, how to, sharepoint 2007, data connection, business processes, microsoft office sharepoint server
-
Stats
- views:
- 814
- posted:
- 1/11/2010
- language:
- English
- pages:
- 18
Document Sample
Chris Beckett | SharePoint Technology Specialist
(206) 965-8257 | chris@sharepointbits.com | www.sharepointbits.com
Agenda 2
1. Forms Services Overview
2. Demo – Publishing and Viewing a Simple Form with Form Services
3. Differences between InfoPath Rich and Web Forms
4. Advantages of Data Connections
5. Demo – Using a Data Connection Library
6. InfoPath Security Modes and Publishing Alternatives
7. Demo – Farm Data Connection Library / Administrator-Approved Form
8. InfoPath Forms Services Query Parameters
9. Demo – Using Custom Query Parameters with VSTO
10. Mobile Forms
11. Demo – Viewing a Mobile Form
12. Resources
13. Q&A
InfoPath Forms Services Overview 3
• The InfoPath Forms Services technology is available in the Microsoft Office
SharePoint Server 2007 Enterprise CAL and also, separately, in Microsoft Office
Forms Server 2007.
• Allows rendering InfoPath Forms in a Browser
• InfoPath client is not required to be installed on the client machine
• Cross-Browser support for IE, Safari, Firefox
Demo – Publishing a Form 4
An introduction to publishing InfoPath
forms for display in InfoPath Form
Services:
1. Open Sample Template
2. Set Compatibility for Browser
3. Set Forms Options
4. Save Locally
5. Publish to SharePoint (Create New
Library)
6. Update Library to display in browser
7. Demonstrate form displaying in
browser
InfoPath Client vs. Forms Services 5
Controls that work with Forms Controls that require InfoPath
Services: client:
• Text Box • ActiveX Control
• Rich Text Box (Partial) • Bulleted List Control
• List Box • Choice Group / Section
• Drop-Down List Box
• Combo Box
• Date Picker
• Horizontal Region / Repeating Table
• Check Box
• Ink Picture Control
• Option Button
• Button • Master/Detail Control
• Section • Multiple-Selection List Box
• Optional Section • Numbered List Control
• Repeating Section • Picture Control
• Repeating Table • Plain List Control
• File Attachment
• Repeating Choice Group
• Hyperlink
• Repeating Recursive Section
• Expression Box
• Scrolling Region
• Vertical Label
InfoPath Features not supported by Forms 6
• Filters • Protected Views
• Submitting data to a database • Word-Based Print Views
• Submitting ADO.NET Change Dataset • Undo / Redo
• Alerts that display dialog boxes
• Check Spelling
• Rules to open a new form
• AutoComplete
• Digitally signing entire form
• XSL customizations with xd:preserve • Information Rights Management
• Data Connections across site collections • Send to Mail Recipient
• Custom code to save forms • Merge Forms
• Custom code to merge data • Export to Excel
• Legacy Code using InfoPath.SemiTrust • COM Add-Ins
• User Roles / Current User Role
• Placeholder Text in Controls
• There are also differences between
• Custom Task Panes what classes and members of the
• Prompting users to save changes when Microsoft.Office.Infopath namespace
closing a form can be used with Forms Services
• Rules to display a dialog box
Data Connections 7
• Xml file in the Universal Data Connection V2 Format
• Abstracts connection details from the InfoPath Form
• Saved to a special library called a “Data Connection Library”
• Can be deployed at a site, or farm-level
• Allows browser-based forms to access Web Services securely, even
across domains (with configuration)
• Allows submitting forms across Site Collections and Web Applications
• Configuration managed from Central Administration under
Application Settings
Demo – Data Connection Libraries 8
Using data connection libraries to improve
the portability of InfoPath Forms:
1. Create a custom list to hold Trip Class
options
2. Add a receive data connection to the
new list
3. Create a Data Connection Library
4. Create a UDCv2 file pointing to the Trip
Class list. Upload to the data connection
library.
5. Add a receive data connection to the
new UDC in the data connection library.
6. Review form manifest to demonstrate
that data connections do not hard-code
connection information into the form.
7. Republish the form as a Content Type
8. Create new form library and add new
content type
9. Display the form and demonstrate data
being retrieved through data connection
library
Form Security Modes 9
USER FORMS / DOMAIN-TRUST
• Forms published directly to SharePoint
Form Libraries or Content Types
• Forms that use Site Collection Data
Connection Libraries
• Local to site collection – if published
to another site collection completely
independent copy (hard to manage
changes)
ADMIN-APPROVED / FULL-TRUST
• Forms with code-behind
• Forms that use Data Connections
from Central Administration
• Can be used in multiple site
collections and web applications
• Single place to make changes
• Additional overhead to publishing
process
Demo – Full Trust Forms 10
Use a Farm-Level data connection library
with an Administrator-Approved Form:
1. Open Central Administration and upload
UDC file to Farm Data Connection Library
2. Add a receive data connection to the new
UDC in the data connection library –
specify “Centrally Managed connection
library”
3. Republish the form as an Administrator-
Approved Form
4. Open Central Administration and upload
form template. Publish to demo site
collection.
5. Open demo site and display published
form template and new auto-generated
content type.
Invoking Forms by URL 11
• URL that references a form template (*.xsn) or form file (*.xml)
• URL that references the built-in FormServer.aspx Web Page
• Custom Page containing the XmlFormView control
http://ServerName/sites/SiteCollection/FormLibrary/Form1.xml?OpenIn=Browser
http://ServerName/sites/SiteCollection/_layouts/FormServer.aspx?XmlLocation=~sitecollection/FormLibrary/Form1.xml
http://ServerName/sites/SiteCollection/FormLibrary/Forms/template.xsn?NoRedirect=true
Parameter Description Allowed Values
Name
XmlLocation Used to open an existing form. The XmlLocation and XsnLocation properties are A valid url to a form file (.xml) in the
mutually exclusive; specifying values for both parameters will result in an error. same site collection.
XsnLocation Used to open a new form based on a form template. A valid URL to a form template file (.xsn)
published on the same site collection.
OpenIn Used to specify how the form will be rendered. Browser | Client |PreferClient | Mobile
Source The location to which the user will be redirected when the form is closed. The A valid URL in the same site collection as
URL must be in the same site collection or an error will be returned. the form.
Options DisableSave is the only allowed value. It hides the Save and Save As buttons DisableSave
and disables saving the form when it is rendered in the browser.
SaveLocation A Save As dialog box is displayed prompting the user for a filename, and then Any valid folder location on the site
it is saved in the specified folder. An error is returned if the specified folder collection.
does not exist.
NoRedirect Does not redirect to FormServer.aspx for client detection or rendering in the False (default) or True
browser. Default value is false. If true and an XmlLocation or XsnLocation is
specified, a File Download dialog is displayed when using Internet Explorer.
Passing Parameters to Forms 12
• Passes any additional query parameters not recognized by
InfoPath Forms Services to browser form as Input Parameters in
the Form Loading event.
http://server/sites/team/forms/DeptReport.xsn?Dept=Accounting
Reading Input Parameters for Form Opened with URL
public void FormEvents_Loading(object sender, LoadingEventArgs e)
{
string purpose = e.InputParameters[“Purpose"];
XPathNavigator xmlNav = CreateNavigator();
xmlNav.SelectSingleNode("/my:travelRequest/my:purpose“, NamespaceManager).SetValue(purpose);
}
Reading Input Parameters for Form Opened in XmlFormView WebPart
public void FormEvents_Loading(object sender, LoadingEventArgs e)
{
string param = HttpContext.Current.Request.Params[“myParam"];
…
}
• Query parameters allow InfoPath to be invoked from links, the
Business Data Catalog, a DataFormView on a custom SharePoint
Designer page, etc.
Demo – Forms Services Query Parameters 13
Demonstrate supported and custom query
parameters for InfoPath Web Forms:
1. Open the demo site and browse to Form
Templates
2. Display the form template using Form
Services Query Parameters
…\TravelRequest.xsn?OpenIn=Browser
3. Switch to the InfoPath Form
4. Open VSTO by selecting Tools >
Programming > Loading Event from
InfoPath
5. Add code to copy the “Purpose”
parameter to the Business Purpose field
6. Republish the form as an Administrator-
Approved Form
7. Open the demo site and create a new
form.
8. Update the URL to add our new custom
query parameter and refresh the browser
9. Display how the query parameter became
the value for the form field
Mobile Forms 14
Mobile Form Design Differences Recommendations
• ASP.NET Controls replaced with • Used buttons and multiple views to
ASP.NET Mobile Controls organize controls for small screens
• HTML Tables and CSS not • Use only supported controls to
supported by some mobile minimize rendering inconsistencies
browsers – visual fidelity is not
• Minimize dynamic data queries that
guaranteed
require round-trips to the server
• Mobile representation rendered
during publishing – may look
different on different devices
• Only support a sub-set of browser
controls:
• Text Box
• List Box
• Check Box
• Drop-Down List Box
• Repeating Section
• Expression Box
• Date Picker
• Buttons
Demo – Mobile Forms 15
Demonstrate rendering a form in a mobile
device:
1. Start the Windows Mobile 6 Emulator
2. Start Pocket IE
3. Browse to demo site mobile view
4. Open the “BreakfastParis” file
5. Demonstrate the form rendering in a
mobile device
Forms Services Configuration 16
• Should publishing
browser forms be
restricted to
Administrators?
• Does access to data
sources need to be
secure?
• Is cross-domain access
to data allowed?
• Located in Central Administration > Applications > InfoPath Forms Services
• Allows configuration of farm settings for Forms Services
• Can be used to enforce secure policies around form connections to data, etc
• Session State Size – Large File Upload support
Resources 17
• Microsoft Office Forms Server 2007 SDK
http://msdn.microsoft.com/en-us/library/ms772301.aspx
• InfoPath Forms Server 2007 – An Essential Guide!
http://www.marclenferna.com/blog/archive/2008/10/31/infopath-forms-server-2007---an-essential-guide.aspx
• TechNet Office System Tech Center – Microsoft Office Forms Server 2007
http://technet.microsoft.com/en-us/office/bb267350.aspx
• Planning and architecture, deployment, and operations for Office Forms Server 2007 (Downloadable Book)
http://technet.microsoft.com/en-us/library/cc197347.aspx
• Office Online - Microsoft Office Forms Server 2007
http://office.microsoft.com/en-us/formsserver/FX100490391033.aspx
• Office Developer Center – InfoPath 2007 Resource Center
http://msdn.microsoft.com/en-us/office/aa905443.aspx
• MSDN VSTO – InfoPath Developer Reference for Managed Code
http://msdn.microsoft.com/en-gb/library/aa941030(VS.80).aspx
• InfoPath Team Blog
http://blogs.msdn.com/infopath
• InfoPath Forms Services 2007 Web Testing Toolkit
http://www.codeplex.com/ipfswebtest
Questions and Answers
Tonight’s Topics:
• Forms Services Overview
• InfoPath Client vs. Forms Services
Email me to
• Custom Web Services Integration
get a copy of
• Advantages of Data Connections this slide
• InfoPath Trust Model deck
• Form Publishing Options
• Admin-Approved Forms
• Invoking Form Services by URL
• Passing Parameters
• Code-Behind with VSTO
• Mobile Forms
Contact me to discuss your next project : www.sharepointbits.com | chris@sharepointbits.com | (206) 965-8257
Related docs
