Difference between revisions of "Testing Article1"

From OnePager Documentation
Jump to: navigation, search
(Split Resources in the Chart)
 
(513 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Overview==
+
==Introduction==
  
Like '''making each''' '''row into a swimlane''', there may be several good reasons to '''merge two or more''' '''swimlanes '''into a '''single swimlane''' at the various '''swimlane levels'''.  This may be to consolidate like sets of '''swimlanes''' with their member '''rows''' into a '''single swimlane level cell''' or to '''reposition''' like '''swimlane level cells''' to a different '''position''' in the chart.
+
This article is focused on using the ''' Column Splitting''' feature with OnePager Bundle '''Standalone''' and '''imported''' Asana '''source plans'''.
  
The command, '''Merge swimlane''', is in the '''swimlane level''' right-click '''context menu''' shown below:
+
==About Splitting and Parsing Fields==
  
<center>[[File:P70-12_21_1-(1)-08072020.png]]</center>
+
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.
<!--<center>P70-12_21_1-(1)-08072020.png</center>-->
+
  
In order to use the '''swimlane level''' right-click '''context menu''', the chart must have at least '''one swimlane level defined''' and '''showing''' and two or more '''swimlanes''' of interest must be selected in the '''same swimlane level'''.
+
===Split Resource Names Example===
  
The '''Merge swimlane '''command is '''disabled''' when the '''swimlane level''' right-click '''context menu''' is accessed and only one''' swimlane level cell '''is '''defined''' and''' showing''' in the chart as illustrated below where the '''Left#1 swimlane level''' is '''defined '''and '''shown''':
+
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:
  
<center>[[File:P70-12_21_1-(2)-08072020.png]]</center>
+
<center>[[File:P72-24_5_3-72-(1)-11022023.png]]</center>
<!--<center>P70-12_21_1-(2)-08072020.png</center>-->
+
<center>P72-24_5_3-72-(1)-11022023.png</center>
  
The '''Merge swimlanes''' command is '''enabled''' when '''two or more swimlane level cells''' are selected as shown below:
+
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:
  
<center>[[File:P70-12_21_1-(3)-08072020.png]]</center>
+
<center>[[File:P72-24_5_3-72-(5)-11272023.png]]</center>
<!--<center>P70-12_21_1-(3)-08072020.png</center>-->
+
<center>P72-24_5_3-72-(5)-11272023.png</center>
  
Since you can configure OnePager charts with up to three '''swimlane levels''', how '''swimlane level cells''' are '''merged''' depends on the membership of the selected '''swimlane level cells''' in the '''swimlane levels''' '''defined''' in the chart.
+
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.
  
This article discusses the '''various possible configurations '''for selected '''swimlane level cells''' and how the '''Merge swimlane '''command produces a consistent result in terms of the configuration of the '''new merged swimlane''', its resulting '''position''' in the chart, and the '''labels''' assigned to the '''new merged swimlane level cell'''.
+
===Enabling Splitting===
  
Depending on the original configuration of the chart and the number of '''swimlane levels''' '''defined''' and '''showing''', the results of applying the '''Merge swimlane '''command follows a consistent pattern discussed in this article.  As an example, we can start by illustrating the results from '''merging swimlane level cells from the Left#3 swimlane level '''in the sequence shown below.
+
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:
  
:1) Start by selecting the top two '''swimlane level cells''' in the illustration below where these selected '''two swimlane level cells''' are members of all '''three defined '''and '''shown swimlane levels'''.
+
<center>[[File:P72-24_5_3-72-(2A)-11022023.png]]</center>
 +
<center>P72-24_5_3-72-(2A)-11022023.png</center>
  
:2) The '''swimlane level''' right-click '''context menu''' is accessed, and the '''Merge swimlane''' command is '''enabled''' as shown here:
+
When you click the '''Next>''' button at the bottom of the form, OnePager accesses the second page of the '''OnePager choices''' form shown below:
  
<center>[[File:P70-12_21_1-(4)-08072020.png]]</center>
+
<center>[[File:P72-24_5_3-72-(2AA)-11022023.png]]</center>
<!--<center>P70-12_21_1-(4)-08072020.png</center>-->
+
<center>P72-24_5_3-72-(2AA)-11022023.png</center>
  
:3) When the '''Merge swimlane''' command is clicked, the result is shown here:
+
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:
  
<center>[[File:P70-12_21_1-(5)-08072020.png]]</center>
+
<center>[[File:P72-24_5_3-72-(2AAA)-11022023.png]]</center>
<!--<center>P70-12_21_1-(5)-08072020.png</center>-->
+
<center>P72-24_5_3-72-(2AAA)-11022023.png</center>
  
The end result in the illustration above is the creation of a '''new merged Prime Left#3 swimlane level cell''' positioned in the same place as the '''original Prime Left#3 swimlane level cell '''with the '''new merged swimlane level cell '''displaying the '''label''' of the '''original Prime Left#3 swimlane level cell’s label'''.
+
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.
  
'''Swimlane level cells''' can be '''merged '''at the '''any swimlane level'''. In the illustration above, the '''lowest swimlane level is Left#3'''.
+
===Split Resources in the Chart===
  
:* In the illustration above the two participating '''Left#3 swimlane level cells''' selected are not members of the '''same Left#2''' or '''Left#1 swimlane level cells'''.
+
Clicking the '''Create new chart''' button completes the process and creates the chart with the '''column splitting''' feature in useThe chart with '''splitting''' looks like this:
:* As shown in the illustration above, the '''Prime Left#3 swimlane level cell''' retains its membership in its '''original Left#2 '''and''' Left#1 swimlane level cells''' because the '''Prime Left#3 swimlane level cell''' contained '''four rows''' while the '''Team 1 Left#3 swimlane level cell''' contained just '''one row'''.   
+
:* OnePager attempts to assign the '''merged swimlane’s label''' at a '''lower swimlane level''' to its '''original higher level swimlanes '''('''Left#1 '''and''' Left#2''') based on the '''modal''' selected '''swimlane level cell''' determined by the '''highest number of row'''.  In this case, the '''modal Left#3 swimlane level cell''' was the '''Prime Left#3 swimlane level cell''' because it has '''four member rows'''.
+
:* When OnePager cannot exactly determine a '''modal swimlane level cell''', the '''label''' assigned to the resulting '''merged swimlane level cell''' is made at '''random''' using the participating selected '''swimlane level cells'''.
+
  
Multiple '''swimlanes''' can be selected and the '''Merge swimlane '''command used to create a '''new merged swimlane'''.   When selecting '''swimlane level cells''', OnePager only allows selection in the '''same swimlane level'''.
+
<center>[[File:P72-24_5_3-72-(2)-11022023.png]]</center>
 +
<center>P72-24_5_3-72-(2)-11022023.png</center>
  
==Merging Swimlanes – One Swimlane Level Chart==
+
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'''.
  
To better illustrate how the '''merge swimlane '''command operates in the '''multiple swimlane level environment''', we start with the situation where one '''swimlane level''' is '''defined''' and '''showing''' in the chart.  In the sub-sections that follow, we start with the '''Left#1 swimlane level defined '''and '''showing''' as the simplest case and proceed step-wise to demonstrated OnePager’s '''Merge swimlane''' command when there are '''two '''and''' '''then''' three swimlane levels defined''' and '''showing''' in the chart.
+
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'''.
  
===Merging Swimlanes from Left#1 Swimlane Level Cells – One Swimlane Level Chart===
+
==Splitting Resources and Task Links==
  
'''Merging swimlanes''' can be illustrated in the '''one swimlane level''' chart shown here as a starting point:
+
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.
 
+
<center>[[File:P70-12_18_1-(4)-07312020.png]]</center>
+
<!--<center>P70-12_18_1-(4)-07312020.png</center>-->
+
 
+
Suppose you want to take the '''Startup swimlane''' and '''merge '''it with the '''Phase II swimlane'''.  To do this, select the '''Startup '''and '''Phase II swimlanes''' using the '''CTL+Left-Click''' method, right-click in one of the selected '''swimlane level cells''' to access the '''swimlane level''' right-click '''context menu, '''and prepare to click the '''Merge swimlane '''command as shown below:
+
 
+
<center>[[File:P70-12_21_1-(6)-08072020.png]]</center>
+
<!--<center>P70-12_21_1-(6)-08072020.png</center>-->
+
 
+
Clicking the '''Merge swimlane''' command reconfigures chart is shown here:
+
 
+
<center>[[File:P70-12_21_1-(7)-08072020.png]]</center>
+
<!--<center>P70-12_21_1-(7)-08072020.png</center>-->
+
 
+
When selected '''swimlanes''' are '''merged''' within an existing '''swimlane level cell''', OnePager places the '''new merged swimlane '''in close proximity to the original selected '''modal swimlane level cell''' to avoid major reconfiguration of the chart.  OnePager assumes that the reason for '''merging swimlanes''' is that, in most schedule presentation situations, the '''new merged swimlanes''' will be '''re-positioned''' elsewhere in the chart and potentially the '''new merged swimlane level cell label''' will be '''edited'''.  As a result, you have the option to retain the '''new merged swimlane''' in the OnePager designated '''position''' or '''move''' the '''new merged swimlane '''using the '''drag and drop''' method to a different '''position''' in the chart.
+
 
+
For more information on '''moving swimlanes''', please see the article at: [[Moving Swimlanes for Version 7.0 | Moving Swimlanes]] <!--12.10.1-70-->
+
 
+
Once the '''new merged swimlane''' is created containing the selected original '''swimlanes''' shown above, the '''new merged swimlane''' can be '''edited''' the same as any other '''swimlane''' in the chart.  '''Edits''' can include changing the '''label''' in the '''Left#1 swimlane level cell''', '''dragging and dropping''' the '''new merged swimlane''' to another '''position''' in the chart, or changing its '''background color''' in some fashion.
+
 
+
For more information on '''editing rows and swimlanes''', please see the two articles at: [[Editing Row Properties for Version 7.0 | Editing Row Properties]] <!--12.22.1-70--> and [[Editing Swimlane Properties for Version 7.0 | Editing Swimlane Properties]] <!--12.23.1-70-->
+
 
+
'''Note''' that in the above example, the '''Phase I Left#1 swimlane level cell''' originally resided between the '''Startup '''and''' Phase II Left#1 swimlane level cells'''.  Since the '''Phase I Left#1 swimlane level cell''' did not participate in the '''merge swimlanes''' operation, OnePager, in this example, pulled the '''merging swimlanes''' together keeping the '''order''' of the '''rows''' as intact as possible.  This resulted in '''moving''' the '''Startup Left#1 swimlane level cells''' and its '''row''' down to the above the '''Phase II Left#1 swimlane level cell'''.  The result is that the '''Phase I Left#1 swimlane level cell''' now appears at the top of the chart.
+
 
+
===Merging Swimlanes from Left#2 or Left#3 Swimlane Level Cells – One Swimlane Level Chart===
+
 
+
Whenever there is only '''one swimlane level defined''' and '''showing''' in the chart, regardless of whether it is '''Left#1''', '''Left#2''', or '''Left#3 swimlane level''', the example provided above in the previous sub-section applies.
+
 
+
==Merging Swimlanes – Two Swimlane Level Chart==
+
 
+
In the sub-sections that follow, we add the '''Left#2 swimlane level''' to the already present '''Left#1 swimlane level'''.  Adding the '''Left#2 swimlane level''' to the original chart gives us a chart with this configuration:
+
 
+
<center>[[File:P70-12_18_1-(9)-08032020.png]]</center>
+
<!--<center>P70-12_18_1-(9)-08032020.png</center>-->
+
 
+
===Merging Swimlane from the Left#1 Swimlane Level Cells – Two Swimlane Level Chart===
+
 
+
In a chart with '''two swimlane levels''' where the '''Left#1 swimlane level''' is the '''highest level swimlane''' (left-most '''swimlane level'''), the results from '''merging swimlanes''' in this case is the same as in the '''one swimlane level '''chart explained in the previous section.  The '''rows''' in the selected '''Left#1 swimlane level cells''' are '''merged''' into '''one swimlane level cell''' and the '''new merged Left#2 swimlane level cell’s label''' is based on the '''modal number of rows''' in the various participating original selected '''Left#1 swimlane level cells'''.
+
 
+
Using an adaptation of the example in the previous section, if we select the '''Startup Left#1 swimlane level cell''' and the '''Phase II Left#1 swimlane level cell''' for our example, the selected '''Left#1 swimlane level cells''' look like this:
+
 
+
<center>[[File:P70-12_21_1-(8)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(8)-08072020.png</center>-->
+
 
+
Above, the selection of the '''two swimlanes''' is made in the '''Left#1 swimlane level cells'''.  Both the selected '''Left#1''' and '''Left#2 swimlane level cell’s labels''' are different so the '''merged Left#1 '''and''' Left#2 swimlane level cell’s labels''' depends on the '''modal number of rows''' in the two selected sets of '''swimlane level cells'''.  '''Four rows''' for the '''Startup/Planning Left#1/Left#2 swimlane level cells''' and '''two rows''' for the '''Phase II/Development Left#1/Left#2 swimlane level cells'''.
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#1 swimlane level cells''' (perhaps the '''Phase II Left#1 swimlane level cell’s label''') and clicking the '''Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(9)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(9)-08072020.png</center>-->
+
 
+
As shown above, the '''six rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1''' and '''Left#2 swimlane levels''' and the respective '''Left#1''' and '''Left#2 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''modal number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' in the chart as close to its '''original position''' as possible and the '''rows''' within the '''merged swimlane level cell''' retain their original '''ordering'''.  This being the case, OnePager places the intervening, non-participating '''Phase I/Development Left#1/Left#2 swimlane level cell''' at the top of the chart.
+
 
+
===Merging Swimlane from the Left#2 Swimlane Level Cells – Two Swimlane Level Chart===
+
 
+
If we change the above example and make the same selections but use the '''Left#2 swimlane level cells''', the selected '''swimlanes''' look like this:
+
 
+
<center>[[File:P70-12_21_1-(10)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(10)-08072020.png</center>-->
+
 
+
In the example above, the '''two swimlanes''' are selected from the '''Left#2 swimlane level cells'''.  As in the previous sub-section, both the selected '''Left#1''' and '''Left#2 swimlane level cell’s labels''' are different so the '''merged Left#1''' and '''Left#2 swimlane level cell’s labels''' depends on the '''modal number of rows''' in the two selected sets of '''swimlane level cells'''.  '''Four rows''' for the '''Startup/Planning Left#1/Left#2 swimlane level cells''' and '''two rows''' for the '''Phase II/Development Left#1/Left#2 swimlane level cells'''.
+
 
+
Continuing the process of accessing the '''swimlane level '''right-click''' context menu''' by right-clicking in one of the selected '''Left#2 swimlane level cells''' (perhaps the '''Development Left#2 swimlane level cell’s label''') and clicking the '''Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(9)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(9)-08072020.png</center>-->
+
 
+
As shown above, the '''six rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1''' and '''Left#2 swimlane levels''' and the respective '''Left#1''' and '''Left#2 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''modal number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' in the chart as close to its '''original position''' as possible and the '''rows''' within the '''merged swimlane level cell''' retain their original '''ordering'''.  This being the case, OnePager places the intervening, non-participating '''Phase I/Development Left#1/Left#2 swimlane level cell''' at the top of the chart.
+
 
+
===Merging Swimlane with Equal Number of Rows – Two Swimlane Level Chart===
+
 
+
The two sets of examples in the two sub-sections above established that selecting '''two or more Left#1 or Left#2  swimlane level cells''' does not depend on which '''swimlane level cells''' ('''Left#1''' or '''Left#2''') are selected.  Additionally, the concept of '''modal number of rows''' governing the resulting '''merged swimlane level cell’s labels''' was also demonstrated.
+
 
+
This sub-section shows the results when '''swimlane level cells''' are selected that have an '''equal number of rows''' and how this determines the '''merged swimlane level cell’s labels'''.
+
 
+
Since selecting in either the '''Left#1 or Left#2 swimlane level cells''' is moot, so we’ll select '''two swimlane level cells''' with '''equal number of rows''' form the '''Left#2 swimlane level''' as shown below:
+
 
+
<center>[[File:P70-12_21_1-(11)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(11)-08092020.png</center>-->
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#2 swimlane level cells''' (perhaps the '''Integration & Testing Left#2 swimlane level cell’s label''') and clicking the '''Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(12)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(12)-08092020.png</center>-->
+
 
+
As shown above, the '''eight rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1 '''and''' Left#2 swimlane levels''' and the respective '''Left#1 '''and''' Left#2 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''same number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' at the bottom of the chart in this case, and the '''ordering''' of '''rows''' is retained within the original '''swimlane level cell’s''' configuration.  OnePager places the intervening, non-participating '''(Phase I/Phase II)/Development Left#1/Left#2 swimlane level cells''' at the top of the chart.
+
 
+
The choices for the '''merged Left#1 '''and''' Left#2 swimlane level cell’s labels''' are made by OnePager at '''random '''since the participating '''original swimlane level cells''' both have an '''equal number of rows''' and there is no establish '''mode'''.  As mentioned earlier in this article, OnePager assumes that after '''swimlane level cells''' are '''merged''' that actions will subsequently be taken to '''editing the merged swimlane level cell’s labels''', '''move''' the '''merged swimlane level cells''' to a different '''position''' in the chart, or do some other form of '''row''' or '''swimlane level editing'''.
+
 
+
==Merging Swimlanes – Three Swimlane Level Chart==
+
 
+
In the sub-sections that follow, we add the '''Left#3swimlane level''' to the already present '''Left#1 '''and '''Left#2 swimlane levels'''.  Adding the '''Left#3 swimlane level''' to the original chart gives us a chart with this configuration:
+
 
+
<center>[[File:P70-12_18_1-(14)-08032020.png]]</center>
+
<!--<center>P70-12_18_1-(14)-08032020.png</center>-->
+
 
+
If you’ve followed along through the discussions involving configurations of '''one''' and '''two swimlane levels''' in the chart, you can rightly suspect that the various combinations involving '''three swimlane levels''' with selected '''swimlanes''' follows a recurring pattern.
+
 
+
===Merging Swimlane from the Left#1 Swimlane Level Cells – Three Swimlane Level Chart===
+
 
+
If we change the example from the previous section and make the same selections but use the '''Left#1 swimlane level cells''', the selected '''swimlanes''' look like this:
+
 
+
<center>[[File:P70-12_21_1-(13)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(13)-08092020.png</center>-->
+
 
+
In the example above, the '''two swimlanes''' are selected from the '''Left#1 swimlane level cells'''.
+
 
+
As in the previous sub-section, both the selected '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are different, so the '''merged Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' depends on the '''modal number of rows''' in the two selected sets of '''swimlane level cells'''.  '''Four rows''' for the '''Startup/Planning/Prime Left#1/Left#2/Left#3 swimlane level cells''' and '''two rows''' for the '''Phase II/Development/Team 2 Left#1/Left#2/Left#3 swimlane level cells'''. 
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#1 swimlane level cells''' (perhaps the '''Phase II Left#1 swimlane level cell’s label''') and clicking '''the Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(14)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(14)-08092020.png</center>-->
+
 
+
As shown above, the '''six rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1, Left#2, '''and''' Left#3 swimlane levels''' and the respective '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''modal number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' in the chart as close to its '''original position''' as possible and the '''rows''' within the '''merged swimlane level cell''' retain their original '''ordering'''.  This being the case, OnePager places the intervening, non-participating '''Phase I/Development/Team 1 Left#1/Left#2/Left#3 swimlane level cell''' at the top of the chart.
+
 
+
===Merging Swimlane from the Left#2 Swimlane Level Cells – Three Swimlane Level Chart===
+
 
+
If we change the above example and make the same selections but use the '''Left#2 swimlane level cells''', the selected '''swimlanes''' look like this:
+
 
+
<center>[[File:P70-12_21_1-(15)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(15)-08092020.png</center>-->
+
 
+
In the example above, the '''two swimlanes''' are selected from the '''Left#2 swimlane level cells'''.
+
 
+
As in the previous sub-section, both the selected '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are different so the '''merged Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' depends on the '''modal number of rows''' in the two selected sets of '''swimlane level cells'''.  '''Four rows''' for the '''Startup/Planning/Prime Left#1/Left#2/Left#3 swimlane level cells''' and '''two rows''' for the '''Phase II/Development/Team 2 Left#1/Left#2/Left#3 swimlane level cells'''.
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#2 swimlane level cells''' (perhaps the '''Development Left#2 swimlane level cell’s label''') and clicking the '''Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(14)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(14)-08092020.png</center>-->
+
 
+
As shown above, the '''six rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1, Left#2, '''and''' Left#3 swimlane levels''' and the respective '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''modal number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' in the chart as close to its '''original position''' as possible and the '''rows''' within the '''merged swimlane level cell''' retain their original '''ordering'''.  This being the case, OnePager places the intervening, non-participating '''Phase I/Development/Team 1 Left#1/Left#2/Left#3 swimlane level cell''' at the top of the chart.
+
 
+
===Merging Swimlane from the Left#3 Swimlane Level Cells – Three Swimlane Level Chart===
+
 
+
If we again change the above example and make the same selections but use the '''Left#3 swimlane level cells''', the selected '''swimlanes''' look like this:
+
 
+
<center>[[File:P70-12_21_1-(16)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(16)-08092020.png</center>-->
+
 
+
In the example above, the '''two swimlanes''' are selected from the '''Left#3 swimlane level cells'''.
+
 
+
As in the previous sub-section, as expected, both the selected '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are different so the '''merged Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' depends on the '''modal number of rows''' in the two selected sets of '''swimlane level cells'''.  '''Four rows''' for the '''Startup/Planning/Prime Left#1/Left#2/Left#3 swimlane level cells''' and '''two rows''' for the '''Phase II/Development/Team 2 Left#1/Left#2/Left#3 swimlane level cells'''.
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#3 swimlane level cells''' (perhaps the '''Team 2 Left#3 swimlane level cell’s label''') and clicking '''the Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(14)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(14)-08092020.png</center>-->
+
 
+
As shown above, the '''six rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1, Left#2, '''and''' Left#3 swimlane levels''' and the respective '''Left#1, Left#2, '''and''' Left#3 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''modal number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' in the chart as close to its '''original position''' as possible and the '''rows''' within the '''merged swimlane level cell''' retain their original '''ordering'''.  This being the case, OnePager places the intervening, non-participating '''Phase I/Development/Team 1 Left#1/Left#2/Left#3 swimlane level cell''' at the top of the chart.
+
 
+
===Merging Swimlane with Equal Number of Rows – Three Swimlane Level Chart===
+
 
+
The three sets of examples in the three sub-sections above established that selecting '''two or more Left#1 or Left#2 or Left#3  swimlane level cells''' does not depend on which '''swimlane level cells''' ('''Left#1''' or '''Left#2 '''or '''Left#3''') are selected.  Additionally, the concept of '''modal number of rows''' governing the resulting '''merged swimlane level cell’s labels''' was also demonstrated.
+
 
+
This sub-section shows the results when '''swimlane level cells''' are selected that have an '''equal number of rows''' and how this determines the '''merged swimlane level cell’s labels'''.
+
 
+
Since selecting in either the '''Left#1, Left#2, '''or '''Left#3 swimlane level cells''' is moot, we’ll select '''two swimlane level cells''' with '''equal number of rows''' form the '''Left#2 swimlane level''' as shown below:
+
 
+
<center>[[File:P70-12_21_1-(17)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(17)-08092020.png</center>-->
+
 
+
Continuing the process of accessing the '''swimlane level right-click context menu''' by right-clicking in one of the selected '''Left#2 swimlane level cells''' (perhaps the '''Integration & Testing Left#2 swimlane level cell’s label''') and clicking '''the Merge swimlanes''' command, produces this result:
+
 
+
<center>[[File:P70-12_21_1-(18)-08092020.png]]</center>
+
<!--<center>P70-12_21_1-(18)-08092020.png</center>-->
+
 
+
As shown above, the '''eight rows''' are '''merged''' into '''one swimlane level cell''' at the '''Left#1, Left#2, '''and''' Left#3 swimlane levels''' and the respective '''Left#1, Left#2, '''and '''Left#3 swimlane level cell’s labels''' are taken from the '''swimlane level cell labels''' containing the '''same number of rows'''.  The '''new merged swimlane level cell''' is '''positioned''' at the bottom of the chart in this case, and the '''ordering''' of '''rows''' is retained within the original '''swimlane level cell’s''' configuration.
+
 
+
OnePager places the intervening, non-participating ('''Phase I/Phase II)/Development/(Team 1/Team2) Left#1/Left#2/Left#3 swimlane level cells''' at the top of the chart.  The choices for the '''merged Left#1 '''and''' Left#2 swimlane level cell’s labels''' are made by OnePager at '''random '''since the participating '''original swimlane level cells''' both have an '''equal number of rows''' and there is no establish '''mode'''.
+
 
+
'''Note''' carefully that in the bottom set of selected '''swimlane level cells '''in the original chart at the '''Left#3 swimlane level''' consist of '''three swimlanes''' with '''three different Left#3 swimlane level cell labels – Prime, Subcontractor A,''' and '''Subcontractor B'''.  In the illustration above with the '''merged swimlane level cells''', OnePager selected '''Prime''' for the '''Left#3 swimlane level cell’s label''' because the '''original Prime Left#3 swimlane level cell''' has '''two rows''' while the '''Subcontractor A '''and''' B Left#3 swimlane level cells''' have only '''one row''' each.  OnePager, as expected, selected '''Prime''' for the '''merged Left#3 swimlane level cell’s label''' because '''Prime''' is the '''model label'''.
+
 
+
As mentioned earlier in this article, OnePager assumes that after '''swimlane level cells''' are '''merged''' that actions will subsequently be taken to '''editing the merged swimlane level cell’s labels''', '''move''' the '''merged swimlane level cells''' to a different '''position''' in the chart, or do some other form of '''row''' or '''swimlane level editing'''.
+
  
 
==Related Links==
 
==Related Links==
  
[[Manual Editing Task/Milestone Shapes and Text Labels for Version 7.0 (Portal) | Manual Editing Task/Milestone Shapes and Text Labels (Portal)]] <!--9.0.1-70-->
+
{| 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
 +
|-
 +
| [[Editing with the Chart Properties form for Version 7.2 (Portal) | Editing with the Chart Properties form (Portal)]] 21.0.1-72
 +
| [[Template Only Features for OnePager Pro for Version 7.2 | Template Only Features for OnePager Pro]] 24.1.1-72
 +
|-
 +
| [[Template Only Features for OnePager Express for Version 7.2 | Template Only Features for OnePager Express]] 24.2.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
 +
|-
 +
| [[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
 +
| [[Splitting and Parsing Columns for OnePager Pro for Version 7.2 | Splitting and Parsing Fields for OnePager Pro]] 24.4.1-72
 +
|-
 +
| [[Splitting and Parsing Columns for OnePager Express for Version 7.2 | Splitting and Parsing Fields for OnePager Express]] 24.5.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
 +
|-
 +
| [[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
 +
| [[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
 +
|-
 +
| [[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
 +
| [[Splitting and Parsing Columns for Wrike in OnePager Version 7.2 | Splitting and Parsing Columns for Wrike in OnePager]] 24.5.11-72
 +
|}
  
[[Creating and Editing Rows and Swimlanes for Version 7.0 (Portal) | Creating and Editing Rows and Swimlanes (Portal)]] <!--12.0.1-70-->
+
(24.5.9-72)
  
[[About OnePager's Rows and Swimlanes | About OnePager's Rows and Swimlanes]] <!--12.0.2-70-->
+
[[Category:Version 7.2]]
 
+
[[Category:Editing the Chart]]
[[Collecting, Formatting, and Sorting Task/Milestones into Rows for Version 7.0 | Collecting, Formatting, and Sorting Task/Milestones into Rows]] <!--12.01.1-70-->
+
[[Category:Task/Milestone Editing]]
 
+
[[Category:Column Splitting]]
[[Creating, Formatting, and Sorting Swimlanes Levels for Version 7.0 | Creating, Formatting, and Sorting Swimlanes Levels]] <!--12.02.1-70-->
+
 
+
[[Creating and Formatting Text Columns for Version 7.0 | Creating and Formatting Text Columns]] <!--12.03.1-70-->
+
 
+
[[Row and Swimlane Borders for Version 7.0 | Row and Swimlane Borders]] <!--12.04.1-70-->
+
 
+
[[Editing Text Columns or Swimlane Labels for Version 7.0 | Editing Text Columns or Swimlane Labels]] <!--12.3.1-70-->
+
 
+
[[Manually Hiding and Unhiding Swimlane Levels for Version 7.0 | Manually Hiding and Unhiding Swimlane Levels]] <!--12.5.1-70-->
+
 
+
[[Resizing the Width of Text Columns and Swimlanes for Version 7.0 | Resizing the Width of Text Columns and Swimlanes]] <!--12.8.1-70-->
+
 
+
[[Resizing the Height of Rows for Version 7.0 | Resizing the Height of Rows]] <!--12.11.1-70-->
+
 
+
[[Hiding and Unhiding Rows and Swimlanes for Version 7.0 | Hiding and Unhiding Rows and Swimlanes]] <!--12.13.1-70-->
+
 
+
[[Adding a Row or Swimlane for Version 7.0 | Adding a Row or Swimlane]] <!--12.16.1-70-->
+
 
+
[[Adding a Row to a Swimlane for Version 7.0 | Adding a Row to a Swimlane]] <!--12.19.1-70-->
+
 
+
[[Making Each Row into a Swimlane for Version 7.0 | Making Each Row into a Swimlane]] <!--12.20.1-70-->
+
 
+
[[Merging Swimlanes for Version 7.0 | Merging Swimlanes]] <!--12.21.1-70-->
+
 
+
[[Editing Row Properties for Version 7.0 | Editing Row Properties]] <!--12.22.1-70-->
+
 
+
[[Editing Swimlane Properties for Version 7.0 | Editing Swimlane Properties]] <!--12.23.1-70-->
+
 
+
[[Zebra Striping for Rows and Swimlanes for OnePager Pro for Version 7.0 | Zebra Striping for Rows and Swimlanes for OnePager Pro]] <!--12.24.1-70-->
+
 
+
[[Zebra Striping for Rows and Swimlanes for OnePager Express for Version 7.0 | Zebra Striping for Rows and Swimlanes for OnePager Express]] <!--12.24.2-70-->
+
 
+
[[Editing with the Chart Properties form for Version 7.0 (Portal) | Editing with the Chart Properties form (Portal)]] <!--21.0.1-70-->
+
 
+
[[Managing Templates for Version 7.0 (Portal) | Managing Templates (Portal)]] <!--24.0.1-70-->
+
 
+
(12.21.1-70)
+
 
+
[[Category:Version 7.0]]
+
 
[[Category:Charts]]
 
[[Category:Charts]]
[[Category:Templates]]
+
[[Category:Task Links]]
 +
[[Category:Ribbon]]
 +
[[Category:Snapshots]]
 +
[[Category:Template Properties Form]]
 
[[Category:Chart Properties Form]]
 
[[Category:Chart Properties Form]]
[[Category:Editing the Chart]]
+
[[Category:Asana]]
[[Category:Rows and Swimlanes]]
+
[[Category:OnePager Bundle]]
[[Category:Multiple Swimlane Levels]]
+
[[Category:Labels]]
+
[[Category:Text Columns]]
+
[[Category:Snapshots]]
+
[[Category:Swimlane Stripes]]
+
[[Category:Mavericks]]
+
[[Category:OnePager Pro]]
+
[[Category:OnePager Express]]
+

Latest revision as of 20:52, 27 November 2023

Introduction

This article is focused on using the Column Splitting feature with OnePager Bundle Standalone and imported Asana source plans.

About Splitting and Parsing Fields

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.

Split Resource Names Example

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:

P72-24 5 3-72-(1)-11022023.png
P72-24_5_3-72-(1)-11022023.png

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:

P72-24 5 3-72-(5)-11272023.png
P72-24_5_3-72-(5)-11272023.png

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.

Enabling Splitting

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:

P72-24 5 3-72-(2A)-11022023.png
P72-24_5_3-72-(2A)-11022023.png

When you click the Next> button at the bottom of the form, OnePager accesses the second page of the OnePager choices form shown below:

P72-24 5 3-72-(2AA)-11022023.png
P72-24_5_3-72-(2AA)-11022023.png

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:

P72-24 5 3-72-(2AAA)-11022023.png
P72-24_5_3-72-(2AAA)-11022023.png

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.

Split Resources in the Chart

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:

P72-24 5 3-72-(2)-11022023.png
P72-24_5_3-72-(2)-11022023.png

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.

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.

Splitting Resources and Task Links

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.

Related Links

Templates versus Charts 4.0.1.3-72 Linking Task and Milestone Using Manual and Data-Driven Task Links (Portal) 19.0.1-72
Editing with the Chart Properties form (Portal) 21.0.1-72 Template Only Features for OnePager Pro 24.1.1-72
Template Only Features for OnePager Express 24.2.1-72 Template Only Features for Primavera P6 Source Plans in OnePager 24.2.2-72
Template Only Features for Smartsheet Source Plans in OnePager 24.2.3-72 Splitting and Parsing Fields for OnePager Pro 24.4.1-72
Splitting and Parsing Fields for OnePager Express 24.5.1-72 Splitting and Parsing Columns for Primavera P6 Source Plans in OnePager 24.5.2-72
Splitting and Parsing Columns for Smartsheet Source Plans in OnePager 24.5.3-72 Splitting and Parsing Columns for Project for the Web Source Plans 24.5.5-72
Splitting and Parsing Columns for Planisware Enterprise Source Plans 24.5.7-72 Splitting and Parsing Columns for Wrike in OnePager 24.5.11-72

(24.5.9-72)