Manually Migrate a Version 10.3 Or Earlier Project to the Current Version of Policy Modeling

1. Open the current version of Policy Modeling and create a new project in a different location to the old project.
2. Make sure that the new project has the same project language as the old project. You can check the project language of the old project by opening the .xprj file using Notepad. The project language will be indicated in the form of a locale (for example, <source-language code="en-GB" /> indicates a project language of British English). For more information on the locale setting, see Locale Codes.

1. Open Policy Modeling 10.x and then:
   1. Open each Word *.doc file and click the Strip Hidden button on the Oracle Policy Modeling toolbar. Then save it as a *.docx file (from the main menu select Save As, then Word Document) into the Rules folder of your new project.
   2. Open each Excel *.xls file and save it as a *.xlsx file (from the main menu select Save As, then Excel Workbook) into the Rules folder of your new project.
      

   These documents should now appear in the Rules tab in your current version of Policy Modeling project (although you may see an error that these are not in a supported format until you complete the next step).

2. In the current version of Policy Modeling, open each rule document and click the Validate button.
   1. If any errors are detected, Policy Modeling displays a clickable error pane, giving details of each error and allowing you to navigate directly to it. In particular, note:
      1. Rules using the Concatenate function will need to be rewritten to comply with the updated syntax which uses the + symbol to combine strings (where previously the & symbol was used).
         
      2. Rules using numerical functions to perform calculations may generate errors if there is no space either side of the mathematical operator. For example, the rule
         

         the monthly amount = the annual amount/12

         
         will need to have a space added either side of the slash (mathematical division operator) as follows:
         

         the monthly amount = the annual amount / 12

         
         Tips:
         • Review the Data tab for odd-looking attributes. For example, a single attribute with the text "the monthly amount = the annual amount/12" indicates a calculation rule that needs fixing. Right-click on the problem attribute to see where it appears in the policy model.
         • On the Data tab, use the filter box to quickly find attributes containing mathematical symbols.
           
           
      3. Rules using natural language forms of Minimum or Maximum ('the lesser of' or 'the greater of') may generate errors if they contain ambiguous expressions. The error pane will indicate the condition or conclusion where Policy Modeling has detected the ambiguous expression, and will state 'Please use parentheses to clarify'. For example, the rule
         

         the work-related child and dependent care costs to be used in the calculation of the Federal Child and Dependent Care Credit = the lesser of the estimated annual child care and dependent care expenses and the maximum amount of work-related child and dependent care costs to be used in the calculation of the Federal Child and Dependent Care Credit

         
         will need to have parentheses added as follows:
         

         the work-related child and dependent care costs to be used in the calculation of the Federal Child and Dependent Care Credit = the lesser of (the estimated annual child care and dependent care expenses) and (the maximum amount of work-related child and dependent care costs to be used in the calculation of the Federal Child and Dependent Care Credit)

         
         
      4. Rules using any of the deprecated functions will need to be addressed.
   2. Search for any rules using 'silent' or 'invisible' operators in rule conditions. 'Silent' and 'invisible' at the rule condition level are not yet supported in the current version of Policy Modeling. For each condition using a silent or invisible operator:
   1. Check the other rules in the project where the same attribute is used and note whether 'silent' or 'invisible' or both are used.
   2. Delete the silent or invisible operator where used with that attribute.
   3. Place your cursor in the text of the relevant attribute and click the Go To button on the Policy Modeling toolbar in Word or Excel.
   4. Select the Edit Attribute option in the pop-up window to open the Edit Attribute dialog.
   5. Use the Explanation Options button to implement your desired logic for 'silent' and / or 'invisible'. For more information, see Hide information in an explanation. Note: It is currently only possible to have one set of Explanation Options per attribute, so ensure that the options you choose are appropriate for every rule where the attribute is used.

1. On the current version of Policy Modeling Data tab:
   1. Manually add any attributes that are not used in rules. (Attributes that are used in the rule documents should have been automatically added to the Data tab in the new project.)
   2. For each attribute, check that the correct attribute type has been automatically chosen, and correct if required in the Edit Attribute dialog. Pay particular attention to currency attributes which may have been migrated as number attributes.
   3. Add any entities.
   4. Add any relationships. (Errors will be reported if there are any unusual relationships in the rule documents.)
2. Click the Debug button. (This will check that no errors are detected in the new policy model.)

1. If your 10.x project used attribute or pronoun substitution you will need to check, and in some cases re-implement, those settings.
2. If your 10.x project used input validations in the Properties file (for example Min, Max, RegEx, Error message) you will need to re-implement those settings in the current version of Policy Modeling. For more information see Validate User Input.

If your 10.x project used commentary, you will need to use other functionality to add notes or help to an interview. For example, you could:

• Add labels directly to the interview screen
• Add links to other HTML pages, such as:
  • other webpages
  • the 10.x commentary HTML files
• Add definitions to terms on an interview screen using HTML

1. On the current version of Policy Modeling Project tab on the Forms subtab, add a new form for each of your existing BI Publisher templates. This will create an *.rtf file for each template in the location <ProjectName>/FormTemplates/<locale>/, in your new project. For example myBenefits/FormTemplates/en-US/. For more information on the locale setting, see Locale Codes.
2. Open each of your existing templates and save it as the corresponding new template *.rtf file, in the location in Step 1.
3. On the current version of Policy Modeling Data tab, add names (previously called 'Public names') to any attributes or relationships used in the generated documents.

Screen files cannot be imported into the current version of Policy Modeling from version 10.x or earlier, however, equivalent functionality can usually be achieved by recreating the screens. See Create a Screen for more information on adding screens in the current version of Policy Modeling.

While re-creating your screens, you can have the current version of Policy Modeling open at the same time as Policy Modeling version 10.2 or later.

The display and order of screens in 12.x is driven by relevancy, so you should check that your interviews are operating as intended. For more information, see Definition of 'relevant'.

Modules cannot be imported into the current version of Policy Modeling from version 10.x, however, equivalent functionality can be achieved by using project inclusions. See Include Assets From Another Project for more information on using project inclusions in the current version of Policy Modeling.

1. On the current version of Policy Modeling Project tab on the Test Cases subtab, add a new testing document.
2. Copy the contents of any existing What-If testing documents into your new testing document and re-applying the testing styles.
3. Re-enter any data stored in test scripts into the new testing format. For more information, see Create, Edit Or Delete a Test Case.

Click the Debug button (or hit F5 from any tab in the current version of Policy Modeling) to test whether the migration has been successful and correct any errors identified.