Journey Strategy and Analytics

First up, we’ve made some upgrades 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. We see this as a big step forward in our approach to analytics for the customer journey age.
You can now export your journey maps 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.

We’ve upgraded to Node.js 6 across the board, which is significantly faster and supports a vast array of modern JavaScript language features ("ES6").
We’ve also pre-packaged libraries for commonly used functions, like date and time manipulation (“moment”), user agent parsing and device detection (“ua-parser-js”), and ID generation (“uuid”). We've also included a toolkit of common utilities that make working with common data structures much much easier ("lodash").

We’ve made even more significant performance improvements across the board

Databases and queues are by far our most commonly used integrations. We have drastically reduced transaction times and increased 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 API HTTP headers and server-side configuration has reduced the number of requests, speeding up page loads and customer experience.

[KIT-567] - Redis trace data should be set to expire
[KIT-599] - Many versions degrades performance of managing versions
[KIT-637] - Can't single click to remove selected area on screen
[KIT-643] - Contact list ids don't follow the big int sequence strategy
[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-696] - get all templates returning with full JSON
[KIT-712] - Testing graphs killed when 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.
[KIT-759] - Split Test producer/consumers don't explicitly close connections

[KIT-621] - Default edit lock to closed when it is locked by the current user.
[KIT-690] - Replace MathJS with lighter weight package
[KIT-693] - When deploying a graph with multiple environments, the graph displays loading state in each environment
[KIT-701] - Set max retries for graphs in arbiter