Difference between revisions of "What's New with OnePager Release 6.0?"

Revision as of 20:22, 22 September 2016

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

Version of OnePager Pro and Express prior to 6.0 required you to insert a column (i.e., flag field) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project plan source files were tyically columns named Flag1 through Flag20. OnePager Pro used these flag columns to control the import of rows from the Microsoft Project plan source file. In both OnePager Pro and Express you could use Numeric type columns or Boolean type columns as long as the contents were 1 to incicate 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 but required a modification to the source file before import to OnePager if you want to 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 Microsoft Project/Excel plan source files is made even more flexible with the additon of our new Conditional Import capability.

1) There are occasions where you would like to import a source plan row but only when the contents of a specified column holds a certain value or range of values. For instance, you might want to include 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 modifity the Flag fields for those rows that met the example condition before importing the source file to OnePager. With OnePager Pro/Express 6.0 you can clearly specify in a Conditional Import rule (defined before the import process begins) that meets the any logical conbination of criteria WITHOUT making modifications to the source file.

2) Accasions migh also arise where you may not be able to modify a Microsoft Project or Excel plan source file thus you might be unable to add the required import control columns and have to import them all and edit out or hide the unwanted row tasks/milestone after the project view is created. Again, OnePager Pro/Express 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 their is data already available in the plan source file.

3) There are also occasions where you may need to go back AFTER a project veiw is created and Update the project view to reflect rows imported controled by another flag column or another logical relationship as described above. Before OnePager Pro/Express version 6.0 handing these situations meant totally starting over by going back to the OnePager Start form and selecting a differnt flag column. In OnePager Pro/Express version 6.0 you can change the import conditions from the Project View Editor by using the Custom Update feature and accessing your Conditional Import rules.

For all three of the above situations described before OnePager Pro/Express version 6.0, making appropriate changes described required starting over with your source file.

Version 6.0 for all our desktop products now has the capability for you to establish Conditional Import rules that are applied at the point where OnePager imports your source file(s) data such that it is easy to first specify and subsequently update the source file columns to maximize your control over the rows that OnePager imports.

Please take a moment to look at the article at the link just below

Read More... Conditional Import (Portal).

Expanded Row and Task Labels

Row Labels

OnePager Pro/Express previously supported just one row labeling option.

1) With version 6.0, OnePager will support up to five (5) additional snapshot-independent row labels which will appear on the left side of the project view and immediately to the right of the row label if it is displayed.

2) Controls for these additional row labels' is provided in the Project-View Properties and Template form's Rows/Swimlanes tab in the Labels" group of controls.

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

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)