The Information Worker, Forms and More in a SharePoint 2013, Office 365, and post InfoPath world WES PRESTON

Abstract Within the Information Worker scope, plan for transitions in SharePoint 2013 as InfoPath sunsets, IW tools transform and 'Cloud' gains focus. We'll connect some of the dots for the no-code solution areas of your roadmap for SharePoint. An overview for SharePoint platform decision- makers and managers of Information Workers.

Wes Preston Independent Consultant Owner of TrecStone Information Worker, Business Analyst No-code/low-code solutions for business SharePointing since linkedin.com/in/wpreston

Agenda Quick Intro Background InfoPath Other Information Worker Tools References & Questions

Background

Roles Users Information Workers Information Workers / Power Users “+” Developers There are a LOT of tools, for a lot of use-cases.

No-Code Solutions (IW) Simple single-list solutions  complex multi-list dashboards using connected web parts Simple InfoPath forms  complex InfoPath applications (often “DGWHID” applications) Simple Data Views with SharePoint Designer SharePoint Designer Workflows Access Services BDC/BCS Solutions with SharePoint Designer 3 rd party web parts 7 7

“Code” Solutions (IW+) Defined by who you talk to – and their comfort zone with code Complex Data Views & Forms with SharePoint Designer HTML/CSS/JavaScript in a Content Editor Web Part ‘Simple’ Client Side Rendering (CSR) using JS Link ‘Advanced’ Access Services solutions HTML, JavaScript, CSS 8 8

Code Solutions (Dev) Custom Web Parts Custom Application Pages Custom Workflows Event Receivers InfoPath Code Behind Full Trust Solutions / Sandbox Solutions (2010).NET, Visual Studio 9 9

InfoPath -> ?

InfoPath Staying alive – on life support - Through 2023 No single tool to replace the functionality Functionality to be replaced on a scenario by scenario basis InfoPath 2013 Client is last release of client software InfoPath Forms Services: last release as part of SharePoint 2013 ◦SharePoint (on premises) 201x (2015/2016?) will not have it. InfoPath Forms Services on Office 365 ◦Will function ‘until further notice’ 11

InfoPath – Now What? It depends. How are you using InfoPath? - Code-behind vs. no-code What platform are you on? – On Prem vs. Office 365 What skill sets and experience do you have available to you? ◦No-code Info Worker ◦SharePoint Lists, Access Services, Excel Surveys ◦‘Lite-code’ Info Worker / Power User ◦More complex Access Services, ‘Simple’ CSR ◦Custom ◦JavaScript,.NET ◦3 rd Party platforms and tools

Streamlined technical product roadmap Ref #SPC348

Excel Surveys – “FoSS” “Forms on SpreadSheets” Already available ◦Available on OneDrive ◦Available on O365 Creates content, columns, etc. within an Excel file

Forms on SharePoint Lists - “FoSL” Coming soon – Release 1: “Mid to Late 2014” Only available on Office 365, until next server version release (‘2016’?) Replaces some of the capabilities SPD had pre-2013 ◦Move and hide fields ◦Nicer interface and assist tools Access Forms Package ◦Design within the web interface – no client app required The new approach to new functionality deployment ◦More on this in a second…

Sidebar… New Approach Microsoft’s current focus is cloud-based services ◦New features will be available on Office 365 first ◦New features will come at a faster rate ◦On premises releases will still be 2-3 years apart – wait for the new stuff New solutions more Mobile-friendly Traditional design and release approach has ‘flipped’ ◦Looking for constant feedback – UserVoice -> “Continuous Improvement” ◦Able to adjust direction to adapt to customer needs ◦No More - Strict focus on 2-3 yr. release cycle and vision locked in features early

Ref #SPC348

Structured Documents Microsoft Word High Fidelity – Printer-friendly format More direction coming by end of 2014 ◦Where will the data be stored? -> TBD ◦Still determining how this will integrate with SharePoint…

Access Web Apps Requires ◦Access Services (SharePoint Server Enterprise licensing) ◦or Office 365 – ANY license Benefits ◦Multiple forms ◦Relational Data ◦Transactions Limitations ◦No workflow ◦Very limited integration with the host SharePoint site All new in 2013 – now creates SharePoint Apps Data stored in SQL Server or SQL Azure, not Lists!

Action Items Watch the SPC348 presentation on Channel9 POCs – Try out what’s available NOW ◦Excel surveys ◦Access Services 2013… no, seriously Start thinking about governance ◦Which tool/approach to which use-case in your environment Give Microsoft feedback – UserVoice ◦

Development - Forms New web standards approaches supported in SharePoint 2013 ◦HTML, JavaScript, CSS Visual Studio.NET ◦Apps.NET with Wizards to get started ◦Napa ◦LightSwitch

3 rd Party Additional, and sometimes substantial, costs. But generally a lot of effort already invested in UI, usability, upgradability (to later versions of their products). ◦K2 ◦Nintex ◦Formotus ◦Qdabra ◦Emgage Turbo ◦and others…

FAQ Ref #SPC348

Other Notes SHAREPOINT

SharePoint Designer WYSIWYG interface removed ◦Data View / Form Web Parts (conditional formatting) ◦Visual Dashboard development Workflow still there BCS still there List and Content Type management still there

Client Side Rendering (CSR) Override default templates for list rendering ◦Use JavaScript to override how a view is displayed ◦Can leverage the JSLink property of a List View Web Part Replacement for XSLT customizations in Data View Web Parts

Resources SharePoint Conference 2014 Videos InfoPath Roadmap session: Conference/2014/SPC348 Conference/2014/SPC348 MNSPUG Presentation on Access Solutions: %202014%20MNSPUG%20Content.pptx %202014%20MNSPUG%20Content.pptx My Blog

Call to action! Speak your mind at: OfficeForms.UserVoice.Com MSAccess.UserVoice.Com OfficeSPDev.UserVoice.Com Solve your roadblocks on StackOverflow [Office][Office] and [SharePoint][SharePoint]