Platform DocumentationPlatform ChangelogAPI ReferencePush & In-App SDKsSDK Release Notes
Platform Changelog
FAQsWebsite
Back to All

Product Update - November 2021

almost 3 years ago by Aditya Aysola

imiconnect v5.6.2 release brings in multiple new features and enhancements to make your platform experience more secure and richer. Here’s a list of the key updates:

  • Option to use short-lived URLs for incoming media/attachments over messaging channels
  • Additional details in the monthly usage reports
  • Updated Push and In-App Messaging SDKs for Android, iOS, and Cordova

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

Added – Option to use short-lived URLs for incoming media/attachments over messaging channels

We’re introducing a new feature to allow you to choose the option of using short lived URLs for accessing the incoming media/attachment files over digital messaging channels like WhatsApp, In-App Messaging, etc.

This feature is currently available in a controlled mode, and you can reach out to the support team if you would like to enable it for your tenant after v5.6.2 release. Once enabled, you will be able to switch it on and configure the public accessibility timeframe for these media/attachments URLs post which accessing these files will require you to authenticate your requests. Please refer to the product documentation (after the release) for details about the authentication mechanism for media received on various channels.

Added – Additional details in the usage reports

We have updated the ‘Usage’ section to include additional usage information covering:

  • Details of inbound SMS usage
  • Details such as usage start time, usage end time, country codes for inbound and outbound SMS usage, country codes for newly purchased/provisioned numbers,
  • A new metric called ‘Automated Interactions Count’ and other minor enhancements

Please refer to the docs on Usage section after the release for more information the above points.

Changed – Improved user experience for buying and managing numbers

  • From this release onwards, you’ll see the ability to specify granular selection criteria (e.g., ability to specify whether you need a number with SMS support alone, vs a number with both SMS and voice support, etc.) when buying new phone numbers using imiconnect. This is applicable only for tenants that have the Buy Numbers option enabled.
  • For 10 Digit Long Code (10DLC) numbers in the US, you’ll now be able to see the details of brand ID and campaign ID in the ‘Assets->Numbers’ listing page.
  • This apart, you will see a single entry for an SMS enabled long code (i.e., listed as phone number in the UI) that can be used as the Sender ID for outbound SMS messages. This change applies only to the numbers that are added after this release. You’ll continue to see two rows (one for Sender ID and one for Phone Number) for the numbers added before this release.

SDK Updates

Changed – Push and In-App related changes

We’re releasing following SDKs as part of imiconnect v5.6.2 release:

  • Android SDK v2.15.3
  • iOS SDK v2.15.3
  • Cordova SDK v2.3.4

Here’s a list of changes we have made since the last update.

  • Added the option to use short lived URLs (with limited time public accessibility) for incoming media/attachment on in-app messaging channel. Refer the section on short lived URLs above for more info.
  • Technical enhancements to improve the handling of media download requests when network connectivity is poor.

Please refer to the SDK docs after the release for more information the above points.

Important Additional Notes

  • Please note that we will be phasing out support for using standard voices for configuring new Text to Speech experiences as Azure has announced that it will be retired by 31st August 2024. Hence, we recommend you begin to use neural voices when configuring new voice services using imiconnect APIs and/or flows.
  • Conditional check for ‘In’ condition in Branch Node was not working as expected and has been fixed in this release.
  • As mentioned in one of our previous communications, WhatsApp has announced that
    they will be deprecating the HSM message type in the future. As a result, we advise you to start using ‘Template’ message type instead of HSM message type for sending notification messages going forward. We also recommend that you migrate your existing services that use HSM message type to Template message type.