Integration of Tealeaf with ForeSee Results

When survey is completed and submitted, ForeSee must first receive and store the Tealeaf® Session ID as part of the survey. As part of the integration the following information must be provided to ForeSee Results to be configured at their end for Tealeaf integration. The actual integration is done by ForeSee support engineer as the configuration elements are not exposed through the dashboard.

About this task

Note: No additional programming tasks are required for ForeSee Results to display a Replay Session link in the online dashboard list of surveys.

Procedure

  1. The name of the session cookie ? normally this is the Tealeaf Session ID used to track session activity for Tealeaf capture. (identified by ?TLTSID? cookie).
  2. The Portal replay link URL ? this is the link to the Tealeaf Portal replay. Typically the link would look like the following:
    http://%(tleaf_hostname)/%(tleaf_servicename)/cxConnect.asmx/
    GetSessionReplayLink?
    SessionType=3&LinkType=1&Field=1&Value=<TLTSID_Value>&SessionDate=
    &SessionPreference=3
    &Redirect=TRUE
    

Results

  • The tleaf_hostname and tleaf_servicename must be replaced with the actual Portal and webservice URL, respectively.
  • The TLTSID_Value is replaced with the actual value by ForeSee Results when the survey replay link is constructed in the dashboard.
    Note: Tealeaf recommends thoroughly testing the Portal replay link URL to ensure accuracy before providing it to ForeSee. A stored session's sessionID can be used for the TLTSID_Value.
Note: URLs referring to Portal.asmx are also accepted. These legacy URLs are automatically remapped to use cxConnect.asmx, which is the preferred standard for this integration method. See cxConnect Integration through replay links.

In the table below, you can review the URL parameter, its corresponding name, and a description. Values listed in the description correspond to the values generated by ForeSee Results, which are converted to string values before execution by the Tealeaf Portal Server.

Table 1. Integration of Tealeaf with ForeSee Results
Parameter Name Description
Tleaf_hostname Tealeaf Host Name The hostname of the Tealeaf replay server the client is running locally.
Tleaf_servicename Tealeaf Service Name The publishing point of a particular replay instance. Some clients have multiple Service Names for multiple websites within their Tealeaf application.
Location Location Variable indicates the type of session. ForeSee generates links for completed sessions only; this value is always set to 2. This parameter is referred elsewhere as SessionType.
LinkType LinkType The type of link to generate:
  • 1 = RTV
  • 2 = BBR
Field Tealeaf Field ID Required variable for Tealeaf to identify the Tealeaf field from the generated URL above.
Value Custom Variable Value The identifier that is used to locate the Tealeaf session.
MD5 MD5 When set to true, the query uses the MD5 of the custom_var value. For example, no TLTSID is generated, yet the LoginID value is available.
SessionDate Tealeaf Session Date The date of the Survey form submission. Since the datetime stamp must be in GMT, it is recommended for now to leave this field blank to cover all available dates in the Portal.
SessionPreference Tealeaf Session Preference If the Field value corresponds to multiple sessions, this value identifies the preference of which session to select:
  • 1 = earliest
  • 2 = latest
  • 3 = any (default)
  • 4 = closest
Redirect Redirect Status Set the value to 1 to create a live link to the replay session.