What's New with OnePager Release 6.0?

About OnePager Version 6.0

0.4-60 Not Edited Beyond This Point.

OnePager Pro (OPP) and Express (OPX) version 6.0 provides additional capabilities for the user as described in this article below. OnePager version 6.0's new features are a response to our customers.

Conditional Import

Versions of OnePager Pro and Express prior to 6.0 require you to insert a column (i.e., flag field) into your plan source file that tells OnePager which rows to import. These flag fields for Microsoft Project plan source files were typically columns named Flag1 through Flag20. OnePager Pro uses these flag field columns to control the import of rows. In both OnePager Pro and Express you could also use Numeric type columns or Boolean type columns as long as the contents were either 1 to indicate Yes (bring in this row) or 0 to indicate No (do not import this row). This approach to controlling the import of Microsoft Project/Excel plan source file rows is quite flexible. However, it required a modification to the plan source file before importing data to OnePager so you can limit the rows presented in the resulting project view.

In OnePager Pro and Express version 6.0 the capability for you to control the import of rows from your plan source files is made even more flexible with the addition of our new Conditional Import capability.

(1) There are occasions where you would like to import a plan source file row but only when the contents of a specified column holds a desired value or range of values. For instance, you might want to include plan source file rows where task/milestone Start dates are greater than a specified date. Prior to OnePager Pro/Express version 6.0 you would have to manually modify the Flag fields for those rows meeting the desired condition before importing data to OnePager. With version 6.0 you can clearly specify, in a Conditional Import rule, defined before the import process begins, the conditions that meet any logical combination of criteria WITHOUT first making modifications to the plan source file.

(2) Occasions might also arise where you may not be able to modify a Microsoft Project or Excel plan source file. For read-only files you might be unable to add the required import control flag field columns. In such a situation, you would have to first import all rows and manually then edit out or hide the unwanted row tasks/milestone after the project view is created. Again, version 6.0 allows you to specify import conditions that meet your needs, say, only the rows which correspond to a particular project phase for which there are data already available in the plan source file.

OnePager Pro/Express version 6.0 both Add-in and Desktop products, with its Conditional Import feature, allows you to make changes described above without starting over from your plan source file.

Detailed articles for using Conditional Import can be found at the link just below the Basic Workflows (Portal) link.

Please take a moment to look at the Read More... article below for an overview of Conditional Import:

Read More... Conditional Import for OnePager 0.4.1.1-60

Additional Text Columns

OnePager Pro/Express previously supported just one text column option - previously called the Row Label. Our user's requested additional text columns' so that source file information could be displayed within the row as an adjunct to the positions to Tasks/Milestones and their associated labels within the graph. For example, not only could you organize your source file data for display into Swimlanes but you could further organize your data visually into rows within swimlanes.

OnePager 6.0 now supports up to five (5) additional snapshot-dependenttext columns which will appear on the left side of the project view and immediately to the right of the left border or the Swimlane labe if swimlane labels are displayed.

Controls for these additional text columns are provided in the Project-View Properties (PVP) and Template form's Rows/Swimlanes tab in the Labels group of controls.

With these controls you may specify what Microsoft Project or Excel source plan data column's are to be imported to populate the text column in the project view. With the same controls you may format the properties you desire OnePager to apply to the data imported in terms of font style, alignment, format, and text column height.

Additionally, the controls in the PVP Rows/Swiimlanes tab's Ordering group continue to support your selection of which text column should be used to order rows (ascending or descending) within a swimlane.

An example showing the usage of the Additional Text Columns feature is given in the article whose link is below:

Read More... Additional Text Columns 0.4.1.3-60

Retroactive Column Mapping

1) Where the new Conditional Import feature of OnePager version 6.0 allows you to reconfigure the import of Microsoft Project or Excel rows before the project view is created, the Retroactive Column Mapping feature allows you to reconfigure your column mapping (i.e., use of source plan columns) after a project view is created.

2) Like the Conditional Import feature, this feature is designed to eliminate the need for you to start over if, for any reason, you wish to utilize a different or additional source plan column for another purpose.

3) Our intent here is to provide you a more efficient way for you to create a new project view for the first time and to efficiently tailor it to fit your schedule conversation needs.

a) As such, the feature is limited to single snapshot project views.

b) This feature does not increase the number of columns that can be mapped from a source plan to your project view. Rather it makes it much easier to make a change to the column mapping after a first project view is created and needs to be modified with respect to column mapping.

4) An example is provided at the link shown below:

Read More... Retroactive Column Mapping 0.4.1.5-60

(0.4-60)