SharePoint Development: When Out-of-the-Box Just Isn’t Enough

Henry Bernet Senior SharePoint Architect Pillsbury Winthrop Shaw Pittman

Tim Kenney, Esq.

VP, Client Success

Handshake Software

Mark Soriano Application Development Manager, Seyfarth Shaw LLP

3rd Party Tools When we use them

• Simple requirements • Short timeline • Developers are busy on other projects • Small user base • Potential for frequent functional changes

PROS

• Faster to design and

implement

• Use less resources

• Minimal testing

• Minimal coding

• Vendor support

• Extensive knowledge base

3rd Party Tools PROS & CONS

CONS

• Functionality limitations

• Look/feel limitations

• Restricted to vendor

development enhancement

& bug/fix cycle

• Ongoing support if vendor is

out of business

Client/Matter Lookup

Intranet SP 2010

Profiles of staff and

attorneys

Extranet SP 2013

Show/Hide list views

and columns

3rd Party Tools Use Cases

Firm Directory Column/View Permissions

Intranet SP 2010

Allows users to search for client and matter

information

Client/Matter Lookup How we did it

• XMLaw – OneView

Webparts

• Microsoft SQL

• SharePoint 2010

Firm Directory How we did it

• XMLaw – OneView

Webparts

• Microsoft SQL

• HTML/JavaScript

• SharePoint 2010

Column/View Permissions How we did it

• SharePointBoost

Solutions

• SharePoint 2013

Custom Code When we use them

• Complex requirements • Firm Initiative • Large internal/external user base • Functionality not available by purchasing 3rd Party

Tools

PROS

• No functionality limitations

• Truly unique and innovative

application development

• Highly customizable

• Full control when integrating

with other systems

Custom Code PROS & CONS

CONS

• Requires more resources

• Extensive unit, load and

functionality testing

• Slower to market

• Ongoing support and

enhancements

New Business Intake

Intranet SP 2010

Allows users to submit conflicts request

Extranet SP 2013

Upload and edit

documents

Extranet SP 2013

Financial data on a

given matter

Custom Code Use Cases

SeyfarthLink Documents

SeyfarthLink Financials

New Business Intake Request Form How we did it

• XMLaw – OneView

Webparts

• C# .NET Web

Application

• Microsoft SQL

• SharePoint 2010

SeyfarthLink Documents Library How we did it

• Telerik Kendo UI

• HTML5/jQuery

• SharePoint 2013

SeyfarthLink Financial Dashboard How we did it

• Telerik DataViz

• HTML5/jQuery

• SharePoint 2013

Getting to “Hello World” …a real world app experience

plan your environment …a pain in the app

• Microsoft Documentation

• Developer Training

• Write it down

plan your environment

• DNS Zones

• App Catalog

• Gotchas

• External Access

setup the infrastructure

show the world …”I'm Good Enough, I'm Smart Enough, and Doggone It, People Like Me!”

• External DNS

• Network Considerations

show the world

make up your own rules …<INSERT THE FUNNY HERE>

• The App Domain

• Security Concerns

make up your own rules

small steps out of the box

“It’s so easy, even I could do it!”

maximizing sharepoint search

• Search Display Templates

• Javascript & HTML

• Managed Properties

maximizing sharepoint search

extend your user profiles

• Timer Jobs

• Data Warehouse

• Filtered Lists

extend your user profiles

document library tree view

• OOB Document Library

• Query String Pusher

document library tree view

“SOLD!”

enterprise search

• Recommind by Decisiv

• Search Scopes

• Lexis Search Advantage

• Custom Webparts

enterprise search

litigation profiles

• Monitor Suite

• Client Team Legal Profiles

• Query String Pusher

litigation profiles

two factor authentication

• SecureAuth

• 2FA via Voice and SMS

• Claim Provider

two factor authentication

Going “Beyond the Box” with Third Party Vendors Help us help you

Focus on Business Utility FIRST – let all other decisions flow from that

• What Problems Are You Solving?

DO

• Focus on solving problems

and giving new benefits

• Get involved and own the

project

• Ask questions – internally

and to the vendor

• Be realistic with expectations

• Get training

Working with Vendors of 3rd Party Tools Best Practices

DON’T

• Invest then not use

• Expect one tool to do it all

Client Example 1

Client Example 1

Sheppard Mullin

Sheppard User Profile

Jones, Skelton & Hochuli

BestPractices in “Going Beyond the Box” with SharePoint

Perkins Coie (above the fold)

Perkins Coie (below the fold)

Hovering over a Client

Record presents a Time

Chart in this case

Limitless options for

rendering business-related

content in a search

Tab interface presents a

Document List

Document List in this case

from Worksite

Client Example 1

Sheppard Mullin – SharePoint Search

DO

• Use the best of what SP

Offers (e.g. Lists, Search)

• Configure with tools instead

of custom code/script (when

possible)

• PERSONALIZE

• Integrate as much as makes

sense for richer experience

• Focus on presentation

Best Practices in “Going Beyond the Box” with SharePoint DO’s and DON’Ts

DON’T

• Build “Because You Can”

• Think in “web parts”

• Give them the same thing in

a different color box

• Build Rome in a day

• Think native SharePoint has

to be the best answer

• Think you’re finished

We’ll now open it up for questions

Questions

Thank You