Difference between revisions of "What's New with OnePager Release 6.0?"
(→Conditional Import) |
(→Conditional Import) |
||
| Line 7: | Line 7: | ||
==Conditional Import== | ==Conditional Import== | ||
| − | Version of OnePager Pro and Express '''prior''' to 6.0 required you to insert a column (i.e., flag field) into your | + | Version of OnePager Pro and Express '''prior''' to 6.0 required 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 used these flag field columns to control the import of rows. 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. However, it required a modification to the plan source file before import 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 | + | 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 | + | :(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 to OnePager. With version 6.0 you can clearly specify, in a '''Conditional Import''' rule, defined before the import process begins, the conditions that meets any logical combination of criteria WITHOUT making modifications to the plan source file. |
| − | 2) | + | :(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. You would have to first import them all and manually 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 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 | + | :(3) There are also occasions where you may need to go back '''AFTER''' a project view is created and '''Update''' the project view to reflect rows imported controlled by another '''flag''' field column or another logical relationship as described above. Before version 6.0 handing these situations meant totally starting over by going back to the OnePager Start form and selecting a different '''flag''' field column. Version 6.0 lets you change the import conditions from the '''Project View Editor''' by using the '''Custom Update''' feature to access your '''Conditional Import''' rules and edit them. |
| − | + | 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 with your plan source file. | |
| − | + | Please take a moment to look at the article at the link just below: | |
| − | + | ||
| − | Please take a moment to look at the article at the link just below | + | |
:Read More... [[Conditional Import for Version 6.0 (Portal) | Conditional Import (Portal)]]. | :Read More... [[Conditional Import for Version 6.0 (Portal) | Conditional Import (Portal)]]. | ||
Revision as of 15:40, 24 September 2016
Contents
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 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 used these flag field columns to control the import of rows. 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. However, it required a modification to the plan source file before import 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 to OnePager. With version 6.0 you can clearly specify, in a Conditional Import rule, defined before the import process begins, the conditions that meets any logical combination of criteria WITHOUT 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. You would have to first import them all and manually 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 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 view is created and Update the project view to reflect rows imported controlled by another flag field column or another logical relationship as described above. Before version 6.0 handing these situations meant totally starting over by going back to the OnePager Start form and selecting a different flag field column. Version 6.0 lets you change the import conditions from the Project View Editor by using the Custom Update feature to access your Conditional Import rules and edit them.
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 with your plan source file.
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)
