Every text page that makes up a whole or (in the case of framed pages) partial user impression almost always makes more calls for other, external files.

These external files, called static content can be images, graphics, fonts, style sheets, javascript, and more. They are generally not captured by cxImpact, as they would expand the data volume of the captured sessions with duplicate data.

The static content often defines most of the visual elements that are seen by the visitor.

• To re-create the user impression, RTV must have access to all files requested by the page.
• While most Tealeaf solutions reference the website from which to fetch these files, your system can be configured to fetch files from a database.
• If static content is unavailable, RTV renders the page to the best of its ability. Some pages are displayed with minor style differences when static content is not available, while others that depend on external script files can be blank.

Depending on the capture mode, availability of static files can vary:

BusinessIT capture with DataDrop: Most Tealeaf systems are configured to operate in the BusinessIT capture mode, coupled with DataDrop rules to eliminate successful static file Requests. Requests for static files that were successfully filled by the web server are not stored. Only Requests for static files associated with errors such as StatusCode 404 or StatusCode 500 are available.

BusinessIT capture without DataDrop: In the BusinessIT capture mode without DataDrop, every Request is stored. Since this configuration greatly increases the volume of stored data, it should be used only as a temporary debugging aid. For example, an RTV user can enable this capture mode to recreate a stored session for greater detail and then re-enable DataDrop.

You can review the source information of every file that is requested by a viewable page. For each selected page, you can see the external files that are requested by RTV as required for the successful replay of the page.