Unsupported product PATROL for Web Transaction and its documentation are no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Limitations of Web Transaction capture

This topic describes the limitations of a Web Transaction capture. 

Related topics

Web-Transaction-Capture-screen-field-descriptions

Capturing-a-Web-Transaction

Adding-authentication-information

Configuring-Web-Transactions-monitoring 

AJAX

AJAX-enabled sites are not supported

Files/Plug-ins

  • Web sites that download content are not supported
    BMC ProactiveNet Web Capture tool does not support transactions that download or upload files such as MS Word documents, spreadsheets, presentation files, PDF files, and ASCII text files.
    For example: http://www.copyright.gov/legislation/dmca.pdf
  • Web sites with Plug-ins are not supported
    The Web Capture tool does not support transactions that involve plug-ins such as Applets, Flash, SVG, and multimedia features.
    For example: www.ebay.com , www.macromedia.com (Flash)

Forms

  • Web sites that reset passwords before a POST are not supported
    Some Web sites clear the password field in a form before doing a POST to the server. In such situations, the Web Capture tool does not record the password.
    Example: www.traderji.com
  • Flash-based Forms are not supported
    This tool does not record data from Flash Forms.
    Example: Search form at www.macromedia.com
  • Form POST is not supported
  • The Web Capture tool does not support pages, which do a POST of values from different forms in the page.
  • The Web Capture tool fails to record the password value when the Password field in a form is reset to an empty string or to a predefined default value before a POST. In such situations, playback and monitor creation fail.
  • This tool does not support forms that do not POST but redirect. Some pages do not POST selected values, but use JavaScript redirection to load the required page. This event may not be recorded by the Web Capture tool.
    Example: www.hsbc.co.in
  • Form Action URLs with dynamic session IDs are not supported
  • The monitor and the Playback tool do not support transactions that have dynamic session ID values as part of the Form action URL.
    Example: www.homedepot.com

Frames

Web sites with Cross-scripting feature are not supported

Due to cross-site scripting (XSS) limitation of Internet Explorer, Web sites that contain frames from a different domain (or a sub-domain) are not recorded.

For example: www.federaldaily.com

Images

  • ImageMaps are not supported
    The Web Capture tool does not support Web sites with ImageMaps. (An Image Map is a list of coordinates relating to a specific image, created in order to hyperlink areas of the image to various destinations)
    Example: http://www.ihip.com/
  • Image tags with OnClick event handlers are not supported
    The Web Capture tool does not record the click event, when the action URL of a form is manipulated and a POST happens in the OnClick event handler of Image tags.
    Example: www.americanairlines.com

Internationalization

  • URLs with internationalized Domain Names are not supported
    The Web Transaction monitor does not support URLs with Internationalized Domain Names (IDN).
    Example: http://www.nestle.com/All_About/All+About+Nestlé.htm
  • Internationalization is not supported in the Attribute pages of the Operations Console
    Attribute pages of the Operations Console do not display Non-English Unicode characters correctly.

For more information on Internationalization support, refer Internationalization Support topic.

JavaScript

  • JavaScript redirection is not supported
    The Web Capture tool does not record JavaScript redirection in Web pages.
  • Suppressing JavaScript Error window
    While recording and playing back a transaction, the Web Capture tool does not suppress JavaScript Error windows that may appear.
    Example: www.perbio.com
  • Transactions with DOM object manipulation not supported
    The Web Capture tool does not support transactions wherein the DOM object of the page is manipulated explicitly in JavaScript functions.
    Example: www.mappoint.msn.com

Log files

Unicode characters not displayed correctly

Web Recorder log files and log files generated by the Validate tool do not display all Unicode characters correctly. Non-English characters may be displayed as '?' or other symbols.

Miscellaneous

  • Pop-up windows with the Close button/hyperlink are not supported
    The Web Capture Tool does not close a pop-up window when the Close button or hyperlink on it is clicked.
    Workaround: Close the pop-up window manually.
  • Monitor plays back blocked pop-up windows
    The Web Transaction monitor does not suppress pop-up windows even if transactions are recorded without selecting the Allow Popups option.
  • Web sites that accept inputs from soft keyboard not supported
    Transactions that require you to specify inputs using a soft keyboard (an on screen keyboard that duplicates the hardware keyboard. One uses the mouse pointer to choose which key/characters to enter) are not recorded.
    Example: www.citibank.co.in
  • URLs with dynamic session IDs are not supported
    The monitor and Playback tool do not support transactions that have dynamic session ID values as part of the URL.
    Example: www.lexus.com
  • Dynamic Page Titles are not supported
  • Page in a site where the title is frequently altered fails in Title Match. Such transactions should be treated as site-specific.
  • Some Web servers change page titles dynamically. In such situations, the Playback tool and Web Transaction monitors fail to match the recorded Title.
    Workaround: Record the transaction without Title Match or edit the transaction file and delete the title of the particular step.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*