Difference between revisions of "What's New with OnePager Release 6.0?"
(→Retroactive Column Mapping) |
|||
| Line 1: | Line 1: | ||
==About OnePager Version 6.0== | ==About OnePager Version 6.0== | ||
| − | |||
| − | |||
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. | 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. | ||
| Line 7: | Line 5: | ||
==Conditional Import== | ==Conditional Import== | ||
| − | Versions of OnePager Pro and Express '''prior''' to 6.0 require you to insert a | + | Versions of OnePager Pro and Express '''prior''' to 6.0 require you to insert a field (i.e., flag field) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project source plan were typically fields named '''Flag1 through Flag20'''. OnePager Pro uses these flag field to control the import of rows. In both OnePager Pro and Express you could also use '''Numeric''' type fields or '''Boolean''' type fields 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 source plan rows is quite flexible. However, it required a modification to the source plan '''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 | + | In OnePager Pro and Express version 6.0 the capability for you to control the import of rows from your source plan 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 source plan row but only when the contents of a specified field holds a desired value or range of values. For instance, you might want to include source plan 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 source plan. |
| − | :(2) Occasions might also arise where you may not be able to modify a Microsoft Project or Excel | + | :(2) Occasions might also arise where you may not be able to modify a Microsoft Project or Excel source plan. For read-only files you might be unable to add the required import control flag fields. 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 source plan. |
<!-- | <!-- | ||
| − | :(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 | + | :(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 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. 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 from your | + | 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 source plan. |
Detailed articles for using '''Conditional Import''' can be found at the link just below the '''Basic Workflows (Portal)''' link. | Detailed articles for using '''Conditional Import''' can be found at the link just below the '''Basic Workflows (Portal)''' link. | ||
| Line 27: | Line 25: | ||
==Additional Text Columns== | ==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 | + | 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 plan 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 plan 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-dependent'''text columns''' which will appear on the left side of the project view and immediately to the right of the left border or the '''Swimlane | + | OnePager version 6.0 now supports up to five (5) additional snapshot-dependent '''text columns''' which will appear on the left side of the project view and immediately to the right of the left border or the '''Swimlane label''' 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. | 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 | + | With these controls you may specify what Microsoft Project or Excel source plan fields 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'''. | 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'''. | ||
| Line 43: | Line 41: | ||
==Retroactive Column Mapping== | ==Retroactive Column Mapping== | ||
| − | The '''Retroactive Column Mapping''' ('''RCM''') feature allows you to reconfigure your column mapping (i.e., use other or additional source plan | + | The '''Retroactive Column Mapping''' ('''RCM''') feature allows you to reconfigure your OnePager column mapping (i.e., use other or additional source plan fields) '''after''' a project view is created. |
| − | 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 | + | 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 field for another purpose. For example, if you may want to unhide and populate a '''Text''' field in Microsoft Project and then use that field to present data in an '''Additional Text Column''' discussed above. |
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. | 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. | ||
| − | :(1) As such, the feature is limited to single snapshot project views. The '''RCM''' feature is turned off for project views with more than one snapshot. | + | :(1) As such, the feature is limited to '''single snapshot''' project views. The '''RCM''' feature is turned off for project views with more than one snapshot. |
| − | :(2) 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'''. | + | :(2) This feature does not increase the number of OnePager 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'''. |
| − | Additionally, and to compliment the '''RCM''' feature, we've changed the '''Other Columns''' tab on the '''Template''' form. The name of the new tab is the '''Field Mappings''' tab. Since the '''RCM''' feature allows you to import all | + | Additionally, and to compliment the '''RCM''' feature, we've changed the '''Other Columns''' tab on the '''Template''' form. The name of the new tab is the '''Field Mappings''' tab. Since the '''RCM''' feature allows you to import all fields from Microsoft Project and Excel source plans, the '''Field Mappings''' tab is a significantly simplified tab which focuses on those Microsoft Project and Excel fields that customers tell us are the most frequent fields they wish to remap into other OnePager colums after a project view is created. For OnePager Pro there are eight (8) Microsoft Project fields as named in the '''Field Mapping''' tab list below: |
:(1) Percent-complete column | :(1) Percent-complete column | ||
| Line 71: | Line 69: | ||
:(8) Deadline | :(8) Deadline | ||
| − | For OnePager Express there are seven (7) | + | For OnePager Express there are seven (7) fields involved with the exception of the '''Critical-path column''' since OnePager Express dose not support '''critical path''' representations. |
For OnePager Pro the '''Retroactive Column Mapping''' includes '''Enterprise Custom Fields''' ('''ECF'''). Care should be taken, however, that you have turned on the '''ECF''' function in the current '''Template''' and established your connection to your project server service before creating the first project view. | For OnePager Pro the '''Retroactive Column Mapping''' includes '''Enterprise Custom Fields''' ('''ECF'''). Care should be taken, however, that you have turned on the '''ECF''' function in the current '''Template''' and established your connection to your project server service before creating the first project view. | ||
| − | As in the '''Other Columns''' tab in previous versions, version 6.0 supports '''column splitting''' with the control on the '''Field Mappings''' tab in the '''Template''' form and '''Project-View Properties''' form. '''Column splitting''' can be performed on any source plan '''string type''' column with '''comma-separated''' | + | As in the '''Other Columns''' tab in previous versions, version 6.0 supports '''column splitting''' with the control on the '''Field Mappings''' tab in the '''Template''' form and '''Project-View Properties''' form. '''Column splitting''' can be performed on any source plan '''string type''' column with '''comma-separated''' components imported either before or after the project view is created. |
The link shown below provides some more details on the '''Retroactive Column Mapping''' feature and should be read before reviewing the more detailed articles within this Wiki: | The link shown below provides some more details on the '''Retroactive Column Mapping''' feature and should be read before reviewing the more detailed articles within this Wiki: | ||
| Line 212: | Line 210: | ||
--> | --> | ||
(0.4-60) | (0.4-60) | ||
| + | |||
| + | [[Category:Version 6.0]] | ||
Revision as of 16:33, 27 December 2016
Contents
About OnePager Version 6.0
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 field (i.e., flag field) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project source plan were typically fields named Flag1 through Flag20. OnePager Pro uses these flag field to control the import of rows. In both OnePager Pro and Express you could also use Numeric type fields or Boolean type fields 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 source plan rows is quite flexible. However, it required a modification to the source plan 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 source plan 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 source plan row but only when the contents of a specified field holds a desired value or range of values. For instance, you might want to include source plan 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 source plan.
- (2) Occasions might also arise where you may not be able to modify a Microsoft Project or Excel source plan. For read-only files you might be unable to add the required import control flag fields. 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 source plan.
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 source plan.
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 plan 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 plan data for display into Swimlanes but you could further organize your data visually into rows within swimlanes.
OnePager version 6.0 now supports up to five (5) additional snapshot-dependent text columns which will appear on the left side of the project view and immediately to the right of the left border or the Swimlane label 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 fields 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
The Retroactive Column Mapping (RCM) feature allows you to reconfigure your OnePager column mapping (i.e., use other or additional source plan fields) after a project view is created.
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 field for another purpose. For example, if you may want to unhide and populate a Text field in Microsoft Project and then use that field to present data in an Additional Text Column discussed above.
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.
- (1) As such, the feature is limited to single snapshot project views. The RCM feature is turned off for project views with more than one snapshot.
- (2) This feature does not increase the number of OnePager 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.
Additionally, and to compliment the RCM feature, we've changed the Other Columns tab on the Template form. The name of the new tab is the Field Mappings tab. Since the RCM feature allows you to import all fields from Microsoft Project and Excel source plans, the Field Mappings tab is a significantly simplified tab which focuses on those Microsoft Project and Excel fields that customers tell us are the most frequent fields they wish to remap into other OnePager colums after a project view is created. For OnePager Pro there are eight (8) Microsoft Project fields as named in the Field Mapping tab list below:
- (1) Percent-complete column
- (2) Critical-path column
- (3) Task-name column
- (4) Start
- (5) Finish
- (6) Baseline start
- (7) Baseline finish
- (8) Deadline
For OnePager Express there are seven (7) fields involved with the exception of the Critical-path column since OnePager Express dose not support critical path representations.
For OnePager Pro the Retroactive Column Mapping includes Enterprise Custom Fields (ECF). Care should be taken, however, that you have turned on the ECF function in the current Template and established your connection to your project server service before creating the first project view.
As in the Other Columns tab in previous versions, version 6.0 supports column splitting with the control on the Field Mappings tab in the Template form and Project-View Properties form. Column splitting can be performed on any source plan string type column with comma-separated components imported either before or after the project view is created.
The link shown below provides some more details on the Retroactive Column Mapping feature and should be read before reviewing the more detailed articles within this Wiki:
- Read More... Overview of Retroactive Column Mapping 0.4.1.5-60
(0.4-60)
