Difference between revisions of "Templates versus Project Views for Version 6.0"

From OnePager Documentation
Jump to: navigation, search
(Created page with "==Overview (PE60-4_3-11232016)== Project views and '''templates''' both let you customize your work and save time making new graphs or updating existing ones. Project views...")
 
(Project View)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Overview (PE60-4_3-11232016)==
+
==Overview==
  
Project views and '''templates''' both let you customize your work and save time making new graphs or updating existing ones.  
+
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.
+
Project views and '''Templates''' have some similar looking forms, so it is important to understand how they differ and what roles they play.
  
 
==Templates==
 
==Templates==
  
A '''template''' is a framework from which you create '''new''' project views.  
+
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.  
 
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, and comment boxes'''.  
+
The '''Template''' establishes default settings for '''color assignments, row and swimlane assignments, font properties, time axis choices, headers, footers, and comment boxes'''.  
  
It also tells OnePager which columns to import from a Microsoft Project plan or a Microsoft Excel plan when a new project view is created.   
+
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 will have no further effect on the project view.
+
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 will have no further effect on the project view.
  
 
==Project View==
 
==Project View==
  
The project view is the graphical representation of the data imported from your Microsoft Project or Microsoft Excel plan under the control of the the '''current template'''.
+
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 may be manually edited on the screen which is called the Project View Editor ('''PVE''').  See the article at this link:  [[Manual Editing for Version 6.0 (Portal) | Manual Editing]] 9.0.1-60 for additional information.
+
The project view may be manually edited on the screen which is called the Project View Editor ('''PVE''').  See the article at this link:  [[Manual Editing for Version 6.0 (Portal) | Manual Editing]] <!--9.0.1-60--> for additional information.
  
You may 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''' changes do not change the settings in the '''current template'''.
+
You may 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 may convert a project view and its property settings into a '''template''' for future use and save it under a file name of your selection.
+
Finally, you may convert a project view and its property settings into a '''Template''' for future use and save it under a file name of your selection.
  
 
(4.3-60)
 
(4.3-60)

Latest revision as of 17:23, 7 April 2017

Overview

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.

Templates

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, 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 will have no further effect on the project view.

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 may be manually edited on the screen which is called the Project View Editor (PVE). See the article at this link: Manual Editing for additional information.

You may 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 may convert a project view and its property settings into a Template for future use and save it under a file name of your selection.

(4.3-60)