Release 2.0.0 (2020-09-11)
  • 09 Sep 2020
  • 3 Minutes to read
  • Contributors
  • Dark
  • PDF

Release 2.0.0 (2020-09-11)

  • Dark
  • PDF

Release 2.0.0 (2020-09-11)

Fix: Remove insecure eval() function

Update code to remove security risk with eval() function (Issue 1091)
This update replaces code reliant on the eval() function to interpret plugin configuration options from the Add-in lists with a secure alternative.

Fix: Correct tracking of Single Page App transitions

Update code to alway fire hits with the navigatedEvent callback (Issue 1155, issue 1360)
Modern view uses SPA behavior and a callback function to trigger new "page view" events in some cases. This update corrects an issue where some nagivatedEvent callbacks were ignored due to trying to reference a deprecated property to detect the page URL. The new logic fires an event regardless of the page URL to ensure consistent behavior.

Enhancement: Improve App Extension and Tag Load Time/Performance

Update code to queries configuration lists in parallel to speed up load time (Issue 1434)
Previously the extension would query the 3 configuration lists and the webtrends.js in sequence which resulted in long load times (upwards of ~10 seconds in Chrome) for the extension that could allow lost page view and link click hits if the user left the page before the extension loaded. This update calls the 3 configurations lists in parallel, and includes the webtrends.js as part of the package, greatly reducing the time it takes to send the initial page view hit to as low as ~4 seconds in Chrome, and as low as ~2 seconds when viewing a second page on the same site.

Enhancement: Add tracking of Hub Site Navigation Mega Menu (SPO)

Update code to support tracking of Hub Site Mega Menus (Issue 407)
SharePoint Online modern sites allow a Hub Site Mega Menu to be used across connected sites. This update adds WT.menu_type=Site to distinguish between Hub (SPO only) and Site (SPO & SP2019) nav menus and updates WT.mega_menu to provide the hierarchy of the menu item on a click event.

Fix: Correct Mega Menu Hierarchy in Modern view

Update code to track latest HTML hierachy of site mega menu (Issue 656)
HTML of SPO Modern site Mega Menus changed and existing code was no longer properly tracking the full hierarchy of a click in WT.mega_menu. We now collect the proper hierarchy in classic and modern, and in the cascading or mega menu layouts.

Fix: Normalize Encrypted user properties

Update code to ensure user properties for session tracking are consistently formatted prior (Issue 974)
The DCS.dcsaut and WT.dcsvid parameter values are copied from another specified parameter. Depending on the property, it's possible for this value to be upper or lower case, or a mixture of the two. The analysis engine sees different cases as different user values. This update converts the value to lower case to ensure it is consistent in the log data to properly identify a unique user.

Fix: Correct intermittent unencrypted user data

Update code to wait longer for the encryption file and to not send user properties if not received (Issue 1303)
In rare cases a user's internet connection may be so slow that the encryption JS file is not delivered within the timeout period. This sometimes resulted in unecrypted user data being sent. We now wait longer for the file to deliver, and if the file is not delivered in time, all iuser parameters specified for obfuscation are removed from that hit entirely.

Fix: Correct actions on Documents in modern Sub Folders passing incorrect URL

Update code to properly retrieve the URL of a document(s) when in a library sub folder (Issue 1351)
In some environments the code was not properly detecting required elements, and as a result was passing the currently library page URL as a document URL rather than the real URL found in the query string. This update ensures that the real URL is properly retreived from the page URL parameter even if the required elements are missing.

Fix: Do not strip non ascii characters from file names and links

Update code to allow non-ascii characters to be sent for document, link title, and URLs (Issue 1444)
Non-ascii characters were previously stripped to improve detection of some interactions, in particular Command Bar actions in document libraries. Some customers found that this caused issues trying to find the correct document name in reports. This update restores non-ascii characters for the reports