Release Date: 12/12/23:

CX Manager

Cases

• We updated the sort order of Cases when a user clicks the View All button on the Case section of the Customer panel in a Case. Cases will now be sorted by created date with the newest created Cases at the top of the list.
• We improved the UI so the Location Block Card information (configured in Settings) is always displayed in the Customer panel of the Cases screen.
• We fixed a bug where setting the Category field to Required to Resolve in a Case Layout was not working properly. If you set the Category field to Required to Resolve, you will not be able to resolve a Case if that field is left blank.
• We fixed a bug where searching in the Cases search bar was returning no results when searching from a screen that has a Group By filter applied. You can now search from any Cases View and get search results returned.
• We fixed an issue where the last activity was not showing on all Case Cards in a Case list.

Communications

• We fixed a bug where SMS messages were able to be sent out from certain Organizations even if an SMS integration was not enabled. If your organization does not have an SMS channel enabled, you will no longer be able to add an SMS channel to a Case.
• We removed the automated bot messages in chats (for Support Cases) that users were not able to control.
• We improve the performance of loading chat messages in the communications panel

Knowledge

• We fixed a bug where some of the modals in the article editor were being cut off. All models will now appear centrally in the editor window so all information and actions are accessible.
• We improved the focus states of accordions and the headers in the “What’s in this article?” section when viewing an external Article. The focus state is now visible around the entire element. We also removed the focus state from text written using the Code format.

Journeys

• We added relative due dates to Tasks on a Journey to allow teams to have more control over the speed of progression of a Journey. The due date of the Task is set relative to when the Task is created.

• We created a Journey Summary component that visually summarizes where the Journey is in the overall process.

• We fixed an issue where the latest published revision of a Journey was not always visible on the Case Timeline view.

• We fixed an issue where the unsaved changes prompt in the Journey Builder was showing when no changes were being made.

• We fixed an issue in the Journey Builder that prevented more than 20 teams from showing in the Owner Team picklist when configuring a Task. You can now assign a Task from a Journey to any Team in your Organization.

APIs

We updated the /lookupByExternalId endpoints to use the context Organization and not the authenticated Organization. This enables Service Provider Organizations to match and update customer data on behalf of their partner organizations when granted proper access.

Security

We resolved several routine security vulnerabilities.

Alan Finlay