Upgrade the interview experience from a previous version

What do you want to do?

Upgrade from Interactive for Java

Upgrade from Interactive for .NET

Upgrade from Interactive for Java

The following describes what needs to be done to effect a migration from Haley Interactive (JRBI) to Oracle Web Determinations.

Recompile the rules

One of the first things you will need to do if you are migrating from Haley Interactive to Oracle Web Determinations, is recompile your rules; to do this:

  1. Open the rulebase in Oracle Policy Modeling; you will be taken through the upgrade wizard.
  2. Build and debug, with screens; your rulebase should function with default styling, allowing you to make determinations.

Screen order and screen flows:

Visio screen flows are no longer supported, and have been replaced by the much simpler integrated screen flows. To update existing rulebases that contain a data review screen, do the following:

  1. If the rulebase has a data review screen, open it and check "default screen order" to make screens appear in the same order as the data review screen; this also enables a progress bar. 
  2. Any Visio screenflows that are more complicated than the default screen ordering, should be rebuilt in the new screen flow editor.

Commentary

Oracle Web Determinations has a different commentary model from Interactive, with commentary deployed and stored with the rulebase itself.  Web Determinations also supports screen commentary, which was previously unavailable.

  1. Build commentary files:  if you wish, you can generate new screen commentary files.  If you want to migrate only the attribute commentary that you previously had in Interactive, leave only "base-level attributes on screens" checked.  After generating the files click the Yes button to open the newly created directory with attribute commentary files. 
  2. Synchronize your existing attribute commentary directory into the new directory by renaming the existing attribute commentary files from .htm to.html if necessary, so that the file names match exactly that which was built by Oracle Policy Modeling.  Existing 'no help' or commentary 404 error pages can be ignored; Web Determinations will not show a commentary link where there is no corresponding commentary file to link to.
  3. Any links in the commentary itself, including CSS file links, are now relative to the commentary URL, not the location of the commentary html file. For example, if you previously had a commentary html file that included:



     <link rel=stylesheet href="commentary.css"> <img src="images/foo.jpg">



    you will need to move the relevant files to:



    <project>Release\web-determinations\WEB-INF\classes\resources\commentary.css

    <project>Release\web-determinations\WEB-INF\classes\images\foo.jpg




    and you'll need to change the references in the commentary HTML file to:



    <link rel=stylesheet href="../../../resources/commentary.css">

    <img src="../../../images/foo.jpg">



IsHTML images

modify all URLs in isHTML.:

IsHTML commentary

Visual styles

This is a complex manual process because Web Determinations uses a completely different rendering process than was used by Interactive.

You are likely to find that there are small differences in the shared portions of code (headers, footers, and so on) between the various customized pages in your Interactive project.  These will need to be reconciled, exceptions made according to screen name or screen type where necessary, JSP code translated to velocity template code, and placed into the various templates (header.vm, footer.vm, question_screen.vm, and so on) in the Web Determinations structure.

Another difference that you will need to account for is that Web Determinations has shifted to a completely CSS-based layout in place of the table-based layout used by Interactive.

Change the progress bar from textual to graphical:

  1. Verify you have the textual progress bar displaying correctly.
  2. If the stages displayed are not what you like, rearrange your question screens into folders with the names (and in the order) that you like.
  3. Rename (or create) graphics for the progress stages, where the names of the graphics files are based on the exact text of the progress stages.  For example, if you have a progress stage with text, "Household" then create two graphics, "Household_active.jpg" and "Household_inactive.jpg"
  4. Modify the includes/stages.vm velocity template to create <img src="..." > tags based on the stage names, instead of just printing the stage names directly.
See also:

isHTML and Web Determinations customization

Upgrade from Interactive for .NET

A major feature of Oracle Policy Automation 10.0 is that it provides support for Web Determinations on the .NET platform for the first time since 8.5. In that time significant changes have been made to the product suite which means that the upgrade path from RBI .NET 8.5 to Web Determinations is dependent on the specific needs of the individual project..

The general things to consider when upgrading are: