Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Alterian Real-Time CX Platform - DDE 4.29 CX 6.34

Release Date: 01/2024

Summary

  • Improved usability when coming back from a system that has timed out.


General

Better conformity on name validation

The validation of names of items in the user interface and the backend did not always match. We have made the validation consistent between the two validation areas.

Theming

Alterian CX allows the choice between three themes in the user interface. The default was set as the dark theme and this was jarring for users who were used to the standard light theme. We now take the browser (Chrome) theme and use this to guide us on the default to use. If users are using the dark theme in Chrome we will use the dark theme as default and the same with the light theme.

You can change the theme at any time and we will honour and remember the decision.

Rule Designer

Rename “Realtime Inputs” in Realtime Input Step

In the Realtime Input step we used to have “Realtime Inputs.” In truth these are set by Query Parameters or headers coming into the Rule. In the Test Runner Screen we call the setting of these values Query Parameters. We’ve changed the naming to be consistent and will now name both Query Parameters.

Revalidation of a Rule

While you are working on a rule in rule designer it’s possible for external changes to be made to that rule that will impact how it behaves and whether it will work at all. Previously these changes would not show in Rule Designer until the user exited and then re-entered rule designer when we would revalidate the rule.

We have now changed the behaviour to provide the user with more information on the changes that occur and to allow the user to react to them.

The changes below will cause a popup to occur. In each case the popup will highlight the change that has occured.

  • Rule Status - Running, Stopped, Paused

  • Linked Rules - Rules linked to the Tiles in the Rule. We inform the user whenever the linked rules status changes or when they no longer exist, the linked rule is deleted

  • Global Parameter changes - We will highlight the parameter that has changed.

Rule Designer Canvas

The Rule Designer Canvas has been updated to allow the following:

  • Select and then move multiple tiles to improve Rule structure

    • You can select by simply clicking tiles one by one or clicking and dragging a box to select tiles of interest

  • Select and delete multiple tiles

We now have a new “Move Mode” indicated by a hand at the bottom right of the canvas. This allows you to move the entire rule within the Canvas to provide more room.

We also now provide “Canvas help” that highlights the various keyboard shortcuts that are now available to users.

Parameters screen redesign

The Parameters screen has been updated and redesigned to make it easier to use. The separate “open” existing parameter button has been removed. Insead a user can right click on the url and choose to open in the same page or a new tab. Parameter editing has been improved with larger editing boxes.

Test Runner

Allow a test to be run with trace logging off

Test runner previously only allowed the logging at a tile and step level. Although both of these options are useful when reviewing a rule they do not represent the logging that would occur when the rule is running in production. You can now choose to turn the trace option off which accurately reflects the logs generated by a rule in production.

Test Descriptions in Test Runner

Tests within Test Runner have a description box where a user can add a description of the test and possibly the expected results. Users were keen to be able to see a description while also reviewing the test request.

We will now show the description from the tab in the test list screen. Where the description is long we will provide elipses and a tooltip so the full description can be seen.

Query Parameters

The Query Parameters section in the Request tab has been updated. We now provide bigger text boxes to make it easier to add and edit the values. We will also now show the default query parameters that are created automatically for each rule. Only the user created query parameters previously showed in this tab.

Rules

We have added a recently used Rules section to the Rules screen. It shows the last seven rules you as a user have used in order or recency left to right. This recently used section sits above the normal filters, this is per design as the filters do ot control the rules that show in this section.

This recently used Rules section can be toggled open and closed to ensure the Rules grid below maintains it’s size if the recently used rules are not the focus of the work being done.

This new design has also replaced the recently used functionality in Journey Playbooks and Journey Analytics.

Steps

DDE Rule has Fire and Forget setting to improve performance

Where you do not require a response back from the system you are calling, you can set the Fire and Forget flag. This continues processing without waiting for a response, making processing quicker.

Alterian Queue will update expiry on fields read into the queue messages

The Alterian Queue allows you to automatically append data stored in a single table to the event being created. Alterian currently uses this to append your Persona and Customer Attribute values to the events created. To ensure this data is not rolled off, the Alterian Queue will now read and then write to update the expiry times (TTLs).

This is currently not configurable from the 18 months set for the Customer Attributes.

Alterian Queue step now supports bundling of events for non-FIFO queues

The Alterian Queue will bundle Messages together to improve performance when using our non-FIFO queues and ensure key events occur in the correct order. Please check with Alterian support before altering these values as you need to be on appropriate versions of Journey Orchestration and Journey Analytics.

Sandboxing Function

To facilitate testing, experimentation, or the execution of newly designed code without compromising the integrity of the overall system we now provide a Sandboxing function.

Journey Analytics

Data Transform

This release contains the following additional capabilities in the Data Transform. The filters and search outlined below work in conjunction with each other to produce the final display.

Pre Transform Search

It is now possible to perform a search on the pre-transformed Location to allow better review of Locations that need a Transform applied

Post Transform Search

It is now possible to perform a search on the post-transformed Location to allow better review of Locations that have been transformed to review the new Locations in preparation for use in analytics.

Transform State Filter

It is now possible to filter the view to only those Locations that have been Transformed, that haven’t been transformed or a show all. Important that the “ucase” function, as it does not “change” the location string, is not included as a Transform in this view, so untransformed Locations may still have had a ucase applied.

Location Mapping

General UI improvements in the Location Mapping screen with row level multi-select and row level options along with the removal of the previous pagination UI for a more traditional scroll method for easier view and multi mapping.

Fixes

DEV-11530

Fix to loss of formatting on Journey Discovery result screen when scrolling

DEV-11559

Fix to an issue displaying no data when a single day date range is selected

DEV-11562

Fix to no-value queries in Attribute values

DEV-11607

Fix to Data Transform screen’s scroll bar not displaying

DEV-11608

Fix to Journey Discovery breadcrumb navigation

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 Cache step delete was not successful: but this is an incorrect log message and should be ignored.

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.

  • No labels