Embed Size (px)
DESCRIPTION
InfoPath allows powers users and developers to rapidly create rich smart forms that integrate directly with SharePoint. It includes features that allow form designers to add business rules and integrate line of business data into their forms. But what if you need to update multiple SharePoint lists with one form? What if you have complex data structures (like in the real world)? What do you do when you’ve reached the edge of InfoPath capabilities? In this session, we will examine real world InfoPath use cases where integration of third party tools or custom development are a must. We will look at sample forms and walk through code examples to better understand how to implement these solutions. We’ll also look at a leading ISV solution (Qdabra qRules) to see how quickly a developer can add the most commonly required features to their InfoPath forms. Lastly, we’ll discuss the implications to SharePoint administration when you opt to build more complex forms. Join Andy Hopkins of Chrysalis | BTS as he discusses: -How to identify scenarios that go beyond out of the box InfoPath -Identify new application scenarios that can be facilitated through InfoPath and extensions -How to address complex data structures in InfoPath forms -Real world insights on what works and what doesn’t
Citation preview
@chrysalisbts
presented by
Andy Hopkins [email protected]
(425) 761-4143 @AndrewSHopkins
REAL WORLD | SHAREPOINT implementing advanced business solutions
@chrysalisbts
presented by
Andy Hopkins [email protected]
(425) 761-4143 @AndrewSHopkins
REAL WORLD | SHAREPOINT advanced form solutions in SharePoint
@chrysalisbts
• Real World SharePoint
• Andrew (Andy) Hopkins - Chrysalis BTS
• Patrick Halstead – Qdabra Software
• What will we discuss today?
Welcome
@chrysalisbts
• Form based Business Process • InfoPath fields as web part connection
parameters to create mash-ups • Enhance workflow processes through custom
workflow forms • InfoPath fields to build advanced SharePoint
views • InfoPath Form Web Part Integrating forms into
SharePoint pages • Custom development
4
Advanced Usage Scenarios
@chrysalisbts
FORM BASED BUSINESS PROCESS USING INFOPATH FORMS TO MANAGE END TO END BUSINESS PROCESS
BACKGROUND
@chrysalisbts
InfoPath Form Services Limitations
• Repeating data cannot be mapped to fields
• Getting user information
• User SharePoint Web Services
• Images and file attachments
• Cannot add custom event handler for “Save” event
• Disable save and save as – use submit button instead
• Rule “Close the Form” doesn’t support prompt on browser-based forms
• Disable the ribbon
• Custom message boxes cannot be displayed
6
Not supported in based browser forms
@chrysalisbts
AUTOMATING EXPENSE REPORTS USING INFOPATH FORMS AND DECLARATIVE WORKFLOW
BACKGROUND
@chrysalisbts
Expense Report End to End Business Process - Approval through Payment
Expense Report Saved
Initial Save EmailTO: Preparer
Start Employee Review
Start Approval Workflow
Start Manager Review
NoIs Preparer also
Employee? Yes
Approved
Employee Review Email
TO: Employee
Deleted Task Email
TO: EmployeeCC: Preparer
Rejected Task Email
TO: PreparerCC: Employee
Deleted Rejected
Manager Review Email
TO: Manager
Pause 3 additional days
Pause 5 additional days
Manager Review EmailReminder 1
TO: Manager
Manager Review EmailReminder 2
TO: ManagerCC: Employee
Start Reviewer ReviewApproved
Rejected Task Email
TO: Employee
Rejected
Deleted Task Email
TO: ManagerCC: Employee
Deleted
Reviewer Review Email
TO: Reviewer
Rejected Task Email
TO: Employee
Deleted Task Email
TO: Modified ByCC: Employee
DeletedRejected
Start Approver Review (ML)
Pause 14 additional days
Reviewer EmailReminder
TO: Reviewer
No Action Taken
Approved
No Action Taken
Rejected Task Email
TO: Employee
Deleted
Approval Email
TO: EmployeeApproved Start Payroll Review
Payroll Processing
TO: ExpenseReport-Payroll
Funded Email
TO: EmployeeFunded
Rejected Task Email
TO: Employee
Deleted Task Email
TO: TaskModifiedByCC: Errorhandling
DeletedRejected
Expense ReportWorkflow
Rejected
Deleted Task Email
TO: TaskModifiedByCC: Errorhandling
@chrysalisbts
InfoPath Advanced – Code Challenges
• Code extensions required for • Copying, sorting tables • Converting images to links • Mapping repeating data to lists • etc.
• Common practices quick and dirty • Programmers hardcode lookups • Versioning/migration nightmares • No multi-dev environment for IP
• Maintenance costs • Code itself requires a developer • Changes require recompile • Separate DLLs duplicate logic
A
B
C
D
E
@chrysalisbts
InfoPath Extensions – Code Best Practice
• Use a Single Common Library • Example: qRules fills 130 feature gaps • No developer required
• Commands are data source agnostic • Not tightly coupled to form’s schema
• Inexpensive • Write once, use multiple • qRules is ~5 hours of developer cost
• Easy to upgrade • Re-inject updates to get new features
• qRules Benefit • Thousands of enterprise users • Works in browser, filler, 2007-2013
Q
@chrysalisbts
Demo – Using Common Library with Rules
• Demo • Copying Repeating Data
• Pros: make your form’s data-driven
• Editing List Data from InfoPath • Pros: use SharePoint lists as InfoPath database
• Solutions: • Use out-of-box Rules and
• Write Common Library
• Try qRules common library
@chrysalisbts
Resources and Contact Real World SharePoint
Please Give Us Your Feedback
• Matt will send you an email with a link to the presentation and the eval or visit… www.chrysalisbts.com/index.php/events/rws/search/eval/
Successful SharePoint is About Community
• Share your Real World SharePoint stories #RWSharePoint
• Ask the global SharePoint community for their insight #SPHelp
• Attend or speak at SharePoint Saturday (We’d love to meet you at #SPRedmond)
• Join your local SPUG
Attend Qdabra InfoPath Master Class
• Next online classes in August (Master & 101)
• Next in-person Master class in September
Real World SharePoint Presentations
• www.slideshare.net/andyhopkins
Andrew (Andy) Hopkins
• @AndrewSHopkins
Patrick Halstead
• @PatrickHalstead
@chrysalisbts 14
&
