This section explains the
Oracle Forms TrueLog structure and the
Form Controls window.
Oracle Forms TrueLog Structure - Overview Explains the Form Controls window, which displays the elements of the selected Oracle Forms applet window in tabular-data representation.
Node Information Explains the information about the current state of all controls that is stored by Oracle Forms nodes.
Working With Web Calls Because Oracle Forms is a mixed protocol that often incorporates Web calls in scripts, TrueLog Explorer enables you to alternate between a tabular data-based representation view for binary Oracle Forms applets and a rendered HTML view for HTML pages.
In Body / Out Body Pages Describes the message block types (OraForms call) that are communicated between Silk Performer and Oracle Forms.
Terminal Messages Describes the three terminal-message types that are used to end communication round-trips between client and server.
Analyzing Errors in Oracle Forms Tests After tests, it is typical to have multiple TrueLog On Error files open in TrueLog Explorer. You can analyze these erroneous transactions chronologically, regardless of which TrueLogs the errors were recorded
in.
Analyzing Oracle Forms Test Scripts Once you have generated a test script you can determine if the script runs without error by performing a Try Script run. A
Try Script run determines if a script accurately recreates the recorded interactions.
Unanticipated Get Calls Describes the scenarios in which you must manually script OraFormsSet and OraFormsOnMessageGet because of unanticipated Get calls.
Setting Silk Performer Log Level to Debug To prepare for manual scripting when an unanticipated get call is received, it is necessary that you analyze the in-data and out-data that is exchanged between the client and server.
This analysis can only be conducted if you have set the Silk Performer log level to debug.