Introduction to sharePoint 2013 Round UP

1. What's New in SharePoint
2013

2. Agenda
• Apps
• Search
• Web Content Management
• Enterprise Content Management
• Social
• Workflows
• Remote Event receivers
• BCS
• Business Intelligence(BI)
• Architectural changes
• Visual Studio Changes
• UI Enhancements

3. Apps
Solutions – To Customize SharePoint 2013

4. Apps
• Farm Solutions – Full trust
1)Destabilize the Farm
2)Difficult to migrate
3)Only Farm Administrator could deploy the Solutions
4)Solutions cannot be hosted on Cloud
• Sandbox Solutions- Partially trust(Subset of the Farm or SharePoint API)
1)Site collection Administrator can deploy Solutions
2)Solutions can be hosted on Cloud
Developers need to know SharePoint API for building Solutions
• Apps - New

5. Apps
• Apps cannot run SharePoint server side API code instead use REST/CSOM
• App Solution does not live on SharePoint instead Executes at the client
context(Browser) or at a different server(IIS server or Azure) and hence
isolated from SharePoint
• Apps are given permissions to SharePoint using OAuth
• Developers need not Know SharePoint API and can use REST and
OAuth(Industry based) for communication with SharePoint
• Developers can Publish apps to
• 1)Marketplace
• 2)Corporate Market Place
• 3)Deploy to on-premise server
• Apps can be hosted in Cloud
• Everything in SharePoint 2013 is called app

6. Configure Apps
• Create a DNS domain name
• Configure the Subscription Settings and App Management service
applications
• Configure the app URLs to use

7. Domain Name

8. Configure App URL

9. Manage App catalog- Apps in
organization

10. Apps-Created in a App web (sub site)

11. Apps- Types of Apps
• SharePoint-Hosted Apps-
1)This app run in the context of the SharePoint and uses
JavaScript .Server side code is not allowed but can use SharePoint
components like lists, library ,OOB web parts ,Pages without code
behind(declarative tags) .Simple Apps
Parent Web
App Web

17. App-permission
Scope URI Permissions
Site http://sharepoint/content/sitecollection Read, Write, Manage, Full Control
Web http://sharepoint/content/sitecollection/web Read, Write, Manage, Full Control
List http://sharepoint/content/sitecollection/web/list Read, Write, Manage, Full Control
Social http://sharepoint/social/core Read, Write, Manage, Full Control
Search http://sharepoint/search QueryAsUserIgnoreAppPrincipal

18. App-tokens
Scope URI
~site The URL of the current website.
~controlTemplates The URL of the ControlTemplates virtual folder for the current website.
~sitecollection The URL of the parent site collection of the current website.
~layouts The URL of the Layouts virtual folder for the current website.
{ItemId} The ID of a item in a list or library (an integer).
{ItemUrl} The URL of the item being acted upon.
{ListId} The ID of the current list (a GUID).
{Site} The URL of the current website.
{SiteCollection} The URL of the parent site of the current website.

19. Apps-Types of Apps
• Cloud-Hosted Apps-
1)This app run in the context of non SharePoint Server. It can be
IIS ,Azure or other cloud based services .We can use REST/CSOM for
commination with SharePoint using OAuth. Complex Apps
A)Provider-Hosted App-The infrastructure for the hosted web will be
Choice of the Developer Ex Asp.net or ASP.net MVC Site hosted on IIS
SharePoint Web Your hosted web

20. Apps-Types of Apps
• Provider-Hosted Apps
1) Provider-hosted app for on-premises will be a high trust app and need to
configure the same
• Add a registry key to disable the app principal access token check
• Create a public and private test certificate
• Configure Server and enable OAuth
Cross Domain calls will be made through SPRequestExecutor.js file from client
side in the app(Only in case of REST and not in case of CSOM)

22. Apps-Types of Apps
2)Auto-Hosted App-This is similar to provider hosted apps but use
windows Azure and SQL azure when the apps are installed.
SharePoint Web Azure

23. Apps-Location
1)Immersive App - Full page
2)Part App - Similar to web parts and can be added to the pages
We need to add Allow Framing control
3)Extension App - provided as a link in ECB menu

25. Search
SharePoint and FAST search Integrated

27. Search
Search –crawl the content and create an index but in FAST the index
was pushed instead of crawler
SharePoint 2013 follows the idea of Continues crawling and the
Continues Crawler is only for the SharePoint index(by looking into log
changes) and not for other data sources
Crawl properties are converted to Managed properties and used in the
Keyword search Query as done in SharePoint 2010

28. Search
Search provide REST and CSOM API
Export and import search setting from Dev-QA- Production(only the
rules,sources and managed properties and not the pages).
Keyword Query Syntax is the preferred Query language for search and
can be used in rest queries
Web service call out – change the managed property and make it as
part of index

29. Search
1)Result sources also know as scope–What part of Index we need to search
Local SharePoint index
Remote SharePoint index
OpenSearch
Exchange
1.1)Query transformation :Build Query ex :Specific list using contentclass
2)Query Rules- we can change the user query to a meaningful search and select the
type of display
Applied to result sources Ex:Slides will return Presentation
3)Result Types – How the results are displayed
Specify the Result Source and a Display template (it’s a comintaion of HTML and Javascript
files)
4)SPNavigationProvider – Similar to tabs in SharePoint 2010
Search center-Site settings-Search Settings

33. Search
Search Hover panel
Result Blocks-Grouping Related results of search in small search
Customize Hover Panel Using Result Types
Recommendations

34. WCM
Web Content Management

35. WCM
1)Clean URL or FURL- No pages and .aspx as part of URL
2)Navigation based on Managed Metadata(taxanomoy)
3)Cross-Site Collection Sharing(Content Reuse)-Item Catalog and Topic Pages
Uses the search index to populate the catalog and master page
4)SEO(Publishing Pages: Set Additional Fields for promoting search results)
5)Image Renditions
6)Design Manager
7)Themes(Composed looks)
8)Device channels

39. WCM
Every new page create a term set in the taxonomy and these terms
know the navigation (clean url)
Cross site collection publishing feature once enabled can share the list
to other site collections
Content by search web part (search by index)
Rollup page and details page (Display Templates)

40. WCM
Managed metadata :Taxonomies- Permission (read, write),more Site
level operation, intended use(search or navigation), pining(copy the
term but cant modify the term)
Roll up Pages :Tied to a specific item in taxonomy and the new web
part will use the item and search in the index
Content can be Item catalog, Authored content, Same or different site
collection, External federated sources
On click of the items in rollup page we will get the details of the page
(Product page or Details page Template)
Publish the taxonomy to different site collection

41. WCM
ContentbySearch Web part
1)Its Based on SharePoint 2013 Search Engine
2)Display Templates: It a combination of HTML file and JavaScript file
which will generate the UI instead of XSLT

42. WCM
Design Manager
1)No Design View for SharePoint Designer 2013
2)Design manager will be available on Activation of Publishing Feature
3)Work with master page and page layouts in HTML
4)Using Design manager we can create minimal master Page,Convert existing HTML
to master page, Page layouts
5)Design manger engine will create a master page from an HTML file
Master page will be HTML + .master
Page layout will be HTML +.aspx
6)Snippet Gallery: Add common snippets to HTML master page or Page layout
7)Create a design package and import to other site collections(sandbox)

45. WCM
• Composed Looks
1)Similar to themes
2)It Includes Master page, Color fonts, Background image and preview
files
3)Not created with office clients like power point presenattion

46. WCM
Device Channels
1)Target area of content on the pages for Specific devices
2)SharePoint Uses user agent of the device to target specific content
for specific device

47. ECM
Enterprise Content Management(SharePoint & Exchange)

48. ECM
Site level Retention policies :
1)Compliance features of SharePoint have been extended to the sites.
2)Users can create and manage retention policies and these policy will
apply to SharePoint and Exchange team mailboxes associated with the
site

49. ECM
Site Mailbox – This brings Exchange mails and SharePoint Documents
together
User will be able to add documents to SharePoint (Site mailbox)directly
from outlook.
Site mailbox feature exists at Farm and web level and need to be
activated- which will provide an app to be installed in the site
Retention policies similar to the sites

50. ECM
EDiscovery –Securing the content from SharePoint and Exchange –
holds for legal cases to meet the compliance
Users can review the content and also export data from the system
SharePoint 2013 Provides a new Discovery Template for creating sites

51. ECM
Document sets –We can have folders and OneNote files
Supports Content by Query and Content by Search web parts
CSOM API for working with document sets

52. Social

53. Social-My Site
1)Users can follow Sites, Docs, People and tags
2)User details is stored in Profile DB and users following different content will
be stored in My Site instead of Profile DB
3)Micro feed - Which will be user or system based feed
4)Store Documents and See the tasks from all the Sites and also from
exchange and project server
5)App fabric – which is used to cache social data
5.1)Available across all the WFE
5.2)Document and Tag Activity are written directly to App fabric
5.3)Sites and People are written to content data base and then
to App fabric
6)Support for CSOM/REST API

55. Social-Communites
1)New Site templates to create comminutes
2)Builds on Discussion,Ratings,Like,Reputations and Badge
3)Uses Wiki Page infrastructure

57. Workflow

58. Workflow
Workflow as a service in SharePoint 2013
Works on Windows Azure Workflow and not in Content Farm
Improves Scalability, stability
Workflow Communicate with SharePoint Using App Model
Technologies like CSOM/Rest and OAuth

59. Workflow(Designer)
Stages similar to state machines introduced
Loops have been introduced
Designer workflows can call REST/Soap Services
Visual Designer

60. Workflow(Visual Studio)
1)Custom Code is not allowed
2)We can include the workflow in Apps
3)Custom code will be written in the web services and activities will be
used to run those web services

61. Remote Event receivers

62. Remote Event receivers
SharePoint talks to the third party application based on the Events in
SharePoint
Ex Steps
1)Update the SharePoint list
2)Request a token from ACS(Access control service)
3)Registered event receiver(custom web service) –inherits from
an interface(IRemoteEventReciver)
4)Web service update LOB system
5)Notification of success or failure returned to SharePoint in simple
scenarios

63. Remote Event receivers
Advanced Call back options: To call back SharePoint from LOB system
Event Scopes: Lisitem, List, Web, App(synchronous and async)
Developing Remote Event receivers is similar to event receivers and
only change will be the Feature receiver will have a url instead of a
class and assembly name

64. BCS
Business connectivity services(Support for SharePoint online)

65. BCS
Different Connectors like
1)Web services
2)SQL connectors
3).NET Connector(Schema is constant)
4)Custom connector(3rd party)
BCS is installed in the office client so that user can work with BCS data offline
using Client Data Cache(Data comes from a metadata store of BCS)
Filter data from the sources itself

66. BCS
OData Support:REST
SharePoint 2010 ECT were at the Farm level
App level External Content Type(Use ECT in Apps) it is like an inmemory
ECT residing in a document library(no support for .Net and Custom
connectors)
Support for CSOM and REST
Notification and Custom Event receivers(events from external list(event
receivers) and notification from external LOB to SharePoint)

67. BI
Business Intelligence

68. BI
Excel
1)Instant analysis through In memory BI engine
2)Power view Add-In
Excel Services
1)Improved Data Exploration
2)Enhanced Timeline controls
3)Calculated Measures and Members
PPS
1)Filter Enhancements
2)Dashboard Migration

69. Architectural changes

70. Architectural changes
Office Web App is a separate product
Analytics is integrated with search Service application
Enhanced Managed metadata service
New Service Application
1)App management Service
2)Work Management Service(Depends on Search Index)
3)Machine Translation service
Minimal Download Strategy
Shredded Storage in SQL Server

71. Visual Studio 2012

72. Visual Studio 2012
List and Content type designers
Site Column template
Sandboxed visual web parts
JavaScript intellisense and debugging

73. UI Enhancements

74. UI Enhancements
Drag and Drop Documents to Document library
Search Inside the Document library
Create view based on Searched data or filtered data