|
|
| (44 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | =OnePager Import of Data from Planisware Enterprise for Version 7.2 (P72-4.0.1.11-72-04212023.txt)=
| |
| | | | |
| − | ==Introduction==
| |
| − |
| |
| − | The purpose of this article is to provide you one place with as much information as possible about how '''OnePager''' is used to create OnePager charts with data '''imported '''from Planisware Enterprise.
| |
| − |
| |
| − | In most cases '''OnePager''' handles data fields from Planisware Enterprise very much like data coming from Microsoft Excel. This article focuses on two major topics:
| |
| − |
| |
| − | :1) Connecting to and '''importing''' Planisware Enterprise data into '''OnePager'''.
| |
| − |
| |
| − | :2) '''OnePager’s''' handling of specific Planisware Enterprise '''column''' data once those data are '''imported'''.
| |
| − |
| |
| − | As a convention, whenever we refer to the '''OnePager''' in the context of Planisware Enterprise, we'll just say '''OnePager''' when it’s absolutely clear that we are discussing '''OnePager''' with Planisware Enterprise. Since only the '''Standalone''' edition of '''OnePager''' connects to Planisware Enterprise files online, we'll just leave the suffix '''"Standalone"''' off.
| |
| − |
| |
| − | ==About Connecting and Importing Planisware Enterprise Data to OnePager==
| |
| − |
| |
| − | '''OnePager imports '''data from Planisware Enterprise by first making the '''connection''' from '''OnePager '''to your Planisware Enterprise account online. Therefore, you must first have a Planisware Enterprise account and '''login credentials''' so '''OnePager '''can access your account, your Planisware Enterprise files, and be able to download selected file or files to your computer.
| |
| − |
| |
| − | Detailed information on setting up you Planisware Enterprise data for import to '''OnePager''' and other topics related to '''getting started using OnePager Bundle''' can be found at this article:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Using Planisware Enterprise Source Plans with OnePager Version 7.2 | Using Planisware Enterprise Source Plans with OnePager]] 3.0.3.11-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Data Imports to OnePager===
| |
| − |
| |
| − | '''OnePager''' expects that you created a Planisware Enterprise '''Project formatted''' file from one of the many available Planisware Enterprise templates. In most cases, the '''column headings''' for the '''Project formatted '''file look like this:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(1)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(1)-04212023.png</center>
| |
| − |
| |
| − | ====Minimum Column Names and Flag Column Definition====
| |
| − |
| |
| − | The minimum '''Column names''' needed by '''OnePager '''are the '''Task Name''', '''Start''', and '''Finish'''. Additionally, Planisware Enterprise has added a '''defined field''' named '''Send to OnePager?''' as a '''Boolean''' field specifically to facilitate the interface between Planisware Enterprise and OnePager. Setting the checkboxes for tasks that you want to '''import''' to OnePager '''ON''' assures that OnePager can identify these tasks and successfully '''import''' them. An example is shown here:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(2)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(2)-04212023.png</center>
| |
| − |
| |
| − | In the example above, the '''Send to OnePager?''' column’s purpose is to instruct '''OnePager '''on which '''rows''' to process when '''importing''' the Planisware Enterprise '''Project formatted '''file. '''OnePager '''expects to see either '''ON''' or '''OFF''' appropriately entered in the cells of the '''Send to OnePager?''' column indicating which '''rows''' to '''import''' ('''ON''') and which '''rows''' not to import ('''OFF''').
| |
| − |
| |
| − | ===OnePager Recognized Data Types===
| |
| − |
| |
| − | What follows is a short discussion of how '''OnePager '''applies it’s built in intelligence functions with respect to Planisware Enterprise’s '''Internally Defined Columns'''. The goal here is to provide an understanding of the process so you know what to expect from '''OnePager '''when various '''column heading''' names and '''data (column) types''' are encountered by '''OnePager '''in your Planisware Enterprise '''source plan'''. There are four (4) '''column types''' that '''OnePager '''looks for when '''importing''' data from Planisware Enterprise:
| |
| − |
| |
| − | :* Dates
| |
| − | :* Numbers
| |
| − | :* Boolean (TRUE or FALSE)
| |
| − | :* Text Strings (A through Z, 0-9, special characters)
| |
| − |
| |
| − | All data, regardless of '''data type''', are '''imported''' from Planisware Enterprise '''Project formatted '''files. '''OnePager '''begins this analysis from top-left to bottom-right. Once the '''column headers '''are located and the '''data types''' are analyzed, '''OnePager '''associates these '''columns''' with specific usages in the '''OnePager choices '''('''OPC''') form as illustrated below. Using the second page of the '''OPC''' form shown below, you can change the '''column''' usage by selecting another '''column''' to serve the function from the dropdown list provided. The dropdown list is built from all the '''column headers''' that '''OnePager '''found during its analysis pass. An example of a dropdown list of '''column header''' names taken from a Planisware Enterprise '''source plan''' is shown here:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4)-04212023.png</center>
| |
| − |
| |
| − | Highlighted above is the second page of the '''OnePager choices '''form showing a dropdown list of Planisware Enterprise available '''column names''' along with '''virtual column names '''created by '''OnePager'''.
| |
| − |
| |
| − | ==Selecting Tasks for Import into OnePager==
| |
| − |
| |
| − | Since '''OnePager '''is connected to your Planisware Enterprise account, it has access to your '''Project formatted '''files. Anyone of these files can be '''imported''' into '''OnePager '''and a chart created. The benefit derived from '''OnePager '''is that you can select the tasks you which to display in your '''OnePager '''chart along with other decorations and features that are best for presentation in a schedule discussion.
| |
| − |
| |
| − | A way to set up a Planisware Enterprise '''Project formatted '''file for '''import''' to '''OnePager '''is to include the Planisware Enterprise '''Send to OnePager?''' field in your '''source plan''' and set the '''Boolean''' value of '''ON''' in the cells for each row in your source plan that you want '''OnePager '''to '''import'''. For illustration here we’ve define the Planisware Enterprise '''defined column''' called '''Send to OnePager?''' as a '''checkbox column''' and with inserted '''“Checkmarks”''' and '''“Unchecked Boxes”''' to indicate to '''OnePager '''which tasks we wish to '''import'''. This is illustrated in the '''source plan '''portion below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4A)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4A)-04212023.png</center>
| |
| − |
| |
| − | When making your first chart, we strongly recommend that you '''import''' 50 or fewer '''Tasks'''. Please note that '''OnePager '''is shipped with a number of fully populated '''templates''' that are based on the Planisware Enterprise '''source plan''' used in the '''Tutorial''' shipped with the product – '''BlueGrass Project Plan'''. Three '''column headings''' must always be present as a minimum: '''Task Name''',''' Start Date''',''' '''and''' Finish Date'''.
| |
| − |
| |
| − | Once you’ve made the determination which '''source plan''' tasks to '''import''' you can launch '''OnePager '''and create your '''OnePager '''chart.
| |
| − |
| |
| − | This discussion continues at this link:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Using Planisware Enterprise Source Plans with OnePager Version 7.2#Launching OnePager Using Planisware Enterprise Source Plans for the First Time | Launching OnePager Using Planisware Enterprise Source Plans for the First Time]] 3.0.3.7-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | There are three (3) '''selection options''' available for controlling '''OnePager’s import '''of task data. These are discussed in the subsections that follow:
| |
| − |
| |
| − | ====Task Selection Option (1): Select All Tasks====
| |
| − |
| |
| − | Planisware Enterprise '''source plans''' like the one shown above with many tasks results in a very large '''OnePager''' chart usually not suitable for detailed schedule conversations. Accordingly, we do not recommend '''importing '''more than 50 tasks so that the resulting chart is a useful one page rendering of the '''source plan'''. However, for small projects where the number of tasks falls below the recommended maximum, using the '''Select all tasks''' shown in the '''Task Selection''' sub-control group of the '''OnePager choice''' form below is an easy way to specify this option:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4B)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4B)-04242023.png</center>
| |
| − |
| |
| − | ====Task Selection Option (2): Select Tasks with ‘Yes’ in field:====
| |
| − |
| |
| − | As mentioned above, one method for telling '''OnePager '''which '''tasks''' to '''import '''is to use a '''Flag''' '''column'''. As shown in the previous section, the Planisware Enterprise '''source plan''' has a '''User Defined Column '''named '''Show It''' and the word '''“Yes” '''is typed into the contents of the '''Show It cell''' for each task '''imported '''into '''OnePager'''. Here is an illustration of the '''OnePager choices''' form where a '''Flag column''' is used to select tasks from the '''source plan''':
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4C)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4C)-04242023.png</center>
| |
| − |
| |
| − | When this is done for the '''source plan '''shown above, and other appropriate settings are made for '''OnePager''', the resulting chart looks like this:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4D)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4D)-04242023.png</center>
| |
| − |
| |
| − | As mentioned earlier, you can also use a Planisware Enterprise '''checkbox '''with a unique '''column header name'''. '''OnePager''' recognizes the '''checkbox column '''as a possible '''flag column '''and makes it available in the '''OnePager choices '''form in the '''dropdown list '''for the '''Select task with ‘Yes’ in field:''' option as shown below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4J)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4J)-04242023.png</center>
| |
| − |
| |
| − | When the '''column heading''' call OnePager is selected in the form above, '''OnePager imports''' rows where the '''OnePager checkbox '''is checked '''ON'''.
| |
| − |
| |
| − | ====Task Selection Option (3): Select Tasks by custom filter: (Conditional Import Rules)====
| |
| − |
| |
| − | You can use the '''Conditional Import feature''' to fine tune the tasks you want to '''import'''. Assuming that you’re familiar with the '''Conditional Import '''feature, the '''Conditional Import Rules '''form can be accessed by selecting the '''Select tasks by custom filter: '''radio button as shown in the illustration below. Using the '''Conditional Import Rules '''form as shown here, it is possible to select tasks between specified '''Budget Dates''' and '''Budget Dates''' including those where '''Send to OnePager?" is '''TRUE'''.
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4E-1)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4E-1)-04242023.png</center>
| |
| − |
| |
| − | When the above '''Conditional Import rules''' are used in the selection process, the resulting chart looks like this:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4F)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4F)-04242023.png</center>
| |
| − |
| |
| − | Any Planisware Enterprise '''column''' found in your '''source plan '''can be used as a '''Field''' in a '''Conditional Import rule'''.
| |
| − |
| |
| − | For more detailed information on the '''Conditional Import feature''', we recommend that you read the articles on this subject under:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Conditional Import for Version 7.2 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Using Other Columns as Flag Columns in Planisware Enterprise===
| |
| − |
| |
| − | '''OnePager '''offers a wide range of Planisware Enterprise '''column''' and '''data types''' to be used as a '''flag '''for controlling the '''import''' of '''rows''' for making OnePager charts as shown below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4J-A)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4J-A)-04242023.png</center>
| |
| − |
| |
| − | Although the above dropdown list is extensive, '''OnePager '''is set to recognize only '''“Boolean”''' situations that resolve to either '''TRUE''' '''import''' to OnePager or '''FALSE''' do not '''import''' to '''OnePager'''. Planisware Enterprise does not have '''Boolean''' '''type columns''' that can be used for this purpose so you must use '''text columns''',''' number '''type '''columns''', or '''checkboxes''' for this purpose as explained in the following sub-sections.
| |
| − |
| |
| − | ====Integers Used as Flag Columns in Planisware Enterprise====
| |
| − |
| |
| − | You can use a Planisware Enterprise '''number column '''with an '''integer''' as a '''flag '''if its contents are '''1’s''' in those cells that are intended to be '''imported '''as tasks. Similarly you can use '''0’s''' as '''flags '''for those tasks that you do not wish to '''import'''.
| |
| − |
| |
| − | ====Decimal Numbers Used as Flag Columns in Planisware Enterprise====
| |
| − |
| |
| − | '''Number columns''' that contain an '''integer and decimal fraction''' are eligible to become '''flag''' when their contents are either '''1.0''' or '''0.0'''. However, such fields are not picked up by '''OnePager '''as a '''flag '''as discussed above for Planisware Enterprise '''text fields'''. Therefore, we do not recommend that '''Number columns''' be used for the purpose of general task selection. Accordingly, it is still useful to consider '''number columns''' for task selection if the values contained in these '''number column '''cells need to be used for decision making on which tasks should be '''imported'''.
| |
| − |
| |
| − | ====Checkboxes Used as Flag Columns in Planisware Enterprise====
| |
| − |
| |
| − | As an alternative you can use a Planisware Enterprise '''checkbox''' where the '''row '''to '''import '''is represented by the '''box checked ON''' as shown here:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4A)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4A)-04212023.png</center>
| |
| − |
| |
| − | '''OnePager''' recognizes '''Checkbox columns''' in Planisware Enterprise as possible '''flag '''columns and makes the '''column''' available in the '''flag '''column selection process discussed later in this article.
| |
| − |
| |
| − | ==Intelligent Changes Made to OnePager Current Template Properties Forms==
| |
| − |
| |
| − | '''OnePager '''is shipped to you with a predefined set of '''Template Properties''' forms. This means that all '''column '''usage settings within these shipped '''Template Properties''' forms are based upon a typical Planisware Enterprise '''source plan'''. Since the flexibility of Planisware Enterprise is considered in the design of '''OnePager''', it is necessary to '''update''' the current '''Template Properties''' form based upon '''your''' Planisware Enterprise '''source plan'''. Accordingly, '''OnePager '''uses the analysis techniques discussed above to modify the '''current Template Properties''' form. '''OnePager''' makes intelligent choices and recommendations on Planisware Enterprise '''source plan column''' usage based on the findings of the intelligent engine.
| |
| − |
| |
| − | You can change or override these findings as follows:
| |
| − |
| |
| − | :1) You can click the '''Edit current Template…''' button on the second page of the '''OnePager choices''' ('''OPC''') form shown here:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(4H)-04242023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(4H)-04242023.png</center>
| |
| − |
| |
| − | :2) Clicking this button accesses the '''Template Properties''' form so you can navigate to the '''Rows and Swimlanes''' tab.
| |
| − |
| |
| − | :3) The settings found in the '''Row & Swimlanes''' tab are determined by the '''current Template Properties''' form and by the intelligent analysis described above.
| |
| − |
| |
| − | :4) If your Planisware Enterprise '''source plan''' contains a '''column heading''' that exists in the '''Template Properties''' form, '''OnePager '''uses that '''column'''.
| |
| − |
| |
| − | :5) Otherwise, it makes an intelligent recommendation from the '''column headings''' it discovers.
| |
| − |
| |
| − | The illustration below shows that several of the settings in the '''Template Properties''' form’s '''Rows & Swimlanes''' tab reflect the decisions that '''OnePager '''made concerning '''column''' usage. These settings are consistent with the selections displayed in the '''OPC''' form.
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(3)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(3)-04252023.png</center>
| |
| − |
| |
| − | The illustration above shows that the '''Late Start column''' from the Planisware Enterprise '''source plan''' is selected as the '''text column''' to appear in the chart. You can change the '''Row & Swimlanes''' tab settings as well as settings in any of the other tabs. When you are ready, click '''Save and use''' button to make these changes part of the '''current Template Properties''' form.
| |
| − |
| |
| − | In other tabs of the '''Template Properties''' form, '''OnePager '''has adjusted settings in a similar way to be consistent with its intelligent engine’s analysis of the Planisware Enterprise '''source plan column headers''' and '''data types'''. If '''OnePager '''cannot find a '''column header''' name in the Planisware Enterprise '''source plan''' that can be correlated with a specific '''OnePager '''purpose, it makes as intelligent a choice as possible and you are then able to make any change necessary. You are '''cautioned''' that all '''current Template Properties''' forms are altered when used in this way. We recommend that unique '''Template Properties''' form names be subsequently given to such modified '''Template Properties''' form for future reference and for sharing these modified '''Template Properties''' form with others.
| |
| − |
| |
| − | For more information on the '''management '''of '''Template Properties '''forms, please see the article at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Managing Templates for Version 7.2 (Portal) | Managing Templates (Portal)]] 24.0.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ==Missing Columns, Column Headers, or Misspelled Column Headings==
| |
| − |
| |
| − | '''OnePager '''also checks '''column headings''' when '''importing''' data in '''UPDATE''' mode. If the '''column''' was used in previous '''snapshots''' for any purpose, '''OnePager '''checks to assure that the new '''import''' for the '''snapshot''' has those same '''columns'''. When '''OnePager '''cannot find the expected '''columns''', one or more '''column heading''' names are missing or blank, the '''column heading''' is recognizably misspelled, or the '''data type''' is different from the previous snapshot, '''OnePager '''provides a '''warning message''' as shown in the example below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(5)-09272021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(5)-09272021.png</center>
| |
| − |
| |
| − | This can occur when you inadvertently attempt to '''update''' a chart from the incorrect Planisware Enterprise '''source plan''' or the desired Planisware Enterprise '''source plan''' was altered to the extent that '''OnePager '''cannot find the '''columns''' needed to accomplish the '''UPDATE''' functions. You are given two choices when the message above is displayed:
| |
| − |
| |
| − | ===Continue with missing field(s)===
| |
| − |
| |
| − | By selecting the '''Continue…''' button, the '''import''' proceeds. '''OnePager '''blanks some values that it cannot find. '''Note:''' The results can be unexpected.
| |
| − |
| |
| − | ===Go back and fix field(s)===
| |
| − |
| |
| − | Selecting the '''Go back…''' button tells '''OnePager '''to '''stop''' the '''import''' process and return control to Planisware Enterprise. You can now correct the Planisware Enterprise '''source plan''' or select another one and start the '''UPDATE''' process again.
| |
| − |
| |
| − | ==Missing Task Start/Finish Dates==
| |
| − |
| |
| − | OnePager requires that, at a minimum, a row from Planisware Enterprise needs to have a task '''Name''', a '''Planned Start''' date, and a '''Planned Finish''' date. The row is ignored if the '''Name''' is not provided even if '''Planned Start''' and '''Planned Finish''' dats are present. When a row is missing either a '''Planned Start''' date or a '''Planned Finish''' date, even if the '''Name''' is provided, OnePager provides the '''warning message''' shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(5A)-02252022.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(5A)-02252022.png</center>
| |
| − |
| |
| − | ==OnePager Chart Representation of Virtual Columns ==
| |
| − |
| |
| − | '''OnePager''' '''imports''' all Planisware Enterprise '''columns''' at the beginning of the chart building process and analyzes them for '''data type''' and how they may be used in charts. Planisware Enterprise has many '''defined columns'''. Planisware Enterprise does not support '''User Defined Columns'''. Any additional columns you may need must be established through discussions with your Planisware Enterprise support. The OnePager intelligent preprocessor '''imports''' all available '''columns''' and analyzes them to set up dropdown lists of '''imported columns''' that are available within OnePager’s control scheme.
| |
| − |
| |
| − | '''OnePager '''also builds additional '''“virtual” columns''' for use in your charts that are '''constructed '''based upon data '''imported '''from your Planisware Enterprise '''Project formatted''' file. These '''virtual columns''' are provided in '''OnePager '''so that you can use all the features of '''OnePager''' when designing your charts.
| |
| − |
| |
| − | ===OnePager Virtual Columns for Planisware Enterprise, an Example===
| |
| − |
| |
| − | ====Levels 1 through 10 Summary ID/Name Virtual Columns for Planisware Enterprise====
| |
| − |
| |
| − | OnePager Pro and OnePager Express users have found it beneficial to use many of the '''OnePager virtual columns''' in their charts as shortcuts. For example, take the Planisware Enterprise '''source plan''' below that has '''indented task names''' that establishes a '''Work Breakdown Structure''':
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(6)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(6)-04252023.png</center>
| |
| − |
| |
| − | Creating the '''OnePager''' chart from the Planisware Enterprise '''source plan''' above, we get this:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(7)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(7)-04252023.png</center>
| |
| − |
| |
| − | This is just one example of the use of '''OnePager virtual columns'''.
| |
| − |
| |
| − | The '''OnePager virtual columns '''used in the example above represent only three of the '''virtual columns '''available for use in charts. '''OnePager '''can represent up to ten (10) levels for '''Summary name '''and '''Summary ID'''. The list of '''Level “x” Summary name '''and '''Level “x” Summary ID''' is shown in this illustration of a '''Swimlane Group by '''dropdown list:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(8)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(8)-04252023.png</center>
| |
| − |
| |
| − | For more information on the use of '''Rows and Swimlanes''', please see the articles at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Creating and Editing Rows and Swimlanes for Version 7.2 (Portal) | Creating and Editing Rows and Swimlanes (Portal)]] 12.0.1-72
| |
| − | | [[Rows/Swimlane Tab for Version 7.2 | Rows/Swimlane Tab]] 21.2.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ====Another OnePager Virtual Column for Planisware Enterprise====
| |
| − |
| |
| − | As mentioned above, '''OnePager '''adds '''virtual columns''', and in most cases, populates these '''virtual column '''cells with data '''imported '''from your Planisware Enterprise '''source plan''' as illustrated above.
| |
| − |
| |
| − | There is one additional '''virtual column''' available in '''OnePager '''charts built with Planisware Enterprise '''source plans''' are discussed in the sub-section below:
| |
| − |
| |
| − | :* Duration (computed)
| |
| − |
| |
| − | The '''Duration (computed) virtual column''' is populated from your Planisware Enterprise '''source plan''' from '''imported''' data. The illustration below shows a '''source plan''' with defined '''Duration (computed)''' as a text column:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_13-72-(12B)-02232023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(12B)-02232023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12B)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12B)-04252023.png</center>
| |
| − |
| |
| − | ==Other Useful Columns from Planisware Enterprise==
| |
| − |
| |
| − | ===Line identifier Column===
| |
| − |
| |
| − | The '''Line identifier column''' provides an integer value counting from one (1) to the number of lines in the '''source plan''' as shown below:
| |
| − |
| |
| − | The '''Line identifier''' is shown in the '''source plan '''below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(6A)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(6A)-04252023.png</center>
| |
| − |
| |
| − | You can display the '''Line identifier''' in a '''text column''' as shown below where the '''Left#1 text column''' is used to show '''Line identifier''' values:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(12A)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12A)-04252023.png</center>
| |
| − |
| |
| − | ===ParentID and SmartsheetTaskID Columns===
| |
| − |
| |
| − | The '''ParentID''' '''column''' cells contain the identification number of the task’s '''parent''' task in the '''WBS'''. The '''SmartsheetTaskID''',''' '''created from the Planisware Enterprise '''source plan’s '''data and maintained by '''OnePager''', is the Planisware Enterprise task’s internal Planisware Enterprise identification number. '''OnePager''' uses the '''SmartsheetTaskID''' values and the relationships between '''parent''' and '''subordinate '''tasks in the project’s '''WBS''' to calculate the individual '''ParentID''' value for each task bar shown in the chart. Where a task bar does not have a '''parent''' task bar, the value of the '''ParentID '''is set to zero (0).
| |
| − |
| |
| − | To illustrate '''ParentID''' and '''SmartsheetTaskID '''consider the '''source plan '''as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(8A)-10172021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(8A)-10172021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(8A)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(8A)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(8A)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(8A)-04212023.png</center>
| |
| − |
| |
| − | When this '''source plan''' segment above is '''imported '''to '''OnePager''' and a chart is created, the portion of the chart containing the above '''parent''' and '''subordinate''' tasks looks like this with the corresponding values for '''ParentID''' and '''SmartsheetTaskID''':
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(8B)-10172021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(8B)-10172021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(8B)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(8B)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(8B)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(8B)-04212023.png</center>
| |
| − |
| |
| − | Using the '''ParentID''' and '''SmartsheetTaskID column''' cells shown above it is possible to see the '''subordinate/parent''' relationship between the two sets of task shown in the two illustrations above.
| |
| − |
| |
| − | ===Row ID Column===
| |
| − |
| |
| − | When '''OnePager imports''' a Planisware Enterprise '''source plan''' it also '''imports '''the '''row number''' for each task or milestone. '''OnePager''' assures that the values for '''Row''' are sequential as shown in the original Planisware Enterprise task listing regardless of how tasks were subsequently inserted into Planisware Enterprise. This information is made available in the '''Row ID virtual column '''as illustrated in the '''source plan '''below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(9)-10052021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(9)-10052021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(9)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(9)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(9)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(9)-04212023.png</center>
| |
| − |
| |
| − | The '''Row ID column''' can be displayed in the chart as a '''text column''' as shown here:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(10)-10052021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(10)-10052021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(10)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(10)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(10)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(10)-04212023.png</center>
| |
| − |
| |
| − | The '''Row ID column''' is useful when editing the chart, for example, when determining additional tasks to add to the chart.
| |
| − |
| |
| − | ===Summary? Column===
| |
| − |
| |
| − | The '''Summary?''' '''column''' is a '''Boolean column''' taking on the value of '''TRUE''' if the associated task is a '''summary '''task, that is, with subordinate-tasks organized below it and '''FALSE''' if the associated task does not have subordinate-tasks organized below it. In the Planisware Enterprise '''source plan '''shown below, '''Summary''' and '''Non-Summary '''tasks are highlighted:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(11)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(11)-04252023.png</center>
| |
| − |
| |
| − | Using the above Planisware Enterprise '''source plan''' to create the '''OnePager '''chart, we can show the values from the '''Summary? column''' as shown below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_11-72-(12)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12)-04252023.png</center>
| |
| − |
| |
| − | The above chart shows which displayed task bars are '''Summary? tasks (TRUE)''' and which are '''Non-Summary tasks (FALSE)'''.
| |
| − |
| |
| − | ===On Critical Path?===
| |
| − |
| |
| − | Planisware Enterprise shows the '''critical path''' in the '''Gantt bar '''display highlighted in red as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12B)-10172021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12B)-10172021.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12B)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12B)-04252023.png</center>
| |
| − |
| |
| − | The '''OnCriticalPath''' '''column''' is a '''Boolean''' value '''column''' whose cells either contain the word '''“True”''' or '''“False”''' depending on whether the individual task is '''ON''' or '''Not ON''' the '''critical path'''. These values are shown in the chart below in the '''OnCriticalPath column''':
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12C)-10172021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12C)-10172021.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12C)-04252023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12C)-04252023.png</center>
| |
| − |
| |
| − | In the illustration above, all task bars that have '''“True”''' in their '''OnCriticalPath''' '''column''' cells are on the '''critical path '''as calculated by Planisware Enterprise.
| |
| − |
| |
| − | ==Representation of Project Scheduling Data Columns from Planisware Enterprise Source Plans==
| |
| − |
| |
| − | ===Representing Percent Complete (% Complete)===
| |
| − |
| |
| − | Planisware Enterprise has an available '''column''' called '''% Complete''' which can be populated with data that indicates the extent to which a task is progressing. The '''% Complete column’s cells''' are automatically populated with your numeric value followed by a '''percent sign''' ('''%'''). A sample portion of a Planisware Enterprise '''source plan '''looks like this with the '''% Complete column '''highlighted:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12H)-10212021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12H)-10212021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(12H)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(12H)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12H)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12H)-04212023.png</center>
| |
| − |
| |
| − | The '''OnePager '''chart created from the above Planisware Enterprise '''source plan''' looks like this:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12I)-10212021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12I)-10212021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(12I)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(12I)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12I)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12I)-04212023.png</center>
| |
| − |
| |
| − | Since Planisware Enterprise has a defined '''column '''called '''% Complete''', it is our recommendation that you use this Planisware Enterprise defined '''column''' in your charts to represent '''percent complete''' for tasks and milestones.
| |
| − |
| |
| − | For more information on using the '''percent complete''' feature, please see the article at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Percent complete for OnePager for Version 7.2 | Percent complete for OnePager]] 10.3.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Representing Multiple Resources===
| |
| − |
| |
| − | '''OnePager''' can represent as many resources in the chart as are assigned to a task in Planisware Enterprise. For example, the Planisware Enterprise spreadsheet below show three tasks with two resources assigned to each task:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12F)-10192021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12F)-10192021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(12F)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(12F)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12F)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12F)-04212023.png</center>
| |
| − |
| |
| − | '''OnePager imports''' the data in the '''Assign to column''' and places each resource into the chart separated by a comma as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12G)-10192021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12G)-10192021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(12G)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(12G)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(12G)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(12G)-04212023.png</center>
| |
| − |
| |
| − | ===Representing Baseline Data===
| |
| − |
| |
| − | When the Planisware Enterprise '''source plan''' is configured with '''baseline start/finish dates''',''' OnePager '''can represent them in the chart when the '''Chart Properties '''form’s '''Task Bars '''and/or''' Milestones '''tabs are configured to do so as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(17)-10182021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(17)-10182021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(17)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(17)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(17)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(17)-04212023.png</center>
| |
| − |
| |
| − | When the '''Baselines '''function is '''enabled''' and the '''Baseline start/finish dates''' are displaced to the right of the '''baseline shape''', the chart looks like this:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(18)-10182021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(18)-10182021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(18)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(18)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(18)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(18)-04212023.png</center>
| |
| − |
| |
| − | For more information on '''Baseline representation''', please see the article:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Baselines for OnePager for Version 7.2 | Baselines for OnePager]] 10.5.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Representing Critical Path Segments===
| |
| − |
| |
| − | Planisware Enterprise '''source plans''' do not support '''critical path segments'''. As a result, OnePager cannot '''import''' such data and does not provide the capability to represent '''critical path segments''' in the chart.
| |
| − |
| |
| − | When the Planisware Enterprise '''source plan''' is configured to produce '''critical-path segments''',''' OnePager '''can represent them in the chart when the '''Chart Properties '''form’s '''Task Bars '''and/or''' Milestones '''tabs are configured to do so as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(17A-A)-02222022.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(17A-A)-02222022.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(17A-A)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(17A-A)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(17A-A)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(17A-A)-04212023.png</center>
| |
| − |
| |
| − | '''OnePager''' can represent '''critical-path segments''' in the chart as calculated by Planisware Enterprise and as shown in the '''source plan'''. As a sample, the Planisware Enterprise spreadsheet below shows several sample tasks highlighted with a narrow red bar across the top of the '''task bar''' which indicates that the '''task bar''' is on a '''critical-path segment''':
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12-F-A)-02222022.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12-F-A)-02222022.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(17F-A)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(17F-A)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(17F-A)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(17F-A)-04212023.png</center>
| |
| − |
| |
| − | '''OnePager imports''' the data from a '''checkbox''' column named '''Critical''' as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12-F-B)-02222022.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12-F-B)-02222022.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(17B-B)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(17B-B)-02152023.png</center>
| |
| − |
| |
| − | As an alternative and as shown in the '''Set critical-path properties''' form, you can use the column called '''OnCriticalPath''' to control the display of the '''critical-path segments''' in the chart.
| |
| − |
| |
| − | For more information on '''Critical-Path Segments''', please see the article:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Critical path for OnePager for Version 7.2 | Critical path for OnePager]] 10.7.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Using the OnePager Deadline Representation Feature===
| |
| − |
| |
| − | '''OnePager '''has a feature that lets you display a '''deadline symbol '''in the chart that represents the '''latest finish date''' for the task or when the milestone must be met. A portion of a chart with '''deadline symbols''' looks like this:
| |
| − |
| |
| − | <center>[[File:P70-10_9_1-(2)-06032020.png]]</center>
| |
| − | <center>P70-10_9_1-70-(2)-09182019.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(2)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(2)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(2)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(2)-04212023.png</center>
| |
| − |
| |
| − | When '''deadlines''' are turned '''ON''', they appear (by default) as '''down-arrow symbols''' in each task bar's row at the '''deadline date''' position with respect to the '''time axis.''' Above, '''deadline symbols''' that are not contained within their respective task bar are shown with '''black dash-dot connecting lines''' to illustrate the capability.
| |
| − |
| |
| − | It is highly recommended that if you want to use the '''deadlines feature''' that you define a '''Deadlines column '''in your Planisware Enterprise '''source plan''' and populate it with appropriate dates. When '''OnePager imports''' your '''source plan''' the intelligent engine recognizes '''“Deadline” '''as containing the dates for this purpose and populates the appropriate dropdown lists.
| |
| − |
| |
| − | Controls for displaying '''deadline symbols '''are provided in the '''Template Properties '''and '''Chart Properties '''form’s '''Task Bars '''and '''Milestones''' tabs where you can specify the Planisware Enterprise '''source plan''' '''column''' to represent '''deadline dates''' and specify their graphical representation in the chart.
| |
| − |
| |
| − | For convenience, '''OnePager '''assumes that the Planisware Enterprise '''Project formatted '''file’s '''Deadline date column''' is the '''default column''' that '''OnePager '''uses to represent '''deadline symbols '''in the chart. This setting is established in all Planisware Enterprise '''distributed Template Properties '''forms.
| |
| − |
| |
| − | The '''deadline''' setting is established in all Planisware Enterprise '''distributed Template Properties '''form’s '''Field Mappings '''tab as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(13-1)-01032022.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(13-1)-01032022.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(13)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(13)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(13)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(13)-04212023.png</center>
| |
| − |
| |
| − | As shown above, the '''Deadline date column name''' can be changed '''before''' the chart is created by using the '''Template Properties '''form’s '''Field Mappings''' tab to select another preferred '''Project formatted date column'''. Changing the '''Deadline date column name after '''the chart is created requires using the '''Field Mappings''' tab in the '''Chart Properties '''form.
| |
| − |
| |
| − | For more information on using '''Deadline symbols''', please see the article at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Deadlines for OnePager for Version 7.2 | Deadlines for OnePager]] 10.9.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Using the OnePager Endpoints Representation Feature===
| |
| − |
| |
| − | '''OnePager '''also has a feature that lets you display a '''multiple endpoint symbols '''in the chart that represent potentially important dates for a task. A portion of a chart with four (4) '''endpoint symbols''' associated with each task bar looks like this:
| |
| − |
| |
| − | <center>[[File:P70-10_11_1-(7-1)-06042020.png]]</center>
| |
| − | <center>P70-10_11_1-(7-1)-06042020.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(7)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(7)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(7)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(7)-04212023.png</center>
| |
| − |
| |
| − | When '''one or more endpoints''' are turned '''ON''', they appear (by default) as '''down-arrow symbols''' in each task bar's row at the '''endpoint’s date''' position'''.''' Above, '''endpoint symbols''' that are not contained within their respective task bar are shown with '''black dash-dot connecting lines''' to illustrate the capability.
| |
| − |
| |
| − | Controls for displaying '''endpoint symbols '''are provided in the '''Template Properties '''and '''Chart Properties '''form’s '''Task Bars '''and '''Milestones''' tabs where you can specify the Planisware Enterprise '''source plan column''' to represent '''endpoint dates''' and specify their graphical representation in the chart.
| |
| − |
| |
| − | For convenience, '''OnePager '''assumes that the following Planisware Enterprise '''Project formatted date columns''' are the '''default columns''' that '''OnePager '''uses to represent '''endpoint symbols '''in the chart:
| |
| − |
| |
| − | :* '''Endpoint 1''': '''Start Date'''
| |
| − | :* '''Endpoint 2''': '''Finish Date'''
| |
| − | :* '''Endpoint 3''': '''Baseline Start'''
| |
| − | :* '''Endpoint 4''': '''Baseline Finish'''
| |
| − |
| |
| − | These setting are established in all Planisware Enterprise '''distributed Template Properties '''form’s '''Task Bars '''tab in the '''Task Bar Decorations''' sub-control group at the '''Endpoints '''button. ('''Milestones''' do not display '''Endpoint symbols'''.) Checking the '''Endpoints '''checkbox '''ON''' and clicking the '''Endpoints''' '''Properties… '''button accesses the '''Set endpoint properties''' form where the '''default endpoint dates''' can be changed '''before''' the chart is created. Following the same path in the '''Chart Properties '''form to the '''Set endpoint properties '''form can accomplish the same result '''after''' the chart is created.
| |
| − |
| |
| − | For more information on using '''Endpoint symbols''', please see the article at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Endpoints for OnePager for Version 7.2 | Endpoints for OnePager]] 10.11.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ===Representing Task Links===
| |
| − |
| |
| − | '''OnePager''' displays '''Task Links''' in the chart when the '''“master switch” '''for '''Task Links '''in the '''Template Properties '''form’s '''Task Link '''tab is checked '''ON''' as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(14)-10182021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(14)-10182021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(14)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(14)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(14)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(14)-04212023.png</center>
| |
| − |
| |
| − | When the '''“master switch”''' is checked '''ON''', '''Task Links '''are '''enabled''' and can be shown in the chart after the '''Show data-driven links''' checkbox is checked '''ON '''in the '''Chart Properties '''form’s '''Task Link '''tab and the '''source plan column''' containing the '''task link predecessor data''' is set in the '''from''' window as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(15)-10182021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(15)-10182021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(15)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(15)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(15)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(15)-04212023.png</center>
| |
| − |
| |
| − | You can use the above form to change the properties of the '''Task Links '''to meet your schedule discussion needs. When the chart is created, the '''Task Links '''look like this:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(16)-10182021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(16)-10182021.png</center>
| |
| − | <center>[[File:P72-4_0_1_13-72-(16)-02152023.png]]</center>
| |
| − | <center>P72-4_0_1_13-72-(16)-02152023.png</center>
| |
| − | <center>[[File:P72-4_0_1_11-72-(16)-04212023.png]]</center>
| |
| − | <center>P72-4_0_1_11-72-(16)-04212023.png</center>
| |
| − |
| |
| − | In the chart shown above, the '''Predecessor column''' is shown as a '''Left#1 text column''' to indicate the task bar that is the '''predecessor''' for the '''task link'''. The '''SmartsheetRowNumber''' '''column''' is shown as the '''Left#2 text column''' to identify the '''successor''' task bar.
| |
| − |
| |
| − | For more information on '''Task Links''', please see the articles at:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | | [[Linking Task and Milestones Using Manual and Data-Driven Task Links for Version 7.2 | Linking Task and Milestone Using Manual and Data-Driven Task Links (Portal)]] 19.0.1-72
| |
| − | |}
| |
| − | </center>
| |
| − |
| |
| − | ==Related Link==
| |
| − |
| |
| − | {| class="wikitable"
| |
| − | | [[Getting Started with OnePager Bundle Version 7.2 | Getting Started with OnePager Bundle]] 3.0.3-72
| |
| − | | [[Using Planisware Enterprise Source Plans with OnePager Version 7.2 | Using Planisware Enterprise Source Plans with OnePager]] 3.0.3.9-72
| |
| − | |-
| |
| − | | [[Basic Workflows for Version 7.2 (Portal) | Basic Workflows (Portal)]] 7.0.1-72
| |
| − | | [[Conditional Import for Version 7.2 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-72
| |
| − | |-
| |
| − | | [[Merging the Wrong Tasks into a Chart for Version 7.2 - OnePager Bundle - Planisware Enterprise | Merging the Wrong Tasks into a Chart - OnePager Bundle - Planisware Enterprise]] 7.22.5-72
| |
| − | | [[Percent complete for OnePager for Version 7.2 | Percent complete for OnePager]] 10.3.1-72
| |
| − | |-
| |
| − | | [[Baselines for OnePager for Version 7.2 | Baselines for OnePager]] 10.5.1-72
| |
| − | | [[Deadlines for OnePager for Version 7.2 | Deadlines for OnePager]] 10.9.1-72
| |
| − | |-
| |
| − | | [[Endpoints for OnePager for Version 7.2 | Endpoints for OnePager]] 10.11.1-72
| |
| − | | [[Creating and Editing Rows and Swimlanes for Version 7.2 (Portal) | Creating and Editing Rows and Swimlanes (Portal)]] 12.0.1-72
| |
| − | |-
| |
| − | | [[Linking Task and Milestones Using Manual and Data-Driven Task Links for Version 7.2 | Linking Task and Milestone Using Manual and Data-Driven Task Links (Portal)]] 19.0.1-72
| |
| − | | [[Data-Driven Task Links for Planisware Enterprise for Version 7.2 | Data-Driven Task Links for Planisware Enterprise]] 19.1.1.9-72
| |
| − | |-
| |
| − | | [[Rows/Swimlane Tab for Version 7.2 | Rows/Swimlane Tab]] 21.2.1-72
| |
| − | | [[Managing Templates for Version 7.2 (Portal) | Managing Templates (Portal)]] 24.0.1-72
| |
| − | |}
| |
| − |
| |
| − | (4.0.1.11-72)
| |
| − |
| |
| − | [[Category:Version 7.2]]
| |
| − | [[Category:Getting Started with Version 7.2]]
| |
| − | [[Category:Planisware Enterprise]]
| |
| − | [[Category:Core Concepts]]
| |
| − | [[Category:OnePager Choices Form]]
| |
| − | [[Category:Templates]]
| |
| − | [[Category:Task Links]]
| |
| − | [[Category:Text Columns]]
| |
| − | [[Category:Rows and Swimlanes]]
| |
| − | [[Category:Multiple Swimlane Levels]]
| |
| − | [[Category:Importing]]
| |
| − | [[Category:Charts]]
| |
| − | [[Category:Tool Bar]]
| |
| − | [[Category:Templates Versus Charts]]
| |
| − | [[Category:Importing]]
| |
| − | [[Category:OnePager Bundle]]
| |
