Latest revision as of 14:33, 29 May 2017

Overview

An overview article with examples is available at: Conditional Import Filters for OnePager . The article is recommended reading before you advance to this article or any other of the product specific articles in this series.

The Conditional Import Filters feature supports imports from all locations and configurations of Microsoft Project source plans including those from your computer, from the cloud; as a single source plan, Integrated Master Schedules (IMS), or multiple separate Microsoft Project source plans.

This article provides details on the use of the Conditional Import Filters feature for OnePager Pro (OPP) Desktop edition.

(1) First, we’ll provide information on how to create Conditional Import Filters rules using the Conditional Import Rules form.

(2) Then, we'll cover a couple of examples on how you might use the Condition Import Filters feature in your every day use of OnePager in preparation for your schedule presentations and discussions.

Adding a Filter Rule to the Conditional Import Rules Form

1) The Conditional Import Rules form resembles to the Conditional Formatting form in look and function. In this form you can add, copy, change, and delete Conditional Import Filters rules. The form is accessed from the OnePager choices (OPC) form as shown below:

a) The Conditional Import Rules form is shown in its initial blank state above. The rules entered become part of any project view subsequently created or updated and are saved with the project view. If you later, create or update a snapshot using a flag field, OPP will save the flag field and clear the Conditional Import Filters rules.

b) Conditional Import Filter rules are typically entered when a project view is first created in the NEW workflow.

c) After a project view is created, rules may be added later for the UPDATE workflow via the OnePager Choices form invoked either from the OnePager Start form or the Project View Editor (Custom Update… button. These workflows are described later in the examples accompanying this article.

2) With the Custom Import Rules form visible and blank, click the Add Rule button to create a new empty row as shown below:

a) There are five cells shown for the new rule row above. The first two cells are used as follows:

i) The first two cells are used as selection cells.

ii) The first left-most cell, when clicked, allows you to use the Copy Rule(s) or the Delete Rule(s) buttons.

iii) The second cell from the left is a checkbox used to allow you to activate or deactivate the rule. If the checkbox is unchecked, OPP will not apply the rule when performing the import function.

b) The Field cell of a row (third from the left) has a dropdown menu that allows you to select a Microsoft Project source plan field to use in creating the selected criterion. When the dropdown menu is selected, the Field cell will look something like this:

c) When a Microsoft Project source plan field is selected, the name will be displayed in the Field cell of the new Custom Import rule row.

d) The look of the rest of the new Conditional Import Filters rule depends on the type of the Microsoft Project source plan field selected. These types are discussed next.

3) Date and Numeric Fields – When Microsoft Project date or numeric types are selected in the Field cell of the rule row, the Operator field dropdown will provide the options shown below:

a) These are the conventional six (6) logical operators used consistently in OPP for date and numeric types. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting Overview for OnePager Pro for complementary details on the use of these logical operators.

b) When the logical statement evaluates to TRUE on the selected Field in a Microsoft Project source plan row, the row is imported. Otherwise it is skipped.

4) Text Fields – When Microsoft Project text types are entered in the Field cell of the Conditional Import Filters rule row, the Operator field dropdown will provide the options shown below:

a) These are the conventional four (4) logical operators used consistently in OPP for the text type. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting Overview for OnePager Pro for complementary details on the use of these logical operators.

b) When the logical statement evaluates to TRUE on the selected Field in a Microsoft Project source plan row, the row is imported. Otherwise it is skipped.

5) Boolean Fields – When Microsoft Project Boolean types are entered in the Field cell of the Conditional Import Filters rule row, the Operator field dropdown will provide the options shown below:

a) These are the two (2) conventional Boolean logical operators used consistently in OPP for the Boolean type. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting with Boolean Fields for OnePager Pro for compeimentary details on the use of these logical operators.

b) Boolean types are a special case as the operator and the value in OPP are combined into one cell of the Conditional Import Filters rule row - the Operator cell.

c) When the selected Field is TRUE (or Yes) in a Microsoft Project source plan row, the row is imported. Otherwise it is skipped.

6) Flag1 Through Flag20 Fields – OPP treats Microsoft Project fields from Flag1 through Flag20 as Boolean types in the same way as described in the previous sub-section.

7) We want to emphasize the flexibility that Conditional Import Filters adds to the way you can import rows from your Microsoft Project source plan. You can formulate sets of Conditional Import Filters rules to controls imports using all available types of Microsoft Project fields and use operators that let you select ranges of values and more complicated combinations of criteria.

Editing an Existing Filter Rule in the Conditional Import Rules Form

8) Suppose you’ve composed several Conditional Import Filters rules in an open Conditional Import Rules form as shown below:

a) Now further suppose, after reviewing these two rules, that you realize that you may not be able to capture any tasks/milestones that happen to Start on 12/31/2015 because the current rule is based on the less than logical Operator.

b) To make the change in the Operator cell, click on the cell’s contents which will highlight the cell in blue and reveals the dropdown menu button which you should click. When you do the Conditional Import Rules form should look like this:

c) To change the rule, click the desired Operator in the dropdown menu, in this case the less than or equal Operator, and it will be displayed in the Operator cell of the second rule as shown here:

d) Any Field, Operator, or Value cell may be edited in this way. Additionally, the On cell may be toggled to control the Conditional Import Filters rule's participation in the import process. Finally, you may switch between the two radio buttons at the top of the form in order to change the relationship among the rules from OR to AND or vice versa.

e) The edits described above may be made to the Conditional Import Rules form regardless of the OPC mode in which you are working (i.e., NEW and UPDATE). Also, you may bring up the Conditional Import Rules form from the OPC form as many times as needed to accomplish your presentation goal. OPP saves the content of the last edit you make to the Conditional Import Rules form.

f) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form. Now you are ready to create a new project view.

Copying an Existing Filter Rule in the Conditional Import Rules Form

9) The Copy Rule(s) button is provided in the Conditional Import Rules form to facilitate the creation of additional rules.

a) To copy a rule to create a new rule, first select the rule row from which you wish to copy as shown below:

b) Once the desired row is selected, clicking the Copy Rule(s) button will copy the contents of the rule selected as indicated by the highlighted left-most cell in the desired rule as shown below:

c) At this point you may edit the copied row in the manner described previously. When you are finished, the new set of three rule rows may look like this:

d) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form. Now you are ready to create a new project view.

Deleting an Existing Filter Rule in the Conditional Import Rules Form

10) There are times when a particular Conditional Import Filters rule will no longer serve its purpose. You can select the rule row to be deleted and click the Delete Rule(s) button.

a) The process for deleting a rule parallels the process for copying a rule row in that the you must select the desired row to delete by clicking the left-most cell in that rule’s row.

b) Once the selection is made, click the Delete Rule(s) button and OPP will first put up a warning message asking if you really want to delete the rule row as shown below:

c) If you select the No option, OPP will abandon the rule deletion operation and the warning message will disappear leaving the selected rule row still selected.

d) If you select the Yes option, OPP will remove the warning message, delete the selected rule row, and leave the Conditional Import Rules form showing the remaining rule rows, if any.

e) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form.

Switching from Flag Fields to New Conditional Import Filters Rules

11) When you click the NEW button, the OPC form will appear as shown below. The process for building a new project view with Conditional Import Filters is the same with the exception that instead of using flag field from your Microsoft Project source plan you will, instead, invoke the Conditional Import Rules form from the OPC form as shown below:

a) In the illustration above, in the Task Selection section of the form, the Select task by custom filter radio button is clicked. This action brings up the Conditional Import Rules form also shown above.

b) At this point you may Add Rules to the form, Copy Rules, Delete Rules, or edit existing rules.

Switching from Conditional Import Filters Rules to Flag Fields or Selecting all Tasks

12) If you subsequently decide after composing one or more Conditional Import Filters rules and clicking OK on the Conditional Import Rules form that you want to use flag fields instead, you may revert back to either of the two other Task Selection options provided in the OPC form shown above.

a) To do this, click either of the other two radio buttons to Select all tasks, or Select task with ‘Yes’ in field:

b) When you click the Select all tasks button there is no further action you need to take on the OPC form.

c) However, if you click the Select tasks with ‘Yes’ in field: you will need to select a field from your Microsoft Project source plan as shown below:

d) In these circumstances where you’ve switched from using Conditional Import Filters rules to either selecting all tasks, or selecting tasks using a flag field, OPP will discard any Conditional Import Filters rules associated with the project view.

Adding, Editing, Copying, and Deleting Conditional Import Filters Rules

13) Managing Conditional Import Filters rules was discussed in previous sub-sections of this article. Please follow the reference links provided below for details on adding, editing, copying, and deleting of Conditional Import Filters rules:

a) Adding a new rule: Adding a Filter Rule to the Conditional Import Rules Form.

b) Editing an existing rule: Editing an Existing Filter Rule in the Conditional Import Rules Form.

c) Copying a rule: Copying an Existing Filter Rule in the Conditional Import Rules Form.

d) Deleting a rule: Deleting an Existing Filter Rule in the Conditional Import Rules Form.

A Simple Example Using Conditional Import

In this section and the one to follow, we’ll provide a couple of examples of a workflow that you might find most useful. First we’ll provide a simple example and then extend it to a more advance use of the workflow.

Setup

1) Suppose you have a situation where you want to focus the attention of your audience on a particular set of tasks that have the following attributes:

a) Where tasks/milestones start on or after October 1, 2015 but no later than December 31, 2015.

b) Where swimlanes represent the Phases of the project

c) Where the two additional text columns represent the Start Dates and the Finish Dates of each displayed task respectively.

d) And where the Legend is organized by Resource Name.

2) Let’s further suppose that we are going to use the BlueGrass Project 2J-303-PMO Microsoft Project source plan as input to OnePager Pro and we want to use the Single Project View Gantt View – Detailed Template.

3) To begin with, the source plan will look like this:

4) Before we launch OnePager Pro Desktop, the Main tab of the Template we will use for this example looks like this:

5) If we launched OnePager Pro Desktop from the desktop icon with the above Template as the current Template, the tasks and milestones included in the project view would be those associated with Yes in the Flag20 field in the source plan above. This is not what we want so we first have to change the task and milestone selection criteria using the Conditional Import Filters feature as we’ll show next.

Changing the Task and Milestone Selection Criteria

6) With the conditions established in the sub-section above, let’s go ahead and launch OnePager Pro Desktop from the desktop icon which will bring up the OnePager Start form as shown below:

7) Next, we’ll click the NEW button which will bring up the abbreviated OnePager Choices (OPC) form shown here:

a) Click the Select… button which brings up the Windows Open form.

b) Use the Open form to select the Microsoft Project source plan you need and click Open in the Windows Open form.

c) OPP Desktop will retrieve the selected source plan where you can fill in the required fields of the OPC form so that it looks like the form shown here:

8) We’ve gone ahead and confirmed that we have the correct source plan and we’ve filled in the Title of New Project View. We see that the Task Selection criteria will be based on the contents of the Flag20 field, and we don’t want this field to be used. We have two ways to invoke the Conditional Import Filters feature and we’ll explain each below:

Using the OnePager Choices Form to Create Conditional Import Filters

9) For this first technique, click on the Select tasks by custom filter radio button, which brings up the Conditional Import Rules form as shown below:

10) Next, we’ll enter the two Conditional Import Filters we specified in the previous subsection and make sure the All of the following are true radio button is selected so the Conditional Import Rules form will look like this when we are done:

11) From here we could go ahead and click the OK button on the Conditional Import Rules form and, once back at the OPC form, go ahead and create the project view. However, before we do that we want to show the alternative way to enter Conditional Import Filters rules.

Using the Template to Create Conditional Import Filters

12) To illustrate this second technique let’s roll back to the OPC form we saw above and notice that the checkbox labeled Show field mappings is checked and the button below the checkbox is called Next>. Now click the Next> button which takes you to the second page of the OPC form which looks like this:

13) Next, click the Edit current template… button which will bring up the current Template as shown below. Then, navigate to the Main tab as we have done here and note the button titled Add/edit conditional import filter…:

14) When the Add/edit conditional import filter… button is clicked, the Conditional Import Rules form will appear and you can enter the two rules we specified in for this example as we’ve shown below:

Creating the Project View

15) After entering the two Conditional Import Filters rules, as shown above, click the OK button on the Conditional Import Rules form and then the Save and Use button at the bottom of the Template form.

16) These actions will take you back to the second page of the OPC form, shown earlier; where you can click the Create new project view button and OnePager Pro will create the project view as shown here:

Editing the Project View

17) Finally, we need to add the two additional text columns specified to show Start and Finish dates.

18) This final requirement is implemented by using the Additional Text Column feature (insert link here). When these actions are taken the project view will look like this:

An Advanced Example Using Conditional Import

The advanced workflow example presented in this section on Conditional Import Filters rules is a continuation of the example in the previous section.

If you haven’t read or reviewed the simple example, we suggest that you do so before reading on in this section.

Continuation of Simple Example

1) What we intend to show you in this section is how to proceed from the creation of the project view in the previous section through successive edits and replacements to get to a project view that will be perfect for a specific schedule conversation.

2) To set the stage, let’s establish some further guidance for the final visual presentation:

a) It needs to be very focused on the apparent trouble spot; say with the Prime contractor just for example.

b) There needs be as few tasks as possible so as to keep the audience’s focus on the real project management issue.

c) The presentation of the schedule issues needs be on one page.

3) Given the above guidance, we need to restructure the project view from the previous section. Of course, we want to do this in the most efficient way so that it what we will describe in the next sub-section.

Using Conditional Import Filters to Update a Project View through Replacement

4) Looking back at the project view from the previous sub-section, we see that it contains tasks from all the Resources available during the time interval we specified in the original set of Conditional- Import rules. Our guidance says that we want to focus more on the Prime contractor. So, we’ll use the Conditional Import Filters feature to refine our import criteria and replace the project view with tasks/milestones that meet the Start criteria and the Resource-Names criteria we need.

5) To modify the Conditional Import Filters rules we will do the following steps:

a) First we go to the project view and bring up the PVP form at the Main tab.

b) Next, we click the Add/edit conditional import filter… button to bring up the Conditional Import Rules form.

c) Then, we use the Add Rule button to make a row for the third rule and compose the third rule to specify Resource Names in the Field column, an equal sign in the Operator column, and the word Prime in the Value column.

d) When you are done adding the new (third) rule, the forms will look like this:

6) Now do the following steps:

a) Click the OK button on the Conditional Import Rules form. This will close the form and take you back to the PVP form’s Main tab.

b) Here, click the Apply button only. This will apply the change to the project view but keep the PVP’s Main tab open.

c) Before doing anything else, go to the Project View Editor’s (PVE) tool bar and select the Data tab. When you are finished with these steps, the PVE and the PVP Main tab will look like this:

7) The last step in this workflow is to click the Replace Snapshot button which is the left-most button on the Data tab tool bar. This is the action that tells OnePager Pro to update the project view by re-importing the source data with task selection controlled by the three rules now active in the Conditional Import Rules form.

8) When the OnePager Pro replace process completes, the project view will be honed to not only restrict the start dates but also to restrict the Resource Names in the chart, like this:

Summary of First Project View Replacement Iteration

9) To summarize what we’ve done we’ve accomplished the following:

a) Used the original project view in conjunction with the Conditional Import Rules form to specify an additional rule that further narrows the tasks in the chart.

b) Used the Replace Snapshot button to tell OnePager Pro display only this refined set of tasks.

Second Project View Replacement Iteration

10) The project view we created above still isn’t quite ready for our schedule conversation. Looking at it closely, we probably don’t need to focus on any tasks/milestones that the Prime contractor has completed. So, in this next iteration let’s modify our Conditional Import Filters to just bring in those tasks/milestones that are less than 100 percent complete.

11) We’ll use the same sequence of steps that were used in the first replacement iteration we described above.

a) In the open PVP form, click the button to bring up the Conditional Import Rule form and add a fourth rule restricting to tasks/milestones that are less than 100 percent complete. The form will look like this when we are done adding the rule:

b) With the above rule added, click the OK button in the Conditional Import Rules form and after it closes, click the Apply button on the bottom of the PVP form’s Main tab.

c)The appearance of the PVE will be like this:

d) The last step is to click the Replace Snapshot button on the OnePager Pro Data tab tool bar. OnePager will perform the snapshot replacement and the project view will look like this:

Summary of Second Project View Replacement Iteration

12) The project view in the illustration above now meets all the Start, Resource Name, and %Complete criteria to support the schedule conversation.

13) This was all done by an iterative workflow that couples updates to the Conditional Import Rules with the Replace Snapshot button on the OnePager Pro tool bar’s Data tab.

14) All that needs to be done now is to copy the project view into the media to be used for the schedule conversation.

Some Additional Comments on this Workflow

15) It’s important to remember for this workflow that you always want to REPLACE the single snapshot in the project view. We advise against ADDING a snapshot as you refine your rules because this can result in empty rows for tasks that were present under a previous set of rules but are now absent.

16) If you want to begin the workflow by OPENING a previously-created project view, it is essential, as mentioned above, that there is a clear and viable path from the project view to its source plan(s). You can confirm this and fix any problems by clicking the Selected Files button on the Data tab.

Difference between revisions of "Conditional Import for OnePager Pro Desktop for Version 6.0"

Latest revision as of 14:33, 29 May 2017

Contents

Overview

Adding a Filter Rule to the Conditional Import Rules Form

Editing an Existing Filter Rule in the Conditional Import Rules Form

Copying an Existing Filter Rule in the Conditional Import Rules Form

Deleting an Existing Filter Rule in the Conditional Import Rules Form

Switching from Flag Fields to New Conditional Import Filters Rules

Switching from Conditional Import Filters Rules to Flag Fields or Selecting all Tasks

Adding, Editing, Copying, and Deleting Conditional Import Filters Rules

A Simple Example Using Conditional Import

Setup

Changing the Task and Milestone Selection Criteria

Using the OnePager Choices Form to Create Conditional Import Filters

Using the Template to Create Conditional Import Filters

Creating the Project View

Editing the Project View

An Advanced Example Using Conditional Import

Continuation of Simple Example

Using Conditional Import Filters to Update a Project View through Replacement

Summary of First Project View Replacement Iteration

Second Project View Replacement Iteration

Summary of Second Project View Replacement Iteration

Some Additional Comments on this Workflow

Related Links

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools

@@ Line 1: / Line 1: @@
-===Conditional Import for OnePager Pro Desktop for Version 6.0 (PE60-7_18_1_1-11092016)===
+=Overview=
-In '''OPP''' and '''OPX''' version 6.0, the capability for you to control the '''import''' of rows from your plan source files is made even more flexible with the addition of new '''Conditional Import''' capability. In this section there are three situations you may have encountered in the past with OnePager that can be facilitated better with '''Conditional Import''':
+An overview article with examples is available at: [[Conditional Import for OnePager Pro/Express Version 6.0 | Conditional Import Filters for OnePager]] <!--0.4.1.1-60-->.  The article is recommended reading before you advance to this article or any other of the product specific articles in this series.
-===When a Flag Field Isn’t Sufficient===
+The '''Conditional Import Filters''' feature supports imports from all locations and configurations of Microsoft Project '''source plans''' including those from your computer, from the '''cloud'''; as a single '''source plan''', '''Integrated Master Schedules (IMS)''', or '''multiple separate Microsoft Project source plans'''.
-) There are occasions where you would like to '''import '''a plan source file row but only when the contents of a specified column holds a desired value or range of values. In this case, using a flag field may not be flexible enough or may be too time consuming to use.
+This article provides details on the use of the '''Conditional Import Filters''' feature for OnePager Pro ('''OPP''') Desktop edition.
+:(1) First, we’ll provide information on how to create '''Conditional Import Filters''' rules using the '''Conditional Import Rules''' form.
-) Suppose you might want to include plan source file rows where task/milestone '''Start''' dates are greater than a specified date. Prior to '''OPP/OPX''' version 6.0 you would have to manually locate and modify the '''flag''' cell contents for those rows meeting the desired condition before importing.  With version 6.0 you can clearly specify, in a '''Conditional Import''' rule, defined before the import process begins, the conditions that meets any logical combination of criteria '''WITHOUT''' making modifications to the plan source file. Here’s how it might work:
+:(2) Then, we'll cover a couple of examples on how you might use the '''Condition Import Filters''' feature in your every day use of OnePager in preparation for your schedule presentations and discussions.
-:a) We’ll use the BlueGrass Project 2J-303 Microsoft Project plan source file as an example.  Recall that  the column headers look something like this:
+==Adding a Filter Rule to the Conditional Import Rules Form==
-<center>[[File:P60-7_18_1-60-(1)-09242016.png]]</center>
+) The '''Conditional Import Rules''' form resembles to the '''Conditional Formatting''' form in look and function. In this form you can add, copy, change, and delete '''Conditional Import Filters''' rules.  The form is accessed from the '''OnePager choices '''('''OPC''') form as shown below:
-<center>P60-7_18_1-60-(1)-09242016.png</center>
+<center>[[File:P60-7_18_1_2-60-(1AA)-03072017.png]]</center>
+<!--<center>P60-7_18_1_2-60-(1AA)-03072017.png</center>-->
-:b) For this example you only want to import tasks/milestones that have a '''Start''' date greater than 10/11/2015 but less than 12/31/2015.  You can do that by first launching Microsoft Project with the plan source file loaded as shown above.  Next, launch '''OPP''' version 6.0 from the Microsoft Project tool bar as you normally do and click the '''NEW''' button option.  When this is done the following '''OnePager Choices '''form appears:
+:a) The '''Conditional Import Rules '''form is shown in its initial blank state above.  The rules entered become part of any project view subsequently created or updated and are saved with the project view.  If you later, create or update a snapshot using a '''flag''' field, '''OPP''' will save the '''flag''' field and clear the '''Conditional Import Filters''' rules.
-<center>[[File:P60-7_18_1-60-(2)-09242016.png]]</center>
+:b) '''Conditional Import Filter''' rules are typically entered when a project view is first created in the '''NEW''' workflow.
-<center>P60-7_18_1-60-(2)-09242016.png</center>
+:c) After a project view is created, rules may be added later for the '''UPDATE''' workflow via the '''OnePager Choices''' form invoked either from the '''OnePager Start''' form or the '''Project View Editor''' ('''Custom Update…''' button.  These workflows are described later in the examples accompanying this article.
-:c) The '''OnePager choices''' ('''OPC''') form above has an additional radio button in the '''Task Selection''' section, '''Select tasks by custom filter''' and a new button called '''Edit filter…'''.  Before clicking the '''Select tasks by customer filter''' button, update the project view name and snapshot date such that the '''OPC''' form looks like this:
+) With the '''Custom Import Rules''' form visible and blank, click the '''Add Rule''' button to create a new empty row as shown below:
-<center>[[File:P60-7_18_1-60-(3)-09242016.png]]</center>
+<center>[[File:P60-7_18_1_1-60-(1AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(1AA)-03032017.png</center>-->
-<center>P60-7_18_1-60-(3)-09242016.png</center>
+:a) There are five cells shown for the new rule row above.  The first two cells are used as follows:
-:d) Now, click the '''Select tasks by custom filter''' button.  When you do, a blank '''Custom Import Rules''' form will appear as show below:
+::i) The first two cells are used as '''selection''' cells.
+::ii) The first left-most cell, when clicked, allows you to use the '''Copy Rule(s)''' or the '''Delete Rule(s)''' buttons.
+::iii) The second cell from the left is a checkbox used to allow you to '''activate''' or '''deactivate''' the rule. If the checkbox is '''unchecked''', '''OPP''' will not apply the rule when performing the '''import''' function.
-<center>[[File:P60-7_18_1-60-(4)-09242016.png]]</center>
+::b) The '''Field''' cell of a row (third from the left) has a dropdown menu that allows you to select a Microsoft Project '''source plan''' field to use in creating the selected criterion.  When the dropdown menu is selected, the '''Field '''cell will look something like this:
-<center>P60-7_18_1-60-(4)-09242016.png</center>
+<center>[[File:P60-7_18_1_1-60-(2AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(2AA)-03032017.png</center>-->
-:e) You can now compose the two rules needed to import rows that have '''Start''' dates greater than 10/11/2015 but less than 12/31/2015.  When you do this, the '''Conditional Import Rules''' form will look like this:
+:c) When a Microsoft Project '''source plan''' field is selected, the name will be displayed in the '''Field''' cell of the new '''Custom Import''' rule row.
-<center>[[File:P60-7_18_1-60-(5)-09242016.png]]</center>
+:d) The look of the rest of the new '''Conditional Import Filters''' rule depends on the type of the Microsoft Project '''source plan''' field selected.  These types are discussed next.
-<center>P60-7_18_1-60-(5)-09242016.png</center>
+) '''Date and Numeric Fields – ''' When Microsoft Project '''date or numeric''' types are selected in the '''Field''' cell of the rule row, the '''Operator''' field dropdown will provide the options shown below:
-:f) Note that the '''All of the following rules are true''' radio button is selected so that the two rules are essentially an '''AND''' operation.  When you click '''OK '''on the form, it will disappear and you will be back at the '''OPC '''form once more.  At this point. click the '''Create new project view''' button and '''OPP''' will create the project view that looks like this:
+<center>[[File:P60-7_18_1_1-60-(3AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(3AA)-03032017.png</center>-->
-<center>[[File:P60-7_18_1-60-(6)-09242016.png]]</center>
+:a) These are the conventional six (6) logical operators used consistently in '''OPP''' for date and numeric types.  They are the same '''Operators''' used in '''OPP''' for '''Conditional Formatting'''.  See the article at [[Conditional Formatting Overview for OnePager Pro for Version 6.0 | Conditional Formatting Overview for OnePager Pro]] <!--11.1.1-60--> for complementary details on the use of these logical operators.
-<center>P60-7_18_1-60-(6)-09242016.png</center>
+:b) When the logical statement evaluates to '''TRUE''' on the selected '''Field''' in a Microsoft Project '''source plan''' row, the row is imported.  Otherwise it is skipped.
+) '''Text Fields – ''' When Microsoft Project '''text''' types are entered in the '''Field''' cell of the '''Conditional Import Filters''' rule row, the '''Operator''' field dropdown will provide  the options shown below:
-:g) In the project view above, there are tasks that extend beyond 12/31/2015 but there are no tasks that '''Start''' on or after 12/31/2015.  Similarly, there are no tasks that '''Start '''before 10/11/2015.
+<center>[[File:P60-7_18_1_1-60-(4AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(4AA)-03032017.png</center>-->
-:h) When the project view is saved, the '''Conditional Import''' rules are saved as well and will be used to control the '''import''' for subsequent snapshots.  Further, in either this snapshot or subsequent ones, the '''Conditional Import''' rules can be edited (i.e., changed, added, or deleted).  When such changes are made to the '''Conditional '''Import rules, the current '''new snapshot''' or the '''snapshot '''being '''replaced '''will be configured by the active set of '''Conditional Import '''rules.  Finally, you can always revert to using '''flag''' columns or select '''All''' tasks for import.
+:a) These are the conventional four (4) logical operators used consistently in '''OPP''' for the text type.  They are the same '''Operators''' used in '''OPP''' for '''Conditional Formatting'''.  See the article at [[Conditional Formatting Overview for OnePager Pro for Version 6.0 | Conditional Formatting Overview for OnePager Pro]] <!--11.1.1-60--> for complementary details on the use of these logical operators.
-:i) An important thing to remember is that the '''Conditional Import''' rules, like the use of a single '''flag''' column, applies to '''only the current snapshot'''.  Therefore, changing the '''Conditional Import''' rules for a down timeline '''snapshot''' will '''NOT '''change the look for all previous snapshots unless further '''Conditional Import '''rules changes are specifically made for these '''snapshots '''via the '''REPLACE snapshot''' procedure.
+:b) When the logical statement evaluates to '''TRUE''' on the selected '''Field''' in a Microsoft Project '''source plan''' row, the row is imported.  Otherwise it is skipped.
-) '''Conditional Import''' is a powerful new capability that allows you to better control the content of your project views.  '''Conditional Import''' also makes project views more useful in '''project schedule analysis''' presentations/discussions that usually accompany project management.  As such, OnePager becomes not only a '''presentation''' tool but an addition to your suite of project schedule '''analysis''' tools.
+) '''Boolean Fields – ''' When Microsoft Project '''Boolean''' types are entered in the '''Field''' cell of the '''Conditional Import Filters''' rule row, the '''Operator''' field dropdown will provide  the options shown below:
-===When Microsoft Project/Excel Plan Source Files are Read-Only===
+<center>[[File:P60-7_18_1_1-60-(5AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(5AA)-03032017.png</center>-->
-) Occasions may also arise where you are not able to modify a Microsoft Project or Excel plan source file.  For instance, with a read-only file you might be unable to add the required '''import''' control '''flag''' columns or be unable to change them. You would have to first import them all and manually edit out or hide the unwanted row tasks/milestones after the project view is created.  Again, version 6.0 allows you to specify '''import conditions''' that meet your needs, say, only the rows which correspond to a particular project '''Phase''' for which there are data already available in the plan’s source file.  The example below will illustrate this:
+:a) These are the two (2) conventional Boolean logical operators used consistently in '''OPP''' for the Boolean type.  They are the same '''Operators''' used in '''OPP''' for '''Conditional Formatting'''.  See the article at [[Conditional Formatting with Boolean Fields for OnePager Pro for Version 6.0 | Conditional Formatting with Boolean Fields for OnePager Pro]] <!--11.5.1-60--> for compeimentary details on the use of these logical operators.
-:a) Consider the Microsoft Project plan source file just below which has no '''flag''' field columns defined and happens to be Read-only:
+:b) Boolean types are a special case as the '''operator''' and the '''value''' in '''OPP''' are combined into one cell of the '''Conditional Import Filters''' rule row - the '''Operator''' cell.
-<center>[[File:P60-7_18_1-60-(7)-09242016.png]]</center>
+:c) When the selected Field is '''TRUE''' (or '''Yes''') in a Microsoft Project '''source plan''' row, the row is imported.  Otherwise it is skipped.
-<center>P60-7_18_1-60-(7)-09242016.png</center>
+) '''Flag1 Through Flag20 Fields – ''' '''OPP''' treats Microsoft Project '''fields''' from '''Flag1''' through '''Flag20''' as '''Boolean''' types in the same way as described in the previous sub-section.
-:b) For the sake of this example, we will assume that '''Flag1''' through '''Flag20''' are not defined and have no data in the rows even if these columns are hidden in Microsoft Project.  You need, again for illustration, something to control the '''import''' of rows.  We’ll use the '''Phase''' column which happens to be the Microsoft Project '''Text30''' column.
+<center>[[File:P60-7_18_1_1-60-(6AA)-003032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(6AA)-003032017.png</center>-->
-:c) Following the same sequences as in the previous example, we’ll launch '''OPP''' from the Microsoft Project tool bar, select the '''NEW''' option from the '''OnePager Start ''' form, and make project view name and snapshot date modifications to the '''OPC '''form as shown below:
+) We want to emphasize the flexibility that '''Conditional Import Filters''' adds to the way you can '''import''' rows from your Microsoft Project '''source plan'''.  You can formulate sets of '''Conditional Import Filters''' rules to controls '''imports''' using '''all available types''' of Microsoft Project '''fields''' and use operators that let you select ranges of values and more complicated combinations of criteria.
-<center>[[File:P60-7_18_1-60-(8)-09242016.png]]</center>
+==Editing an Existing Filter Rule in the Conditional Import Rules Form==
-<center>P60-7_18_1-60-(8)-09242016.png</center>
+) Suppose you’ve composed several '''Conditional Import Filters''' rules in an open '''Conditional Import Rules''' form as shown below:
-:d) In the Microsoft Project plan source file there are a total of six (6) possible '''Phase''' names.  In this example, we’ll use '''Conditional Import''' to just build a project view showing '''Phase II''' task and milestones by creating a '''Conditional Import '''rule that looks like this:
+<center>[[File:P60-7_18_1-60-(5BB)-03022017.png]]</center>
+<!--<center>P60-7_18_1-60-(5BB)-03022017.png</center>-->
-<center>[[File:P60-7_18_1-60-(9)-09242016.png]]</center>
+:a) Now further suppose, after reviewing these two rules, that you realize that you may not be able to capture any tasks/milestones that happen to '''Start''' on 12/31/2015 because the current rule is based on the less than logical '''Operator.'''
-<center>P60-7_18_1-60-(9)-09242016.png</center>
+:b) To make the change in the '''Operator''' cell, click on the cell’s contents which will highlight the cell in blue and reveals the dropdown menu button which you should click.  When you do the '''Conditional Import Rules''' form should look like this:
-:e) This simple '''Conditional Import''' rule gives you access to all the tasks associated with '''Phase II'''.  So now click the '''OK '''button on the above form and then click the '''Create project view''' button on the '''OPC''' form to create the project view as shown below:
+<center>[[File:P60-7_18_1_1-60-(7AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(7AA)-03032017.png</center>-->
-<center>[[File:P60-7_18_1-60-(10)-09242016.png]]</center>
+:c) To change the rule, click the desired '''Operator''' in the dropdown menu, in this case the less than or equal '''Operator''', and it will be displayed in the '''Operator''' cell of the second rule as shown here:
-<center>P60-7_18_1-60-(10)-09242016.png</center>
+<center>[[File:P60-7_18_1_1-60-(8AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(8AA)-03032017.png</center>-->
-) Since '''OPP''' was told to generate the legend using the '''Resource Names''' column from the Microsoft Project plan source file, you see that only one phase name is displayed. '''Team 2''' is shown in the legend as the only resource name participating in '''Phase II''' of the project.  Using '''Conditional Import''' first overcomes any difficulty dealing with a Read-only file and, second, allows you to '''focus''' on the second phase of the project to see the details in the plan.  In this case the resources assigned.  Again, '''Conditional Import''' becomes an '''analysis''' aid as well as a '''presentation''' aid.
+:d) Any '''Field, Operator, or Value''' cell may be edited in this way.  Additionally, the '''On''' cell may be toggled to control the '''Conditional Import Filters''' rule's participation in the '''import''' process.  Finally, you may switch between the two radio buttons at the top of the form in order to change the relationship among the rules from '''OR''' to '''AND''' or vice versa.
-===Analysis Using an Existing Project View===
+:e) The edits described above may be made to the '''Conditional Import Rules''' form regardless of the '''OPC''' mode in which you are working (i.e., '''NEW and UPDATE''').  Also, you may bring up the '''Conditional Import Rules''' form from the '''OPC''' form as many times as needed to accomplish your presentation goal.  '''OPP''' saves the content of the last edit you make to the '''Conditional Import Rules''' form.
-) There are also occasions where you may want to go back '''AFTER''' a project view is created and '''update''' the project view to look at rows controlled by another '''flag '''column.  You may also want to build project views to do some '''analysis''' on the project schedule.  This is easily done '''AFTER''' the project view was created by looking at other logical relationship within the Microsoft Project/Excel plan source file data.
+:f) When satisfied with the structure of your '''import''' rules, click the '''OK''' button at the bottom of the form to return to the '''OPC''' form.  Now you are ready to create a new project view.
-====Changing the Flag Field AFTER the Project View is Created====
+==Copying an Existing Filter Rule in the Conditional Import Rules Form==
-) Making changes to the '''flag '''field column case after a project view is created is quite easy using the controls from the OnePager '''Project View Editor’s '''Data''' '''tab.
+) The '''Copy Rule(s)''' button is provided in the '''Conditional Import Rules''' form to facilitate the creation of additional rules.
-:a) First, launch Microsoft Project with the original plan source file and click the '''OnePager''' button on the Microsoft Project tool bar.  Then, click the '''UPDATE''' button on the '''OnePager Start''' form. This will load the project view into the '''OPP’s''' '''Project View Editor '''('''PVE''')'''. '''
+:a) To copy a rule to create a new rule, first select the rule row from which you wish to copy as shown below:
-:b) With the '''PVE''' running, go to the '''Data tab''' and click the '''Custom Update''' button which brings up the '''OPC''' form shown in the illustration below.
+<center>[[File:P60-7_18_1_1-60-(9AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(9AA)-03032017.png</center>-->
-:c) In this form, make sure the '''Select tasks with ‘Yes’ in column''' button is on, click the dropdown menu, and select the alternate '''flag''' field column as shown below:
+:b) Once the desired row is selected, clicking the '''Copy Rule(s)''' button will copy the contents of the rule selected as indicated by the highlighted left-most cell in the desired rule as shown below:
-<center>[[File:P60-7_18_1-60-(11)-09242016.png]]</center>
+<center>[[File:P60-7_18_1_1-60-(10AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(10AA)-03032017.png</center>-->
-<center>P60-7_18_1-60-(11)-09242016.png</center>
+:c) At this point you may edit the copied row in the manner described previously.  When you are finished, the new set of three rule rows may look like this:
-:d) In the above project view, which was created originally using '''Custom Import''' rules, you are changing the '''import''' control back to a defined '''flag '''column, specifically, '''Flag10'''.  When you do this and '''REPLACE''' the snapshot you get the following updated project view:
+<center>[[File:P60-7_18_1_1-60-(11AA)-03032017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(11AA)-03032017.png</center>-->
-<center>'''Doing the above described action doesn’t presently work either from OPEN or UPDATE (12)'''</center>
+:d) When satisfied with the structure of your '''import''' rules, click the '''OK''' button at the bottom of the form to return to the '''OPC''' form.  Now you are ready to create a new project view.
-:e) This example illustrates how you can revert from using '''Conditional Import''' rules to the more conventional use of '''flag''' columns to control '''import'''.
+==Deleting an Existing Filter Rule in the Conditional Import Rules Form==
-====Changing Custom Import Rules AFTER the Project View is Created====
+) There are times when a particular '''Conditional Import Filters''' rule will no longer serve its purpose.  You can select the rule row to be deleted and click the '''Delete Rule(s)''' button.
-) As was mentioned earlier, before version 6.0, handling '''import '''condition change situations meant totally starting over by going back to the '''OnePager Start''' form and selecting a different '''flag''' column.  Version 6.0 lets you change the '''import conditions''' from the '''PVE''' by using the '''Data tab’s Custom Update''' button to access your '''Conditional Import''' rules and edit them.  Here’s how changing '''Conditional Import''' rules can be done '''AFTER''' the project view is created:
+:a) The process for deleting a rule parallels the process for copying a rule row in that the you must select the desired row to '''delete''' by clicking the left-most cell in that rule’s row.
-:a) Consider the previous example where you wanted to create a project view consisting of tasks/milestones with '''Start''' dates later than 10/11/2015 and earlier than 12/31/2015.  Suppose you have that project view in the '''PVE''' and you want to '''import''' additional tasks/milestones for display that have '''Finish''' dates less than 4/1/2016.
+:b) Once the selection is made, click the '''Delete Rule(s)''' button and '''OPP'''  will first put up a warning message asking if you really want to '''delete''' the rule row as shown below:
-:b) You can do this by first bringing up the project view from Microsoft Project by launching OnePager and clicking the '''UPDATE''' button in the '''OnePager Start''' form.  This brings up the '''PVE''' displaying the project view with the two '''Start''' date '''Conditional Import Rules''' defined previously.
+<center>[[File:P60-7_18_1_1-60-(12)-09272016.png]]</center>
+<!--<center>P60-7_18_1_1-60-(12)-09272016.png</center>-->
-:c) Next, go to the '''Data tab''', click the '''Custom Update''' button bringing up the '''OPC''' form created in a previous example.
+:c) If you select the '''No''' option, '''OPP''' will abandon the rule deletion operation and the warning message will disappear leaving the selected rule row still selected.
-:d) Then, click the '''Edit Filters…''' button to bring up the '''Conditional Import Rules''' form which displays the two rules.  You can now modify the '''Conditional Import''' rules by '''Adding''' a new rule as shown below:
+:d) If you select the '''Yes''' option, '''OPP''' will remove the warning message, delete the selected rule row, and leave the '''Conditional Import Rules''' form showing the remaining rule rows, if any.
-<center>[[File:P60-7_18_1-60-(13)-09242016.png]]</center>
+:e) When satisfied with the structure of your '''import''' rules, click the '''OK''' button at the bottom of the form to return to the '''OPC''' form.
-<center>P60-7_18_1-60-(13)-09242016.png</center>
+==Switching from Flag Fields to New Conditional Import Filters Rules==
+) When you click the '''NEW''' button, the '''OPC''' form will appear as shown below.  The process for building a new project view with '''Conditional Import Filters''' is the same with the exception that instead of using '''flag''' field from your Microsoft Project '''source plan''' you will, instead, invoke the '''Conditional Import Rules''' form from the '''OPC'''  form as shown below:
-<center>'''The Add Rule button didn’t work.  Used the Copy Button to copy the second rule then edited it to make above screenshot.  '''</center>
+<center>[[File:P60-7_18_1_2-60-(1AA)-03072017.png]]</center>
+<!--<center>P60-7_18_1_2-60-(1AA)-03072017.png</center>-->
-:e) Now, click '''OK''' on the '''Conditional Import Rules''' form to return to the '''OPC''' form where you should click the '''REPLACE existing snapshot with date''' button and use the dropdown calendar to select a '''replacement snapshot date''' as shown below:
+:a) In the illustration above, in the '''Task Selection''' section of the form, the '''Select task by custom filter''' radio button is clicked.  This action brings up the '''Conditional Import Rules''' form also shown above.
-<center>[[File:P60-7_18_1-60-(14)-09242016.png]]</center>
+:b) At this point you may '''Add Rules''' to the form, '''Copy Rules, Delete Rules,''' or edit existing rules.
-<center>P60-7_18_1-60-(14)-09242016.png</center>
+==Switching from Conditional Import Filters Rules to Flag Fields or Selecting all Tasks==
-:f)  Then, click the '''Replace dates''' button on the '''OPC '''form and the following project view will appear:
+) If you subsequently decide after composing one or more '''Conditional Import Filters''' rules and clicking '''OK''' on the '''Conditional Import Rules''' form that you want to use '''flag''' fields instead, you may revert back to either of the two other '''Task Selection''' options provided in the '''OPC''' form shown above.
-<center>[[File:P60-7_18_1-60-(16)-09242016.png]]</center>
+:a) To do this, click either of the other two radio buttons to '''Select all tasks''', or '''Select task with ‘Yes’ in field:'''
-<center>P60-7_18_1-60-(16)-09242016.png</center>
+:b) When you click the '''Select all tasks''' button there is no further action you need to take on the '''OPC'''  form.
-'''Using the three rules shown CI Rule form above gives what I think is an erroneous result above.  I conclude that using the Copy Rule and editing that rule does not produce the desired results.  A previous attempt using the Copy Rule and editing that rule to be Finish&gt;4/1/2016 gave a two row project view.  The project view should have all the tasks shown in P60-7_18_1-60-(6)-09242016.png plus additional task/milestones that have Finish dates less 4/1/2016.  The only difference between this 3 rule project view and the previous 2 rule project view is show in the red rectangle above.'''
+:c) However, if you click the '''Select tasks with ‘Yes’ in field:''' you will need to select a '''field''' from your Microsoft Project '''source plan''' as shown below:
-'''It may be that the combination of rules and the actual date in the .mpp file has conspired to give this result.  I will investigate.'''
+<center>[[File:P60-7_18_1_1-60-(13)-09272016.png]]</center>
+<!--<center>P60-7_18_1_1-60-(13)-09272016.png</center>-->
-==Related Links:==
+:d) In these circumstances where you’ve switched from using '''Conditional Import Filters''' rules to either '''selecting all tasks''', or '''selecting tasks using a flag field''', '''OPP''' will discard any '''Conditional Import Filters''' rules associated with the project view.
+==Adding, Editing, Copying, and Deleting Conditional Import Filters Rules==
+) Managing '''Conditional Import Filters''' rules was discussed in previous sub-sections of this article.  Please follow the reference links provided below for details on adding, editing, copying, and deleting of '''Conditional Import Filters''' rules:
+:a) '''Adding a new rule''':  [[Conditional Import for OnePager Pro Desktop for Version 6.0#Adding a Filter Rule to the Conditional Import Rules Form | Adding a Filter Rule to the Conditional Import Rules Form]].
+:b) '''Editing an existing rule''': [[Conditional Import for OnePager Pro Desktop for Version 6.0#Editing an Existing Filter Rule in the Conditional Import Rules Form | Editing an Existing Filter Rule in the Conditional Import Rules Form]].
+:c) '''Copying a rule''':  [[Conditional Import for OnePager Pro Desktop for Version 6.0#Copying an Existing Filter Rule in the Conditional Import Rules Form | Copying an Existing Filter Rule in the Conditional Import Rules Form]].
+:d) '''Deleting a rule''':  [[Conditional Import for OnePager Pro Desktop for Version 6.0#Deleting an Existing Filter Rule in the Conditional Import Rules Form | Deleting an Existing Filter Rule in the Conditional Import Rules Form]].
+=A Simple Example Using Conditional Import=
+In this section and the one to follow, we’ll provide a couple of examples of a workflow that you might find most useful.  First we’ll provide a simple example and then extend it to a more advance use of the workflow.
+==Setup==
+) Suppose you have a situation where you want to focus the attention of your audience on a particular set of tasks that have the following attributes:
+:a) Where tasks/milestones '''start''' on or after October 1, 2015 but no later than December 31, 2015.
+:b) Where swimlanes represent the '''Phases''' of the project
+:c) Where the two '''additional text columns''' represent the '''Start Dates''' and the '''Finish Dates''' of each displayed task respectively.
+:d) And where the '''Legend''' is organized by '''Resource Name'''.
+) Let’s further suppose that we are going to use the '''BlueGrass Project 2J-303-PMO''' Microsoft Project '''source plan''' as input to OnePager Pro and we want to use the '''Single Project View Gantt View – Detailed Template'''.
+) To begin with, the '''source plan''' will look like this:
+<center>[[File:P60-7_18_1_1-60-(14-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(14-1)-05092017.png</center>-->
+) Before we launch OnePager Pro '''Desktop''', the '''Main''' tab of the '''Template''' we will use for this example looks like this:
+<center>[[File:P60-7_18_1_1-60-(15-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(15-1)-05092017.png</center>-->
+) If we launched OnePager Pro '''Desktop''' from the desktop '''icon''' with the above '''Template as the current Template''', the tasks and milestones included in the project view would be those associated with '''Yes''' in the '''Flag20''' field in the '''source plan''' above.  This is not what we want so we first have to change the task and milestone selection criteria using the '''Conditional Import Filters''' feature as we’ll show next.
+==Changing the Task and Milestone Selection Criteria==
+) With the conditions established in the sub-section above, let’s go ahead and launch OnePager Pro '''Desktop '''from the desktop '''icon''' which will bring up the '''OnePager Start''' form as shown below:
+<center>[[File:P60-7_18_1_2-60-(16-1)-05222017.png]]</center>
+<!--<center>P60-7_18_1_2-60-(16-1)-05222017.png</center>-->
+) Next, we’ll click the '''NEW''' button which will bring up the abbreviated '''OnePager Choices '''('''OPC''') form shown here:
+<center>[[File:P60-7_18_1_2-60-(16AA-1)-05222017.png]]</center>
+<!--<center>P60-7_18_1_2-60-(16AA-1)-05222017.png</center>-->
+:a) Click the '''Select…''' button which brings up the Windows Open form.
+:b) Use the Open form to select the Microsoft Project '''source plan''' you need and click '''Open''' in the Windows Open form.
+:c) '''OPP Desktop''' will retrieve the selected '''source plan''' where you can fill in  the required fields of the '''OPC''' form so that it looks like the form shown here:
+<center>[[File:P60-7_18_1_1-60-(17-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(17-1)-05092017.png</center>-->
+) We’ve gone ahead and confirmed that we have the correct '''source plan''' and we’ve filled in the '''Title of New Project View'''.  We see that the '''Task Selection '''criteria will be based on the contents of the '''Flag20 '''field, and we don’t want this field to be used.  We have two ways to invoke the '''Conditional Import Filters''' feature and we’ll explain each below:
+===Using the OnePager Choices Form to Create Conditional Import Filters===
+) For this first technique, click on the '''Select tasks by custom filter''' radio button, which brings up the '''Conditional Import Rules''' form as shown below:
+<center>[[File:P60-7_18_1_2-60-(18AA-1)-05222017.png]]</center>
+<!--<center>P60-7_18_1_2-60-(18AA-1)-05222017.png</center>-->
+) Next, we’ll enter the two '''Conditional Import Filters''' we specified in the previous subsection and make sure the '''All of the following are true''' radio button is selected so the '''Conditional Import Rules''' form will look like this when we are done:
+<center>[[File:P60-7_18_1_1-60-(19-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(19-1)-05092017.png</center>-->
+) From here we could go ahead and click the '''OK''' button on the '''Conditional Import Rules''' form and, once back at the '''OPC''' form, go ahead and create the project view.  However, before we do that we want to show the alternative way to enter '''Conditional Import Filters '''rules.
+===Using the Template to Create Conditional Import Filters===
+) To illustrate this second technique let’s roll back to the '''OPC '''form we saw above and notice that the checkbox labeled '''Show field mappings''' is checked and the button below the checkbox is called '''Next&gt;'''.  Now click the '''Next&gt;''' button which takes you to the second page of the '''OPC''' form which looks like this:
+<center>[[File:P60-7_18_1_1-60-(20-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(20-1)-05092017.png</center>-->
+) Next, click the '''Edit current template…''' button which will bring up the current '''Template''' as shown below.  Then, navigate to the '''Main''' tab as we have done here and note the button titled '''Add/edit conditional import filter…''':
+<center>[[File:P60-7_18_1_1-60-(21-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(21-1)-05092017.png</center>-->
+) When the '''Add/edit conditional import filter…''' button is clicked, the '''Conditional Import Rules ''' form will appear and you can enter the two rules we specified in for this example as we’ve shown below:
+<center>[[File:P60-7_18_1_1-60-(22-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(22-1)-05092017.png</center>-->
+===Creating the Project View===
+) After entering the two '''Conditional Import Filters '''rules, as shown above, click the '''OK '''button on the '''Conditional Import Rules''' form and then the '''Save and''' '''Use '''button at the bottom of the '''Template''' form.
+) These actions will take you back to the second page of the '''OPC''' form, shown earlier; where you can click the '''Create new project view''' button and OnePager Pro will create the project view as shown here:
+<center>[[File:P60-7_18_1_1-60-(23-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(23-1)-05092017.png</center>-->
+===Editing the Project View===
+) Finally, we need to add the two '''additional text columns''' specified to show '''Start and Finish''' dates.
+) This final requirement is implemented by using the '''Additional Text Column''' feature '''(insert link here)'''.  When these actions are taken the project view will look like this:
+<center>[[File:P60-7_18_1_1-60-(24-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(24-1)-05092017.png</center>-->
+=An Advanced Example Using Conditional Import=
+The advanced workflow example presented in this section on '''Conditional Import Filters''' rules is a continuation of the example in the previous section.
+If you haven’t read or reviewed the simple example, we suggest that you do so before reading on in this section.
+==Continuation of Simple Example==
+) What we intend to show you in this section is how to proceed from the creation of the project view in the previous section through successive '''edits''' and '''replacements''' to get to a project view that will be perfect for a specific schedule conversation.
+) To set the stage, let’s establish some further guidance for the final visual presentation:
+:a) It needs to be very focused on the apparent trouble spot; say with the '''Prime '''contractor just for example.
+:b) There needs be as few tasks as possible so as to keep the audience’s focus on the real project management issue.
+:c) The presentation of the schedule issues needs be on one page.
+) Given the above guidance, we need to restructure the project view from the previous section.  Of course, we want to do this in the most efficient way so that it what we will describe in the next sub-section.
+===Using Conditional Import Filters to Update a Project View through Replacement===
+) Looking back at the project view from the previous sub-section, we see that it contains tasks from all the '''Resources''' available during the time interval we specified in the original set of '''Conditional- Import '''rules.  Our guidance says that we want to focus more on the '''Prime '''contractor. So, we’ll use the '''Conditional Import Filters''' feature to refine our '''import criteria''' and '''replace '''the project view with tasks/milestones that meet the '''Start''' criteria and the '''Resource-Names''' criteria we need.
+) To modify the '''Conditional Import Filters '''rules we will do the following steps:
+:a) First we go to the project view and bring up the '''PVP''' form at the '''Main '''tab.
+:b) Next, we click the '''Add/edit conditional import filter…''' button to bring up the '''Conditional Import Rules '''form.
+:c) Then, we use the '''Add Rule''' button to make a row for the third rule and compose the third rule to specify '''Resource Names''' in the '''Field''' column, an '''equal '''sign in the '''Operator '''column, and the word '''Prime '''in the '''Value''' column.
+:d) When you are done adding the new (third) rule, the forms will look like this:
+<center>[[File:P60-7_18_1_1-60-(25-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(25-1)-05092017.png</center>-->
+) Now do the following steps:
+:a) Click the '''OK''' button on the '''Conditional Import Rules''' form.  This will close the form and take you back to the '''PVP''' form’s '''Main''' tab.
+:b) Here, click the '''Apply''' button only.  This will apply the change to the project view but keep the '''PVP’s Main''' tab open.
+:c) Before doing anything else, go to the '''Project View Editor’s '''('''PVE''') tool bar and select the '''Data''' tab.  When you are finished with these steps, the '''PVE''' and the '''PVP Main''' tab will look like this:
+<center>[[File:P60-7_18_1_1-60-(26-1AA)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(26-1AA)-05092017.png</center>-->
+) The '''last''' step in this workflow is to click the '''Replace Snapshot''' button which is the left-most button on the '''Data '''tab tool bar.  This is the action that tells OnePager Pro to update the project view by re-importing the source data with task selection controlled by the three rules now active in the '''Conditional Import Rules''' form.
+) When the OnePager Pro '''replace''' process completes, the project view will be honed to not only restrict the start dates but also to restrict the Resource Names in the chart, like this:
+<center>[[File:P60-7_18_1_1-60-(27-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(27-1)-05092017.png</center>-->
+===Summary of First Project View Replacement Iteration===
+) To summarize what we’ve done we’ve accomplished the following:
+:a) Used the original project view in conjunction with the '''Conditional Import Rules''' form to specify an additional rule that further narrows the tasks in the chart.
+:b) Used the '''Replace Snapshot''' button to tell OnePager Pro display only this refined set of tasks.
+===Second Project View Replacement Iteration===
+) The project view we created above still isn’t quite ready for our schedule conversation.  Looking at it closely, we probably don’t need to focus on any tasks/milestones that the '''Prime''' contractor has completed.  So, in this next iteration let’s modify our '''Conditional Import Filters''' to just bring in those tasks/milestones that are less than '''100 percent complete'''.
+) We’ll use the same sequence of steps that were used in the first '''replacement iteration''' we described above.
+:a) In the open '''PVP''' form, click the button to bring up the '''Conditional Import Rule''' form and add a fourth rule restricting to tasks/milestones that are '''less than 100 percent complete'''.  The form will look like this when we are done adding the rule:
+<center>[[File:P60-7_18_1_1-60-(28-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(28-1)-05092017.png</center>-->
+:b) With the above rule added, click the '''OK '''button in the '''Conditional Import Rules''' form and after it closes, click the '''Apply '''button on the bottom of the '''PVP '''form’s '''Main''' tab.
+:c)The appearance of the '''PVE '''will be like this:
+<center>[[File:P60-7_18_1_1-60-(29-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(29-1)-05092017.png</center>-->
+:d) The last step is to click the '''Replace Snapshot''' button on the OnePager Pro '''Data''' tab tool bar.  OnePager will perform the '''snapshot replacement''' and the project view will look like this:
+<center>[[File:P60-7_18_1_1-60-(30-1)-05092017.png]]</center>
+<!--<center>P60-7_18_1_1-60-(30-1)-05092017.png</center>-->
+===Summary of Second Project View Replacement Iteration===
+) The project view in the illustration above now meets all the Start, Resource Name, and %Complete  criteria to support the schedule conversation.
+) This was all done by an iterative workflow that couples updates to the '''Conditional Import Rules''' with the '''Replace Snapshot '''button on the OnePager Pro tool bar’s '''Data''' tab.
+) All that needs to be done now is to copy the project view into the media to be used for the schedule conversation.
+===Some Additional Comments on this Workflow===
+) It’s important to remember for this workflow that you always want to '''REPLACE''' the single''' '''snapshot in the project view.  We advise against '''ADDING''' a snapshot as you refine your rules because this can result in empty rows for tasks that were present under a previous set of rules but are now absent.
+) If you want to begin the workflow by '''OPENING''' a previously-created project view, it is essential, as mentioned above, that there is a clear and viable path from the project view to its source plan(s).    You can confirm this and fix any problems by clicking the '''Selected Files''' button on the '''Data''' tab.
+=Related Links=
 [[Basic Workflows for Version 6.0 (Portal) | Basic Workflows (Portal)]]
-[[Conditional Formatting for Version 5.3 (Portal) | Conditional Formatting (Portal)]]
+[[Conditional Formatting for Version 6.0 (Portal) | Conditional Formatting (Portal)]] <!--11.0.1-60-->
-[[Using the OnePager "Data" Tab's "Selected file(s)" Button for Version 6.0 | Using the OnePager "Data" Tab's "Selected file(s)" Button]]
+[[Using the OnePager "Data" Tab's "Selected file(s)" Button for Version 6.0 | Using the OnePager "Data" Tab's "Selected file(s)" Button]] <!--7.17.1-60-->
-[[OnePager Express Import of Data from Microsoft Excel]]
+[[OnePager Express Import of Data from Microsoft Excel for Version 6.0 | OnePager Express Import of Data from Microsoft Excel]] <!--4.4-60-->
 [[Message to Assist with Setting Import Flags When No Data Are Imported]]
-[[Understanding Project Views and Snapshots for OnePager Pro]]
+[[Understanding Project Views and Snapshots for OnePager Pro for Version 6.0 | Understanding Project Views and Snapshots for OnePager Pro]] <!--4.1-60-->
-[[Understanding Project Views and Snapshots for OnePager Express]]
-(7.18.1.1-60)
+(7.18.1.2-60)
 [[Category:Version 6.0]]
-[[Category:Add-in]]
 [[Category:Desktop]]
 [[Category:Basic Workflows]]
-[[Category:Conditional Import]]
+[[Category:Conditional Import Filters]]
 [[Category:Importing]]
 [[Category:Project Views]]
@@ Line 178: / Line 413: @@
 [[Category:Conditional Formatting]]
 [[Category:Getting Started with Version 6.0‏‎]]
+[[Category:Integrated Master Schedules]]
+[[Category:Enterprise Custom Fields]]
 [[Category:OnePager Pro]]