Professional Documents
Culture Documents
Written by Doug Davis, Director of Product Management, Quest Software Contributing Author Adam Woodruff, Solutions Architect, Quest Software
White Paper
WARRANTY
The information contained in this document is subject to change without notice. Quest Software makes no warranty of any kind with respect to this information. QUEST SOFTWARE SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTY OF THE MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Quest Software shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in connection with the furnishing or use of this information.
TRADEMARKS
All trademarks and registered trademarks used in this guide are property of their respective owners. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com e-mail: info@quest.com Please refer to our Web site (www.quest.com) for regional and international office information. UpdatedAugust 2009
WPA-FiveKeys2BuildingShPSites-US-AG
CONTENTS
INTRODUCTION ..........................................................................................1 THE SHAREPOINT FRUSTRATION PROGRESSION ........................................2 KEY 1: LEVERAGE WEB PARTS WHEREVER POSSIBLE..................................5 THE CASE FOR ADDITIONAL WEB PARTS ............................................................... 5 QUICKLY UNLOCKING SHAREPOINTS FULL POTENTIAL ............................................... 6 1. I just want to combine and enhance information in SharePoint............ 7 2. I want to enhance the user interface and develop applications. ........... 7 3. I want to use SharePoint to front-end my external data, and write back to the external databases from SharePoint......................... 8 KEY 2: USE SIMPLER DEVELOPMENT INTERFACES ......................................9 CONFIGURE RATHER THAN CODE ........................................................................ 9 KEY 3: BUILD UPON THE STRENGTHS OF SHAREPOINT ............................. 11 KEY 4: STOP WORRYING ABOUT WHERE THE DATA LIVES ........................ 13 KEY 5: DONT REINVENT THE WHEEL ........................................................ 15 CONCLUSION ............................................................................................ 16 ABOUT THE AUTHORS ............................................................................... 17 ABOUT QUEST SOFTWARE, INC. ................................................................ 18 CONTACTING QUEST SOFTWARE ....................................................................... 18 CONTACTING QUEST SUPPORT ......................................................................... 18
White Paper
INTRODUCTION
SharePoint is an excellent collaboration platform out of the box, with the added promise of allowing organizations to build business applications on its foundation. In fact, many organizations are thinking beyond using SharePoint just as a document repository and a place for team sites. They are considering (and using) SharePoint for: Hosting simple interfaces for their business applications Re-platforming applications that are based on aging technologies Building new applications as alternatives to .NET development Doing advanced project management portals and other core sites Pushing the collaboration envelope well beyond traditional methods
But using SharePoint beyond its out-of-the-box capabilities to create complex applications can be tedious, cost-prohibitive, time-consuming and, for some, even impossible. To deliver on the promise of SharePoint application development, most organizations are forced to rely on custom coding, with its inherent learning curve, costs and project delays. As long as SharePoint application development is dependent on custom coding, SharePoint cannot be the low-cost platform for rapid application creation that organizations envisioned when they invested in it. A core challenge for many organizations adopting SharePoint is that even basic development tasks can require a major investment in time and resources. Once SharePoint is entrenched in an organization, and its usage requirements become more complex, much more work must be devoted to satisfying those requirements. This paper will first explain how frustrations arise as usage requirements become more complex, then provide guidance to help you address these frustrations.
Unlocking the full potential of SharePoint may not mean creating a customer relationship management (CRM) system, help desk application or project management portal for your organization. It might be simply combining information to improve efficiency of daily tasks so that anybody can take advantage of it. Complex SharePoint usage can include seemingly simple tasks, such as: Enhancing, combining and viewing information Rolling up multiple lists into a report or a 3-D chart Creating a hierarchical list view Modifying information within lists across sites Copying or moving documents between document libraries Creating advanced forms with tabs Improving the flow of actions in an application Combining SharePoint data and external data into sites
Take the basic example below. This site was built in about 15 minutes without any additional Web Parts or coding. The result is a useful site for file sharing and basic collaboration, and may be all an organization needs initially.
White Paper
But satisfaction can quickly lead to frustration as usage and demand for complexity grows.
You can eliminate this frustration by following five key guidelines for building better SharePoint sites, with more speed and simplicity than you ever imagined. These five keys will help you unlock the full value of SharePoint for your organization to get the most out of your SharePoint investment and provide a richer user experience for everyone. The results will be that: IT can deliver SharePoint as a service to the organization Business owners get as much as they need from SharePoint and can use it as a reliable tool to efficiently manage projects Developers deliver value of SharePoint faster, then can focus on higherend coding (rather than tedious SharePoint tweaks)
White Paper
However, each of these Web Parts is only a piece of the puzzle and each comes with caveats. One good example of this is the native discussion Web Part ,which does not track discussions intuitively and often introduces more confusion than help. Each web part has both the data and the presentation layer bound to the information that it is displaying, which will not allow for a combination of data from multiple lists into a single view. What is commonly known as a parent-child relationship is not possible in this locked-down dynamic.
While you can get some Web Parts from various sources, it often makes sense to use a combined set of them to get more from your application. Thats because many of the elements and design parameters will be the same from Web Part to Web Part, and they may even be integrated with one another and designed to work in tandem.
5
Notice the dramatic change in whats possible in such a short amount of time. The power of these Web Parts increases your organizations ability to deliver SharePoint as a service and improves the business owners satisfaction level (with having all data in one place). And this site was built without coding! The user-friendly Web Parts enables power users, business analysts and developers to make changes like this and other SharePoint enhancements on the fly. The Quest Web Parts solution includes 18 Web Parts, three application templates, computer-based training, free trial downloads of industry-leading workflow software, and more. Lets take a closer look at them based on what your organization wants to do.
White Paper
1.
WEB
KEY CAPABILITY
Allows you to easily combine data from multiple lists, even across sites, site collections and Web applications Allows you to create compelling 2-D or 3-D charts with information from multiple lists, even lists in different sites, site collections and Web applications Allows you to combine all your calendars into one view, including data from non-calendar lists Allows you to view data in Microsoft Excel, based on criteria passed from qListView, even when that data is not shown in the qListView Allows you to view the topic and responses of multiple discussion lists in one tree view and preview the selected item in a preview panel
2.
QUEST WEB PART qListForm qSelector qMultiSelector qItemDisplay qPanelMenu qCascadingMenu qCaptionDisplay qHelpLink qPageRedirector
KEY CAPABILITY Provides a more advanced and capable list form, including functionality for separating form into tabs and creating space Displays data from a SharePoint list in a drop-down control Allows you to view master-detail data in multiple selectors Allows you to view a single item that has been selected in the qSelector, qListView or qListForm Allows you to have a collapsible and hierarchical panel menu for better navigation Provides a hierarchical menu system, letting you create complex menus that occupy minimum screen real estate Displays a message from a centralized SharePoint list, which allows you to maintain the content of the message easily Facilitates linking to a help file for your application Allows you to redirect a user to a specific page based on the mapping specified in the page redirector list
3.
I want to use SharePoint to front-end my external data, and write back to the external databases from SharePoint.
The following Quest Web Parts enable easy data integration, including read/write capability, even in WSS. Its true.
KEY CAPABILITY Displays data from your external data source in a grid and allows you to execute some actions on the data Allows you to create, view and edit your external data in a form Allows you to display your external data in a compelling 2-D or 3-D charts Allows you to display your external data in a dropdown control
The functionality provided in these 18 Web Parts is essential for getting the most from your SharePoint investment. Youd think most of it would natively come with SharePoint, but it doesnt. You might be able to create and design many of these elements using advanced tools such as SharePoint Designer and Visual Studio, but the time required to do so can be prohibitive and these design tools are not for novice users.
White Paper
Figure 1: Quests ezEdit configuration interface radically simplifies Quest Web Part configuration, allowing non-developers to quickly and easily create menus, dashboards, charts and more. For the developer, ezEdit accelerates tedious tasks, but also exposes the code in cases where that is preferred.
10
White Paper
11
InfoPath, with all its strengths, does not allow you to display data across multiple tabs. This need is real for most organizations and has traditionally been filled by a developer creating an ASP.Net form. Quest Web Parts provide the alternative to custom development. With Quest Web Parts, the end user, business analyst or even developer can consolidate data, create a place to enter additional data, and update it as needed across those multiple locations, without coding. This building block of application development without coding allows you to present any datasuch as that related to the help desk, human resources and customer relationship managementon the fly.
12
White Paper
13
Figure 3: The Quest SI Web Parts simplify the process of connecting to external data and bringing it into SharePoint. And besides bringing in the data, you can use that data, edit it, chart it and create meaningful applications.
14
White Paper
15
CONCLUSION
SharePoint is an excellent collaboration platform environment out of the box, with the added promise of allowing organizations to build business applications. But most organizations are forced to rely on custom development coding, with its inherent learning curve, costs and project delays. This paper discussed how frustrations arise as usage requirements become more complex, then explained how you can eliminate this frustration by following five key guidelines for easily building better SharePoint sites without custom coding. Central to these five guidelines are Quest Web Parts, which offer value and capabilities far beyond whats available in native tools. Leveraging Quest Web Parts will help you get the most out of your SharePoint investment and provide a richer user experience for everyone.
16
White Paper
Doug Davis
Since 1999, Doug Davis has held senior positions at Quest Software in development, research and now product management. He is currently the director of product management for Quest's SharePoint group. Prior to joining Quest, Doug spent seven years as a network administrator for Stentor Canada and Telesat Canada. Doug graduated from Carleton University in Ottawa Canada.
17
Web site:
Please refer to our Web site for regional and international office information.
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf
18