Export (0) Print
Expand All

Plan for Project Server 2010 Web Parts

 

Applies to: Project Server 2010

Topic Last Modified: 2013-03-28

Microsoft Project Server 2010 is built on SharePoint Products architecture. Users who access Project Server 2010 through the Web interface (Microsoft Project Web App) are using pages that are composed of Web Parts, which are modular elements that present information on SharePoint pages.

A Web Parts page is an ASP.NET Web page that includes Web Parts controls that let users personalize the page, such as selecting the information to display. In SharePoint Products 2010, a Web Parts page can be used to combine data, such as lists and charts, and Web content, such as text and images, into a dynamic information portal. Web Parts are server-side controls that provide functionality to a site page. For example, the default Project Web App home page is a Web Parts page that contains the PWA Reminders Web Part and also contains room for additional Web Parts to be added.

Project Server 2010 includes a set of Web Parts that users can add to farm Web site pages after the product is installed. If an organization needs custom Web Parts, a developer can write custom ASP.NET Web Parts and ask you to install them to a deployment of Project Server 2010. This process should include testing and approval of code before the Web Parts are deployed.

For more information about how to develop Web Parts for Project Server 2010, see Developing Project Server 2010 Web Parts (http://go.microsoft.com/fwlink/p/?LinkId=204589) in the Project 2010 SDK in the MSDN Library Online.

For more information about how to manage Web Parts pages in SharePoint Server 2010, see Manage Web Parts (SharePoint Server 2010).

This article contains the following sections:

For more information about Project Web App Web parts in Project Server 2010, see the following articles:

There are 18 Web Parts that are installed with Project Server 2010 that provide Project Server 2010 functionality. They are available in the Web Parts Gallery in the Project Web App category folder. The following table describes the 18 predefined Web Parts that are available with your Project Server 2010 installation.

 

Web Part name Description

Approval Center

Displays task updates for approval and rejection submitted to you by team members.

Issues

Displays active issues that are assigned to you.

My Queued Jobs

Displays queue status for jobs generated by you.

My Schedule

Displays a calendar view of tasks assigned to you.

My Tasks

Displays tasks assigned to you.

My Timesheet

Displays your timesheet information.

Project Center

Displays a list of projects on the server.

Project Details

Displays more information about specific projects on the server.

Project Fields

Displays a list that may consist of project custom fields, project summary fields, and project inherent fields such as project name, description, or owner. The list is editable. This Web Part can only be used within the Project Detail Pages infrastructure.

Project Fields (Backwards Compatible)

Displays all enterprise custom fields except fields whose behavior is controlled by workflow. Use this Web Part to emulate the "Edit Project Properties" page used in Microsoft Office Project Server 2007. This Web Part can only be used within the Project Detail Pages infrastructure.

Project Sites

Displays a list of project sites that are available to each user. This Web Part can only be used within the Project Detail Pages infrastructure.

Project Strategic Impact

Displays the business driver ratings information for a project. This Web Part can only be used within the Project Detail Pages infrastructure.

Reminders

Displays a list of user item reminders.

Resource Assignments

Displays assignment information where the resources have been assigned.

Resource Center

Displays a list of resources on the server.

Risks

Displays active risks that are assigned to you.

Team Tasks

Displays team assignments.

Workflow Status

Displays workflow status information for a project. This Web Part can only be used within the Project Detail Pages infrastructure.

noteNote
As noted in this table, some Project Web App Web Parts can only be used within Project Details Pages (PDPs). Project Detail Pages are Web Parts pages in Project Server 2010 that can be used to display or collect information from the user. They are used in different stages of the Demand Management feature in Project Server 2010. For more information about Demand Management, see the Demand Management in Project Server 2010 Resource Center (http://go.microsoft.com/fwlink/p/?LinkId=204588).

Project Web App Web Parts can be integrated into Web Parts pages in several scenarios. The following table specifies which scenarios are supported and not supported for the integration of PWA Web Parts.

noteNote
For the purposes of this example, http://contoso/PWA is considered the PWA root site.

 

Scenario Supported Not supported

Non-Project site in the Project Web App site collection. (For example, http://contoso/PWA/Proj1TeamBuilder.)

X

Project site in the Project Web App site collection. (For example, http://contoso/PWA/Project1ProjectWorkSpace.)

X

Site that is not in the Project Web App site collection. (For example, http://contoso/SharePointSite1.)

X

Site that is located on a different Project Web App instance. (For example, http://contoso/PWA1 using a PWA Web Part to view data in http://contoso/PWA.)

X

Site on a different SharePoint farm. (For example, http://liteware/PWA trying to use a PWA Web Part to view PWA data in http://contoso/PWA.)

X

You cannot use Web Parts to view Project Server 2010 data from a different farm. For example, you cannot use a Project Center Web Part from Farm A on a Web site that is located on Farm B.

noteNote
For information about resolving Project Web App Web Parts issues that can occur in Web Part integration scenarios after you upgrade to Project Server 2010, see Upgrade considerations for Project Web App Web Parts.

The SimpleUI parameter is a URL option that can be used to hide or show parts of pages in Project Web App. URL options can reduce the amount of screen space that Project Web Access uses or simplify the page view for different user tasks. The SimpleUI parameter enables you to remove common elements in Project Web App pages so that the page display matches your user requirements. For example, changing the Project Web App home page URL from http://contoso/pwa/default.aspx? to http://contoso/pwa/default/aspx?simpleUI=31 removes six common elements from the page and enables you to only view the Notifications Web Part and part of the server ribbon. Other SimpleUI= parameter values (ranging from 0-30) remove other common elements from the Project Web App page, although use of these values is unsupported (with the exception of SimpleUI=16, which returns your pages to the default view.).

importantImportant
The only SimpleUI parameter that is supported is SimpleUI=31. When you use SimpleUI=31 in the Page Viewer Web Part to view Project Web App sites, part of the server ribbon (the status bar) will appear within the display in the IFrame.
importantImportant
The SimpleUI=31 value, once set, will persist across all PWA pages in the site collection. This also applies to the SimpleUI=16 value.

For more information about the SimpleUI parameter, see the MSDN article URL Options: Modifying the Query String Parameters (http://go.microsoft.com/fwlink/p/?LinkId=204590).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft