Journey Strategy and Analytics

There have been a number of changes to the Journey Editor that make it easier to measure and share your customer journeys.

You can now visualize metrics overlaid on the customer journey map, making it easier to correlate your key performance indicators with steps along the journey.
You can drill in to these metrics over time, with 1-minute, 5-minute, up to 1-day levels of aggregation. This as a big step forward in our approach to analytics for the customer journey age.
Journey maps can now be exported as PDF or PNG files for embedding in other documents or sharing with stakeholders, including custom branding.

Scripting Upgrades

We’ve upgraded and standardized our scripting capabilities in the JavaScript Node:

There has been an upgarde to Node.js 6 across the board, which is significantly faster and supports a vast array of modern JavaScript language features ("ES6").
The JavaScript Node now also has pre-packaged libraries for commonly used functions:
- Date and time manipulation (“moment”)
- User agent parsing and device detection (“ua-parser-js”)
- ID generation (“uuid”)
- A toolkit of common utilities that make working with common data structures much much easier ("lodash")

There have been a number of significant performance improvements across the board:

Databases and queues are by far our most commonly used integrations. Connection caching has been introduced that drastically reduces transaction times and increases throughput, on average 3-5X, including API and web tracking graphs
Intelligent use of caching and compression has reduced the user interface load times and increased UI responsiveness overall
Changes to the API HTTP headers and server-side configuration has reduced the number of requests, speeding up page loads and customer experience

It is now possible to reorder columns in decision tables - there is a shift-left and shift-right button on each decision
The ability to tag environments and engine groups, filter by tags
The log of deployment events, including starts, stops, and errors is now visible to administrators on the Deployment tab
To manage the number of alerts raised deployment state degradation must last longer than one minute for an alert to be raised. This means that simple restarts are not alerted. These often happen if a Kitewheel engine is recycled in the pool.
Default edit lock notification to closed for locking user

[KIT-599] - Many versions degrades performance of managing versions
[KIT-637] - Can't single click to remove selected area on screen
[KIT-644] - Listener count/max count mismatch on deployments page
[KIT-667] - Environment dropdown when viewing split test producer in a version
[KIT-674] - UI freezes when trying to 'Create and Associate Graph' in journey map
[KIT-677] - Database listener max wait time interval
[KIT-682] - Nested subgraphs in loop node subgraphs cause error on engine format (or validation)
[KIT-683] - Resizing comments doesn't work in some zoom levels
[KIT-695] - Don't Allow selecting a journey template as a type of new graph to associate
[KIT-712] - Testing graphs killed when browser tab in background
[KIT-718] - DB Insert: Inserting null into JSON fields results in string value 'null' not null value
[KIT-719] - DB Insert: spacing before literal text inserts can cause inaccurate value splitting
[KIT-720] - JSON strings with newlines get inserted as strings, not objects.
[KIT-738] - Fix issue with metrics failing to update if processing fails out before it sets the expiration
[KIT-754] - Split Test Producers in subgraphs don't get initialized
[KIT-757] - Twitter Listener occasionally stops listening.