Jadu CXM: Product Updates

We have made a number of improvements designed to make CXM speedier:

Improvement An improvement to the 'new case' modal which addresses an issue where it can be slower to load after a change is made to a CXM case type.

Improvement When opening a case, the timeline now loads after the page has rendered. This is so that users can view details in the ribbon, or perform actions without needing to wait for the timeline to load if there are lots of entries.

Improvement Fixed an issue where opening a case with cases notes is slow.

Improvement A minor improvement aimed at reducing page load times for a case, the cases page and the 'new case' modal.

We have made a number of improvements to addresses in CXM:

Improvement When an address is selected for use (for example when a person is created, a case is created or edited etc.) we now re-fetch the address to ensure we have the latest version of that address. This overcomes an issue where properties were being updated in the source service but not in CXM.

Improvement For customers using Singlepoint or Esri LocatorHub address services, it is now possible to exclude properties from property results based on their 'logical status'. This can be done through a setting in the integrations hub page where you can add one or more statuses to be excluded.

Other things we've been working on: 

Improvement It is now possible to search the logs for an integration by a case reference so that it is easier to find the log and diagnose a potential issue with an integration.

New We have added the ability to get a person record by telephone number through the CXM API. This could help with tailoring the experience to a user ringing up based on their previous CXM cases.

Fix Fixed an issue where a field cannot be used in a filter if it has been created as part of a case type import.