Defect # Description Workaround 39386 TrueLog Explorer may crash by running into a seeming endless re-direction loop. The problem occurs if document A redirects to document B which again loads document A (e.g.: as a frame) using the identical request URL already used to request A. While a Web server may identify a differentiator by analyzing the available HTTP request headers, e.g. the Referrer header, TrueLog Explorer does not have this ability and builds an endless loop, as it knows only that A follows B and B then follows A again. Disable "frame and image loading"; avoid clicking on the relevant API node 34040 Oracle Forms TrueLog crashes after some transactions. De-select the "Applet execution" setting in Settings -> Options -> Display -> HTML rendering. 33416 The rendered view of terminal emulation applications using non-ascii characters may display strange characters. Change the default GUI font of the Workbench (Settings -> System -> Layout -> Font & Colors) to a font that better supports your character set. Restart TrueLog Explorer after changing the font to apply the settings to TrueLog Explorer. 32943 On-access virus scanner software may cause TrueLog Explorer to crash. Turn off the on-access scan functionality of your virus scanner software, or open a TrueLog in TrueLog Explorer after the test run has finished. 17060 TrueLog Explorer"s Post Data and Form Data tabs may show incomplete form data if parameter types that require data type conversion (casting) are used for customization. It is recommended to use parameters of data type "string" only for form data customization. 16807 TrueLog Explorer is unable to handle form submissions containing form fields with equal names. Tooltips in the Post Data tab may show incorrect data, value customization may result in customizing a wrong form field. None. 17775 TrueLog Explorer crashes if more than 65k characters are selected in the Rendered tab. None. 10367, 16239, 19992 Visual Script Modifications fail if the related transaction is in an include file. Do not move transactions to bdh files. 4181, 5624 When the JavaScript execution is enabled, certain JavaScript statements inside the HTML contained in a TrueLog may lead to unexpected behavior in the TrueLog Explorer. For example, the JavaScript may close or resize the rendered HTML view in TrueLog Explorer. Disable JavaScript execution (Settings -> Options -> Script execution). 6482, 8085 Certain non-ASCII characters may cause problems when customizing a script with TrueLog Explorer. For example, the HTML token "€" is rendered to the Euro symbol, €. When selecting a text containing such non-ASCII characters and trying to insert a parsing or verification function, the TrueLog Explorer will respond with a message stating that the selected text is not contained in the visible part of the page"s HTML code. If you encounter this behavior, try to exclude such non-ASCII characters from the selection, and try again. None Visual User Data Customization does not work for browser-level scripts. This behavior is by design as TrueLog Explorer only considers forms submitted by WebPageSubmit calls (Page-based Browser-level API), because the HTML form names are required to match HTML and BDL forms. If you want to customize your script using TrueLog Explorer"s Visual User Data Customization feature, you have to have a page-based browser-level API script.
↧