Social25 Release notes

Features and Bugfixes

Features:

• Maximize chat window in order to view full text area

Bug fixes:

• outbound URL was blue on blue chat bubble
• Alignment of chat bubble was offset for long text messages
• Chat window sometimes crashed on receiving vCard attachment

Changes

• Feature: Refactored a part of the chat window because of bad pusher events handling
• Bugfix: Correct handling of URL's from Facebook Messenger
• Bugfix: Messages are visible again without having to refresh the page

Changes

Bugfix: Changed the way the trigger checked if personaccounts are enabled Feature: Possibility to relate outbound messages also to account/contact and socialpersona

Changes

Features: - Browser notifications for active chats We have introduced a new feature where open Salesforce tabs with an active Social25 chat will send browser notifications when not viewing the chat directly. We have disabled this feature by default and can be enabled by following the setup guide here: https://gen25-jira.atlassian.net/wiki/spaces/SOC/pages/1906802693/Set+up+Browser+Notifications

Bug Fixes: - In some cases messages were not shown correctly in the chat window when an agent responded too quickly on incoming messages. This has now been fixed. - Fixed an issue where the chat window in Salesforce mobile was not shown correctly

Changes

• Added support for a deleted message
• Standard trigger now run only in before insert and not in before update anymore
• Added the ability to publish a platform event on incoming and outgoing messages
• Added Giphy logo to all Giphy screens

Fix

• Removed socialpost copy check

Changes:

• Added permission set for the integration user
• Message copy to socialpost first checks if it already exists
• Template mapping field was causing errors in lightning app builder

Bug fixes

Adding Salesforce specific CSS to the code base, so Social25 renders correctly when displayed in an iframe

Bug fixes and improvements

Change the way Social25 provides and displays symbols and icons from the static resources Change the WhatsApp business logo Minimize the size of static resources Bugfix: Pusher is now only called when all static resources are loaded Bugfix: It is now no longer possible to upload a file when the chat has expired"

Bug fixes and improvements

Design improvements: user placeholder image General usability improvements Bugfix: When retrieving a message, the time stamp is now in the correct time zone Component height: The component height can now be adjusted by the user

Bug fixes

2nd part of the trigger redesign Cache control of all static resources are public now

Bug fixes

Feature: Social25 is now supporting the official WhatsApp-Business API for HSM-Templates Bugfix: Improvement from Pusher error handling

Bug fixes and improvements

Feature: Whatsapp-Business logo support Bugfix: Emojis are not changing URLs when selecting them through the emoji overlay Bugfix: Audio files can be sent from WhatsApp to Social

Features

Feature: If there is a pusher error, the customer gets an custom error message Feature: Status of messages are always visible now

Features

Feature: Social25 is supporting Events send from a Facebook-Bot.

Bug fixes

Bugfix: Post Template Message substitutes datetimes and date values correctly

Bug fixes

Upgrade Pusher.js library to v5.0.2 Improve error handeling from pusher

Bug fixes

Bugfix: Fixed a bug where an exception from Pusher was not processed correctly by Social25

Bug fixes

Bugfix: Fixed a bug, where a message couldn't be sent when the emoji picker is open Bugfix: Fixed a bug, where too long messages could be sent from Social to WhatsApp but weren't delivered

Bug fixes and improvements

Small design improvements Bugfix: Fixed a bug where the send posibilities for send option "Enter" was not correct Feature: Social25 supports WhatsApp inbound contacts Bugfix: Fixed a bug, where the browsers spellchecker couldn't be used

Features

Feature: Add better visibility to bubbles when they fail to send Feature: Audio messages showing now, when it is transcribing an audio message

Bug fixes and improvements

Bugfix: Fixed a bug where line breaks where not shown in the chat bubble in Social25 Bugfix: Fixed a bug where a video might not be displayed properly in the upload preview window Bugfix: Proper error handling, if a file upload was unsuccessful Bugfix: Fixed a bug where Emoji's quick-search could change the order of words in the text message Bugfix: Fixed a bug where punctuations in the Emoji's quick-search could throw an error Smaller design and UX improvements It is now possible to switch account record type from persontype to business type and from business type to persontype Bugfix: Chat window will now properly check if gifs are supported Feature: Incoming audio messages are getting transcripted by an AI

Bug fixes and improvements

Implemented folder structure and merge fields for quick text (merge fields can be used for related fields on a case) Emoji ux improvements Bugfix: Undelivered messages no longer receive a read symbol after reloading the page

Bug fixes

Fixed styling on button in the chat window footer Fixed a bug where dragging in a file could make the chat window not accessible anymore.

Bug fixes and improvements

Added a feature that allows the user to quickly access emojis by writing “:” and the name of the emoji title Added support for Facebook templates (Structured Messages) for the generic template and the button template Added support for location messages in WhatsApp Added support for contacts sent through the WhatsApp Business Connector Bugfix: Fix where the chat might not expire correctly Bugfix: Fixed a bug that could occur when dragging a file in the Social25 chat window Bugfix: Fixed a bug where messages are sent twice when Facebook Echo is enabled for a Facebook page Bugfix: Fixed a bug where unsupported messages did not show a general error message

Bug fixes

Accesstoken is now passed to next request during multiple callout methods

Bug fixes

Added Post Template Message callout method Bugfix: Long urls was still breaking out the message bubble for incoming messages Bugfix: Hotkey for quicktext was throwing an error when quicktext was not configured

Minor improvements

Added Post Conversation callout method

Bug fixes

Bugfix: Long urls was breaking out the message bubble Bugfix: Quicktext view is not getting refreshed when quicktext is disabled Implemented proper error messages in the chat window instead of a general one Refactored the Social25 Callout methods

Bug fixes

Bugfix: Contact merge failed when victor contact was not related to an account Bugfix: Expired WhatsApp conversation was not enabled again after receiving a message Chat window is now supported on other SObjects

Bug fixes

Fixing a bug where the file upload could through an error. Fixing a bug where the agent could send a text message before an image was completely uploaded Implemented Quick Text Implemented WhatsApp Template messages

Bug fixes

Fixed empty body in PostQRCode method

Bug fixes

Correct implementation of async of the post message method References to a not existing attribute are removed Fixing a bug where loading new messages could through an error Fixing a bug where sending files with a text in WhatsApp are not correctly delivered

Bug fixes

Fix for Salesforce Winter 20 Edition, which prevented the user from accessing an overlay above the chat window Improvement on updating the database Overlays (GIFs, Emojis, Attachments) can now be closed by clicking the ESC-Key Smaller design improvements

Bug fixes

Fixed Salesforce Winter 20 Edition, which prevented the user from accessing the chat window Fix for WhatsApp GIFs where GIFs disappeared after reloading the chat window

Minor improvement

Added configuration for the staging environment

Various improvements and bug fixes

Features

Closing other open overlays when dragging and dropping files in the chat canvas Conversation origin is now retrieved from the API New file Icons for Word, PDF and Excel Added preview for videos in upload

Bug fixes

Fix for uploading images when two cases are open in two different tabs Fix for using GIFs when two cases are open in two different tabs Destroy Timer for Case when closing a case window Fix for Safari when deleting an uploaded file

Process Builder and Flow support

Global post message function for Process Builders and Flows

Bug fix

Fixed wrong reference to a Static Resource

Minor improvements

Features

Conversation expire timer Every Lightning Component now works on API version 45

Bug fixes

Bugfix for showing GIFs via Twitter channel Showing a message in chatscreen when no config is found Added custom labels

Minor improvements

Changes in Connected App

Styling fixes

Fixed typo's in the configuration page

Bug fix

Bug fix in the tab highlighting

Bug fixes

Fixed overlay model Fixed unsubscribe from Pusher

Minor feature

Implemented a max length on text messages

Bug fixes

Fixed auto-grow on text area

Bug fix

Added missing Static Resource

Minor features

Implemented tab highlighting when receiving messages

Bug fixes

Potential fix for the javascript errors Increased text area with multiple lines

Bug fixes

Fixed the versioning in the endpoint urls

Styling fixes

Styling fixes in chat window

Bug fixes

Fixed a few styling issues in the chat screen

Merge window

• Fixed and issue where clicking on a Contact in the Contact Merge window in Lightning Experience would open the Contact record in Classic

Bug fix

• Cases will not always be updated when sending and receiving messages

Assignment rules

• Possibility to make Social25 Case creation follow active Case Assignment Rules

Bugfix

• Bugfix: Outbound messages also copied to SocialPost

Bug fix

• Name field was not correctly set on SocialPost

Upgraded Social Studio support

• Allow to make use of the SocialPost object when this is available

Access token

• Added a global function to retrieve an Access Token

Platform Identifier

• Added the Platform Identifier to the Case object

Custom field labels

• Made changes in custom field labels

Added Sentiment fields

• Added Sentiment Probability field
• Added Sentiment Value field

Improved code coverage

• Added a few extra unit tests

Bug fix

• Bug fix in Merge functionality

Improved Merge

• Switched merge direction
• Added extra search fields in the Account and Contact merge functionality

Permission Sets

• Added some permissions in the Permission Sets

Minor improvement

• Added a migration to set the timestamp on existing messages

Implemted GDPR compliancy

• Added possibility to remove user data from Heroku

Added fields

• Added fields to the HerokuMessage object

Minor improvement

• Changes in Account settings visibility

Default values for custom fields

• Added possibility to set default values for required custom fields

Expanded Link options

• Added 'None' to the linking options

Bug fix

• 'Account' field on Case no longer set when relating a Business Contact

Added fields

• Added 'Reply sent' field on Case, Opportunity and Lead

Removed Opportunity Creation setting

• Removed the Opportunity Creation setting

Changed Link options

• Only one Link option is now possible

Link SocialPersona to Lead

• Possibility to link SocialPersonas to Leads

Changed use of Names

• 'First Name' and 'Last Name' is now used instead of 'Full Name'

Added Permission Sets

• Created Permission Sets 'Social25 Admin' and 'Social25 User'

Bug fix

• Conversation medium is now filled in on SocialPersona

Implemented Record Type support

Added posibility to select default Recordtypes for Account, Case, Lead and Opportunity objects

Implemented Account & Contatc merge

• Added Account and Contact merge functionality

Bug Fix

• Messages are also related to the correct Account and Contact now

Implemented solution when Social Studio objects are not available

• Implemented a custom SocialPersonas object for when the default SocialPersona object is not available
• 'Source' fields on Lead and Opportunity object are also filled in now

Integrated Social Studio

• Implemented SocialPersonas
• Possibility to reopen or create new cases when a new message is sent

Modified the send message endpoint.

• The send message endpoint now accepts an "count_as_inbound" boolean parameter which is added to the auxiliary data of the Heroku Message object.

Bugfixes.

• Fixed an issue that causes audio/x-m4a files to not deliver on WhatsApp for Business.
• Fixed an issue where Twitter file extensions were not correctly set on inbound messages.

Social25 is mainly used for social servicing use-case, but not limited to that functionality. Therefore we made it possible to push messages to your Salesforce environment without delay. This will consume way more API calls but offers up new possibilities on how to interact with the platform.

• Added a direct push for the composite API push method.
• Added new indicators on the conversation endpoint to show how long a conversation will still be valid.
• Added new indicators on the channel to show if HSM messages are supported instead of having this hardcoded.
• Fixed an issue were social post attachment URLs were unsigned instead of signed.

Bugfixes.

• Fixed an issue that prevented customers from sending outbound PDF messages via a specific WhatsApp broker.

Fixed an issue that caused the chat windows to not show the template picker on expired conversations.

• Return the correct platform name instead of the broker name for WhatsApp conversations.

In this release we made the preparation for the release of Google Business Messages and released the renewed Line integration.

• Renewed Line integration.
• Renamed vendor name to a more generic naming convention to allow for multiple platform support.
• Populate file types of the Heroku Message on outbound messages.
• Add support for Google Business Messages via a broker.

Bugfixes and monitoring.

• Added a fix to the Tyntec connector that allows for one webhook per WhatsApp account id, instead of a webhook per number.
• Added a logger statement to monitor how many HSM messages are sent per API call.

Several bug fixes and service stability improvements.

• Support multiple Tyntec Whatsapp account names within the same tenant context by utilising a different cache key for WhatsApp templates.
• Fixed an issue where retrieving stickers if the files were not downloaded caused the conversation endpoint to break.
• Fixed an issue where inbound Tyntec SMS conversations were mapped to the wrong conversation.
• Save the WhatsApp ID on conversation records created before the data mismatch errors fixed 1.7.3 and 1.7.4.

The CM.com integration has been released providing even more options of linking up your existing WhatsApp accounts to Social25.

• Added CM.com WhatsApp connector
• Added CM.com initiate conversation support
• Added CM.com HSM support
• Outbound messages now support the prevent sync status
• Added Facebook template message support without the need of the separate generic API call
• Upgraded Celery to version 5
• Increased threads on web and worker processes
• Fixed an issue where the HUMAN_AGENT tag was not properly applied after 24 hours for business with the tag enabled.

Fixed an issue in the conversations API for sticker retrieval.

• Instead of showing an error if the sticker files can't be loaded don't load a file URL.

Added an option to synchronize custom data on the Heroku Message records.

• Added several performance improvements to the Salesforce sync.
• Added the possibility to store custom data on a outbound message.
• Added the possibility to store custom data on a conversation object.
• Made it possible to prevent synchronizing message to Salesforce if a conversation status is configured to not sync.
• Added custom data to the auxiliary data that is pushed to the Heroku Message object.

It is now possible to initiate conversation in bulk and send messages in bulk.

• Platforms that offer support for the URL message type can now send this via the API.
• Added the new initiate conversation endpoint.
• Added the new bulk send message endpoint.

Extended the Tyntec connect to support an additional platform.

• SMS support via the Tyntec broker has been added to the platform.
• Initiate conversation support for SMS has been added.

Changes to accommodate to the Facebook API guidelines.

• Retrieve templates in larger batches and store for a longer duration of time to prevent expiration if the API call fails.
• Template cache keys are now prefixed based on platform so Tyntec and Whatsapp for Business don't clash.
• Daily refresh of templates does not remove old cache only overwrites.
• A issue in the Facebook API will not reset the template cache.
• Don't parse JSON on GET requests.

We are taking a huge step by providing APIs to have your platforms easely onboarded by the Social25 Salesforce Package.

• Added support for easy onboarding via Salesforce.
• Added support for connected app authentication via Social25.
• Added a tenant detail endpoint.
• Fixed an issue in the maestro_e credit card concealer.
• Fixed an issue in the media_hsm endpoint for Tyntec platforms.

Major performance enhances for the platform and several bug fixes.

• Improved the way we retrieve the messages that need to be pushed to the database.
• Improved the way we retrieve HSM templates and store them.
• Added support for receiving inbound button templates.

Several bugfixes and stability improvements.

• Fixed an issue in the creditcard concealer that accidentally concealed survey URLs and order numbers.
• Fixed an issue in the Initiate Conversation endpoint where a internal server error was raised if a initiated conversations ids already existed due to a mismatch with the WhatsApp ID.
• Fixed an issue in the send media HSM endpoint where the conversation ext identifier did not get updated with the WhatsApp ID.

Bugfixes.

• Fixed a bug in the WhatsApp Business connector where a "+" was added to a national phone number.

Various bug fixes and stability improvements for the WhatsApp for Business connector.

• Fixed an issue for the Facebook connector where URLs are sometimes processed as file.
• Fixed an issue for the Intercom connector where combined text and image sends from social25 were not processed.
• Fixed an issue in the WhatsApp connector via our broker so that the new WhatsApp Media HSM templates are supported.
• Upgraded the Intercom connector to support the new V2 endpoints. In this new version we changed the endpoints that are called to retrieve user details.
• Added support to the Intercom connector for storing conversation or user tags in the auxilirary data.
• In case of a 1006 or 1013 WhatsApp API error we display a message in the text bubble that says that the users does not have WhatsApp or is a unkown resource.
• Fixed an issue for the WhatsApp Business connector for inbound media files where the proxy class was undefined.
• Upon sending a HSM via any supported endpoint a WhatsApp validate call will be performed. The results of the WhatsApp validate will modify the ext_identifier of the user and the conversation. This in turns makes it possible to match inbound messages of WhatsApp to the correct conversation even if the used phone number differs from the WhatsApp id.

Fixed an issue in the WhatsApp connector for Mexican phone numbers.

• In case of Mexican phone number with country code +52 the WhatsApp ID should be +521. In this change we modify the endpoints to utilise +521.

Bugfixes.

• Instead of just calling the validate contact on the media HSM also call it on the standard HSM for WhatsApp for Business.

This release contains a minor bug fix for the Twitter connector and the API and an improvement on the WhatsApp for Business connector.

• Raise a proper 404 not found error in case of sending messages to a non existing conversation.
• Twitter GIFs now receive the correct mimetype so they show up in the chat window.
• Before sending media HSMs via the WhatsApp for Business API we validate the contact to ensure the HSM messages are delivered.
• We've removed the validate method from the initiate conversation as this is now done in the bulk media HSM sent and the send message media HSM endpoints.
• Added the possibility to still validate on the initiate conversation endpoint with the "validate" parameter.

Fixed an issue in the rendering of template on the WhatsApp media bulk HSM endpoint.

• Retrieve templates on the bulk HSM endpoint and render the text.

Bug fixes for initiate conversation on WhatsApp for Business.

• Modified the WhatsApp for Business endpoint to correctly validate the initiate conversation numbers with the WhatsApp for Business API.
• Fixed an issue where certain channels got credit card obfuscation without having the functionality activated.
• Fixed an issue where credit card obfuscation utilised charachters that were not supported in the LWC.

Several changes to the WhatsApp for Business integration have been deployed to support components in HSM messages.

• Return components from the WhatsApp media template endpoint.
• Allow for the use of components in the send message endpoint.
• Added a bulk media HSM endpoint.
• Added text compilation to the bulk media HSM endpoint to support the template message in the chat window.
• Added audio support to the WhatsApp for Business, Tyntec and WhatsApp broker integration.

Bug fixes.

• Fixed an issue in the retrieval of the media_title. In case of PDF files for WhatsApp this value was empty causing the Social25 LWC to chrash.

In release 1.7.0 we've implemented a new channel in the API to connect with a Whatsapp Broker Tyntec directly for customers unable to gain access to the Whatsapp for Business API directly.

• Integrated with Tyntec to offer Whatsapp for Business support with easy onboarding and possibility for quick starting your social servicing on Salesforce.
• Upgraded the platforms to the latests packages for enhanced support and security.
• If a customer removes a message on Whatsapp we will now also remove the message and file from the Social25 system.

We've deployed our extended Marketing Cloud integration, in this integration it becomes possible to register your Marketing Cloud account and use our Social25 MC integration to sent out Whatsapp HSM messages directly from your journey.

• Marketing Cloud integration endpoint.

This release contains a major upgrade of the Salesforce packages utilises for pushing data to Salesforce and an update in how we lock messages.

• Upgraded the Salesforce libraries to the latest versions
• Updated the locking mechanism that marks messages as locked during the message push to prevent messages getting unlocked while not being in the actual push.

Fixed an issue in the status updates for Whatsapp.

• Status updates on the Whatsapp Business API messages now do not causes messages to become unlocked if the business does not allow status updates.

Fixed an issue in the connection to the Whatsapp API.

• If the main proxy connection fails the API call for retrieving templates did not use the fallback proxy connection.

Bugfix for Facebook status updates.

• Fixed an issue where Facebook status updates caused message to be re-synced to Salesforce and the status update to never properly execute.

Update WeChat release.

• To support encrypted end-2-end messaging for WeChat an upgraded version of the integration has been released.
• Integrated Facebook Handover protocol into the standard Facebook connection.

A new channel has been added. A production stable version of Intercom has now been released and is ready for use!

• Production stable Intercom integration released
• Fixed an issue where VCARD messages from the Small Whatsapp for business API were not processed accordingly

Don't have your headphone near? No problem we can now transcribe audio messages for you

• Transcribe endpoint for audio messages (Amazon Transcribe)
• Populate media title and mimetype for files send through Facebook
• Add a supports_gif option to all platforms

Minor API update and bug fix.

• Update the endpoints to pass auxiliary data as JSON instead of a string.
• Fixed an bug where Facebook message echo's got duplicated into the database and pusher.

WhatsApp template messages for Business

• Added the new functionality of retrieving template messages from WhatsApp business accounts

Platform and stability upgrades.

• In this update the underlying stack used on Heroku has been upgraded to the latest verison as well as all the major version releases of the underlying packages used in the application.
• Fixed an bug where whitespaces in filenames on AWS S3 storage caused an issue in the chat window.
• Fixed an bug where a caption of a file caused the file to be sent twice to the chat window.

New push methods available for pushing data to Salesforce.

• In addition to the Bulk API Social25 now supports the REST composite tree API as alternative for synchronizing data to Salesforce environments

Enhanced logging now enables us to do much more pro active monitoring on the platform and keep track of all data flows.

• Added functionality to monitor all inbound message counts and synchronization counts to enhance pro active monitoring on the platform.
• Added the capability to change batch size in real time for all customers.
• Added pagination for the agent list endpoint.

Changed the way messages are forwarded in the forwarding API to make sure you have all the information you need without making additional API calls.

• Changed the format of messages that is forwarded to the customer to be standard for all platforms.
• Added a fix for timezones registered on the created date for customers.
• Updated certificate support for the forwarding API.

Various fixes and sticker support.

• Added sticker support in the chat window. Stickers are now shown as such instead of displaying them as standard images.
• Added media caption support for all channels in the API and inbound requests. All connectors now decided if a caption is supported for attachments and splits them if needed into multiple messages. The API now assumes all channels support captions.
• Fixed an issue where WhatsApp videos where accidentally classified as GIF.

Minor fixes and upgrades.

• Changed the way data is encrypted in the database to support key rolling.
• Increased the number of retries performed after a broken inbound request.

Minor fix.

• Fixed an issue in the upload parameters for Cloudinary.

In preparation of showing when cases expired in the Social25 client the API now provides the expiry date of the conversations in the conversation en

• Show conversation expiry time in the conversations detail endpoint.

Some shiny new features to play with. With the latest addition of sticker support in WhatsApp we decided that we love this feature so much that we needed it as soon as possible! The wait is now over, you can now enjoy all the goodness of stickers that customers send you.

• Added inbound sticker support
• Added support to send an message with an image/GIF or any other type of attachment in one go instead of having to send two messages.

New features and functionalities have been added to the platform. Besides the new functionalities several core stability upgrades have been

• Twitter DM support
• Configure your Twitter account in no-time
• AWS S3
• Restricted Salesforce IP support
• GIF Support
• Chat/Message deletion endpoint
• New V2 whatsapp API with business Whatsapp support
• Restricted Salesforce domain support added to the login

Due to recent updates to the Whatsapp platform we had to implement a new version of the API.

• Implemented a new version of the WhatsApp API

Facebook has changed some rules, so we change some rules as well.

• Made sure we use the user_ref in case of the Facebook Opt-in
• Fixed a bug in the API where we stored profile images double if the url changed but the image stayed the same.

Prevent a race condition in the Facebook connector.

• If the auto-reply was enabled for a Facebook page we experienced a race condition that created two conversations and users. This has been resolved on database level now.
• Push two new fields in the Salesforce Connector (Social25__Conversation_Medium__c, Social25__Conversation_State__c)
• Due to the breaking changes in the checkbox plugin of Facebook we modified our opt-in flow to merge opt-in conversations with the first messages of the user.

Improvements to the Facebook Connector.

• The Facebook Connector now support the Facebook echo protocol. Messages send trough Facebook or other tooling connected to a page can now be duplicated and send to Social25.
• Performance improvements for handling the X-Hub-Signature authentication on the Facebook endpoint.

First major release of Social25. This version is now marked 1.0.0 from now on all changes to the API can be found on the website.

• Message forwarding. By registering a webhook all messages can now be forwarded to and given endpoint. This feature can be leveraged to connect bots, webhooks or third party systems
• A new user profile has been added, using this manager profile you can observe all assigned, closed and queued chats in the system
• The manager profile now has a reporting function to monitor the amount of incoming messages, outgoing messages and some other statistics about the platform.
• New API endpoint for the Facebook connector to enable the use of Facebook message templates.
• Added support for the Facebook Opt-in. Social25 will use an externally provided conversation id in all communication from and towards Salesforce and in the API. This can be used to actively send customers Facebook updates like flight updates, boarding passes or even e-tickets.
• API rebuild to the latest version of DRF.
• Swagger docs are now generated by the API.
• Permissions have been implemented for all users.
• Performance upgrades to the Salesforce validate endpoint.