Templates versus Project Views for Version 6.1
Project views and Templates both let you customize your work and save time making new graphs or updating existing ones.
Project views and Templates have some similar looking forms, so it is important to understand how they differ and what roles they play.
A Template is a framework from which you create new project views.
It contains no imported tasks or milestones and it is never displayed on the screen as graphics. It is just a convenient way of standardizing the parameters for creating new project views.
The Template establishes default settings for color assignments, row and swimlane assignments, font properties, time axis choices, headers, footers, task links, and comment boxes.
It also tells OnePager which fields to import from a Microsoft Project or a Microsoft Excel source plans when a new project view is created.
Once you have created a project view using a Template, the project view becomes independent of the Template. You can change the Template and it has no further effect on the project view.
The project view is the graphical representation of the data imported from your Microsoft Project or Microsoft Excel source plan under the control of the the current Template.
The project view can be manually edited on the screen which is called the Project View Editor (PVE). See the article at this link: Manual versus Data-Driven Editing (Portal) for additional information.
You can also use the Project-View Properties (PVP) form accessed from the Home tab to make edits and changes to the project view which override the settings in the Template. These PVP form changes do not change the settings in the current Template.
Finally, you can convert a project view and its property settings into a Template for future use and save it under a file name of your selection.
The Project View Versus Template Relationship
Given the explanations provided above for project views and Templates, we can visualize the relationship between the two and include the relationship between project views and snapshots as well. The figure below shows this relationship:
The vertical columns overlaying Project A and B represent the control that the three Templates have over the look and feel of the project views and snapshots created for each of the three audience groups - Executives, the project Team, and Regulators. Each Template can create different project views that are tailored to the needs of each audience when it comes to telling a part of the schedule story.
Templates can be applied to many different projects as show above and can be tailored with different settings as required.
The project views and their snapshots respond to the settings in their respective Template by displaying tasks/milestones, decorations, adornments, and other project view features in accordance with Template settings.
For more information on Templates, please see the articles in this series: Managing Templates (Portal).
For more information on the management of project views, please see the articles at: Managing Project View Data (Portal).