There are a set of new features and bug fixes in this release. The highlights are:
The error message system of the Kitewheel Engine has been changed so that all errors that are returned have a unique and diagnosable error code.
Kitewheel previously had two partner levels identifiable in the software. These different levels provided different feature sets for the level of partnership. With this release, Kitewheel has created a new OEM (Original Equipment Manufacturer) level of partnership that provides significant white-label capabilities for the Kitewheel Hub. Depending on the level of partnership for your organization, different features and levels of customization are available.
This means that some new features which are referenced in the documentation will only be accessible to particular partner types.
Partnership Type | |||
|---|---|---|---|
Capability | Agency | Strategic | OEM |
| Access to Hub | |||
| Connector Library | |||
| Graph API | |||
| Use Managed Graphs | |||
| Customizable URL | |||
| Interface Rebranding | |||
| Single Sign On | |||
| Child Organizations | |||
| Provisioning API | |||
| Publish Managed Graphs | |||
| Custom Documentation | |||
| 1st & 2nd Level Support |
| ||
| 24x7 Support | |||
if you are interested in changing your partnership level please speak to your Kitewheel account manager.
Graphs can now have parameters that allow schema values to be passed in to the graph when calling the parameterised graph as a sub-graph.
A graph can only have a Listener or Parameters - it can not have both.
Managed graphs are a new type of "shareable" graph that allows full graphs to be published and used by other hub users without having to hydrate the whole graph. The update of the managed graph is controlled centrally by the publisher. The user of the graph can not see the contents of the managed graph.
This means that Kitewheel has two means of sharing useful and reusable graph content:
The ability to publish managed graphs is currently an OEM partnership level capabiltity - this may change in a future release of the Kitewheel hub. Any user can use a Managed Graph that is available to them.
Kitewheel now supports the Azure Service Bus queue connection type. The queue provides the standard Read, Write, and Listen functionality as with all of the other queue connection types.
Kitewheel now has a provisioning API that allows the creation, update, and deletion of Organizations, Users, and Projects. This is an OEM Partnership level feature. The documentation is in the restricted section of the library.
Kitewheel now provides single sign-On capabilities for Acquia Lift customers. This is an OEM Partnership level feature. Kitewheel is evaluating other single sign-on capabilities for future releases.
Kitewheel has made an improvement to the web tracking JavaScript.
There is now an option to allow the specification of the domain on which the KItewheel cookie will be registered. This simplifies cross-site tracking for sub-domains. Normally, the Kitewheel web tracking cookie "kwcookie" would be set on the full domain of the site on which it was loaded. The option now allows you to specify the domain on which the cookie will be set. If the Kitewheel tracking JavaScript is unable to set the cookie on the specified domain, then it will revert to the original behaviour.
The option is enabled by ticking the Specify Cookie Domain option in the Xponent Graph API Web Tracking and Recommendation panel.
This will generate JavaScript tag code that looks like this - note the "specifyCookieDomain" option in the _kw.options object:
<script>
var _kw = {};
_kw.options = {
"listenerId": "6ae3ffc7cb0abde65e896801a917642e",
"listenerHost": "http://127.0.0.1:8080/api/v1/listener/",
"specifyCookieDomain": {"enabled": true, "domain": "corp.com"}
}
_kw.events = {
"trackViews": {"track": true},
"trackClicks": {"track": true,"noConflict": false},
"trackForms": {"track": true,"noConflict": false},
"trackButtons": {"track": true},
"trackBlurs": {"track": true},
"trackDivs": {"track": false},
"trackGeo": {"track": false},
"trackFingerprint": {"track": false}
};
_kw.success = function(data) {
// Handle returned data here
};
</script>
<script src="https://cdn.kitewheel.com/webTrack.v1.js"></script> |
A bug has also been fixed with the Kitewheel fingerprint capability that could sometimes lead to different fingerprints being delivered in the same browser.