Difference between revisions of "Additional Text Columns for OnePager Pro 6.0"

Revision as of 15:54, 2 May 2017

About Additional Text Columns

OnePager Pro and Express version 6.0 is enhanced to increase the number of text columns that can be displayed in the graph.

1) As a comparison, below is a typical OnePager Pro project view with rows and swimlanes as depicted in previous versions:

2) In OnePager Pro and Express version 6.0, you can display up to 5 text columns which can create a project view that looks like this:

3) In the enhanced project view above, there are three (3) additional text columns designated Start, Finish, and Deadline. For the purpose of the intended audience, these Start and Finish dates and their proximity to the Deadline date are important and require a place to display in text.

4) Version 6.0 provides the controls necessary to define additional text columns as well as the controls to manage their properties such as font characteristics, color, and other text properties such as Bold, Underline, and Italic fonts.

5) The position of the text columns may be reordered left to right by using the Project-View Properties (PVP) form’s controls in the Rows and Swimlanes tab to redefine which text column should be first, second, etc., from left to right.

6) The PVP form is expanded to provide all the controls necessary to define and manage the additional text columns.

a) The new PVP form is shown below:

b) The controls are modified in the Labels group with the addition of the Text Column Properties… button which provides access to the Custom Text Columns form shown here:

c) There are five tabs in the above form each provides the capability to define an additional text column from either the left project view border (if Swimlanes are not displayed) or to the right of the Swimlane column.

d) Each tab gives you the capability to turn the text column on or off (Show this checkbox), use the Field window dropdown to select the source plan data field to populate the designated text column, and use the Formatting group of controls to format the text which will appear in the text column represented by the tab you are working in.

7) Looking back at the PVP form’s Rows and Swimlane tab’s Ordering group, you have the capability to order the rows displayed in the project view as you did before.

a) Simply specify what type of row ordering you want (Order like Project or Order rows by a selected source plan data field).

b) For example, once you click the Order rows by radio button, you can use the dropdown window to select a source plan data field for Ordering the rows. This selection may be one of the source plan data fields defined in the Custom Text Columns form or another available source plan data field that meets your needs. This has not changed from previous versions of OnePager Pro or Express.

8) Text column content is snapshot dependent; so whenever the data from the source plan changes, the information in the displayed text columns is updated.

9) The additional text column feature is also supported by OnePager’s Multi-Page output capability where all displayed text columns are treated as one text column for the purpose of controlling the repeat of text columns on the multiple pages of project view output.

10) To use this feature effectively, it is important to make sure that all source plan data fields you wish to use are imported by OnePager Pro or Express. If the text column feature determines that source plan data fields are not imported, it will display blank content in the associated text column.

11) Any project view files (.TAMs) created prior to OnePager Pro or Express version 6.0 will automatically display rows and swimlanes as before. To maintain capability, any legacy project views imported and opened by OnePager Pro or Express version 6.0 will update the PVP form to reflect the current row and swimlane display status.

12) Templates distributed with OnePager Pro and Express version 6.0 minimize the display of rows and swimlanes. Additionally, user defined Templates from previous versions of OnePager Pro or Express are converted to the OnePager Pro/Express version 6.0 format when these user defined Templates are opened for first use.

a) Templates created by users with previous versions of OnePager Pro/Express are converted to the OnePager Pro/Express version 6.0 format and when re-saved by the user are saved in the OnePager Pro/Express version 6.0 format as the primary option.

b) Users have the option when saving a user defined Template or a Template distributed with the installation of OnePager Pro/Express version 6.0 in a format which can be shared with other OnePager Pro/Express users who do not use OnePager Pro/Express 6.0.

c) Since OnePager Pro/Express version 6.0 will automatically convert a legacy Template to the version 6.0 format, Templates may always be shared from legacy OnePager Pro/Express users and version 6.0 users. The reverse is also true.

d) When version 6.0 Templates are saved in the format of a previous OnePager Pro/Express version, any additional text columns beyond the first are removed along with all the properties associated with these up to four (4) text columns.

e) An additional consideration to keep in mind when saving OnePager Pro/Express version 6.0 Templates to a legacy OnePager Pro/Express format is that any Conditional Import properties will also be stripped off and lost. Although the Template may be later restored to the OnePager Pro/Express 6.0 format when subsequently opened, any Conditional Import instructions will not be present and the Template will need to be updated for the Template to correctly control Conditional Import actions.

13) As with previous versions of OnePager Pro/Express, version 6.0 project views can be saved in legacy formats back to OnePager Pro/Express 5.0.

a) Saving OnePager Pro/Express version 6.0 project views in a legacy format is done using the Save As command on the File tab of the OnePager Pro/Express tool bar and clicking on the Save as type dropdown on the Windows Save As form to select the legacy format desired:

b) Saving a project view in a legacy format prior to OnePager Pro/Express 6.0 will strip off any visibility of additional text columns beyond one. This is done because the saved .TAM file associated with the project view is converted to the format associated with the version of OnePager Pro/Express to which it is being saved. It is not possible to retrieve this information if the saved project view is reopened in OnePager Pro or Express 6.0 as the converted .TAM from the now legacy format will be converted to the version 6.0 format in the simplest way with the data available.

c) Saving in any of the none-legacy OnePager Pro/Express formats shown in the above illustration will preserve all displayed text columns as applicable.

d) As with Templates, discussed above, an additional consideration to keep in mind when saving OnePager Pro/Express version 6.0 project views to a legacy OnePager Pro/Express format is that any Conditional Import properties will also be stripped off and lost. Although the project view may be later restored to the OnePager Pro/Express 6.0 format when subsequently opened, any Conditional Import instructions will not be present and the project view will need to be updated for it to correctly control Conditional Import actions.

(0.4.1.3-60)