Oracle® Insurance Rules Palette
The Debug pane is a tool that can be used to debug errors in the math section of a policy- or client-level transaction. This tool moves through execution steps in sequence, and displays all math variables and their associated values at each step. Debugging not only walks through the transaction’s configuration, but automatically opens any called functions, steps through all of the math variables and displays values according to what was passed in from the transaction configuration.
Before using the debug feature, make sure remote debugging is set up in the Rules Palette.
Steps to Check Remote Debugging in Rules Palette
Right-click on the environment connection in the Main Explorer tab.
Select Properties. The Properties Window will open.
Scroll down to the row for the Debug Web Service URL.
Click the button to the right of the field. An Environment Properties window will open for the Debug Web Service. The URL should be listed.
Debug functionality is available for transactions at both the policy level and the client level.
The methods for debugging the configuration are as follows. The buttons for these functions are located at the top of the EventList Window.
Buttons Available in the Debug Pane
To start a debug session for a client-level transaction:
All translation, compilation and runtime errors must first be fixed in order to use the Debug pane. Debug can be performed when the transaction is checked-in or checked-out; however, configuration problems can only be fixed if the transaction is checked out.
To start a debug session for a policy-level transaction:
All translation, compilation and runtime errors must first be fixed in order to use the Debug pane. Debug can be performed when the transaction is checked in or checked out; however, configuration problems can only be fixed if the transaction is checked out.
Debug Pane and Related Windows
In the EventList Window, a blue or green
button appears next
to the math variable execution steps. The blue
button indicates the math variable is part of the transaction. The
green button indicates the math variable is part of a called function.
Double-click on either button to be brought to
the math variable in the transaction or function configuration.
The remote debugger does not debug Function rules separately, only as called within a transaction.
Use the
ContextList Window to view the state of the math variable at each step
in the debug session. If the value does not fully
display in the column, click the ellipsis (...) button to see the full
details. When a Valuation element is debugged, a dollar sign icon is available instead of the ellipsis button. Clicking it will open a Policy Valuation window that displays valuation and fund information.
Note: To clear all values in the ContextList Window and restart debugging, click the Rewind button at the top of the EventList Window.
The Debugger will not display the values of MathUpdate math variables or the field itself.
Another debugging feature is the ability to set-up breakpoint(s) in
the configuration. Breakpoints are places in the code where execution
is stopped for debugging purposes. In the Rules
Palette, select as many breakpoints as needed by checking the BP checkbox.
After breakpoints are selected, use the Run button
in EventList window to step through configuration.
Important: Breakpoints
can be set for a loop that then displays math variables and associated
values for each iteration of the loop. Use the Run button
to step through each iteration of a loop.
Breakpoint Column on Debug Pane
To clear all the breakpoints, select the Clear All
button.
Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices