Implementing the Solution

This section walks through each requirement and implements each element outlined in the solution overview.

Enabling self-service site creation

We want to encourage team and project collaboration for employees by allowing employees to create their own WSS sites. Configuring this setting involves two steps:

To turn on self-service site creation in Central Administration, follow these steps:

To configure the permissions of the portal so that users with rights to contribute can also create sites, follow these steps:

Modify site directory categories

To ensure that sites that users create are findable, you are going to modify the categories that were provided by the site directory to match the structure of your organizational groups and roles, so that users provide this information when they create sites.

To modify the site directory categories, follow these steps:

1.	Navigate to the site directory and click View All Site Content from the Quick Launch navigation.
2.	Select Sites in the Lists section.
3.	From the Settings menu, choose List Settings.
4.	Click Division in the Columns section.
5.	Modify the choices by replacing the default choices with the following values entered on a separate line: Accounting Administration AppDev Consulting Cross-Functional Executive Networking Consulting PM Recruiting SI Consulting Sales
6.	Specify that the column requires information, as shown in Figure 21.2. Figure 21.2. Modifying the division column to require information [View full size image]
7.	Click OK.
8.	Click Region in the Columns section. Because this company is located only in one region, you are going to reuse this column to reflect what type of site is being created.
9.	Change the Column name field to Site Status.
10.	Modify the choices by replacing the default choices with the following values entered on a separate line: Active Closed Resource
11.	Click OK.
12.	Use the breadcrumb to click back to the home page of the site directory site and you will see the modified categories displayed, as shown in Figure 21.3. Figure 21.3. Viewing the modified categories for the site directory [View full size image]

Creating a Wiki site collection

To support the unstructured collaboration and communication, you should create a Wiki site collection for users to provision Wiki sites and blogs. Implementing this objective involves three high-level tasks:

This section breaks each of these high-level tasks into detailed steps.

To create a new managed path for your wikis namespace, follow these steps:

1.	Open the central administration site for the portal and click the Application Management tab.
2.	Click Define managed path in the SharePoint Web Application Management section.
3.	Select your port 80 Web Application in the Web Application section.
4.	Enter wikis in the Path field and select Wildcard inclusion in the type section, as shown in Figure 21.4 Figure 21.4. Defining a new managed path [View full size image]
5.	Click OK to add the managed path.

To create a new site collection and site directory in your new managed path, follow these steps:

1.	Open the central administration site for the portal and click the Application Management tab.
2.	Click Create site collection in the SharePoint Site Management section.
3.	Select the port 80 Web application in the Web Application section.
4.	Enter a title in the Title field.
5.	Select wikis in the URL pull-down and enter team for the URL, as shown in Figure 21.5. Figure 21.5. Creating a new site collection for your unstructured collaboration in the wikis namespace [View full size image]
6.	Click the Enterprise tab and select the Site Directory template for the site.
7.	Enter primary and secondary site administrators, making sure to include yourself as one or the other so that you have access to the site.
8.	Click OK.

To modify the site templates available for subsite creation from the site directory, follow these steps:

1.	From the home page of the new site directory in the wikis namespace, click Site Actions.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Select Page layouts and site templates from the Look and Feel section.
4.	Select the Subsites can only use the following site templates radio button.
5.	Add Wiki Site and Blog, as shown in Figure 21.6. Figure 21.6. Restricting the subsites to only the Wiki site and blog templates. [View full size image]
6.	Click OK.

Creating a custom sales pipeline list

To track sales opportunities, you are going to create a custom SharePoint list for the inside and outside sales people to use. The customer contacts are stored in a SQL Server database used by the CRM application, so that you have three high-level steps for implementing the custom sales pipeline list:

Creating a BDC application definition for customer contacts

The BDC application definition enables you to refer to the customer contacts in your sales pipeline list. To enable this functionality, first create an application definition file and then import it to your shared service provider.

The following code is used in the Application Definition XML file:

   <?xml version="1.0" encoding="utf-8" standalone="yes"?>
   <LobSystem xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://schemas.microsoft.com/office/2006/03/B
   usinessDataCatalog BDCMetadata.xsd" Type="Database"
   Version="1.0.0.1" Name="Contacts"
   xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCa
   talog">
     <Properties>
       <Property Name="WildcardCharacter"
   Type="System.String">%</Property>
    </Properties>
     <LobSystemInstances>
       <LobSystemInstance Name="CRM Contacts">
         <Properties>
           <Property Name="Authentication Mode"
   Type="System.String">PassThrough</Property>
                 <Property Name="DatabaseAccessProvider"
   Type="System.String">SqlServer</Property>
           <Property Name="RdbConnection Data Source"
   Type="System.String">servername</Property>
           <Property Name="RdbConnection Initial Catalog"
   Type="System.String">CRMtest</Property>
            <Property Name="RdbConnection Integrated Security"
   Type="System.String">SSPI</Property>
            <Property Name="RdbConnection Pooling"
   Type="System.String">false</Property>
         </Properties>
       </LobSystemInstance>
     </LobSystemInstances>
     <Entities>
       <Entity EstimatedInstanceCount="1000" Name="Contact">
         <Properties>
           <Property Name="Title"
   Type="System.String">LastName</Property>
         </Properties>
         <Identifiers>
           <Identifier TypeName="System.Int32" Name="tp_ID" />
         </Identifiers>
         <Methods>
           <Method Name="GetContacts">
             <Properties>
               <Property Name="RdbCommandText" Type="System.String">

                   select tp_ID
                   , Modified
                   --, tp_Editor
                   , LastName
                   , FirstName
                   , FirstName + ' ' + LastName as FullName
                   , Customer
                   , email
                   , workphone

                   from Contacts_VW
                   Where lastName like @lastName And firstName like
   @firstName AND tp_id = Case When @tp_ID = 0 then tp_ID else
   @tp_ID End

                    </Property>
               <Property Name="RdbCommandType"
   Type="System.Data.CommandType, System.Data, Version=2.0.0.0,
   Culture=neutral, PublicKeyToken=b77a5c561934e089">Text</Property>
             </Properties>
             <FilterDescriptors>
               <FilterDescriptor Type="Comparison" Name="tp_ID" />
               <FilterDescriptor Type="Wildcard" Name="LastName">
                 <Properties>
                   <Property Name="UsedForDisambiguation"
   Type="System.Boolean">true</Property>
                   <Property Name="Comparator"
   Type="System.String">Equals</Property>
                   <Property Name="IsDefault"
   Type="System.Boolean">true</Property>
                 </Properties>
               </FilterDescriptor>
               <FilterDescriptor Type="Wildcard" Name="FirstName">
                 <Properties>
                   <Property Name="UsedForDisambiguation"
   Type="System.Boolean">true</Property>
                 </Properties>
               </FilterDescriptor>
             </FilterDescriptors>
             <Parameters>
               <Parameter Direction="In" Name="@tp_ID">
                 <TypeDescriptor TypeName="System.Int32"
   IdentifierName="tp_ID" AssociatedFilter="tp_ID" Name="tp_ID">
                   <DefaultValues>
                     <DefaultValue
   MethodInstanceName="ContactFinderInstance"
   Type="System.Int32">0</DefaultValue>
                   </DefaultValues>
                 </TypeDescriptor>
               </Parameter>
               <Parameter Direction="In" Name="@lastName">
                 <TypeDescriptor TypeName="System.String"
   AssociatedFilter="LastName" Name="LastName">
                   <DefaultValues>
                     <DefaultValue
   MethodInstanceName="ContactFinderInstance"
   Type="System.String">%</DefaultValue>
                     <DefaultValue
   MethodInstanceName="ContactSpecificFinderInstance"
   Type="System.String">%</DefaultValue>
                   </DefaultValues>
                 </TypeDescriptor>
               </Parameter>
               <Parameter Direction="In" Name="@firstName">
                 <TypeDescriptor TypeName="System.String"
   AssociatedFilter="FirstName" Name="firstName">
                   <DefaultValues>
                     <DefaultValue
   MethodInstanceName="ContactFinderInstance"
   Type="System.String">%</DefaultValue>
                     <DefaultValue
   MethodInstanceName="ContactSpecificFinderInstance"
   Type="System.String">%</DefaultValue>
                   </DefaultValues>
                 </TypeDescriptor>
               </Parameter>
               <Parameter Direction="Return" Name="Contacts">
                 <TypeDescriptor TypeName="System.Data.IDataReader,
   System.Data, Version=2.0.3600.0, Culture=neutral,
   PublicKeyToken=b77a5c561934e089" IsCollection="true"
   Name="ProductDataReader">
                   <TypeDescriptors>
                     <TypeDescriptor
   TypeName="System.Data.IDataRecord, System.Data,
   Version=2.0.3600.0, Culture=neutral,
   PublicKeyToken=b77a5c561934e089" Name="ProductDataRecord">
                       <TypeDescriptors>
                         <TypeDescriptor TypeName="System.Int32"
   IdentifierName="tp_ID" Name="tp_ID">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName
   LCID="1033">tp_ID</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                           <Properties>
                             <Property Name="DisplayByDefault"
   Type="System.Boolean">true</Property>
                           </Properties>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="FirstName">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName LCID="1033">First
   Name</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                           <Properties>
                             <Property Name="DisplayByDefault"
   Type="System.Boolean">true</Property>
                           </Properties>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="LastName">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName LCID="1033">Last
   Name</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                           <Properties>
                             <Property Name="DisplayByDefault"
   Type="System.Boolean">true</Property>
                           </Properties>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="FullName">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName LCID="1033">Full
   Name</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                           <Properties>
                             <Property Name="DisplayByDefault"
   Type="System.Boolean">true</Property>
                           </Properties>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="email">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName
   LCID="1033">email</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="Customer">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName
   LCID="1033">Customer</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                         </TypeDescriptor>
                         <TypeDescriptor TypeName="System.String"
   Name="workphone">
                           <LocalizedDisplayNames>
                             <LocalizedDisplayName
   LCID="1033">workphone</LocalizedDisplayName>
                           </LocalizedDisplayNames>
                         </TypeDescriptor>
                       </TypeDescriptors>
                     </TypeDescriptor>
                   </TypeDescriptors>
                 </TypeDescriptor>
               </Parameter>
             </Parameters>
             <MethodInstances>
               <MethodInstance Type="Finder"
   ReturnParameterName="Contacts"
   ReturnTypeDescriptorName="ProductDataReader"
   ReturnTypeDescriptorLevel="0" Name="ContactFinderInstance">
               </MethodInstance>
               <MethodInstance Type="SpecificFinder"
   ReturnParameterName="Contacts"
   ReturnTypeDescriptorName="ProductDataReader"
   ReturnTypeDescriptorLevel="0"
   Name="ContactSpecificFinderInstance">
               </MethodInstance>
             </MethodInstances>
           </Method>
         </Methods>
       </Entity>
       </Entities>
   </LobSystem>

Once you create the XML file using this code, you are ready to import the application definition to your shared service provider. To do this, follow these steps:

1.	Open a browser and navigate to the Shared Services administrator page.
2.	Click Import application definition in the Business Data Catalog section.
3.	Browse or enter the path to your application definition file in the Application Definition section, as shown in Figure 21.7. Figure 21.7. Configuring the BDC columns for the sales pipeline list [View full size image]
4.	Select Model in the file type section.
5.	Select Localized Names, Properties, and Permissions in the Resources to import section.
6.	Click Import.

Creating sales pipeline list

After you have added the BDC application definition, you are going to create the sales pipeline list to track opportunities with these fields:

• Opportunity Name

• Contact Name, phone number, e-mail, company name (from BDC)

• Consulting Area (AppDev, Networking, or SI)

• Chance of Closing (10, 30, 60, 90, 100)

• Sales Status (in progress, proposal preparation, proposal delivered, won, lost)

• Estimated Revenue

• Account Manager (person)

To create the sales pipeline list, follow these steps:

To add your columns to the sales pipeline custom list, follow these steps:

Creating sales pipeline list views

You are going to create two views for the sales pipeline list. The first groups and totals all active opportunities (not won or lost) by consulting area and chance of closing and will be used on the sales home page. The second view shows each sales person which opportunities are in his or her pipeline.

To create the Active Opportunities view, follow these steps:

1.	From the View menu in the upper right corner of the list, choose Create View.
2.	Choose Standard View.
3.	Enter Active Opportunities as the view name and select Make this the default view.
4.	Deselect Attachments, Contact:email, Contact:workphone, Consulting area, and Chance of Closing fields in the Columns section.
5.	Select Estimated Revenue in the Sorting column and select Show items in descending order.
6.	In the Filter section, select Show items when the following is true and select Sales Status is not equal to lost and Sales Status is not equal to won, as shown in Figure 21.8. Figure 21.8. Configuring the filter values for the Active Opportunities view [View full size image]
7.	Expand the Group By section and select Chance of Closing in descending order as the first group-by field, and Consulting Area in ascending order as the second group by field.
8.	Select Expanded in the By default, show groupings field.
9.	Expand the Totals section and choose Sum for the Estimated Revenue field.
10.	Click OK.
11.	Review your new default view, as shown in Figure 21.9. Figure 21.9. The Active Opportunities view of the sales pipeline list [View full size image]

To create the My Opportunities view, follow these steps:

Standardizing project documentation

To ensure that documentation is tagged consistently across projects, and that project templates are standardized across the organization and easily updated from a central location, you are going to create a content type for project documentation (the statement of work, in this case) and a template site for projects. This process involves several steps:

Creating site columns

To create the site columns that will provide the metadata for the statement of work project documentation, follow these steps:

You can create additional site columns for your other project documentation if desired.

Creating a site content type

In this section, you create a site content type using the site column(s) you created in the previous section.

1.	From the home page of the top-level site of the portal, click Site Actions.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Under Galleries click Site content types.
4.	Click Create.
5.	Enter these values:
6.	Click OK.
7.	At the bottom of the Site Content Type: Statement of Work page, click Add from existing site columns.
8.	From the Select columns from: pulldown, choose Project Management.
9.	Click the Add button to add the Project Status column (see Figure 21.10). Figure 21.10. Add columns to the Site Content Type: Statement of Work page. [View full size image]
10.	Click OK.

Adding a template to the content type

Adding a template to a site content type allows you to associate a document with the content type. If you update the document template, you can update it at the content type and all new content types will then use the updated template.

1.	From the home page of the top-level site of the portal, click Site Actions.
2.	Choose Modify All Site Settings from the Site Settings menu.
3.	Under Galleries click Site content types.
4.	Click the Statement of Work content type.
5.	In the Settings section, click Advanced settings.
6.	Select Upload a new document template and browse to your SOW template.
7.	Select Yes in the Should this content type be read-only? field so that only administrators can modify the statement of work content type, as shown in Figure 21.11. Figure 21.11. Associating a template with the content type [View full size image]
8.	Click OK.

Creating a Project Team site

You must add the statement of work content type in a project site so that site can be used as a project site template. To create and customize this site, follow these steps:

Creating a custom site template for projects

Now that you have created a project site and added the Statement of Work content type, create a site template from that site so that all new project sites can be provisioned with that content type already added. To do this, follow these steps:

1.	From any page in the project site, click Site Actions from the upper-right corner.
2.	Choose Site Settings.
3.	Click Save site as template in the Look and Feel section.
4.	Enter Projects in the File name field.
5.	Enter Projects in the Template name field and a description, as shown in Figure 21.13. Figure 21.13. Creating a new site template [View full size image]
6.	Click OK.
7.	To confirm that your template has been added to the site template gallery for the site directory, browse to the site directory home page.
8.	Click Create Site.
9.	You should see a new tab for Custom that contains the Projects template, as shown in Figure 21.14. Figure 21.14. Viewing the new project template [View full size image]

Create project status tracking for PMs

You can now build out the lists that will be used for project managers and executives to track project activity and status. There are three components to this process:

Creating a project status list

To track active projects, you must create a project list that provides all the key information for projects that you are delivering on. This list will track:

• Project name: Name of project.

• Contact: The customer contact stored in the CRM database and accessible to the project list by use of the BDC app definition that you created and added in the sales pipeline section of this chapter.

• Project code: Unique code for each project that will be used in this project list and in the accounting and time tracking systems to identify projects.

• Consulting Area: Selection of primary group that is responsible for the project from the values provided by the site column you created in the sales pipeline section of this chapter.

• Project Status: Choice of Active, Closed, and Waiting for Signoff.

• PO Number: Reference to the PO number provided by the customer.

• PO Amount: Amount of project.

• Project Manager: Choice of project manager alias.

To create this list, follow these steps:

To add your columns to project status custom list, follow these steps:

Creating the milestone tracking list

The milestone tracking list provides a place where project managers can enter and track milestones for their projects, and the overall organization can get an idea of upcoming milestones. To create this list, use the Task List template and modify the fields for your purposes.

To create the milestone tracking list, follow these steps:

To customize the columns for your milestone tracking list, follow these steps:

1.	Open the milestone tracking list and choose List Settings from the Settings menu.
2.	Select the Title column. Change the Column name to Milestone Name.
3.	Click OK.
4.	Click the Assigned To field and rename to Project Manager.
5.	Click OK.
6.	Click the Task Group field and select Delete.
7.	Click OK to confirm deletion.
8.	Click Create column.
9.	Enter Project Code as the Column name and select Lookup as the column type.
10.	Select Project status as the Get information from field and Project code as the In this column field, as shown in Figure 21.15. Figure 21.15. Creating a lookup field for project code [View full size image]
11.	To add the Consulting Area column, select Add from existing site columns in the Columns section.
12.	Select Consulting Area from the Available site columns and click Add.
13.	Click OK.

Creating the project central list view

We need to create a view for each of the consulting areas that shows active and upcoming milestones. To create these views, follow these steps:

1.	From the View menu in the upper-right corner of the list, choose Create View.
2.	Select Active Tasks in the Starting from an existing view section.
3.	Enter Active AppDev Milestones as the view name and do not select that it is a default view.
4.	Select Project code in the Columns section.
5.	In the Filter section, add an additional filter for when Consulting Area is equal to AppDev, and make sure that the criteria is set to And between the two filter sections, as shown in Figure 21.16. Figure 21.16. Adding an additional view filter for the Consulting Area [View full size image]
6.	Click OK.
7.	Repeat steps 1 to 5 for the Infrastructure and networking active tasks view, replacing the filter criteria with the appropriate area.

Executive KPIs

The executives want to see a status overview of the sales pipeline and project status to identify areas that might need help and focus. To achieve this objective, you are going to create sales and project KPIs for the Executive Dashboard by following three high-level steps:

Creating the sales views to support KPIs

You need to create four views of the sales lists to support the KPIs you want to configure:

• 60% or higher of closing for all opportunities

• 60% or higher of closing for AppDev opportunities

• 60% or higher of closing for Networking opportunities

• 60% or higher of closing for Infrastructure opportunities

To create these views, follow these steps:

To create the view for each consulting area, follow these steps:

Creating sales KPIs

You will now add a KPI for each view that you created in the previous section.

1.	Navigate to the Management site.
2.	Select View All Site Content in the left navigation.
3.	Select Create in the top navigation bar.
4.	Select KPI List from the Custom List section.
5.	Enter the name of the KPI list as Organizational Indicators and click Create.
6.	Choose Indicator using data in SharePoint list from the New menu.
7.	Enter All Sales Opportunities in the Name field.
8.	Enter the location of the sales pipeline list and select the 60% opportunity view in the SharePoint List and View section, as shown in Figure 21.17. Figure 21.17. Entering the list and view for a KPI [View full size image]
9.	Select Calculation using all the list items in the view and select that you would like to sum the estimated revenue field.
10.	Enter the goal (green) and warning (yellow) values for the organization. This example used 400,000 for the green value and 350,000 for the yellow value.
11.	Enter the link to the sales pipeline view in the Details Link section for drilling down on the indicator.
12.	Click OK. Repeat steps 6 to 12 for the AppDev, Networking, and Infrastructure views/indicators.

Creating projects KPIs

You will now add KPIs for your project milestones. To do this, follow these steps:

1.	Choose Indicator using data in SharePoint list from the New menu.
2.	Enter AppDev Project Status in the Name field.
3.	Enter the location of the milestone tracking list and select the Active AppDev Milestones view in the SharePoint List and View section.
4.	Select Percentage of the list items in the view where and enter % complete is less than 100 and Due Date is less than [Today], as shown in Figure 21.18. Figure 21.18. Calculating percentage of not completed items that are past due [View full size image]
5.	Change the better values to be lower and enter the goal (green) and warning (yellow) values for the organization. This example used 5 (5%) for the green value and 30 (30%) for the yellow value.
6.	Enter the link to the milestone tracking list in the Details Link section for drilling down on the indicator.
7.	Click OK. Repeat steps 1 to 7 for the Networking and Infrastructure views/indicators.

Adding the KPI Web Part to the Management home page

To highlight the importance of the KPI list items, add them to the home page of the management site so that executives can easily see them every time they visit the site. To do this, follow these steps:

1.	Navigate to the home page of the Management collaboration site.
2.	Choose the Site Actions menu, select Edit Page.
3.	Select Add a Web Part in the left zone.
4.	Select Key Performance Indicators from the Dashboard section.
5.	Click Add.
6.	From the Edit menu of the Key Performance Indicator Web Part, select Modify Shared Web Part.
7.	Browse or enter the path to the Organizational Indicators in the Indicator List field.
8.	Select Traffic Lights in the Change Icon field.
9.	Click OK.
10.	Click Exit Edit Mode.
11.	Confirm that the KPI list has been added to the page and looks like Figure 21.19. Figure 21.19. KPI List Web Part on the Management home page [View full size image]

Creating an accounting dashboard

To create a central location so that the accounting department and project managers can see the invoices and time submitted for a project and date range, create an accounting dashboard. This dashboard will use a Datasheet Web Part to display the invoicing data from a SharePoint list and a Report Viewer Web Part to display the time tracking data from an SQL Server database.

You will complete the following high-level tasks to create this dashboard:

Create an invoicing list by importing a spreadsheet

You have an Excel spreadsheet for invoicing data that you will use to create the invoicing list and import the existing data. To do this, follow these steps:

1.	Select View All Site Content from the Quick Launch navigation of the Accounting site.
2.	Select Create in the top navigation bar.
3.	Select Import Spreadsheet from the Custom Lists section.
4.	Enter Invoices as the name for your list and enter or browse to the location of the spreadsheet.
5.	Click Import.
6.	Select Range of Cells in the Range Type Field and then click the – symbol to the right of the Select Range field.
7.	Drag the selector circle around the data that you want to include in your spreadsheet import, and click the icon with the red down arrow to the right of your named range, as shown in Figure 21.20. Figure 21.20. Using the Range Selector to define your spreadsheet import [View full size image]
8.	Click Import.

Publishing a reporting services report to the report library

In this section, you publish the time tracking report with defined parameters for start date, end date, and project code to your report library.

To publish a report to a SharePoint report library, follow these steps:

1.	Open your report project in SQL Server Business Intelligence Development Studio.
2.	Right-click your report and set the path to the report library, as shown in Figure 21.21. Figure 21.21. Setting the publishing URL [View full size image]
3.	From the Build menu, choose Deploy <project name>.

Creating a dashboard page

To create the dashboard page that will host your connected Web Parts, follow these steps:

Implementing the Data View Web Part for the invoicing list

In this section, you use the Data View Web Part to add the invoicing list data to the accounting dashboard. You use the Data View Web Part because a SharePoint list can connect to only one filter and you want to connect to three.

Adding the Report view Web Part and connecting the filters

In this section, you add the Report view Web Part to display your timesheet report and connect the report to the Filter Web Parts so that the Filter Web Parts provide the report parameters. To do this, follow these steps:

Now you are going to add two date filters and a text filter to the dashboard page by following these steps:

To connect the Filter Web Part, follow the steps below:

1.	Open the accounting dashboard page and choose Edit Page from the Site Actions menu in the top right corner.
2.	Select Connections Send Filter Values To [Report Viewer Web Part] from the edit menu of the Start Filter Web Part, as shown in Figure 21.24. Figure 21.24. Configuring the Filter Web Part connections [View full size image]
3.	Select the filter parameter that you want to connect to from the Configure Connection dialog box as shown in Figure 21.25. Figure 21.25. Select the report parameter to which the filter is connected.
4.	Click Finish.
5.	Repeat steps 2 to 4 for connecting both the end date filter and the project number filter to the Report Viewer Web Part.
6.	Repeat steps 2 to 4 for the start date, end date, and project number filter to the Data View Web Parts.
7.	Exit Edit Mode for your page.
8.	Enter a start date, end date, and project number and click Apply Actions to apply filters to the invoice and time information, as shown in Figure 21.26. Figure 21.26. Applying filters to connected Web Parts

Excel Services

This scenario uses Excel Services to expose spreadsheets that are used to track what resource positions have the most bench time. This provides a communication path between the project managers and the recruiting team so that the recruiting team knows what positions to focus on. While you are configuring Excel Services, you are going to add a trusted path for the Accounting library as well because you know that they will be distributing ad-hoc financial reports.

To accomplish your architecture to meet this requirement, you have two high-level steps:

Adding trusted file locations

You are going to add two trusted file locations to the Excel Services configuration—one for the resource management spreadsheet and one for the accounting reports. To add a trusted file location for the resource spreadsheets, follow these steps:

For the accounting spreadsheets, you know that you have a sophisticated group of spreadsheet users that will be accessing data from many different sources. Because of those factors, you are going to add a trusted file location for the accounting site with more external data capability than the settings you used for the resource management spreadsheet. To add a trusted file location for the accounting spreadsheets, follow these steps:

Publishing resource Excel file

Now that you have trusted the document library on the project management site that will store the resource management spreadsheet, you can publish your resource file to the site. However, the spreadsheet has four worksheets that you want to expose, so you will first name those ranges so that the users can flip between them. To do this, follow these steps:

1.	Open the Excel spreadsheet, select the cells that you want to name on the first worksheet, right-click your selection, and choose Name a Range from the menu.
2.	Enter a name (no spaces or special characters allowed) as shown in Figure 21.27. Click OK. Figure 21.27. Named range dialog box [View full size image] Repeat step 2 for the AppDev, Networking, and Infrastructure tabs and ranges.
3.	From the main Excel menu, choose Publish Excel Services.
4.	Enter the URL and file name for your spreadsheet in the File name field, or browse for the site in the Save in field and type the file name in the File name field.
5.	Click Excel Services Options.
6.	In the Show tab, select Items in the Workbook from the drop-down menu and select All Named Ranges, as shown in Figure 21.28. Figure 21.28. Configuring the Excel Services Options [View full size image]
7.	Click OK to exit the Excel Services Options dialog box.
8.	Click Save to publish the file to your SharePoint site.

To add the Excel Web Access Web Part to the recruiting page, follow these steps:

Configuring file share content source

To make the archive content on the file share available, add a content source for that file share and create a search scope for the site collection to expose that content.

To implement the content source for the file share, follow these steps:

To define a scope for your site collection, follow these steps:

You are going to enter keywords because you know that SOWs have also been named Statements of Work in the past and so to ensure that historical SOWs are returned with our newly published SOWs, we add the keywords as detailed in the following steps:

Configure the portal as an extranet portal

To enable consultants to reach the portal content when they are working from home or from a client site, configure your portal as an extranet portal. The server front end will still sit on the corporate network, and the ISA server that provides a network firewall will reverse proxy requests to the SharePoint server.

To configure the portal to enable extranet access, complete the following high-level tasks:

Configuring SSL

To configure SSL, follow these steps:

Creating alternate access mapping

Once you have a SSL enabled on the IIS site, add an alternate access mapping so that the site can be accessed via https. To do this, follow these steps: