Ibm Tealeaf Ui Capture: Ibm Tealeaf Ui Capture Release Notes

Transcript

IBM Tealeaf Version 5 Release 2.0 November 2016 UI Capture Release Notes IBM Note Before using this information and the product it supports, read the information in “Notices” on page 13. This edition applies to version 5, release 2, modification 0 of IBM Tealeaf UI Capture and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1999, 2016. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents UI Capture Release Notes . . . . . . . 1 New features New features New features New features New features Version 3.1.0 Version 3.0.1 Version 3.0.0 and changes in 5.2.0 and changes in 5.1.0 and changes in 5.0. and changes in 4.1. and changes in 4.0. . . . . . . . . . . . . . . . . . . . . . © Copyright IBM Corp. 1999, 2016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 4 4 5 6 7 8 Version 2.1.0 Version 2.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . IBM Tealeaf documentation and help . 8 . 9 11 Notices . . . . . . . . . . . . . . 13 Trademarks . . . . . . . Privacy Policy Considerations . . . . . . . . . . . . . . 14 . 15 iii iv IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes UI Capture Release Notes These release notes pertain to version 5.2.0 of the IBM Tealeaf UI Capture SDK. New features and changes in 5.2.0 The UI Capture version 5.2.0 library includes the following new features, bug fixes, and improvements. New features v New enhancement to privacy handling for non-standard controls using the blockedElements configuration setting. UI Capture enables the blocking and masking of user input data by element ID, name, and xpath. Masks can be expressed as an explicit string, replacements for character types, or custom functions. Use the blockedElements configuration setting in the Core configuration file to define a set of elements for which no user interaction is to be reported. v Privacy masking is extended to select list controls. When a select list control is included in the privacy masking rules; all properties, except for the value property, are removed from the control state that is recorded in the type 4 message. The value property is masked in accordance with the privacy rule. v New TLCookie module. The TLCookie module is required for SaaS deployments and can be configured through the Configuration wizard or by modifying defaultconfiguration.js. The TLCookie module is used to record cookie values for each screenview load that occurs. v New TLT.getLibraryVersion API call. The TLT.getLibraryVersion API call can be used to return the version number of the UI Capture library. It is recommended to use the latest version of the UI Capture library with your applications. v New support for regex matching of screenview names in DOM Capture load and unload triggers. Bug fixes and improvements v Improvement to inactivity timeout. The inactivity timeout setting stops recording user interactions for a page after specified amount of user inactivity on the page. The orientationchange event is now excluded from the event types that are reset by the inactivity timer. The orientationchange event is not reset because the mobile device might report an orientationchange event when the user is not deliberately interacting with the application. For example, the orientation of the mobile device might change while it is stored inside a pocket, bag, or carrier. v URL parsing for type 2 screenview messages now detects semicolons (;) as a query string separator. v Added the domain property to the webEnvironment section. v Added the url, host and charset properties for frame snapshots in the type 12 DOM Capture messages. © Copyright IBM Corp. 1999, 2016 1 v Improved automatic screenview logging by detecting URL path and hash changes even when there is no hash change event. TLT.logScreenviewLoad and TLT.logScreenviewUnload are used to log nested screenview messages. v Improved handling of erroneous viewport values from the Google Search Appliance (GSA). v Normalized tlType property values for submit, reset, image, and other input element types. v Changed the TLTSID cookie value to only contain uppercase characters. v Fixed a bug which prevented successful DOM Capture and replay of textarea elements. v Fixed a bug in the cxOverstat module which was causing erroneous counts for hover events. v Fixed a bug which provided incorrect checkbox state in type 12 DOM capture messages on Internet Explorer 10. v Fixed a bug where privacy rules containing CSS selectors would not get applied to elements in child frames and iframes. v Fixed an edge case where the screenviewOffset would be incorrect for type 2 screenview unload messages. v Fixed the tlType property values for type 9 messages. v Fixed a bug when applying privacy mask type 3 to the period (.) character. v Fixed a bug in the jQuery version check. v Fixed a bug in the PHP target page to use CONTENT_LENGTH instead of HTTP_CONTENT_LENGTH. v Removed debug and MD5 functions that are no longer used from the target page examples. v Added a X-Tealeaf-syncXHR request header which allows the recipient to differentiate between synchronous and asynchronous requests (XHR) that are handled by the Queue service. v Diagnostic logging related to XHR can be enabled by setting the xhrLogging setting in the queue service configuration. The log data is appended to the JSON. The log data is used by IBM technical support for troubleshooting. Do not change the xhrLogging setting without contacting IBM technical support first. New features and changes in 5.1.0 The UI Capture version 5.1.0 library includes the following new features, bug fixes, and improvements. New features v New check endpoint setting. When enabled, the configured endpoint is sent a test request after each page load to verify that the service is available. The test request can be identified by the presence of the X-Tealeaf-EndpointCheck HTTP request header. If a timeout occurs, the UI Capture library shuts own and no session data for the page is sent to the collector. This feature can be used as a safety check when the endpoint is hosted cross-domain. Note: The check endpoint setting should be enabled for use with IBM Tealeaf Customer Experience on Cloud. v New threshold setting for DOM Diff mutations. 2 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes The DOM Diff service captures and processes the changes in a screenview that occur when a user interacts with a page. Processing the changes is often faster than performing a full DOM capture of a page on each user interaction. For example, on a page that dynamically displays content in response to the user interaction by toggling the CSS properties of the elements, only the CSS style attribute changes are captured as part of the DOM Diff enabled capture. Without DOM Diff enabled, the entire HTML content of the page would be captured. Depending on the application, there could be a high number of DOM differences to capture. Processing all of the DOM differences into one capture can decrease application performance. The number of mutations that were processed by the UI Capture SDK are indicated in the mutationCount property of the type 12 DOM Capture message. It is recommended to set a threshold for the maximum number of DOM Diff mutations to capture. If the threshold is exceeded, the UI Capture SDK ignores the DOM mutations and performs a full DOM Capture for the page. When the UI Capture SDK reverts to the full DOM Capture, the forced property is added to the type 12 DOM Capture message. The UI Capture SDK automatically switches back to capturing DOM Diffs for subsequent triggers. v The UI Capture now supports the ability to enable full a full DOM capture for a specific target while DOM Diff is enabled. v New inactivity timeout setting. After initialization, the UI Capture library records user interactions that occur in a page until the page unloads or the browser is closed by the user. If there is an extended period of inactivity where no user interactions are observed, the library ends the recording. Terminating the recording prevents later POST requests (UI hits) of the library from creating one-hit or orphaned sessions. The termination also prevents any interference or accidental activation of the keep-alive behavior within an application. v New useCapture setting. Added a useCapture setting to the browser service configuration which enables the use of capture mode for listening to DOM events. The useCapture setting is enabled by default. When disabled or if the browser does not support event capture; then, event bubbling is used. Some events might be missed if the application is preventing the events from bubbling. For more information about event capture and bubbling, see the W3C DOM specification at https://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-flow. Bug fixes and improvements v Removed the feature that allows the dynamic loading of module scripts and SizzleJS due to potential security vulnerability. v Fixed an issue where ClientState type 1 messages are not reported for the Opera Mini browser. v The viewPortHeight property of the ClientState message is now limited to a positive range of values between 0 - 10000. Any values outside this range are not reported. v Explicit definition of the TLT object to ensure it is accessible in the global scope. v Improvements to click-event message ordering in relation to screenview messages in certain cases. UI Capture Release Notes 3 New features and changes in 5.0 The 5.0 release contains updates to the DOM Capture feature, extra configuration for Tealeaf® SaaS, and modifications and additions to the JSON messages that are generated by the SDK. New features v The DOM Capture feature was enhanced to incorporate DOM Diff functions. DOM Diff is enabled by default. When enabled, the first DOM Capture of the page is a full snapshot and subsequent DOM Captures capture only the differences from the previous snapshot. v For Tealeaf SaaS: – A cookie module was added to the configuration so that cookies can be configured based on how Tealeaf SaaS handles sessionization for the application. – Configuration options were added to test the target page at SDK initialization. You can configure the SDK to send an async test and configure a time to wait for a response back from the target page before the SDK shuts down. v The JSON messages that are affected include: – Type 1 (Client Environment) - the definitions for orientation, width, height, deviceWidth, and deviceHeight were updated. – Type 11 (Gestures) - scrollX and scrollY fields were added. – Type 12 (DOM Capture) - now shows the changes in a page to support the DOM diff service. New features and changes in 4.1 New features v The documentation was updated and modified for use in the IBM® Knowledge Center. With the IBM Knowledge Center documentation, the user can: – Search across all of the Tealeaf documents and across all IBM product documentation – Create collections of specific topics that they use frequently – Create pdf documentation of the collections they create v IBM Tealeaf UI Capture now has the means to capture geolocation information on the user's device. The application programmer must ask for user's permission to collect the geolocation data. The information can be collected automatically when the application starts. Geolocation information can be manually collected as specific points in the application with the geolocation API. Changes v JSON messages were added for geolocation capture events. There are now 13 JSON message types supported. The message added to the documentation in this release is: – Type 13: Geolocation - Geolocation information. If the user does not give permission to collect geolocation data, a geolocation type 13 error message is sent. v Custom events can now be used as triggers for DOM capture. v DOM Capture can now be delayed until the frames finish loading. 4 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes New features and changes in 4.0 This section describes the new features and changes that are introduced in version 4.0 of IBM TealeafUI Capture. New features v DOM Capture is now an option for hybrid applications. DOM Capture relies on the Document Object Model (DOM), which provides a structured representation of the web page (document). The DOM Capture Service captures a "snapshot" of the rendered DOM. The Configuration Wizard has been modified to configure basic DOM settings for hybrid applications. v IBM Tealeaf UI Capture now has the means to capture gestures the user makes on a mobile application. The gestures that are captured include: – Tap – Tap and hold – Double tap – Swipe vertically – Swipe horizontally – Pinch open – Pinch close Changes v The hybrid bridge has been expanded so that Native iOS and Native Android APIs are now accessible from the UI Capture JavaScript. The android APIs that are available to JavaScript are: – Enable Tealeaf Framework – Disable Tealeaf Framework – Log Screen Capture – Start New Tealeaf Session – Current® Session ID – Default Value for Configurable Item – Value for Configurable Item – Set Configurable Item – Add Additional HTTP Header – Log Custom Event Bridge The iOS TLFApplicationHelper APIs that are available to JavaScript are: – -(void)enableTealeafFramework; – -(void)disableTealeafFramework; – -(void)requestManualServerPost; – -(BOOL)startNewTLFSession; – -(NSString*)currentSessionId; – -(BOOL)setConfigurableItem:(NSString*)configItem value:(id)value; – -(id)valueForConfigurableItem:(NSString*)configItem; – -(id)defaultValueForConfigurableItem:(NSString*)configItem; – -(void) addAdditionalHttpHeader:(NSString*)value forName:(NSString*)name; The iOS TLFCustomEvent APIs that are available to JavaScript are: – - (BOOL)logEvent:(NSString*)eventName; UI Capture Release Notes 5 – - (BOOL)logEvent:(NSString*)eventName values:(NSDictionary*)values; – - (BOOL)logPrintScreenEvent; v DOM Capture is now an option for hybrid applications. DOM Capture relies on the Document Object Model (DOM), which provides a structured representation of the web page (document). The DOM Capture Service captures a "snapshot" of the rendered DOM. The Configuration Wizard has been modified to configure basic DOM settings for hybrid applications. v JSON messages were added for gesture capture and DOM capture events. All of the message types from 9.0 were updated to include the message type number. The complete list of messages is: – Type 1: Client State - Current state of client. – Type 2: Application Context - Message to indicate divisions in application view which could be current page/view/activity user is on. – Type 3: Connection - Any request/response application performs during capture. – Type 4: Control - User interface control that fires an event we listen to capture. – Type 5: Custom Event - Any custom log event from any place in application. – Type 6: Exception - Any exception application can throw. – Type 7: Performance - Performance data from a browser. – Type 8: Web Storage - An object containing information about local storage information on the browser. – Type 9: Overstat® Hover Event - An object containing information about mouse hover and hover-to-click activity. – Type 10: Layout - Current display layout of native page. – Type 11: Gesture - Gesture that fires a higher touch event Tealeaf listens to and captures. – Type 12: DOM Capture - An object containing serialized HTML data (DOM snapshot) of the page. Version 3.1.0 New features This section describes the new features and changes that are introduced in version 3.1.0 of IBM TealeafUI Capture. v Two new APIs were added to the UI Capture library. TLT.logScreenCapture instructs the underlying native functionality to take a screen capture. TLT.registerBridgeCallbacks is used to register callback functions, which are invoked by the UI Capture library in specific instances. This API supports messageRedirect, screeCapture, and addRequestHeaders callbacks. The messageRedirect callback can be registered to redirect and intercept messages from UI Capture. The screeCapture callback can be registered to enable a JavaScript API to allow a screen capture to be taken. The addRequestHeaders callback can be registered to enable a third-party JavaScript to return custom HTTP headers that need to be set on the UI Capture libraries POST request. v In the development builds of the library, several APIs now throw exceptions and log the exception to the console when the library is not initiated for API calls that depend on the library. In production builds of the library, the API call fails silently if the library was not initialized. The following APIs throw this exception in development builds. 6 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes – getSessionData – logCustomEvent – logExceptionEvent – logScreenviewLoad – logScreenviewUnload – logScreenCapture v The UI Capture configuration wizard contains several new options. – In the Browser Service Configuration step, Internet Explorer Excluded Links option is added to handle beforeunload in Internet Explorer. – You can Enable asynchronous XHR on page unload to turn on asynchronous requests during page unload in the Queue Service Configuration step. – Remove Target and Remove Privacy Configuration are added to remove a single target or privacy configuration when you configure multiple privacy masks in the Message Service Configuration step. – In the Modules step, you can now add custom replay events in the Modules step. You can also enable the overstat module. The overstat module adds mouseout, mousemove, and click overstat events to your configuration. v Cross-domain communication is added to send UI Capture POST request to a different server than the parent page. Known issues v Incorrect orientation values may be reported on certain Android devices. This issue occurs because the devices themselves report non-standard values for portrait and landscape modes. v Pinch open & close is not reported on the Android platform. Bug fixes and improvements v Fixed jQuery version check for jQuery 1.10 and above. v An exception was thrown if multiple copies of the UI Capture were detected. v Fixed the reporting of width, height, and scale values for Android Chrome. v The navigationStart property in the performance timing object returns the absolute time stamp value instead of 0. v Any leading or trailing white space is trimmed from InnerText values of link elements. v Module events are not subscribed to if the module is not enabled. v Fixed a bug in the relXY positioning calculation by correctly factoring the elements scroll position. v JSON message version was updated to 3.0.0.0 to reflect additions that were made to the JSON format in the IBM Tealeaf 9.0 release. Version 3.0.1 Bug fixes and improvements v A bug was fixed so that frames blacklist works for CSS class based selectors. v Conditional comments were replaced with user agent check (MSIE) and document mode detection. v A close button was added for the Regex Tester in the Configuration Wizard. v The timer interval for flushing the queue is now set to 5 minutes in the default configuration. UI Capture Release Notes 7 Version 3.0.0 New features This section describes the new features and changes introduced in the 8.8 version of IBM TealeafUI Capture. v Added a new module, Overstat, that tracks two new events; hover duration and hover to click time. v Added event delegation support for jQuery flavor of UI Capture. v Added support for cross-domain POSTs. Bug fixes and improvements v Added a host property to the screenview message that now contains the URL scheme and host. v Check for exceptions when unregistering handlers since the target may no longer be valid in some cases. v Library configuration object supports specifying window and document objects as strings (for example, target: "document") v The Configuration Wizard was fixed so the masking function value is displayed and not the function ID. v Certain cases of user input not being updated in the Configuration Wizard when using Firefox were fixed. v Clean up frame-related resources and events after a frame reloads. v Made improvements to the xpath algorithm. v UI Capture was fixed so that it does not send an empty performance object on legacy Internet Explorer when calculateRenderTime is disabled. v Added help text for Performance settings and Replay Events under Advanced Options on the Modules page of the Configuration Wizard. v Allow privacy masking functions to be specified the same way that we allow JSON parser, stringifier, and jQuery Sizzle configuration. v Set tlType to month for HTML5 input element of type=month. Because HTML5 elements are not uniformly supported across all browsers, this fix only works for browsers that have underlying support for this element. v Ensure that messages get flushed in the right order when screenview load and unload are used. v The Configuration Wizard displays the UIC version string. v The queue service was modified so that serialization for native bridge uses the serializer service abstraction instead of the global JSON object. Version 2.1.0 New features v A new public API was implemented, TLT.getSessionData(), that returns the Tealeaf Session id information in JSON format. v Support was added for blacklisting frames. v Support was added for render time on legacy browsers that do not implement the W3C Navigation Timing API. In such cases, the library can optionally calculate render time based on the difference between the library load and page load. 8 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes Bug fixes v Changes were made to TLT.init logic to improve performance on load. v Made performance improvements to the xpath algorithm. v Legacy Internet Explorer (and IE9 in quirks mode) access denied issue when document domain is changed were fixed. v window.JSON calls were replaced with the serializer service abstraction. The JSON stringifier and parser are now configurable. Use of the built-in stringifier and parser is configurable. v Made performance improvements to the getBoundingClientRect algorithm. v Fixes implemented to the same origin detection for frames support and multi-level frame support. v jQuery is no longer assumed to be in the global scope. The configuration is used to specify the jQuery location. v Performance improvement to break out of the privacy processing loop once a privacy match is found. For targets that are configured multiple times in the privacy configuration, only the privacy mask that is specified for the first match s applied. v When the initial focus time on a target element is missing, the default dwell time is set to 0 instead of the timestamp. v Fixed XHR when using Microsoft ActiveX object. v Check for negative values of the selectedIndex for cases when the select list is empty. v Removed contenteditablefrom the target selector in the Configuration Wizard and the default configuration. For websites using HTML5 elements with contenteditable attributes, this must be configured manually. v If the target element's value is empty, the masked value is empty irrespective of the mask type (empty, basic, or type). v sizzleURL must be configured explicitly and is no longer included in the configuration by default. v Prioritize use of Sizzle engine over jQuery when available. jQuery detection logic checks for jQueryObject specified in the configuration before assuming jQuery in global scope. Location of the Sizzle engine is now configurable. The library checks for sizzleObject in the configuration before assuming Sizzle in the global scope. Version 2.0.4 First release. UI Capture Release Notes 9 10 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes IBM Tealeaf documentation and help IBM Tealeaf provides documentation and help for users, developers, and administrators. Viewing product documentation All IBM Tealeaf product documentation is available at the following website: https://tealeaf.support.ibmcloud.com/ Use the information in the following table to view the product documentation for IBM Tealeaf: Table 1. Getting help To view... Do this... Product documentation On the IBM Tealeaf portal, go to ? > Product Documentation. IBM Tealeaf Knowledge Center On the IBM Tealeaf portal, go to ? > Product Documentation and select IBM Tealeaf Customer Experience in the ExperienceOne Knowledge Center. Help for a page on the IBM Tealeaf Portal On the IBM Tealeaf portal, go to ? > Help for This Page. Help for IBM Tealeaf CX PCA On the IBM Tealeaf CX PCA web interface, select Guide to access the IBM Tealeaf CX PCA Manual. Available documents for IBM Tealeaf products The following table is a list of available documents for all IBM Tealeaf products: Table 2. Available documentation for IBM Tealeaf products. IBM Tealeaf products Available documents IBM Tealeaf CX v IBM Tealeaf Customer Experience Overview Guide v IBM Tealeaf CX Client Framework Data Integration Guide v IBM Tealeaf CX Configuration Manual v IBM Tealeaf CX Cookie Injector Manual v IBM Tealeaf CX Databases Guide v IBM Tealeaf CX Event Manager Manual v IBM Tealeaf CX Glossary v IBM Tealeaf CX Installation Manual v IBM Tealeaf CX PCA Manual v IBM Tealeaf CX PCA Release Notes © Copyright IBM Corp. 1999, 2016 11 Table 2. Available documentation for IBM Tealeaf products (continued). IBM Tealeaf products Available documents IBM Tealeaf CX v IBM Tealeaf CX RealiTea Viewer Client Side Capture Manual v IBM Tealeaf CX RealiTea Viewer User Manual v IBM Tealeaf CX Release Notes v IBM Tealeaf CX Release Upgrade Manual v IBM Tealeaf CX Support Troubleshooting FAQ v IBM Tealeaf CX Troubleshooting Guide v IBM Tealeaf CX UI Capture j2 Guide v IBM Tealeaf CX UI Capture j2 Release Notes IBM Tealeaf cxImpact v IBM Tealeaf cxImpact Administration Manual v IBM Tealeaf cxImpact User Manual v IBM Tealeaf cxImpact Reporting Guide IBM Tealeaf cxConnect v IBM Tealeaf cxConnect for Data Analysis Administration Manual v IBM Tealeaf cxConnect for Voice of Customer Administration Manual v IBM Tealeaf cxConnect for Web Analytics Administration Manual IBM Tealeaf cxOverstat IBM Tealeaf cxOverstat User Manual IBM Tealeaf cxReveal v IBM Tealeaf cxReveal Administration Manual v IBM Tealeaf cxReveal API Guide v IBM Tealeaf cxReveal User Manual IBM Tealeaf cxVerify v IBM Tealeaf cxVerify Installation Guide v IBM Tealeaf cxVerify User's Guide IBM Tealeaf cxView IBM Tealeaf cxView User's Guide IBM Tealeaf CX Mobile v IBM Tealeaf CX Mobile Android Logging Framework Guide v IBM Tealeaf Android Logging Framework Release Notes v IBM Tealeaf CX Mobile Administration Manual v IBM Tealeaf CX Mobile User Manual v IBM Tealeaf CX Mobile iOS Logging Framework Guide v IBM Tealeaf iOS Logging Framework Release Notes 12 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: © Copyright IBM Corp. 1999, 2016 13 IBM Bay Area Lab 1001 E Hillsdale Boulevard Foster City, California 94404 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Trademarks IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. 14 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes Privacy Policy Considerations IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. A cookie is a piece of data that a web site can send to your browser, which may then be stored on your computer as a tag that identifies your computer. In many cases, no personal information is collected by these cookies. If a Software Offering you are using enables you to collect personal information through cookies and similar technologies, we inform you about the specifics below. Depending upon the configurations deployed, this Software Offering may use session and persistent cookies that collect each user's user name, and other personal information for purposes of session management, enhanced user usability, or other usage tracking or functional purposes. These cookies can be disabled, but disabling them will also eliminate the functionality they enable. Various jurisdictions regulate the collection of personal information through cookies and similar technologies. If the configurations deployed for this Software Offering provide you as customer the ability to collect personal information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for providing notice and consent where appropriate. IBM requires that Clients (1) provide a clear and conspicuous link to Customer's website terms of use (e.g. privacy policy) which includes a link to IBM's and Client's data collection and use practices, (2) notify that cookies and clear gifs/web beacons are being placed on the visitor's computer by IBM on the Client's behalf along with an explanation of the purpose of such technology, and (3) to the extent required by law, obtain consent from website visitors prior to the placement of cookies and clear gifs/web beacons placed by Client or IBM on Client's behalf on website visitor's devices For more information about the use of various technologies, including cookies, for these purposes, See IBM's Online Privacy Statement at: http://www.ibm.com/ privacy/details/us/en section entitled "Cookies, Web Beacons and Other Technologies." Notices 15 16 IBM Tealeaf UI Capture: IBM Tealeaf UI Capture Release Notes IBM® Printed in USA