| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
There are a number of improvements in the March 2018 Release of Kitewheel. The highlights include:
- Schema Navigation - making it easier to work with large schemas
- S3 File Adaptor - read and write files from AWS S3 buckets
- Kitewheel Graph API Consumes XML - the graph API will now accept and parse XML
- Web Tracking Do-Not-Track Features
- Cross-Engine Visual Testing
- Template Synchronization Control
There were a number of other bug fixes and minor improvements made during this release. We hope you like it.
...
To clear your search filter press the Clear Search Filter buttonbutton 
.
S3 File Adaptor
...
The File Connector currently only supports Amazon S3 as the Type (we plan to extend this to Azure Blob Storage soon). The Connector requires the S3 Bucket name which is the top-level bucket name without any additional path, and the AWS Access Key and Secret Access Key.
...
A JavaScript Node can be used to generate a file name that uses a timestamp and a unique identifier to ensure that files are ordered by creation date and also that there is no clash or accidental overwriting if multiple engines are processing and writing files simultaneously. The TransactionId from Schema Metadata can also be used to get a unique identifier.
Reading a File From an S3 Bucket
...
- XML elements become JSON arrays
- XML attributes becomes become "$" object objects with fields
- XML body text becomes "_" when there are attributes
- All element names are flattened to lowercase
- Attribute names are not flattened
...
On Windows the operating system color choose will bring up the Windows color chooser:
Cross-Engine Visual Testing
Kitewheel has supported remote engine stacks for some while. However it was not previously possible to perform visual testing with a remote stack. In this release we have enabled visual testing for remote stacks.
A remote engine stack is any engine configuration that is not the default engine configuration for the Kitewheel Hub. This includes dedicated production stacks within the Kitewheel AWS environment but also in remote AWS and Azure environments that are managed by Kitewheel. Remote engine stacks are used for production workloads to provide dedicated throughput and security for connection to on-premise or other cloud environments. If you are interested in using a remote stack for these purposes please speak to your Kitewheel account manager.
Template Synchronization Control
In this release we have improved the way that templates synchronise between different Kitewheel and dedicated partner OEM hubs. This makes the process more robust and gives a much finer level of control on how templates and managed graphs are distributed.
Bug Fixes
...
...
Web Tracking Do-Not-Track Features
The Xponent Graph API web tracking JavaScript has been modified to add a "doNotTrack" configuration section that allows the specification of HTML DOM elements and cookies that should not be tracked.
- cookies - the cookies specified will not be returned in the web tracking events
- names - any HTML DOM elements that match the list of names will not be returned
- ids - any HTML DOM elements with the specified ids will not be returned
- classes - any HTML DOM elements that have this class will not be tracked
The doNotTrack option is currently only available by modifying the JavaScript _kw.options object. There is no UI configuration available as part of this release.
For example if you had a HTML body like this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<body>
<h1>Hello world!</h1>
<div id="content">
<code id="response">This is a div tag</code>
</div>
<div id="testers">
<a href="index.html" class="doNotTrack">This is a link!</a><br/>
<div id="form">
<form action="index.html" method="post">
<input type="text" name="myText"/>
<input type="password" name="passField"/>
<input type="submit" value="Submit me"/>
</form>
</div>
</div>
</body> |
The following "doNotTrack" object could be used within the _kw.options object:
| Code Block |
|---|
_kw.options = {
"listenerId": "0123456789000000",
"listenerHost": "https://api.kitewheel.com/api/v1/listener/",
"doNotTrack": {"enabled": true,
"names": ['passField', 'field1'],
"ids": ['content', 'passID'],
"classes": ['doNotTrack'],
"cookies": ['privateCookie']
}
} |
This would have the following effect:
- The password field would not be tracked in a blur or a formSubmit event because of the names setting
- The content div will not be tracked
- The link will not be tracked as it has the "doNotTrack" class - this is the recommended approach
- The cookie "privateCookie" will not be returned as part of any packet
Cross-Engine Visual Testing
Kitewheel has supported remote engine stacks for some while. However it was not previously possible to perform visual testing with a remote stack. In this release we have enabled visual testing for remote stacks.
A remote engine stack is any engine configuration that is not the default engine configuration for the Kitewheel Hub. This includes dedicated production stacks within the Kitewheel AWS environment but also in remote AWS and Azure environments that are managed by Kitewheel. Remote engine stacks are used for production workloads to provide dedicated throughput and security for connection to on-premise or other cloud environments. If you are interested in using a remote stack for these purposes please speak to your Kitewheel account manager.
Template Synchronization Control
In this release we have improved the way that templates synchronise between different Kitewheel and dedicated partner OEM hubs. This makes the process more robust and gives a much finer level of control on how templates and managed graphs are distributed.
Bug Fixes
- [KIT-1246] - Update Migration Strategy for Engine / Reporting DB to avoid potential database locks
- [KIT-1317] - Custom engine group settings for environment disappear on a version restore
- [KIT-1330] - Page freeze on organizations admin if navigating immediately after login
- [KIT-1376] - Webtrack: Tag attributes missing in data return object when event tracked is not a tag
- [KIT-1307] - Fix for large schema elements not passing correctly to JavaScript microservice
- [KIT-1321] - Duplicate deployments on Azure / Kubernetes stacks
- [KIT-1354] - Schema filtering fails with arrays in the Schema
- [KIT-1356] - UTF8 Characters not encoded correctly when an JSON object is inserted into the database
Other Improvements
- [KIT-1249] - Logging system overhaul implementation (metrics and trace) - this should improve the performance and reliability of metric updates whilst opening the next stage of loggig and trace analysis.
- [KIT-1346] - Upgrade SQL Alchemy and database libraries. SQL Alchemy has been upgrdaed to 1.25 and the underlying database libraries have also been updated.