Capabilities rolling out in June 2023
Alterian Real-Time CX Platform - DDE 4.24/CX 6.29
Release Date: 05/06/2023
Summary
Improvements to Template Builder making the setup process and ongoing usage much easier.
Show recently used templates in the Template Selection screen making it much easier to reuse templates previously selected.
New GET CXID Bulk Optimised Public Template to make it a lot easier to load non customer related data or data gathered out of realtime providing no impact on customer specific metrics.
Templates Screen
Templates screen redesign
The Templates screen has been redesigned to make it easier for a user to see the details of a templates without having to open each one.
Template Builder
Making it easier to start Template builder
The process to start template builder has been simplified. Instead of having to separately start Template builder you simply choose how your want to access template builder, either to create a new template or editing existing and we will start template builder as part of that process.
We will show you the progress through setup and allow you to shutdown template builder when no longer required.
Making it easier to use template builder
You can now open Template builder from the “Create new” functionality in the home page and main bar.
You can open a Template directly into Template builder from the “About” section of the template in the Templates screen and in Rule designer.
You can also open the templates by right clicking on the Template in the Templates screen and on the Tile in Rule Designer.
These improvements make it significantly easier to adjust your templates.
Rule Designer
Make it easy to reuse recently utilised templates
The Template Selection screen now provides a separate view that contains the most recently utilised Templates allowing them to be quickly selected.
The recently used Templates screen will honour the standard template selection screen filters and search.
Show status of linked Rules
Linked rules now show the status of the linked rule and we allow it to be stopped or started from the linked Rules screen.
If the linked rule does not yet exist, we allow a rule to be easily created.
Testing
We now provide the headers provided back by the tests run.
Journey Playbooks
Choose background colour for steps
You can now choose to colour coordinate steps in a playbook by selecting a specific background colour. This can be used to signify a specific link between the steps wiht a shared colour. Perhaps a shared action or outbound channel represented by the colour used. For example, all outbound email steps should have a light blue background.
Steps/API
Enhancements to S3 output step
The S3 Output step now requires that the Node Name check box is checked to ensure these details are written to the exported files to aid future triage.
We now provide a Rule Name check box that will append to the end of the file name the name of the Rule that created it. This decreases the chance that files are overwritten if multiple rules are writing to the same place.
Enhancements to Autoloader functionality
In a previous release we provided functionality that allowed discrete values in the data loaded to Jounrey Orchestration to be recorded for use in switch cases. Previously this functionality was restricted to a single field being loaded. You can now opt to gather the discrete values for any of the fields being loaded via the autoloader functionality.
Fields created and written by the Autoloader process can now optionally have a TTL applied to the fields written.
Public Templates
Get CXID Bulk Optimised
The customer attribute table can take fifteen banded elements of data and this can be used in switch cases in your rules to change influencer rule decisions. We can also add this same information into each event created so you can better filter your journeys in Journey analytics.
This data is about an individual but not created by an individual, so we do not want to change any standard information we hold on them. For example the last seen date for an individual should not change just because you have loaded their ”Persona” information overnight.
The new GET CXID - Bulk optimised public template has been designed to allow our customers to efficiently bulk load data into Alterian CX but it does not change any customer attributes.
The GET CXID - Bulk optimised public template should be used whenever you are loading in data related to an individual but not driven by the user themselves.
Find out more how this template should be used here.
New Event Queue - action process
To understand why a customer takes a certain action, it is important to determine the factors that influenced their behaviour. The action can be a result of the customer's own choice or it may be influenced by external factors, such as influencer rules.
Additionally, the events generated in the course of the customer's interactions with the business can also affect their behavior. Events like a delayed order or the organization of a return can impact what the customer does next. For example, if an order is delayed, do customers the call centre? Does booking a test drive lead to improved communication and purchase?
These events, including actions like order shipping, order delivery and expected order dates, can be associated with specific customers and can significantly influence their behaviour without them initiating the action.
The event queue Event Queue - action process allows these Action Process events to be loaded into Alterian CX where they will show as a separate event type in Journey Analytics.
These events when loaded will probably also use the new GET CXID Bulk Optimised Public Template. To find out more about how each of these Public Templates should be used check here.
Journey Analytics
No major features have been released in this version of Journey Analytics
Fixes
DEV-10281 | Template input and output connectors cannot be set to disabled on upload |
Known Issues
DEV-5353 | Loading an existing Sankey in Side by side, when using the Quick Access fails to load. Using the grid option does work correctly |
DEV-8342 | Cache delete was not successful errors inaccurate. The logs may include messages like |
DEV-4283 | Cache Data report does not correctly show numeric field data. If you have a Cache table and a counter table of the same name the numeric value is never pulled back by the Cache Data report. |
Report Issue
To report an issue with the application not detailed here, please contact Technical Support. Please use our Service Desk to report issues.