|
|
| (212 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | =OnePager Import of Data from Project for the Web for Version 7.2 (P72-4_0-1_9-72-02142023.txt)=
| |
| − |
| |
| | ==Introduction== | | ==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 Microsoft's Project for the Web.
| + | This article is focused on using the ''' Column Splitting''' feature with OnePager Bundle '''Standalone''' and '''imported''' Asana '''source plans'''. |
| | | | |
| − | In most cases '''OnePager''' handles data fields from Project for the Web very much like data coming from Microsoft Project. This article focuses on two major topics:
| + | ==About Splitting and Parsing Fields== |
| | | | |
| − | :1) Connecting to and '''importing''' Project for the Web data into '''OnePager'''.
| + | The OnePager '''column splitting''' feature allows you to '''duplicate task bars''' when a task in your Asana '''source plan''' is assigned to '''multiple resources''' (or anything else). Because assignments from Asana often are '''comma-delimited''', this feature enables OnePager to '''parse the comma-delimited list''' and '''create a unique task bar''' for each instance in the '''comma-separated''' list. |
| | | | |
| − | :2) '''OnePager’s''' handling of specific Project for the Web '''column''' data once those data are '''imported'''.
| + | ===Split Resource Names Example=== |
| | | | |
| − | As a convention, whenever we refer to the '''OnePager''' in the context of Project for the Web, we'll just say '''OnePager''' when it’s absolutely clear that we are discussing '''OnePager''' with Project for the Web. Since only the '''Standalone''' edition of '''OnePager''' connects to Project for the Web files online, we'll just leave the suffix '''"Standalone"''' off.
| + | Say you want to use '''color-codes''' on task bars/milestone symbols based upon your Asana '''source plan’s Assigned to''' column as shown below: |
| | | | |
| − | ==About Connecting and Importing Project for the Web Data to OnePager==
| + | <center>[[File:P72-24_5_3-72-(1)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(1)-11022023.png</center> |
| | | | |
| − | '''OnePager imports '''data from Project for the Web by first making the '''connection''' from '''OnePager '''to your Project for the Web account online. Therefore, you must first have a Project for the Web account and '''login credentials''' so '''OnePager '''can access your account, your Project for the Web files, and be able to download selected file or files to your computer. | + | Some of the entries in the '''Assigned to''' column consist of multiple, '''comma-separated''' items and some tasks only used one '''resource'''. Without the '''column splitting''' feature, a chart '''created''' from these data and assigned task bar/milestone symbol '''colors''' based upon the '''Assigned to''' column looks like this: |
| | | | |
| − | Detailed information on setting up you Project for the Web data for import to '''OnePager''' and other topics related to '''getting started using OnePager Bundle''' can be found at this article:
| + | <center>[[File:P72-24_5_3-72-(5)-11272023.png]]</center> |
| | + | <center>P72-24_5_3-72-(5)-11272023.png</center> |
| | | | |
| − | <center>
| + | OnePager, in this case, treats the '''entire string''' as an individual '''Assigned to''' value. To provide more flexibility in displaying task bars that have '''multiple resources''' assigned, OnePager supports the concept of a '''column splitting'''. This feature recognizes '''comma-separated''' values in a '''designated column''' and '''creates a separate task bar''' for each of the '''comma-separated''' values. |
| − | {| class="wikitable"
| + | |
| − | | [[Using Microsoft Project for the Web Source Plans with OnePager Version 7.2 | Using Microsoft Project for the Web Source Plans with OnePager]] 3.0.3.5-72
| + | |
| − | |}
| + | |
| − | </center>
| + | |
| | | | |
| − | ===Data Imports to OnePager=== | + | ===Enabling Splitting=== |
| | | | |
| − | '''OnePager''' expects that you created a Project for the Web '''Project formatted''' file from one of the many available Project for the Web templates. In most cases, the '''column headings''' for the '''Project formatted '''file look like this: | + | To use this feature requires turning '''ON''' the feature in the Asana '''Template Properties''' form you intend to use to make the chart. The setting must be turned '''ON''' before the chart is created so launch OnePager Bundle from the '''desktop icon''', click the '''NEW''' button on the '''OnePager Bundle Start''' form to access the '''OnePager choices''' form, '''select''' your Asana '''source plan''', and type in the chart's '''title''' as shown here: |
| | | | |
| − | <center>[[File:P72-4_0_1_9-72-(1)-01312023.png]]</center> | + | <center>[[File:P72-24_5_3-72-(2A)-11022023.png]]</center> |
| − | <center>P72-4_0_1_9-72-(1)-01312023.png</center> | + | <center>P72-24_5_3-72-(2A)-11022023.png</center> |
| | | | |
| − | ====Minimum Column Names and Flags====
| + | When you click the '''Next>''' button at the bottom of the form, OnePager accesses the second page of the '''OnePager choices''' form shown below: |
| | | | |
| − | The minimum '''Column names''' needed by '''OnePager '''are the '''Task Name''', '''Start''', and '''Finish'''. For those OnePager Pro users, Project for the Web does not make '''Boolean''' fields available to OnePager that are used by OnePager Pro to select tasks for '''import'''. To provide a means for you to have control over the tasks you require to be shown in OnePager from Project for the Web '''source plans''', OnePager provides a new form accessed from the '''OnePager choices''' form or '''OPC''' form that can be used for this purpose. More information on how to select tasks using the '''Project for the Web Task List''' form is provided below.
| + | <center>[[File:P72-24_5_3-72-(2AA)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2AA)-11022023.png</center> |
| | | | |
| − | ====Adding Your Own Columns====
| + | Clicking the '''Edit current template''' button accesses the current '''Template Properties''' form. Navigate to the '''Field Mappings''' tab on the form, check the '''Enable splitting on:''' checkbox to '''ON''' and (in this example) select the '''Assigned To''' column from the dropdown list provided. The results are shown here: |
| | | | |
| − | Project for the Web features the capability for you to add your own '''User Defined Columns''' to the '''Project formatted''' file which '''OnePager imports'''. These additional '''column''' names can be used to organize your '''OnePager '''chart such as for defining '''Rows''' and '''Swimlanes''' in the chart or for presenting '''text '''information to be displayed in the chart as '''text columns'''. As a further example, the illustration below shows several '''User Defined Columns''' that can provide data for the '''OnePager '''chart and enhance your schedule presentation:
| + | <center>[[File:P72-24_5_3-72-(2AAA)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2AAA)-11022023.png</center> |
| | | | |
| − | <center>[[File:P72-4_0_1_9-72-(3)-01312023.png]]</center>
| + | Click the '''Save and use''' button to complete the process and close the current '''Template Properties''' form returning you to the second page of the '''OnePager choices''' form show above. |
| − | <center>P72-4_0_1_9-72-(3)-01312023.png</center>
| + | |
| | | | |
| − | ===OnePager Recognized Data Types=== | + | ===Split Resources in the Chart=== |
| | | | |
| − | What follows is a short discussion of how '''OnePager '''applies it’s built in intelligence functions with respect to Project for the Web’s '''User 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 Project for the Web '''source plan'''. There are four (4) '''column types''' that '''OnePager '''looks for when '''importing''' data from Project for the Web:
| + | Clicking the '''Create new chart''' button completes the process and creates the chart with the '''column splitting''' feature in use. The chart with '''splitting''' looks like this: |
| | | | |
| − | :* Dates | + | <center>[[File:P72-24_5_3-72-(2)-11022023.png]]</center> |
| − | :* Numbers
| + | <center>P72-24_5_3-72-(2)-11022023.png</center> |
| − | :* Text Strings (A through Z, 0-9, special characters)
| + | |
| | | | |
| − | All data, regardless of '''data type''', are '''imported''' from Project for the Web '''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 Project for the Web '''source plan''' is shown here:
| + | In the chart with '''column splitting''' shown above, there are now several more task bars in the '''Chart Editor''' than there were before. The task bar for '''Plate Movement''' is now '''split into two (2) separate task bars''', one for each of the '''two resources assigned'''. The task bar for '''Centrifugal Barrier''' is now '''split into three (3) separate task bars''', one for each of the '''three resources''' that were assigned to this task in the Asana '''source plan'''. Each of the '''resources''' has a unique '''color''' assigned. Each of the '''resources''' appears by itself in the '''Legend'''. The '''Legend title''' shows the '''column name''' that is used for '''splitting the columns'''. |
| | | | |
| − | <center>[[File:P72-4_0_1_9-72-(4)-01312023.png]]</center>
| + | With this feature, you can use '''column splitting''' just like any other column by using the dropdowns in the '''Template Properties''' form or '''Chart Properties''' form to assign '''colors, highlight task bars and milestone symbols, and to define and label rows and swimlanes'''. |
| − | <center>P72-4_0_1_9-72-(4)-01312023.png</center>
| + | |
| | | | |
| − | Highlighted above is the second page of the '''OnePager choices '''form showing a dropdown list of Project for the Web available '''column names''' along with '''column names '''made available by '''OnePager'''.
| + | ==Splitting Resources and Task Links== |
| | | | |
| − | ==Selecting Tasks for Import into OnePager==
| + | When task bars with '''Data-Driven''' or manual '''Task Links''' are '''split''', the '''Task Links''' ('''Data-Driven''' and manual) are '''not shown'''. Further, the '''Task Links''' that are now '''hidden''' and '''do not''' have entries in the '''Where are My Links?''' form. |
| | | | |
| − | Since '''OnePager '''is connected to your Project for the Web 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.
| + | ==Related Links== |
| | | | |
| − | 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 Project for the Web '''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 Microsoft Project for the Web Source Plans with OnePager Version 7.2#Launching OnePager Using Microsoft Project for the Web Source Plans for the First Time | Launching OnePager Using Microsoft Project for the Web Source Plans for the First Time]] 3.0.3.5-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====
| |
| − |
| |
| − | Project for the Web '''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_9-72-(4B)-01312023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(4B)-01312023.png</center>
| |
| − |
| |
| − | ====Task Selection Option (2): Select individual task to import:====
| |
| − |
| |
| − | This task selection option is recommended because it provides you with control over all the tasks in the '''source plan''' that can be '''imported'''. Clicking the '''Select individual task to import:''' radio button or the '''Choose tasks''' button accesses the '''Project for the Web Task List''' form as shown below:
| |
| − |
| |
| − | <center>[[File:P72-3_0_3_5-72-(10A)-12192022.png]]</center>
| |
| − | <center>P72-3_0_3_5-72-(10A)-12192022.png</center>
| |
| − |
| |
| − | The '''Project for the web Task List''' form is displayed with the '''Show''' column having all its checkboxes checked '''OFF''' or blank. Check the checkbox '''ON''' for each task listed in the '''grid''' that you intend to '''import''' into OnePager for your chart. The '''Project for the web Task List''' form's allow you to:
| |
| − |
| |
| − | :* '''Show All tasks'''
| |
| − | :* '''Hide All tasks'''
| |
| − | :* '''Filter specific tasks to be shown'''
| |
| − | :* '''Sort the Sequence, Task Name, Start Date, Finish Date, and Task ID''' columns into '''ascending''' or '''descending''' order.
| |
| − |
| |
| − | Shown in the illustration above is the '''file name''' for the Microsoft Project for the Web '''source plan''' and the distributed Microsoft Project for the Web '''Template Properties''' form that '''OnePager''' selects as a starting point for you. Also shown above is the name selected for the '''OnePager Bundle NEW''' chart. At this point you can change the '''Template Properties''' form used to build the chart by clicking the '''Change''' button in the '''Starting Template''' sub-section of the '''OnePager Choices''' form.
| |
| − |
| |
| − | ====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 '''Start Dates''' and '''Finish Dates''':
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_9-72-(4E)-01312023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(4E)-01312023.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_9-72-(4F)-01312023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(4F)-01312023.png</center>
| |
| − |
| |
| − | The illustration created above includes tasks within the '''Scheduled Start Dates '''and''' Scheduled Finish Dates''' included in the '''Conditional Import Rules''' form. The '''Conditional Import Rules '''form with the three rules is shown below:
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_9-72-(4G)-01312023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(4G)-01312023.png</center>
| |
| − |
| |
| − | Any Project for the Web '''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>
| |
| − |
| |
| − | ==OnePager Chart Representation of User Defined Columns and Virtual Columns==
| |
| − |
| |
| − | '''OnePager''' '''imports''' all Project for the Web '''columns''' at the beginning of the chart building process and analyzes them for '''data type''' and how they may be used in charts. Project for the Web has a minimum number of '''defined columns'''. Project for the Web users can add '''User Defined Columns''' to their '''source plans''' as needed to suit their scheduling goals. As explained below, Project for the Web '''User Defined Fields''' are not available to OnePager.
| |
| − |
| |
| − | ===Project for the Web User Define Columns===
| |
| − |
| |
| − | 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. However, it must be kept in mind that Project for the Web does not make it's '''source plan's''' '''User Defined Columns''' available to OnePager at this time. As a result, OnePager cannot '''see''' Project for the Web '''User Defined Columns''' from your '''source plans''' and, therefore, these columns do not appear in '''column dropdown lists''' available to you in OnePager.
| |
| − |
| |
| − | Should your requirements for schedule conversations using Project for the Web require the use of '''User Defined Fields''', we encourage you to contact Microsoft Corporation to express your needs at this link:
| |
| − |
| |
| − | <center>
| |
| − | {| class="wikitable"
| |
| − | [https://feedbackportal.microsoft.com/feedback/idea/3636b0e9-9a2f-ed11-a81b-000d3a7dd504 Make Project custom fields discoverable via Microsoft.Xrm.Sdk]
| |
| − | |}
| |
| − | </center>
| |
| − | <!--
| |
| − | For example, the chart shown below has three '''User Defined Columns''' (Sub-Project, Phase, and Category):
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_9-72-(3A)-02022023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(3A)-02022023.png</center>
| |
| − |
| |
| − | These '''User Defined Columns''' are '''imported''' by '''OnePager '''and can be used to control '''rows''' and '''swimlanes''' as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(4D)-09282021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(4D)-09282021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(4D)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(4D)-02142023.png</center>
| |
| − |
| |
| − | In Project for the Web you can create as many '''User Defined Columns''' as needed, specify their '''data type''', and populate data for each task. '''OnePager imports''' all '''columns''' defined and makes them available for use in your chart.-->
| |
| − |
| |
| − | ===OnePager Virtual Columns for Project for the Web, an Example===
| |
| − |
| |
| − | '''OnePager '''also builds additional '''“virtual” columns''' for use in your charts that are '''constructed '''based upon data '''imported '''from your Project for the Web '''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 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 Project for the Web '''source plan''' below that has '''indented task names''' that establishes a '''Work Breakdown Structure''':
| |
| − |
| |
| − | <center>[[File:P72-4_0_1_9-72-(6)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(6)-02142023.png</center>
| |
| − |
| |
| − | Creating the '''OnePager''' chart from the Project for the Web '''source plan''' above, we get this:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(7)-09282021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(7)-09282021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(7)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(7)-02142023.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:P71-4_0_1_7-71-(8)-09282021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(8)-09282021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(8)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(8)-02142023.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>
| |
| − |
| |
| − | ===More OnePager Virtual Columns for Project for the Web===
| |
| − |
| |
| − | As mentioned above, '''OnePager '''adds '''virtual columns''', and in most cases populates these '''virtual column '''cells with data '''imported '''from your Project for the Web '''source plan''' as illustrated above.
| |
| − |
| |
| − | The following '''virtual columns''' available in '''OnePager '''charts built with Project for the Web '''source plans''' are discussed in the sub-sections below:
| |
| − |
| |
| − | :* PartentID
| |
| − | :* TaskID
| |
| − | :* RowNumber
| |
| − | :* Summary
| |
| − | :* Outline level
| |
| − | :* Level “x” summary ID/name
| |
| − | :* OnCriticalPath
| |
| − |
| |
| − | ====ParentID and TaskID Columns====
| |
| − |
| |
| − | The '''ParentID''' '''column''' cells contain the identification number of the task’s '''parent''' task in the '''WBS'''. The '''TaskID''',''' '''created from the Project for the Web '''source plan’s '''data and maintained by '''OnePager''', is the Project for the Web task’s internal Project for the Web identification number. '''OnePager''' uses the '''TaskID''' 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 '''TaskID '''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_9-72-(8A)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(8A)-02142023.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 '''TaskID''':
| |
| − |
| |
| − | <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_9-72-(8B)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(8B)-02142023.png</center>
| |
| − |
| |
| − | Using the '''ParentID''' and '''TaskID 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.
| |
| − |
| |
| − | ====RowNumber Column====
| |
| − |
| |
| − | When '''OnePager imports''' a Project for the Web '''source plan''' it also '''imports '''the '''row number''' for each task or milestone. '''OnePager''' assures that the values for '''RowNumber''' are sequential as shown in the original Project for the Web task listing regardless of how tasks were subsequently inserted into Project for the Web. This information is made available in the '''RowNumber 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_9-72-(9)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(9)-02142023.png</center>
| |
| − |
| |
| − | The '''RowNumber 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_9-72-(10)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(10)-02142023.png</center>
| |
| − |
| |
| − | The '''RowNumber 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 Project for the Web '''source plan '''shown below, '''Summary '''and '''Non-Summary '''tasks are highlighted:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(11)-10052021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(11)-10052021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(11)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(11)-02142023.png</center>
| |
| − |
| |
| − | Using the above Project for the Web '''source plan''' to create the '''OnePager '''chart, we can show the values from the '''Summary column''' in a '''text column '''along with the '''RowNumber''' as shown below:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12)-10052021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12)-10052021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(12)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12)-02142023.png</center>
| |
| − |
| |
| − | The above chart shows which displayed task bars are '''Summary tasks (TRUE)''' and which are '''Non-Summary tasks (FALSE)'''. These can be correlated back to the original Project for the Web '''source plan '''using the corresponding '''RowNumber'''.
| |
| − |
| |
| − | ====Outline level Column====
| |
| − |
| |
| − | The '''Outline level column''' provides an integer value counting the '''level of indentation''' of task bars starting at level one (level 1).
| |
| − |
| |
| − | The '''Outline level''' is shown in the '''source plan '''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_9-72-(8A)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(8A)-02142023.png</center>
| |
| − |
| |
| − | In the Project for the Web '''source plan '''above, '''Planning Phase''' is at the highest level with '''Assemble Resources''' and '''Create Working Plans''' at the next level down. Additionally, '''Mechanical Engineers''', '''Electrical Engineers''', and '''System Engineers''' are at one more '''subordinate '''level below '''Assemble '''Resources'''. Finally, '''Phase 1 Estimation''' is at a '''subordinate''' level below '''Create Working Plans'''. There are '''three levels''' represented in the '''source plan '''shown above and when it is '''imported''' to '''OnePager''', the chart portion looks like this with the '''Outline level column''' containing the level values in each cell:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12A)-10172021.png]]</center>
| |
| − | <center>P71-4_0_1_7-71-(12A)-10172021.png</center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(12A)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12A)-02142023.png</center>
| |
| − |
| |
| − | The '''Outline level '''values shown above represent the '''WBS levels''' for the displayed portion of the '''source plan'''.
| |
| − |
| |
| − | ====Level “x” summary ID/name Fields ====
| |
| − |
| |
| − | '''OnePager''' provides a feature that allows you to conveniently display '''levels of indention''' based upon the '''source plan’s Work Breakdown Structure'''. '''OnePager '''supports ten (10) '''levels of indention''' which can be based on the '''ID''' or the '''Name '''of the '''WBS Element'''.
| |
| − |
| |
| − | As an example, take the portion of the Project for the Web '''BlueGrass Project Plan''' shown below and note how '''OnePager''' interprets the '''WBS''':
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12D)-10182021.png]]</center>
| |
| − | <center> P71-4_0_1_7-71-(12D)-101892021.png </center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(12D)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12D)-02142023.png</center>
| |
| − |
| |
| − | When the '''OnePager''' chart is created using the '''Show It=Yes''' to control the '''import '''of data and the '''Left#1 swimlane '''is set to '''Level 1 summary name''' and the '''Left#2 swimlane '''is set to '''Level 2 summary name''', the chart looks like this for the portion of the '''source plan''' above:
| |
| − |
| |
| − | <center>[[File:P71-4_0_1_7-71-(12E)-10182021.png]]</center>
| |
| − | <center> P71-4_0_1_7-71-(12E)-101892021.png </center>
| |
| − | <center>[[File:P72-4_0_1_9-72-(12E)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12E)-02142023.png</center>
| |
| − |
| |
| − | ====OnCriticalPath Column====
| |
| − |
| |
| − | Project for the Web 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_9-72-(12B)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12B)-02142023.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_9-72-(12C)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12C)-02142023.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 Project for the Web.
| |
| − |
| |
| − | ===Representing Percent Complete (% Complete) from Project for the Web Project Formatted Files===
| |
| − |
| |
| − | Project for the Web 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 Project for the Web '''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_9-72-(12H)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12H)-02142023.png</center>
| |
| − |
| |
| − | The '''OnePager '''chart created from the above Project for the Web '''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_9-72-(12I)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12I)-02142023.png</center>
| |
| − |
| |
| − | Since Project for the Web has a defined '''column '''called '''% Complete''', it is our recommendation that you use this Project for the Web 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 from Project for the Web Project Formatted Files ===
| |
| − |
| |
| − | '''OnePager''' can represent as many resources in the chart as are assigned to a task in Project for the Web. For example, the Project for the Web 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_9-72-(12F)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12F)-02142023.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_9-72-(12G)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12G)-02142023.png</center>
| |
| − |
| |
| − | ===Representing Baseline Data from Project for the Web Import Source Plans===
| |
| − |
| |
| − | When the Project for the Web '''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_9-72-(17)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(17)-02142023.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_9-72-(17)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(17)-02142023.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 from Project for the Web Project Formatted File===
| |
| − |
| |
| − | When the Project for the Web '''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_9-72-(17A-A)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(17A-A)-02142023.png</center>
| |
| − |
| |
| − | '''OnePager''' can represent '''critical-path segments''' in the chart as calculated by Project for the Web and as shown in the '''source plan'''. As a sample, the Project for the Web 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_9-72-(12F-A)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12F-A)-02142023.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_9-72-(12F-B)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(12F-B)-02142023.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 with Project for the Web===
| |
| − |
| |
| − | '''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>
| |
| − |
| |
| − | 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 Project for the Web '''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 Project for the Web '''source plan''' '''column''' to represent '''deadline dates''' and specify their graphical representation in the chart.
| |
| − |
| |
| − | For convenience, '''OnePager '''assumes that the Project for the Web '''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 Project for the Web '''distributed Template Properties '''forms.
| |
| − |
| |
| − | The '''deadline''' setting is established in all Project for the Web '''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_9-72-(13)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(13)-02142023.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 with Project for the Web===
| |
| − |
| |
| − | '''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>
| |
| − |
| |
| − | 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 Project for the Web '''source plan column''' to represent '''endpoint dates''' and specify their graphical representation in the chart.
| |
| − |
| |
| − | For convenience, '''OnePager '''assumes that the following Project for the Web '''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 Project for the Web '''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 from Project for the Web Project Formatted Files ===
| |
| − |
| |
| − | '''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_9-72-(14)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(14)-02142023.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_9-72-(15)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(15)-02142023.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_9-72-(16)-02142023.png]]</center>
| |
| − | <center>P72-4_0_1_9-72-(16)-02142023.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 '''RowNumber''' '''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" | | {| class="wikitable" |
| | + | | [[Templates versus Charts for Version 7.2 | Templates versus Charts]] 4.0.1.3-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 | | | [[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 Microsoft Project for the Web Source Plans with OnePager Version 7.2 | Using Microsoft Project for the Web Source Plans with OnePager]] 3.0.3.5-72
| |
| | |- | | |- |
| − | | [[Basic Workflows for Version 7.2 (Portal) | Basic Workflows (Portal)]] 7.0.1-72 | + | | [[Editing with the Chart Properties form for Version 7.2 (Portal) | Editing with the Chart Properties form (Portal)]] 21.0.1-72 |
| − | | [[Conditional Import for Version 7.2 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-72 | + | | [[Template Only Features for OnePager Pro for Version 7.2 | Template Only Features for OnePager Pro]] 24.1.1-72 |
| | |- | | |- |
| − | | [[Merging the Wrong Tasks into a Chart for Version 7.2 - OnePager Bundle - Project for the Web | Merging the Wrong Tasks into a Chart - OnePager Bundle - Project for the Web]] 7.22.1-72 | + | | [[Template Only Features for OnePager Express for Version 7.2 | Template Only Features for OnePager Express]] 24.2.1-72 |
| − | | [[Percent complete for OnePager for Version 7.2 | Percent complete for OnePager]] 10.3.1-72 | + | | [[Template Only Features for Primavera P6 Source Plans in OnePager Version 7.2 | Template Only Features for Primavera P6 Source Plans in OnePager]] 24.2.2-72 |
| | |- | | |- |
| − | | [[Baselines for OnePager for Version 7.2 | Baselines for OnePager]] 10.5.1-72 | + | | [[Template Only Features for Smartsheet Source Plans in OnePager Version 7.2 | Template Only Features for Smartsheet Source Plans in OnePager]] 24.2.3-72 |
| − | | [[Deadlines for OnePager for Version 7.2 | Deadlines for OnePager]] 10.9.1-72 | + | | [[Splitting and Parsing Columns for OnePager Pro for Version 7.2 | Splitting and Parsing Fields for OnePager Pro]] 24.4.1-72 |
| | |- | | |- |
| − | | [[Endpoints for OnePager for Version 7.2 | Endpoints for OnePager]] 10.11.1-72 | + | | [[Splitting and Parsing Columns for OnePager Express for Version 7.2 | Splitting and Parsing Fields for OnePager Express]] 24.5.1-72 |
| − | | [[Creating and Editing Rows and Swimlanes for Version 7.2 (Portal) | Creating and Editing Rows and Swimlanes (Portal)]] 12.0.1-72 | + | | [[Splitting and Parsing Columns for Primavera P6 Source Plans in OnePager Version 7.2 | Splitting and Parsing Columns for Primavera P6 Source Plans in OnePager]] 24.5.2-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 | + | | [[Splitting and Parsing Columns for Smartsheet Source Plans in OnePager Version 7.2 | Splitting and Parsing Columns for Smartsheet Source Plans in OnePager]] 24.5.3-72 |
| − | | [[Data-Driven Task Links for Smartsheet for Version 7.2 | Data-Driven Task Links for Smartsheet]] 19.1.1.4-72 | + | | [[Splitting and Parsing Columns for Project for the Web Source Plans for Version 7.2 | Splitting and Parsing Columns for Project for the Web Source Plans]] 24.5.5-72 |
| | |- | | |- |
| − | | [[Rows/Swimlane Tab for Version 7.2 | Rows/Swimlane Tab]] 21.2.1-72 | + | | [[Splitting and Parsing Columns for Planisware Enterprise Source Plans for Version 7.2 | Splitting and Parsing Columns for Planisware Enterprise Source Plans]] 24.5.7-72 |
| − | | [[Managing Templates for Version 7.2 (Portal) | Managing Templates (Portal)]] 24.0.1-72 | + | | [[Splitting and Parsing Columns for Wrike in OnePager Version 7.2 | Splitting and Parsing Columns for Wrike in OnePager]] 24.5.11-72 |
| | |} | | |} |
| | | | |
| − | (4.0.1.9-72) | + | (24.5.9-72) |
| | | | |
| | [[Category:Version 7.2]] | | [[Category:Version 7.2]] |
| − | [[Category:Getting Started with Version 7.2]] | + | [[Category:Editing the Chart]] |
| − | [[Category:Smartsheet]]
| + | [[Category:Task/Milestone Editing]] |
| − | [[Category:Core Concepts]]
| + | [[Category:Column Splitting]] |
| − | [[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:Charts]] |
| − | [[Category:Tool Bar]] | + | [[Category:Task Links]] |
| − | [[Category:Templates Versus Charts]] | + | [[Category:Ribbon]] |
| − | [[Category:Importing]] | + | [[Category:Snapshots]] |
| | + | [[Category:Template Properties Form]] |
| | + | [[Category:Chart Properties Form]] |
| | + | [[Category:Asana]] |
| | [[Category:OnePager Bundle]] | | [[Category:OnePager Bundle]] |
-11022023.png)
-11272023.png)
-11022023.png)
-11022023.png)
-11022023.png)
-11022023.png)
