Simpler and faster out-of-the-box assets
We know that not everybody has the time and know-how to create complex queries and events. That’s why we’re coming to you with out-of-the-box assets. With Experience Analytics Version (Tealeaf) 10.2, you’ll be able to use predesigned attributes to help with fraud detection, struggle analysis, and more. For more information about this feature and configuration, go to Out-of-the-box events.
Support for the AES cipher for encryption of data
To fulfill the need of hybrid deployment where data within sessions needs to be encrypted, SAPrivacy and SAPrivacyEx now support the AES cipher for encryption of data. An AES encryption key can be generated using SearchConfig.exe or using search server configuration in TMS. In addition, there is a stand-alone tool, keygen.exe, that can be used to generate encryption keys.
Updates to user management
Version 10.2 is introducing changes to user management that make it easier and safer for Tealeaf admins to run the organization. This includes grouping all password-related settings together. These password settings can now be accessed by going to the Modify or Reset password link for each user.
PCA capture and processing improvements
PCA now handles capture and processing of large size compressed data without dropping or corrupting any pages. The following parameters will need to be tuned appropriately in the PCA configuration file ctc-conf.xml:
To handle the large data size on the CX side as well, the MaxDataSize parameter in TealeafCaptureSocket.cfg and Max size per session parameter in canister configuration will also need to be tuned up.
Protect your network and your users
Security is our top priority. That’s why Tealeaf 10.2 includes anti-brute-force measures that protect user accounts from attacks.
- In case of brute-force login attempts the affected accounts will become locked, preventing further logins by this username.
- Locked accounts can be unlocked by the administrator or by the users themselves through an automated verification email.
Read more about this feature: Brute-force lockout measures.
Enabling authentication lockout for your users
- Go to CX Settings > Users and select Authentication lockout. Then, choose Enabled. You can choose whether you want your users to be able to reset their accounts themselves (User self-service reset) or if it has to be done by the administrator (Administrator reset).
- Go to Authentication lockout criteria to choose how many login attempts are allowed before an account is locked out.
Support for replay of Shadow DOM Diff and Shadow DOM Cache Content
In order to take advantage of this feature, you must implement the UI Capture SDK version 6.0.1 or above. After you implement the SDK, complete the following steps.
- On your Portal machine, go to the Tealeaf_Home/Portal/WebApp/js folder. In the replayConfig.js file, set the value for useOverlay to true. Then, reset the IIS.
- Add the captureShadowDOM and shadowDomCacheEnabled properties to the UIC DOM Capture service configuration and set these to true as follows:
Canister storage de-duplication control
You can now control whether software encryption and compression is enabled on a canister-by-canister basis.
If your hardware infrastructure can perform encryption, compression, and data de-duplication, then your software encryption and compression in the canister configuration can be disabled. However, this functionality should only be disabled when there is a hardware solution for data de-duplication in place.
For more information, check out Enabling compression and encryption for Long Term Canister.
- We have migrated Canister Services to 64-bit. This addresses the need to increase the virtual memory limit. Support for the 64-bit Canister session agent and 64-bit pipeline on the Canister machine will be available in future releases.
- BBR Annotations are now called Comments. This feature has been improved in general so it’s easier to note things down.
Note: For customers who are running Tealeaf 10.02 or older, this version combines the features released with version 10.1. For a full overview of those, check out What’s new for Acoustic Experience Analytics (Tealeaf) Version 10.1.
Available training resources
Check out the available training resources below for more details about our newest release.
- Tealeaf 10.2 overview
- New out-of-the-box events
- Improved Canister scalability and compression
- Security enhancements
- Replay enhancements
- Session retention
Known issues and limitations
Extending midnight session expiration dates
There is a border condition where sessions recorded shortly before midnight get saved in the LSSN for the following day. For example, a session recorded on January 1 gets stored in the LSSN for January 2. Tealeaf calculates session expiration dates based on the session date. That’s why, when Tealeaf shows that the session expires in less than one day, for some sessions this might mean that the expiration date is already in the past. In this case, when you want to extend the session by one day, you will see the session expiration date as less than one day. If you want to extend such a session by one day, you will need to extend it by two days instead.
TealeafST1 / TealeafST2 stats pipelines don't show any hits processed
If TealeafST1 and / or TealeafST2 stats pipeline don't show any hit count, then restart the transport service on that machine and wait a couple of minutes. Repeat this step if hit flow is not observed in the stats pipeline.
Error in Report Builder
You might see an error if you access the Report Builder immediately after upgrading. To make sure you don’t experience this issue, wait for few minutes before accessing the Report Builder. Otherwise, restart Tealeaf Data Service.
Session replay navigation not showing
Sometimes, the navigation for a session replay might not display when you start to replay a session. It should show up correctly once you finish replaying that session.
DOMDiff session error
On restart of Replay service, sometimes DOMDiff sever is not started. As a result, during replay of DOMDiff session, error 12029 occurs. You can restart the Tealeaf Replay server service from the Windows services list to fix the error.