Product Update - v6.8.0, August 2024

Webex Connect v6.8.0 release brings multiple new capabilities to help you continue delivering seamless customer experiences. Here’s a list of the key updates and enhancements that are a part of this release:

Summary

• Support for Apple Messages for Business App Clip Rich Links
• Outbound webhook for Resubscribe event
• Push, In-App Messaging, and Live Chat-related enhancements
• Usage Report Enhancements
• New parameters in Outbound Webhooks and Data Stream Payloads
• Ability to stream Audit logs using Data Stream
• Ability to map multiple Sender IDs while publishing a flow when using dynamic SMS Sender ID config in the
  Receive Node
• Messenger Page Reauthorisation
• Granular access controls for Service Key, JWT Token, and Profile/Media Access Key
• Restriction to invite users with temporary/disposable email addresses
• New fields in 10DLC Campaign Registration

Please refer to the details below to learn about all the changes and enhancements.

📘

Release Date

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

Details

Added - Support for Apple Messages for Business App Clip Rich Links

We’ve added support for the latest Apple Messages for Business feature i.e., App Clips interactive message
type. An App Clip is a small part of your app that lets people complete a quick task without installing the app in
their devices.
App Clips interactive message type is an enhancement to existing feature wherein a text message with the link
is automatically divided into separate text messages and rich link messages to improve the messaging
experience for the end user. Going forward, Webex Connect will up-convert such links into an App Clip when
configured. If you don’t choose to send the link as an App Clip, it will be sent as a Rich Link, as per the existing
behaviour.
This feature is supported by both Messaging API v1 and the Apple Messages for Business Send Node in the
Visual Flow Builder. The optional parameters in Messaging API v1 that need to be used for sending links as App
Clips are:

• "sendLinkAsAppClip": true
  • If this optional parameter is not passed, the link will be sent as Rich Link.
• "storeRegion": "\<Alpha 2 Country Code>"
  • This optional parameter will be required only if the App Store region is not US.

Refer to the Apple Messages for Business Node (v6.8.0) documentation after the release for more information about this capability.

Changed – Outbound webhook for Resubscribe event

We’ve added two new parameters to the Outbound Webhook notification that’s triggered when a customer
resubscribes to an email sent by you. This is applicable only for emails that use Unsubscribe & Resubscribe
Management capability offered by the Webex Connect platform. The parameters are as follows:

• "senderId" - Email address used to send the concerned email to the recipient.
• "correlationId" - Value of the correlationId mentioned when sending the email. This can be used to
  uniquely identify the email that was sent to a recipient in cases where you have used the same ‘Sender
  ID’ for sending multiple emails.

These two variables will be available for all resubscribe events received after this release is live. However, the
values will be populated only for the resubscribe events related to the emails sent, after this release is live in
your region.

Refer to the Outbound Webhook - Email chapter (v6.8.0) for more information on updated payload and supported information.

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

We are releasing the following SDK versions as part of Webex Connect v6.8.0 release:

• Android v2.20.4 - This SDK resolves an issue where Geofence events were not invoking on devices
  running on Android OS version 12 and above. This fix ensures compatibility and proper functionality of
  Geofence events across all supported Android versions.

This apart, we are happy to announce that we are launching a new set of modular SDKs for Android and iOS
(for each of Push Messaging, In-App Messaging, and more) to provide you with the flexibility to add selective
functionality to your mobile apps depending on your requirements. The existing SDKs will continue to be
supported until further notice.

Important: For new implementations, we recommend using our modular SDKs for easier development and
integration. For existing implementations, we recommend continuing to use the existing SDKs, we'll release an
updated version of the new modular SDKs to enable a smooth transition.

Changed – Usage Report Enhancements

We have made a few enhancements to the Usage Reports that can be exported from the ‘Usage’ section of
the platform UI. Here are the details:

• Two new fields ‘country_ISO’, and 'carrier_name' have been added to the “RCS” sheet of the report.
  Further, the existing field i.e., ‘operator' has been renamed to 'carrier_name’.

These changes will be applied to the first Usage Report that will be generated after v6.8.0 has been released in
your region.

Refer to the Usage Reports Fields (v6.8.0) documentation for more information about this capability.

Added – New parameters in Outbound Webhooks and Data Stream Payloads

We are updating the payloads for Outbound Webhook notifications and Data Stream events by adding new
parameters. These parameters will be added to:

• Incoming Message event type for Messenger channel
• Incoming Message and Postback event types for Live Chat/In-App Messaging channels
• and the Incoming Message event type for WhatsApp channel

Please refer to the documentation after this release for the complete list of newly added attributes. As
mentioned in our documentation, enhancements are made to these payloads overtime for various reasons.
Please keep your application at the receiving end flexible to avoid any impact when new parameters are
added.

Added – Ability to stream Audit logs using Data Stream

We’re introducing a new feature to stream audit logs for user actions such as updating a channel asset/app,
copying API credentials and more to a Kafka destination. These logs are similar to the details available within
User Audit section in the platform. Please note this feature is currently in controlled Beta mode. Reach out to
your account manager if you would like to know more.

Refer to the Data Streamschapter (v6.8.0) in Platform Help documentation for more information on updated payload and supported information.

Added – Ability to map multiple Sender IDs while publishing a flow when using dynamic SMS Sender ID config in the Receive Node

When using the Dynamic configuration option for Number filed in the Receive Node for SMS channel, we now
require selection of the numbers that the Receive Node will wait for a response on at the time of flow
publishing using the ‘Make Live’ button.

Existing flows with a Dynamic Number on an SMS Receive Node will continue to function as is. However, once
the flow is updated, you will be required to select the numbers when the flow is made live, as mentioned
above. A similar mapping will need to be done in sub-flows if you are invoking one flow from another, using
the Call Workflow node.

Refer to the Receive Node (v6.8.0) documentation for more information about this capability.

Added – Messenger Page Reauthorisation

Starting with this release, Webex Connect will send email notifications to users with Full Access, Tenant
Owner, and the user who created a Messenger asset when the page access token for the Messenger Page
associated with Webex Connect is invalidated due to the concerned user changing their Meta/Messenger
password, or due to the de-linking of that Messenger page with Webex Connect.
Admins of the concerned Messenger page with Tenant Owner or Full Access roles can use the ‘Reauthorise
Page’ option in the Messenger App management section, to reauthorise/relink their page with Webex Connect.

Refer to the Facebook Messenger (v6.8.0) documentation for more information about this capability.

Changed - Granular access controls for Service Key, JWT Token, and Profile/Media Access Key

In this release, we have added granular controls for restricting access to Service Key, JWT Token, and
Profile/Media Access Key. Going forward, only the Tenant Owner and Full Access users will have access to
these keys by default, with the ability to update permissions at the user-level for other Full Access users. All
other users and roles, including Support and Help Desk users, will be restricted from accessing these keys,
providing an additional layer of security and control.

This change may impact the access level for some of the existing users. Please make relevant changes after
this release as per your requirements.

Refer to the Teammates (v6.8.0) documentation for more information about this capability.

Added – Restriction to invite users with temporary/disposable email addresses

In this release, we have restricted the ability to invite users with temporary email addresses, for examples,
email addresses with "maildrop.cc", "mailinator.com", "yopmail.com", and "sharklasers.com" domains. Usage
of such public email addresses for accessing Webex Connect pose security risks, hence we do not recommend
it. This is a growing list and we will continue to add more domains on an ongoing basis. If you have used such
email addresses previously, you will continue to use them at the moment, however we highly recommend that
you remove such users from your tenants, and adopt a more secure method such as single sign-on (SSO) for
logging into Webex Connect.

Refer to the Teammates (v6.8.0) documentation for more information about this capability.

Changed - New fields in 10DLC Campaign Registration

We have updated the 10DLC campaign registration form to include three new required fields. Customers need
to provide details for the following fields: ‘Links to your terms and conditions’, ‘Privacy policy’, and ‘Embedded
links’.

Refer to the Register a Campaign (v6.8.0) documentation for more information about this capability.

Important Additional Notes

• Starting August 29th 2024, WhatsApp businesses globally are limited to sending a maximum of
  two marketing template messages in a 24-hour conversation window, without the customer
  responding. If the customer responds, an additional marketing template is permitted, and freeform
  messages can be used to continue the conversation. Starting September 17th, 2024,
  businesses can utilise a new error code i.e., "131049", to help understand when a message is not
  delivered for WhatsApp ecosystem health reasons, such as the per user marketing template
  message limit. This error code will be reported by Webex Connect as part of "additional_info"
  field, within the 'Failed' delivery notification, when configured.
• This apart, support for WhatsApp Channel via Send Message API v1 that's already available in
  Webex Connect production accounts, will now be available as part of the new Webex Connect
  Sandbox accounts as well.

Changelog