Webex Connect v6.14.0 release brings multiple new capabilities to help you continue delivering seamless customer experiences.

Summary

• RCS Automated Interactions Count in Usage Reports
• Support for Content ID in Email payloads (Inbound & Outbound)
• Push, In-App Messaging, and Live Chat-related enhancements

📘

Release Date

The date of release will be communicated separately over an email.

Details

Changed: RCS Automated Interactions Count in Usage Reports

The Webex Connect platform now tracks and includes counts of automated interactions for outbound and
inbound transactions for the RCS channel. The Automated Interactions data will be displayed in two areas:
the ‘Automated Interactions Count’ tab within the user interface (UI), and the Automated Interactions sheet
in exported Usage Reports.

Added – Support for Content ID in Email payloads (Inbound & Outbound)

When emails with inline attachments are received from consumers, the HTML message and Attachments
payloads can now be combined through Content ID parameter referred to as “cid”, to preserve the
attachment placeholders, so that the downstream applications can accurately present the email content.
With this change, you will (clients) start seeing the “cid” key-value pair inside the ‘Attachments’ payload of
Outbound Webhooks and Output Variables.
Similarly, for the outbound emails, Send Message API v2 now allows sending emails with inline images
using the “cid” parameter or placeholder in the HTML payload referencing the Attachments array. This
method is an alternate way to the existing way of sending images as part of the HTML page.

Added – Push, In-App Messaging, and Live Chat-related enhancements

We are releasing the following SDK versions as part of this release:

• iOS SDK v3.0.6
• JavaScript SDK v1.7.2

Here’s a summary of the changes:

In iOS SDK, we’ve made various technical enhancements and fixed an app crash occurring during
concurrent ‘RetryRequest’ operations.

We’ve released an updated JavaScript SDK that resolves an issue where delivery receipts failed to retry
when the JWT token had expired. The SDK now refreshes the token correctly during the retry process.
Additionally, we’ve reduced the delivery receipt retry interval to 3 minutes, enabling faster processing and
more timely handling of delivery receipts.

New Error Codes for Push Message Delivery Failures

We have introduced new error codes to improve visibility into Push message delivery failures for FCM and
APNs. These codes will be available in Outbound Webhooks, Notify URLs, Data Streams, Export Logs,
Debug Logs, and Reports as part of this release.

Important Additional Notes

• Conditional Triggering for the RCS Start Node is currently not functioning as expected for 'Postback'
  and 'Location Response' events. It only works for 'Incoming Message' and 'Incoming Attachment'
  events. We are actively working on a fix to ensure consistent behavior across all supported Event
  Types. Also, please note that Conditional Triggering is not applicable for Unsubscribe and Subscribe
  events, as these event types are not available in the Receive Node.

Deprecated Items

None

Changelog