Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The January 2018 Kitewheel release brings together several streams of work that we have been performing on the back end and the underlying user interface technology. A lot of these changes have no immediate noticeable user interface impact but set us up well for what is coming in future releases. 

...

Kitewheel now enforces a stricter password policy than it did before. All passwords in Kitewheel must now meet the following requirements: 

  • At least 8 characters - though we would encourage longer ones if possible - up to a maximum of 50 characters 
  • Contain one lower case letter, contain one upper case letter, one digit and one of the characters: !@#$%^&*
  • Can not be a password that has been used in the five previous passwords

Password Expiry 

Passwords will now expire after 90 days and you will be asked to choose a new password when you log in: 

...

The Acquia Lift Node now supports a Visitor Query action. 

The Acquia Lift Connection should be set up as described here.
There are three parts to the Acquia Lift Visitor Query, the identifier, identifier_type, and person_tables. These need to be filled in by parameters or by literals depending on the project needs. The identifier is value of what will be looked up (for example a specific email address). The identifier_type is what kind of value is being looked up in the table (for example 'email' or 'tracking'). The person_tables is the table that will be searched for the value (for example 'identifiers' or 'event').

With these parameters filled in the Visitor Query will do a lookup on person_tables for the identifier value searching through identifier_type. This node will return an object with the name equal to identifier_type with an array of all the rows of data it found matching the identifier in the table. 

Bug Fixes

  • [KIT-1043] - Deployed Graph Log Shows Old Error Messages
  • [KIT-1070] - Improve and Impose Password Policy
  • [KIT-1093] - Change noConflict label in webtracking to be called "JQuery noConflict"
  • [KIT-1135] - Trace data display in visual testing assumes certain prototype/template ids to exist
  • [KIT-1136] - Security High: nginx Integer Overflow - identified by penetration scan and fixed
  • [KIT-1137] - Security High: Cross-Site Scripting - identified by penetration scan and fixed
  • [KIT-1143] - Metadata Expansion Tag is in front of the hover text for schema actions
  • [KIT-1160] - AWS Secret Key should be treated as a password and starred out 
  • [KIT-1172] - Graphs lose data source in parameters when hydrated from Graph Template
  • [KIT-1179] - Custom LESS not appearing on OEM grand child orgs
  • [KIT-1182] - Child Organisations do not see search filter on the home screen
  • [KIT-1192] - Engine Trace Logging Causes Engine Failure
  • [KIT-1213] - Update Webtrack options spelling for JQuery

...