5. • Business Connectivity
Services Model
Authoring
• Workflow Authoring
• SharePoint Focused UI
• Reusable Content
• Export to Visual Studio
6. Simple SharePoint List SharePoint Workflow Custom SharePoint
Solutions Applications Applications
• Work both online / • Business Connectivity • InfoPath Web Part
offline Services • XmlFormView
• Sandboxed Solutions
9. Client Server
• Surfacing • Access document • Automate • Word, Excel,
customizations content document Access Services
• Modify processes • Workflow
document • BI
content
UI Object Office
Open XML
Extensions model Services
10. Ribbons and Outlook Form Backstage
Task Panes
Context Menus Regions View
11. File Container
Document Open XML SDK 2.0
Properties
Comments Content Level
Markup
Styles
Package Level
Images, sound,
Packaging
video Schemas
API
Embedded code
Custom XML
12. Word Excel Access Visio
• Conversions • Calculations • Publish to • JavaScript OM
• Field Updates • UDFs SharePoint
• REST • UI Macros
• JavaScript OM • Data Macros
• Web Services
13. Business Analyst Professional Developer
Power User
Visio
Visual Studio
SharePoint
Designer
SharePoint
14. Status Chart Web Performance
Excel Services BI Search Visio Services
Indicators Parts Point Services
24. • SharePoint Designer or Visual Studio 2010
– SPD targeted to Power Users
– Visual Studio targeted to Developers
– Integration allows users to work together
SharePoint Designer Visual Studio 2010
2010
25. • Each tool plays a specific role
– Visio allows business analyst to define process
– SPD allows power users to implement process
• Round Trip Import/Export
Visio 2010 SharePoint Designer
2010
26. • Special SharePoint Workflow Template
– Contains shapes for conditions and actions
– Allows exporting of process to SPD
27. • New workflows are attached to a container
– List Workflows are attached to a specific list
– Reusable Workflows are not attached to a list
• May be constrained to a content type
• Attached later using browser
– Site Workflows are attached to the current site
28. • SharePoint 2010 Project Types for Workflow
– Import Reusable Workflow
– Sequential Workflow
– State Machine Workflow
31. Office Client SharePoint Server 2010
External Business Parts SharePoint Site
Custom Code VSTO External
Custom Code
Package List
Office Integration
Search, Workflow, Web Parts
Business Connectivity Services Secure Store Service (SSS)
Business Connectivity Services
Client
Runtime Cache External Content Types Server
(ECT) Runtime
SQL WCF Custom .NET Connector
External Data
32. Describes the schema and data
access capabilities of an external
Office Clients (Rich) data source and its behavior
within Office and SharePoint
BCS
*formerly known as BDC Entity
External Data
External
Source
Content Type (Web Service, DB, .Net
(ECT) object, LOB system, Web
2.0 service, etc.)
BCS BCS-enabled solutions rely on ECTs to
integrate external data into SharePoint
SharePoint (Thin) and the Office client applications
33. Advanced
Simple
SharePoint
Designer
Power User / No code
RAD Dev Advanced Dev Custom Code
• OOB UX on thin and rich clients • Custom UX and data integration on
(Outlook and Groove) based on thin and rich clients (apps that
External Lists support VS Office add-ins)
• Custom Forms in SharePoint and • Through Office, SharePoint and BCS
Groove Object Models
• Connect to existing back-end • Custom back-end connectivity
integration services or simple through .Net objects
databases • Complex BDC models (many
• Simple BDC Models (few ECTs, simple ECTs, complex associations)
associations)
• Transparent packaging (managed by • Explicit packaging (managed by dev)
BCS)
35. • System.IO.Packaging
APIs •
•
•
Open XML SDK
PHPExcel
Open XML 4J
• File Format Converters
Tools
• Open XML SDK
• Open XML Power Tools
• Package Explorer
• Content Control Toolkit
36. string relationshipType = "http://schemas.openxmlformats.org/...";
using (Package package = Package.Open("mydocument.docx"))
{
PackageRelationship relationship = null;
foreach (PackageRelationshipsearchRelation in
package.GetRelationshipsByType(relationshipType))
{
relationship = searchRelation;
break;
}
Uri partUri = PackUriHelper.ResolvePartUri(
relationship.SourceUri, relationship.TargetUri);
PackagePartmainPart = package.GetPart(partUri);
// Do something with mainPart
}
37. using (WordprocessingDocument document =
WordprocessingDocument.Open(“mydocument.docx”))
{
MainDocumentPartmainPart = document.MainPart;
// Do something with mainPart
}
41. • JavaScript Object model
• REST API
• Chart Web Part data provider
• Visio data provider
42. • Integrate with Excel Web Access
• Read / write depending on EWA
var ewa;
function initialize()
{
ewa = new Ewa.EwaControl("ewa");
ewa.openWorkbookAsync("http://server/mywb.xlsx",
Ewa.SessionMode.View, "salesreps", onWorkbookLoaded);
}
function onWorkbookLoaded(result)
{
if (!result.succeeded)
{
alert("Error");
return;
}
// hook up to events that we're interested in
workbook = ewa.get_activeWorkbook();
...
}
43. • Read Access to Excel data
http://example.com/_vti_bin/ExcelRest.aspx/library/sales.xlsx/model
http://example.com/_vti_bin/ExcelRest.aspx/library/sales.xlsx/model/Ranges
http://example.com/_vti_bin/ExcelRest.aspx/library/sales.xlsx/model/Charts
http://example.com/_vti_bin/ExcelRest.aspx/library/sales.xlsx/model/Charts('Chart 1')
• Set values on named ranges
• Expose data as
– ATOM
– HTML
– Image
44. • Access Databases Published
to SharePoint
– Not just saving an .accdb to
a document library
• Translation to SharePoint
technologies
– Tables Lists
– Queries, Reports, Forms Web equivalent
• Synchronized changes between rich client
and SharePoint
48. • Renders InfoPath forms in the browser
– Better performance in SharePoint 2010
– Managed via Central Admin or PowerShell
– Accessibility - WCAG 2.0 AA
– XHTML 1.0 and strict CSS
49. • InfoPath is a tool for creating rich web parts
– Exposes or receives data via connections
– Ex. Host submission form on main portal page
