Release Notes




Fall Release 2021

1. Overview

With the Fall Release 2021, SMS-Magic empowers its customers to drive happier and uninterrupted conversations through a wider range of channels, thereby saving time and effort while conversing. The introduction of the Line channel will widen the scope for the customers to converse seamlessly and delight more service seekers globally.

The Salesforce experience cloud and console improvements will enable you to make the most of every conversation opportunity. Converse one-to-one from your CRM, reach a wider audience with a personal touch, standardize and speed up conversations to empower partners and representatives beyond the walls of your organization.

2. LINE Messaging

With nearly 200 million global users, LINE is poised to be the world’s 20th most popular social messaging channel. With SMS-Magic business solutions allowing you to start business messaging over LINE, you would be able to connect to your customers with this popular chat app globally.

Once you have connected your LINE channel with SMS-Magic and recipients have subscribed to your LINE channel, you will be able to send one-to-one messages or bulk messages to a single LINE recipient or multiple LINE recipients who have subscribed to your channel. You can send text, text templates, or multimedia messages of image, audio, and video with a maximum size of 1MB. Similarly, you will be able to receive those as incoming messages.

Line messaging fall release

3. Salesforce Experience Cloud Improvements

Help partners and representatives beyond the walls of your organization standardize and speed up the conversations

About Bulk Messaging on Salesforce Experience Cloud

Messaging Templates on Salesforce Experience Cloud 

Partner relationship managers need to enable partner representatives to standardize and speed up regular conversations with their common audience.

This feature is enabled for template creation as an innovative feature for community users to manage their templates.

Create new template salesforce experience cloud improvements
Edit template salesforce experience cloud improvement

New Community User Power License for Salesforce Experience Cloud Users

Support for community-specific low-cost user licenses has been newly added so that customers don’t have to buy standard SMS-Magic licenses for enabling messaging capabilities for their community users.

Console Improvements

Respond faster with visual efforts for new customers

Sales and marketing executives need to stay on top of new incoming messages while multitasking at their desks.

Now easily spot and attend to new messages as their tabs color up among dozens of opened tabs to visually alert you.

Highlight Primary Tab on Incoming Message

On the primary tab, a record will be highlighted with a color when a new incoming message is received for that record so that the console user gets notified about new messages and can reply to the message quickly.

Highlight primary tab

4. Make the most of every conversation opportunity

Ability to control and manage Sender IDs visibility

We have added a configuration mechanism for admin users using which they would be able to better control and manage the Sender ID’s visibility across users. Admin users can now assign specific Sender IDs to a user and also define a Sender ID to act as a default Sender ID for that user.

Sender ID & Assignment.

Sender ID and Template Search in Message Composer

Sales and marketing representatives who have hundreds of message templates and dozens of business Sender IDs assigned to them and find scrolling is a difficult way to search a particular message template or Sender ID.

Earlier, it was time-consuming for messaging users to find the exact Sender ID or a template from the list of 100s of Sender IDs/Templates in the messaging composer. To simplify this, we now have a feature allowing messaging users to search for a Sender ID or a template while composing a message.

 Sender ID and Template Search in Message Composer

Visual indicator for queued messages

We have added a visual indicator in the conversation user interface that can help the messaging users identify that a particular message is in a queued state due to throttling or business hours settings enabled at the account.

Queued Message
Queued message visual indicator

Persisting the Converse Inbox Filters and pinned Conversation tabs

The Converse Desk inbox filter, as well as conversation pinned tabs, were getting vanished as soon as the messaging user refreshes the Converse Desk or refreshes the browser tab, or performs logout and login operation. This was leading to an additional effort for users to select the respective filter as well as conversation tabs once again. We have now added functionality that will help the application persist the last opened Converse Inbox filter view as well as pinned tabs at a user level even when the user refreshes the Converse Desk or refreshes browser tab or performs logout and login operation

Converse inbox filter

Bulk-send your messages more confidently using WSYIWSG (What You See Is What You Get) Preview

Marketing and sales representatives use merge fields to personalize their bulk messages.

On the bulk message sending interface, the application displays the message with merge fields (if used) but does not have an option to see the preview of the message against a specific user to see the actual message text after resolving the merge fields. We have now given an option for messaging users to see a preview of the message at a recipient level. This can help users to check resolved message text for some of the recipients and know in advance if any changes are needed in the recipient level data or used merge fields or in the messaging template before sending messages.

Message preview

Drive Uninterrupted Conversation

View Thread of messages in the email notification

Sales representatives who receive new message notifications on their email. Need the context of the conversation to respond better using email-to-text.

Whenever the system sends out an email notification to the respective user based upon the configuration done by the admin user when an incoming message is received.

The notification template was used to display the message text from the latest incoming message 

but was not showing any of the past conversation messages. Because of this, the user receiving the email notification was not able to understand the context of the conversation in order to respond to the message directly from the email. 
So, we have added an option for admin users to configure the HTML template for email notification which will by default have a view of the last 5 messages exchanged with the recipient and thereby giving the context of the latest message.

Message thread in email notification

Notifying Record Owners over email

Sales representatives who receive new message notifications on their email. They need the context of the conversation to respond better using email-to-text.

Sales and marketing teams where multiple employees simultaneously converse with a given customer. In such cases, it is important to send new response email notifications to the right representative to avoid confusion about who should be responding.

Notify record owners over email

5. Known Issues

Sr No  Description
1. Not able to send MMS from all Bulk UI
2. Send button is disabled after adding URL from the URL icon
3.   UI breaks in the conversation box
4. Send button not getting enabled on old compliance org
5. Line channel events for followed not created in the sandbox
6. getDomain API calls are getting made with one click of the URL shortening icon from anywhere



Version 1.68

Patch 1.68.15

Date: 17th August 2021

Bug fixed
  1. Issue: The customer was receiving a component error on the case record page

Fix: A component error was appearing every time the customer was trying to send a message from a case record. The package was upgraded from 1.68.9 to 1.68.14 but the component error was still appearing.

Although the component error was appearing, the customer was able to send SMS but for this, they had to close 4 to 5 error windows. The customer was getting an error as shown in the image.

There was a reference to the attribute “slashTagBackUp” in the JS helper file. This attribute did not exist in the component which was causing the issue. 

To solve this issue, the reference of this attribute was removed from the JS helper file.

Component error on the case record page1
Component error on the case record page2
Component error on the case record page3

Patch 1.68.14

Date: 14th July 2021

Bug fixed
  1. Issue: Customer was not able to install SMS-Magic package on Salesforce essential

Fix
While trying to install the SMS-Magic package on Salesforce essential, the customer was getting an error message, ‘Your request to install package “SMS-Magic Converse Winter2021” was unsuccessful. None of the data or setup information in your salesforce.com organization was affected.’ 

In CampaignManageControllerTest.cls an operation was being run on a Product object which was a Salesforce-provided object. This was causing issues in Salesforce essentials as this object was not present in Salesforce essentials.

To solve this issue, the Product object was replaced with Contact & respective fields

  1. Issue: Error during an attempt to de-reference a null object

Fix
The user was creating a Consent record by calling the Invocable method from the process builder. For Phone type compliance, if the user does not add Sender ID in the process builder & tries to run that process builder, it was throwing an error in the error log object, “Attempt to dereference Null object”.

In the consent service, the Sender ID was being searched & if Sender ID was available then only the channel code was being checked.

In this case, Sender ID was always blank and that’s why it was pushing channel code as null while creating the consent.

To solve this issue, after Sender ID & channel code was checked, a check was added to see if the channel code is null. If yes, then ‘1’ was assigned as a default channel code.

Patch 1.68.12

Date:  17th June 2021

Bug fixed
  1. Issue: User was receiving a Sound Notification for Incoming SMS even when the notification was disabled from the SMS-Magic Converse settings

Fix
The default value of attribute ‘isIncomingVoicePermission’ in conversationView component was set to true. In controller.js the value of this attribute was set only if the corresponding flag value in global settings was set to true. Due to this, the value of the sound notification setting configured in the converse setting was properly populating in the Converse desk component. Thus even if it was set to false, the sound notification was getting played on incoming messages.

To solve this issue, the default value of the sound notification attribute in the conversation view was set to false. With this, the sound notification was not received on incoming messages.

  1. Issue: Admin was not able to access the SMS-Magic Converse Settings

Fix
The customer was not able to access the Converse Settings and was receiving an error, “You do not have a License which provides access to this feature.” in spite of having the required license. 

The code was checking for the profile name of the logged-in user to be “System Administrator”. Thus even if the user had admin privileges, as the profile was not “System Administrator”, the user was not able to access the Converse settings.

To solve this issue, the unnecessary “System Administrator” profile check was removed.




Version 1.64

Patch 1.64.34

Date: 20th Aug 2021

Bug fixed
  1. Issue – Unnecessary continuous debug logs were getting created in the Dev Console

Fix –
In the developer console, there were unnecessary debug logs getting generated from SMS-Magic.

The periodic polling mechanism was generating continuous logs. This call should not have been made for non-licensed users.

To solve this issue, a license check was added in the method ‘conversationsWrapper’ of MessageComposerServreController.cls. and access check was also added in conversationsComponent before calling apex method to fetch the latest messages.

Unnecessary continuous debug logs
Unnecessary continuous debug logs 1

Patch: 1.64.33

Date:  06th Aug 2021

1. Issue: Non-selective query against large object error.
Fix
The customer was receiving the error ‘Non-selective Query’ even after indexing the fields. The query was arising when they were trying to send automated SMSs in the converse app. While querying on SMS history records in the ‘FetchMonthlyMessages’ method of ConsentService class, it was throwing an exception because ‘status != and template!=null’ was used in the clause and to solve the issue. Changes were made in the query. To solve this issue, the method ‘status in (status set) and Is_SMS_Template_Empty__c = false’ was added. != condition was removed from both places.

Patch: 1.64.32

Date: 02nd Aug 2021

Bug fixed
  1. Issue: The fallback Sender ID set for action was not consistent with the UI of the Converse App action

  Fix
When a customer was trying to update the Sender ID on the UI of Converse App Action, it was getting auto-updated to the old one. Existing functionality was that while fetching Sender IDs based on SenderId value rather than Record Id, we were assigned the first element of the list to that Sender ID.

If an org contains Sender IDs with the same alphanumeric value, it was producing a list of Sender IDs with more than one value, and each time the first Sender ID was getting assigned to Converse app action.

The proposed solution was that instead of fetching Sender IDs based on values, now it would be fetched based on Record Ids, so that every time a unique Sender ID will get produced.

Senderid set actions was not consistent
  1. Issue: Unable to Send MMS Via Bulk SMS button

Fix
The customer was facing an issue where the users were unable to attach media while sending messages via the Bulk SMS Button. 

To solve this issue, implemented negation for the ‘AllowToChangeTemplateSelection’ variable.Negation for attribute ‘AllowToChangeTemplateSelection’ was missing in the ‘class’ attribute of the button element. A class with the name ‘slds-is-disabled’ was getting assigned to the button element thus the button was clickable yet shown disabled.

Unable to send bulk mms
Unable to send bulk sms via bulk sms button
Unable to send bulk sms via bulk sms button issue

Patch 1.64.29

Date: 14th June 2021

Bug fixed
  1. Issue – Issue of SMS getting sent to duplicate number in Converse App >> Bulk Campaign

Fix
ID of the converse app task was not passed to batch before execution. Thus the required check for duplicate numbers was not happening.

To solve this issue, the ID of the Converse App task was passed to batch ensuring check for duplicate numbers. With this, sending messages to duplicate numbers was avoided.

  1. Issue – Need to pass the record ID parameter to the injection service:CustomConsentService

Fix
The client wanted to check for field on the record and based on that they wanted to manage the Consent record. For customization, the case record ID was required to be passed to the custom class (“CustomConsentService”) at the injection point.

At the injection point, the record ID was passed to the custom class (“CustomConsentService”) to support the customization case.

Patch 1.64.27

Date: 24th May 2021

Bug fixes
  1. Issue: Customer was getting an error while sending SMS from Bulk Campaign from the Converse App

Fix
When any object from parent-child relationship was configured in the Message Configuration Object (MOC), the package code was not able to resolve the relationship to get the value of the opt-out field. Due to this, the customer was getting an error while sending SMS from Bulk Campaign from the Converse App.

To resolve this issue, the code was updated to resolve the relationship and get the value of the opt-out field as expected.

  1. Issue: Customer was facing an issue with lookup object on SMS consent record

Fix
The last updated record ID was getting attached to each consent record that was created. This was causing the mentioned error.

To solve the issue, the unique record ID which is fetched from input consent data was updated.

Patch 1.64.24

Date: 17th May 2021

Bug fixed

Fix: Conversations Lightning component was not loading messages properly. The customer was facing an issue where the messages before 16th march were not loading on the conversation component on the record page layout. In message.cmp there was an unnecessary use of the method sanitizeUrl() that was causing an issue while parsing the object instead of a string.

To solve this issue, we removed the unnecessary use of the method. Used it at a relevant place from a security perspective.

Conversion lightning component not loading

Patch 1.64.23

Date:  5th May 2021

Bug fixed
  1. Issue: Customer asked for customization for SenderId Injection point

Fix: Customer wanted Sender IDs to be available in a specific sequence.

In the injection point, the data was run through the “transformData” method which was causing an issue in implementing the desired customization for the customer.

To address this customization requirement from the customer, an ‘IF’ condition was added where a deprecated flag ‘smagicinteract__Canned_Responses_Only__c’ from the ‘globalSetting’ was used. If it was true then the data was not transformed, if false, the functionality was executed as usual.

Patch 1.64.17

Bug fixed
  1. Issue – Consent was not getting created for SMS channel via process builder

Fix -Customer had configured a process builder named “Lead Driven Processes on Lead” to create consent for SMS and WhatsApp channel when the conditions were fulfilled. This was done by the apex class coming with the managed package.

It was working fine, the customer could see that consent entries were getting created for the SMS channel till 17th March 2021.

Later, it only created consent for the WhatsApp channel.

The customer could see an entry created under the error log at the same time with an error “Attempt to de-reference a null object”.

  1. Issue – Consent was not getting created even when the criteria were met

Fix – A process builder was created for consent creation that calls apex” smagicinteract__ConsentService”, when the criteria of the checkbox “Consent to contact via Whatsapp” getting checked was met. But the number in the WhatsApp number field was not opted-in (Condition 2 and 3 in the process builder)

  1. Issue – 

Issue #1:

When any user was logging in and selecting any Sales or Service Path where the utility bar component was assigned, the tab at the top showed “Converse Desk|SMS-Magic”. The client users were getting confused with this and so the client wanted this to be resolved.

Issue #2:

Misspelling in the error message that was getting displayed.

If the user does not have any license then they were getting an error message, “You don’t seems to have required license to send SMS or MMS”.

Here, in the error message, there was a spelling mistake; it should have been ‘SEEM’ and not ‘SEEMS’.

Issue #3:

The ‘Send SMS’ button was configured on Lead, Opportunity, Account, and Case object. When the customer user was clicking on the button, it was not fetching the mobile number to send the SMS.

If the VisualForce pages assigned to the Send SMS button were edited and the phone fields were added to it, it was fetching the phone info. However, the client did not want to add any manual steps to update the VisualForce page script.

As per logic, the Send SMS VisualForce pages should have displayed the phone fields configured in the MOC, however it was not working.

Fix

Issue 1 – Added a condition in ConversationView to skip the execution of setting title if SF1 was not found in the context

Issue 2 – Custom Label was changed

Issue 3 – Removed the condition from LightningBulkSMSController which was limiting the selection of Phone Field from MOC configured.

  1. Issue – Issue with Lightning Tab and with Send SMS button

Fix – 

Issue 1:

When any user logs in then selects any Sales or Service Path where we have assigned the utility bar component, the tab at the top shows “Converse Desk|SMS-Magic”.The user are getting confused with this and client wants this be resolved asap.

Lightning app name: Sales Path (Sales Management app for Lead Gen)

Issue#2:

We have configured Send SMS button on Lead, Opportunity, Account and Case object. When we click on the button, it is not fetching the mobile number to send the SMS.

Patch 1.64.12

Date:  24th Feb 2021

Bug fixed

Issue – The 24hr Conversation Window was not working properly on Facebook and WhatsApp

Fix

The 24hr Conversation Window was available on One record with the same mobile number and Sender ID. However, it was not available on another Object. The system was checking for the 24hr window on the basis of recordID, phone, Sender ID, and channel. The recordID was causing the issue.

To solve this issue, recordID was removed from the key. With this, the 24hr Conversation Window started functioning properly on WhatsApp and Facebook both.

Patch 1.64.10

Date:  20th Jan 2021

Bug fixed

Issue – The consent records were not getting created with country code prefix

Fix

Consent records were not getting created with country code prefix for those who have set a specific country as messaging destination (other than the ‘All’ option). Consent records and compliance enforcement functionality was not working as expected.
To solve this issue, security enhancements were done in the country-specific consent recording.




November 2020 Release

This article covers the major upgrades on the SMS-Magic Interact extension of Zoho CRM as a part of November 2020 Release.

Key Features

The November 2020 Release is focused mainly on the Converse Desk to help businesses establish a dialogue with their customers. We also have a new channel added to your communication options – WhatsApp!

Converse Desk

Converse Desk provides an intuitive, easy-to-use Inbox style user interface; making it simple for you to start one-on-one messaging with little or no training. Connect with your leads, contacts, and phone numbers in your custom modules without having to leave the Zoho CRM. The Converse Desk features intelligence that guides users to effectively manage and respond to any number of messaging conversations.

Key Converse Desk Features Include:

  1. Converse Desk in Zoho CRM – One-click access to launch conversation with customers from standard and custom modules within the Zoho environment.
  2. Multi-channel Support – Reach out to customers on the channel of their preference. Send text and media messages on both SMS and WhatsApp.
  3. User Friendly Inbox – The new and improved Inbox provides an intuitive interface to access messages, track conversations and quickly respond to messages. 
  4. Initiate Conversations with Your Zoho CRM Records – You no longer need to go to SMS-Magic Web Portal to send one-on-one messages. Now, you can send messages to Zoho CRM Leads, Contacts, and phone numbers in your custom modules directly from Zoho CRM.
  5. New Chat Window for Interactive Conversations – Converse with your customers in a familiar way; using the new chat window that mimics texting on your phone.
  6. Team Inboxes – Admin can monitor their teams’ conversations.
  7. Assign Customer Conversations to Team Members – Admin users can easily assign conversations to any team member.
Zoho release 2020

Communication over WhatsApp

Introducing WhatsApp support; a new channel for you to reach out to your customers from the SMS-Magic Web Portal.  Use the same familiar interface to message your customers in WhatsApp!

Establish Communication over WhatsApp:

  1. Record Your Customer Consents – Record your customer consent to reach out to them on WhatsApp.
  2. WhatsApp Conversations – With the same simplicity as SMS, you now can have one-to-one conversations with your customers on WhatsApp. Your customers can initiate conversations directly, or you can initiate conversations via a registered WhatsApp message template.
  3. Send Text or Media via WhatsApp – With WhatsApp, you can send text and media messages to your customers. And you can personalize your messages with emoticons too.

Functional enhancements

Bulk SMS to Custom List Views

Send SMS to Custom List Views – This feature allows you to send messages to more than 100 records at one time directly from Zoho CRM using the Custom List Views of the CRM modules.

Technical Enhancements

SSO to SMS-Magic Web Portal from Zoho CRM

No more Login screens!  Using Single Sign On, you will be able to directly navigate to the Send Bulk Messages user interface directly from the Zoho CRM when you click the Send SMS button. 

Removed Email Dependency for Sales Signal Notifications

An Email ID is no longer required in order to receive incoming message notifications for Sales Signal Notifications.

Related documentation

For more information on the above-mentioned features and latest enhancements on SMS-Magic Web Portal please refer to the below links:

SMS-Magic Interact for Zoho User Guide
Release Notes of SMS-Magic Portal – November 2020 Release
SMS-Magic Portal User Guide




Grant Access to Custom Settings – Critical Update

Salesforce Spring’20 Critical Updates

Users without the Customize Application permission can read custom settings using APIs that are provided by Salesforce. This access will be revoked as part of a critical update that is scheduled to be rolled out with the Spring ’20 release on January 3, 2020.After the critical update, users without the Customize Application permission no longer can access custom settings. You can read more at critical update.

SMS Magic Impact

This critical update will affect SMS-Magic capabillities like sending messages, receiving incoming messages, etc. If you are unable to send messages or see any error message shown in the below example, please check the debug logs.

This can be checked by debugging logs. This can be tested by sending a SMS from Salesforce from any source. The expected error for the aforementioned issue would display empty API Key. A sample log has been shared below.

08:51:23.27 (168325762)|FATAL_ERROR|
System.SecurityException: Empty key Class.System.Crypto.
generateMac: line 20, column 1 Class.smagicinteract.
SMSUtility.getSignatureHMAC: line 250, column 1 Class.smagicinteract.
SMSUtility.makeHTTPCallout: line 294, column 1 Class.smagicinteract.
SMSUtility.sendSMSHTTPRequest: line 119, column 1 Class.smagicinteract.
SMSUtility.callSMSAPI: line 91, column 1 08:51:23.27 (168341216)|FATAL_ERROR|
System.SecurityException: Empty key Class.System.Crypto.
generateMac: line 20, column 1 Class.smagicinteract.
SMSUtility.getSignatureHMAC: line 250, column 1 Class.smagicinteract.
SMSUtility.makeHTTPCallout: line 294, column 1 Class.smagicinteract.
SMSUtility.sendSMSHTTPRequest: line 119, column 1 Class.smagicinteract.
SMSUtility.callSMSAPI: line 91, column 1 08:51:23.168 (168349756)|CUMULATIVE_LIMIT_USAGE 0

Changes to be Made

  • You must manually assign the “View All Custom Settings” permission under Profiles / Permission of users.

OR

  • You must assign SMS-magic packaged permission set “SMS Converse conversation user” to give access to only SMS-magic custom settings. [To get the desired package version link, Please reach out to us at care@screen-magic.com]



Version 1.60

Patch: 1.60.75

Date:  17th Aug 2021

Bug fixed
  1. Issue: The customer was facing an issue while using the Injection code and the code was not working.

 Fix –
Sender Id Allocation – It allows students from multiple Accounts to send texts to – which was considered brand bleed and the aspect was unique sender number by Account / Partner and separate/unique content by Account / Partner. It was showing all Sender Numbers that were purchased under the Wiley Account as Sender Numbers was restricted to one sender number that applied to the Account associated with the students chosen for bulk SMS. 

Therefore, the customer received the underlying code/page/component (from package code) and applied these 2 restrictions, and used the same Bulk SMS Sending Page. The design injection points were not enabled for the bulk components. 

To solve this issue the backward compatibility (upgrade scenarios) and use cases of other customers was kept, the record id check was not removed and an alternative flag was added. The injection point was functional for the bulk interface as well and a certain flag was enabled.

Patch: 1.60.74

Date: 29th July 2021

Bug fixed
  1. Issue: Customer was facing Issues with Auto Append text in compliance

Fix
When the customer was trying to create an SMS History record via Process Builder, in sendSMSTriggerhelper .sendSMSBeforeTrigger(), the source was checked in both fields. In this case, the source had an automated message & for the automated message the opt-out instruction message was appending. In the sendSMSAfterTrigger() method, the template was resolved by passing automatedSmsList() to resolve the template method. While adding values in automatedSmsList, it was checked if SMS Text is null & that condition was falling before triggering the appending opt-out instruction. That’s the reason it was sending a null text in SMS Text. 

To solve the issue this method was removed, call to the ConsentService.append Opt-Out Instruction() method from before trigger & added in after trigger & passed the list which gets after resolving the template. The values were upserting in the SMS History record. 

Auto Append text in compliance
  1. Issue: Name field from SMS History object was blank and Automation was triggered from Converse App

Fix: Here, the name field was auto-populating. To solve this issue added a name field in the messageAutomationHelper class

Name field blank sms history object
fix business phone field empty step 1
Fix business phone field step 2
Fix business phone field step 3

Patch 1.60.73

Date: 24th June 2021

Bug fixed
  1. Issue – Last Incoming SMS lookup was not working

Fix
When a new conversation was created by the first incoming message, the code was populating the lookup of the last incoming message record. But if the conversation existed (created due to the first outgoing message), the code populated lookup of the last outgoing message only.

To solve this issue, the code and login in the ‘ConversationService’ class were updated to populate both fields ‘Last Incoming Message’ and ‘Last Outgoing Message’ for every corresponding incoming and outgoing message.

  1. Issue – Customer was getting a component error while accessing utility bar item

Fix
This was an intermittent issue, occurring when a method of a service component ‘conversationDataService’ was called. The issue was occurring because intermittently, the code was not able to confirm the availability of component ‘conversationDataService’; and when its method was called the component error was thrown.

To solve this, a check for the availability of the service component ‘conversationDataService’ was added before calling its method. That way, for any reason, if the service component was not available, its method would not be called and the component error would not be thrown.

Patch 1.60.71

Date: 9th June 2021

Bug fixed

Issue: Injection code not working as expected

Fix:
Customer had implemented customization to show specific sender IDs in SenderID dropdown while sending messages. This worked as expected for interactive interfaces. The customer wanted the same functionality to be available on the bulk interface as well (bulkSMSComponent).

By design, the injection point was made available only for interactive interfaces. For that reason, there was a check for the record ID added at the injection point. In the case of bulk interface, record ID was not available, thus the logic of injection point did not work and the implementation customization did not reflect.

To solve this, two specific configurations were made to make the injection point work for bulk interfaces and to maintain backward compatibility:

1] Enabled the injection point for Sender ID customization: In globalsetting (custom setting) the value of field “Max SMS Text Length” was set to “101”

2] Enabled the injection point for Template customization: Enabled the flag “Enable Internal Note”

Patch 1.60.70

Date: 8th June 2021

Bug fixed
  1. Issue: Incoming SMS were not getting pushed to Salesforce

Fix
The incoming SMS were not getting pushed to Salesforce. On incoming SMS, a user from the previous outgoing message was identified, and that user was assigned as the owner of the new incoming message. Since the user was inactive, Salesforce was not allowing to create the SMS History record with the inactive user as the record owner. On incoming message, while doing a lookup of the previous outgoing message, if it was found that the owner of that outgoing message is inactive, the owner of the new incoming message was set to the OAuth user. This solved the issue.

  1. Issue: Uncaught Error in $A.getCallback() [Cannot read property ‘getInboxFilter UnreadCount’ of undefined]

Fix
A data service component was passed as a parameter while calling the helper function in the AURA component. With the Summer ’21 update that was deprecated, it was causing the error, where the property ‘getInboxFilter UnreadCount’ was not getting read.

To solve the issue, the parameter was removed and the respective data service component was identified in the corresponding helper method.

Patch 1.60.69

Date: 19th May 2021

Bug fixed
  1. Issue: In the SMS-Magic Converse App, the Bulk Campaign was getting stuck in a running state

Fix
In the SMS-Magic Converse App, the Bulk Campaign was getting stuck in a running state. In the Details section, List View details were not getting displayed for both the Bulk Campaigns. This was due to the wrong formation of the List View clause query. 

To solve this issue, the List View query was modified by adding ‘from’ + ‘object name’ in the ‘where’ clause of the list view.   

  1. Issue: Conversations were not getting created for WhatsApp automated messages

Fix
Conversations were not getting created for WhatsApp automated messages. The automated messages triggered through the customer’s WhatsApp number were not creating conversations because of which they were not showing on the Converse Desk. There were entries created in the error log with the error ‘Empty SMS List’.

To solve the issue, the condition where we were checking SuccessList size for callout, was removed. Now Conversation Association is happening as expected in all cases and in the SMS-Magic Converse App, the Bulk Campaign is not getting stuck in the running state.

Patch 1.60.68

Date: 26th April 2021

Bug fixed

Issue – Messages were reaching the SMS-Magic server even when the ‘Disable SMS’ option on Trigger was set to ‘1’ by the client.

Fix
Messages were reaching the SMS-Magic server even when the ‘Disable SMS’ option on Trigger was set to ‘1’ by the client.

SMS records with the ‘Disable SMS’ option on Trigger was set to ‘1’ and were added to the failed SMS list. But they were also added to the SMS list which we are sending to a callout in the sendMessage method of SMSUtility class. That’s why they were reaching the server.

To solve the issue, the if-else condition was added: ‘If disable on the trigger is 1 then add to the failed list else add to the callout list’. With this, the messages stopped reaching the SMS-Magic server when the ‘Disable SMS’ option on Trigger was set to ‘1’ by the client.

Patch 1.60.67

Date: 26th April 2021

Bug fixed

  1. Issue: Get conversations function was calling for update/insert of the recently used filter on the converse desk.

Fix
In the conversation controller class, get conversations function was calling for update/insert of the recently used filter. Due to this, Apex job was getting created for every filter selection on Converse Desk. That was unnecessary.

To solve this issue, the logic was changed so that the new apex job enqueued only when required.

  1. Issue: Incoming text notification was not working properly.

Fix
Incoming text notification was not working. In the Lightning environment, pushtopic subscription was supposed to happen via “empApi” which is integrated into the “streamingDataService” component. But, empApi was forced-disabled due to which the incoming text notification was not working.

To solve this issue, the forced disabled state of empApi was removed so that it would function as expected in the Lightning environment.

Patch 1.60.62

Date: 12th March 2021

Bug fixed
  1. Issue – Unable to create manual consent record from consent object, when contact is entered

Fix
Unable to create manual consent record from consent object, when contact is entered. In complianceService class, the GROUP BY clause is used to fetch the phone fields. In this case, the customer used the FORMULA field as a phone field to fetch the phone fields. Salesforce doesn’t support the FORMULA field to be grouped. To solve this issue, the GROUP BY clause was removed.

Patch 1.60.60

Date:  23rd Feb 2021

Bug fixed
  1. Issue – MMS messages were getting delivered even after they were Opted Out by the customer

Fix
The customer had opted out of MMS messages in the contact object, yet they were receiving them.

In the MMSDetail trigger, SMS History records with MMS Type and failed status was not checked, and so the corresponding MMS records were triggered even after customers had opted out. To solve this issue, a check in MMSDetail trigger for MMS Type was added.  

  1. Issue – When the User was trying to write an Internal Note from the Conversation View on the Record Detail page, it was throwing an error message

Fix
When the User was trying to write an Internal Note from the Conversation View on the Record Detail page, it was throwing an error message: Conversation: id of incorrect value: 00Q.

To solve this issue, the Internal Notes tab in the composer component in the Message Notification component was disabled, based on the origin Name value in requestContext.

For “Conversations” component changes are made in the ‘composerWrapper’ method of ‘MessageComposerServerController.cls’. Value of flag for ‘isInternalNoteEnabled’ is set to false if the the object name retrieved from available record id is not ‘smagicinteract__Conversation__c’

  1. Issue – After an upgrade to the package from 1.46 to 1.60.56, the Converse App tab was opening in full-screen view.

Fix – 
After an upgrade to the package from 1.46 to 1.60.56, the Converse App tab was opening in full-screen view. The tab notification panel was not accessible once the user navigated to Templates in the converse App. This was because the wrong event was used to replace the deprecated ones. To solve the issue, the “lightning:navigation” component was used to navigate from one component to another component in the lightning environment.

  1. Issue – Send Bulk SMS button on maps was throwing an error, ‘Invalid ID’ 

Fix – 
When the customer was using the “Send Bulk SMS” button on the maps app, they were getting an error, “Invalid id: 034A00003Dp7yzQAB”.

This issue was occurring because the package code was trying to trim the list of ids, assuming that the list has square brackets at first and last position. But in the real scenario, the square brackets are not present, thus the trim function was causing an issue. To solve this issue, the list of ids were trimmed based on the presence of square brackets. Used Substring function on ‘idList’ string only if square brackets are present in the string. Bulk messaging functionality now works flawlessly for normal list view and communities.

Patch 1.60.57

Date: 2nd Feb 2021

Bug fixed
  1. Issue – While creating a template, the customer noticed that 2 SMS credits were getting consumed for a message that was less than 160 characters in length. (158 characters with space). Ideally, if a message crosses 160 characters, it should consume 2 SMS credits. 

Fix
While trying to send the same template from the detail page, it was correctly showing that 1 SMS credit will be consumed. 

This was happening because of the wrong syntax that was used where the text length was compared with a single message length (160 characters).

To solve this issue, the syntax was corrected and hence the comparison was correctly handled. Now, while creating a template, if the message length is below 160 characters, only 1 SMS credit is being consumed.

Patch 1.60.56

Date:  6th January 2021

Bug fixed
  1. Issue – A component error was occurring while creating a template in the Converse App or while accessing the Converse App.

Fix – 
Initially “force:navigateToComponent” was used to navigate from 1 Lightning component to another Lightning component. It was throwing an error while navigating to the Converse app.

To solve this issue, we changed “force:navigateToComponent” to “lightning: navigation” as suggested by Salesforce Support.

Patch 1.60.55

Date:  4th Dec 2020

Bug fixed

1.Issue – The system was throwing a ‘Component error’ when the Converse App was accessed with any console other than the SMS-Magic app

Fix – 

When the “Converse Apps” tab was accessed with any console app other than SMS-Magic and the user was trying to create a template, the system was throwing a component error. This was hampering the user experience and functionality. This was NOT observed when the Converse Apps tab was accessed within the SMS-Magic app. Create template action was navigating the user from one component to another. For this, we used the “force:navigateToComponent” event. This event was not handled properly in other console apps, since Salesforce was advocating the use of the “lightning:navigation” event instead of the “force:navigateToComponent” event. 

To solve this issue, the “lightning:navigation” event was used instead of the “force:navigateToComponent” event to navigate from one component to another. 

2.Issue – Not able to open PDF from converse desk via WhatsApp

Fix – 

The issue was observed with WhatsApp Addon. When a customer received any incoming message with a PDF file, a message was displayed as ‘Broken UI’ and the user was not able to access the PDF file in the message. We embedded the PDF file into an iFrame to enable the preview of the file and to allow the user to click on it. With recent security enforcements, Salesforce deprecated embedding external URLs into iFrame.

To solve this issue, we changed the implementation. Instead of embedding the PDF in an iFrame, we are now showing a download button to let the user click on it and download the PDF.

3.Issue – Exception in Migration Batch; 11th step in the migration failed 

Fix – 

After upgrading customers from any version below 1.5 to 1.60, migration steps were required to populate phone number and sender ID values in the newly created conversation records. The 11th step in the migration failed with an error. An external script was required to be run to achieve the required migration.

To solve this issue, the code of the migration step was updated to properly resolve fields and proceed with the data population required for migration.


Patch 1.60.54

Date:  12th Nov 2020

Bug fixed

1.Issue –Callout Exception error – when multiple jobs were queued, after the first job callout, the next jobs were failing due to DML being in progress.

Fix – 

To address the CPU timeout issue during the bulk campaign, the approach to break the records count into multiple batches was changed. With this, each batch was getting processed separately. While doing this, after the first batch callout, DML was attempted to update the lookups for the records. At the same time, the callout for the next batch was getting processed, which failed because of the DML.

To solve this issue, the DML setting is changed; now the DML for updating lookup is attempted only after completion of all callouts.

2.Issue – Automated SMS not being sent as the system was throwing an error of ‘available jobs limit consumed’ 

Fix – 

The customer was not able to schedule a bulk campaign (converse app) as the system was throwing an error of ‘available jobs limit consumed’. For instance, although the customer had consumed only 97 out of 100 available scheduled jobs in his org, the system was throwing an error of ‘available jobs limit consumed’. 

This issue was due to the check for the max scheduled jobs in the org, which was 95 instead of 100. 

To solve this issue, the check for existing scheduled jobs was changed from 95 to 100. Now, even if there are 99 scheduled jobs present in the org, the user is able to consume the last one to schedule the bulk campaign.

3.Issue – Bulk campaign from the Converse App was not running properly 

Fix – 

The customer had created a lookup of a custom object (say object A) with another object (say object B). Object A was configured on the MOC, and the SMS opt out field of Object B was configured as the opt out field for Object A via lookup. While identifying the opt out value of the record, the error was logged in the debug log. There was no visual indicator for the error.

Because of incompatible syntax, the code was not able to resolve the SMS opt out field configured via lookup. This was throwing the error.

To solve this issue, we updated the syntax/code to properly resolve the lookup field value and obtain the boolean value of the opt out field.


Patch 1.60.53

Date: 26th October 2020

Bug fixed

1.Issue – Apex CPU Time Limit was getting exceeded 

Fix:

Due to heavy processing on each outgoing record, the Apex CPU time limit was getting extended. So while sending bulk messages it threw a CPU time limit exception. To solve this issue, we processed the bulk messages asynchronously in batches of 50 if the count exceeded 100 records.

2.Issue – Permission error was getting displayed in Utility Bar and Converse Desk

Fix:

The users have access to the case object but not to the lead object. So, while reading messages of the case object, users were facing permission error of the lead object.

When the Utility bar is opened we check for conversations and while checking conversations we fetch all the MOC records. We were not checking whether the MOC record is having permission or not. To solve this, we added a check for permission of objects configured in the MOC.

3.Issue – The “Do not send Confirmation” checkbox was misbehaving; a confirmation message was being sent.

Fix:

The user was able to save the consent record without changing the previous consent status. Since the status was not changed, the old value of the “Do not send confirmation message” checkbox was referred and a confirmation message was sent to the record. To solve this, we added a validation on the consent edit UI. The “Save” button is disabled until the consent status is changed.

4.Issue – Issue with Bulk SMS for Partner Community

Fix:

The processing time required for each message was high. To solve this, we processed the message asynchronously if the bulk count exceeds 100 records.


Patch 1.60.52

Date: 6th October 2020

Bug fixed

1.Issue – The label name in the ‘To’ field of the Conversation Component was not getting displayed properly. 

Fix:

The user was not able to see the Lookup values in the ‘To’ drop-down field in the Conversation view while sending a message. To solve this issue, we showcased the label of the lookup field created on the MOC object instead of showing the label of the lookup object name.
e.g.
MOC Object = Contact
Lookup field on Contact = AccRelatedToContact (lookup of account)
Before fix : Contact > account > phone field
After fix : Contact > AccRelatedToContact > phone field

2.Issue – Record count under Campaign was not getting reflected as expected

Fix:
The record count under campaign was not getting reflected as expected, i.e., as per the actual field selected. Even if the custom field created by the user was selected instead of the default field in MOC, while running the campaign it displayed record opt-out count based on the default field & sent messages based on the custom field. Ideally, it should show the count based on the field that is used in the MOC, i.e., the custom field. It was referring to the default field and not the custom field because the hardcoded value of the default opt-out field was getting passed to record the count. To solve this, instead of passing the default value, we started fetching value from MOC & passed it for accurate record count.

Improvements

N/A


Patch 1.60.51

Date: September 16, 2020

Bug fixes

1. Issue: Bulk Action from Converse App remains in Running state for Object with Spaces in the name

Fix:
When users run a bulk action in the Converse App on an object, which has multiple words in the name field (space between the object name), the status would always remain in Running state. e.g., Student_Section__c. To solve this issue, we used a substring function to split the query that we receive from Salsforce.

Improvements

N/A


Patch 1.60.50

Date: September 08, 2020

Bug fixes

1. Issue: Issue with the SF campaign.

Fix:
Whenever customers tried to send messages through Campaign with both, contact and a lead member, the SMS history for contact reached the portal but not the lead. We executed Campaign Batch jobs differently for both, Lead and Contact, to solve this issue of multiple primary objects.

2. Issue: Issue with SMS Scheduled Record.

Fix:
When the message is scheduled through a Single or Bulk SMS button, SMS Scheduled record is created with all the field values such as SenderID, Text, etc. But when we scheduled the message through the Converse App, it created an SMS scheduled record without the SenderID. To solve this, we populated the fields required by the customer so that they can create a correct report on the SMS schedule object.

Improvements

N/A


Patch 1.60.49

Date: August 25, 2020

Bug fixes

1. Issue: Primary object lookup happening intermittently for incoming messages.

Fix:
Removed the unwanted, unformatted mobile number check from the logic of the primary object lookup which was causing this issue. With this fix, the primary object lookup should happen for each incoming message.

2. Issue: While sending outgoing messages from the record detail page conversation view, the direction field was not getting updated correctly in the conversation object.

Fix:
As a part of performance enhancement, we had modified conversation assignment logic because of which the last message direction field in the conversation object was not getting updated for the record detail page. As a part of this fix, we have corrected the logic so that it updates the last message direction field in the conversation object only after the conversation assignment is done.

Improvements

N/A


Patch 1.60.48

Date: August 19, 2020

Bug fixes

1. Issue: Component error for the non-SMS-Magic users. This is due to the latest critical update imposed by Salesforce on 9th August.

Fix:
The issue was on the Conversation View on the Utility Bar and Conversation View on the record detail page. Made changes in the notification manager component to handle the exception thrown by Salesforce and show the correct notification to the users.

2. Issue: Utility bar back button was not working properly.

Fix:
Here the back button of the utility bar was not functioning properly. In the case of a closed conversation’s component, the selected RecordId was coming intermittently as null. So removed the condition and replaced the logic which will include the button name to decide whether to close the tab or take the back action.

3. Issue: New conversation created for every incoming SMS.

Fix:
The issue happened because the conversation logic code was reverted to 1.58 implementation from the routing logic. The root cause for the failure of older conversation logic implementation was that 1.58 did not have the country prefix in the SMS History whereas versions 1.59 and above have the country prefix in the SMS History. We implemented the logic of 1.58 to solve the issue.

4. Issue: Converse bulk issue.

Fix:
When we call the API while running the bulk campaign, Salesforce returns fields of the object in Query. So, we were getting a few unnecessary fields in the query. This was throwing an error in Apex Job & status was not changing. To solve this, we split the query into 2 parts (Left & right side of the “FROM” field). With this, the unnecessary fields from the query from Salesforce were ignored and the issue was resolved.

5. Issue: Error while sending SMS from the Converse app.

Fix:
This issue was there because a static variable was used to scan the depth of the master-detail relationship. When multiple records got edited at the same time, this static variable overflowed to scan the fixed depth of the master-detail relationship, and thus the issue occurred. We replaced the static variable with a normal variable.

Improvements

N/A


Patch 1.60.47

Date: August 04, 2020

Bug fixes

1. Issue: Utility Bar Issue- On load dropdown, the selected value is not getting displayed in Chrome, it’s working in Firefox.

Fix:
When the Utility bar on sales console is enabled, read/unread drop-down appears. That dropdown was blank for Chrome, it did not display the required values. The utility bar showed blank values on the initialization of filter dropdown in the Chrome browser. We fixed this by making HTML changes.

2. Issue: Utility Bar issue- User got redirected to the Conversation Inbox when clicked on CRM action (i.e view contact, view lead, etc.)

Fix:
Corrected the conditions to check whether the utility bar is working in contextual scenario and implemented fail-safe ‘try:catch’ in ‘StreamingAPIController.cls’

Improvements

N/A


Patch 1.60.46

Date: July 28, 2020

Bug fixes

1. Issue: Users Getting Error “Object Name: Organisation”

Fix:
Fixed the issue where users got an error “Object Name: Organisation” does not have permission to read fields.

The Error Occured when users click on Conversation Record.

2. Issue:Related conversations are not loading on Converse Desk.

Fix:
Fixed the issue where related conversations did not load in the Converse Desk.

Improvements

N/A


Patch 1.60.45

Date: July 27, 2020

Bug fixes

Issue: Utility Bar Notification Not Working.

Fix:
Fixed the issue where the users did not get notified when an incoming message was received. The users needed to refresh the page to see the notification.

Improvements

N/A


Patch 1.60.44

Date: July 23, 2020

Bug fixes

1. Issue: ApexCPU Time out error.

Fix:
Fixed the issue when

  • Customer tried to send messages to bulk records. (He has created a list view and tried to send messages to all records.)
  • Process builder triggered bulk messages (190+) for given conditions.

2. Issue: Unable to use ‘Time’ datatype fields while sending messages using templates.

Fix:
Fixed the issue where the customer was not able to use “Time fields” while sending the messages. For a custom created template with a time field, the user received an error message “Invalid date/time: 00:00:00:000z”.

3. Issue: Error message “Attempt to de-reference a null object”.

Fix:
Fixed the issue where the customer was getting “Attempt to de-reference a null object” when a template is selected while sending a message from Send Bulk SMS or Send SMS button, if Auto Append interval was enabled.

Improvements

N/A


Patch 1.60.41

Date: July 06, 2020

Bug fixes

1. Issue: Some conversations not visible under Converse Desk.
Messages for particular records were not visible in Converse Desk.

Fix:
Added check for Access check for Push Topic in professional org.

Note: Users need to add the domain URL manually in remote site settings. Then lookups and list views will be accessible and everything work as expected.

Patch 1.60.40

Date: July 01, 2020

Bug fixes

1. Issue: Error while accessing Converse app.
All the users faced the below error while accessing the converse app. “Aggregate query has too many rows for direct assignment, use FOR loop” The issue occurs when customers have more than 200 converse app actions for each converse app.

Fix:
The count will be displayed as 199+ if the number of actions exceeds 200 records. Although, users can always open the converse app to view the exact amount of actions present in the app.

Improvements

N/A


Patch 1.60.38

Date: June 30, 2020

Bug fixes

1. Issue: Component error.

Fix:
Fixed the intermittent issue where the customer was facing a component error while accessing a contact record (any contact record).

2. Issue: Unable to schedule SMS from the Partner Community license.

Fix:
Fixed the issue for scheduling SMS the users with community licenses.

3. Issue: Spell Check not working.
When the Customer Opens a New Message Window in Utility Bar & Typed Text, customer corrects the spelling using standard spell check utility however when customer posts the text, the words corrected in spell check are not updated. It sends incorrectly spelled words.

Fix:
Users can send an SMS from the utility bar after changing the incorrect word.

Improvements

N/A


Patch 1.60.37

Date: June 26, 2020

Bug fixes

Issue: Intermittent issue for notification in Utility bar.

Fix:
Fixed the issue with the utility bar as it is not getting blinks automatically on incoming SMS.

Improvements

Changes in SMS Magic Interact Package package to adopt the changes for Australian server addition on the portal.


Patch 1.60.36

Date: June 17, 2020

Bug fixes

1. Issue: ComplianceConsentList component is not showing the changes when we refresh the Lightning record tab.
Records were not visible in conversation view in Converse app.

Fix:
In the Converse App, conversation component, only the messages sent from Converse App will be displayed

2. Issue: Receiving an error message on clicking Send SMS Button.
When the customer clicks the Schedule/ send SMS button on the Enquiry object. The customer was getting the following error message:
“This page has an error. You might just need to refresh it. Error in $A.getCallback() [Cannot read property ‘setListViewData’ of undefined] Callback failed:
apex://smagicinteract.LightningBulkSMSController/ACTION$lightningBulkWrapper Failing descriptor:

Fix:
After clicking on the button the error message will not appear.

3. Issue: Validation rule on SMS history does not display the error message on the UI.
A customer had a validation rule on SMS history. This will not allow users to send SMS to any mobile numbers. The mobile number should be associated with a contact record in Salesforce to send out the SMS.
When users do send SMS to mobile numbers, they get a message on UI saying the ‘Message has been sent’ while the message has not been sent when checked in the error logs object.

Fix:
The validation rule error message is displayed.

4. Issue: Messages did not appear in the Embedded Desk.
The Owner of Conversation & SMS History gets updated to the Owner of Sender ID Correctly. The Notification in the Embedded Desk (Utility Bar )also blinks to the user but the conversation does not appear in the unread section.

Fix:
Messages will appear in the Embedded Desk.

5. Issue: Record owner sender did not work.
This is a coding bug. This was modified when we released a patch for a customer, as they wanted to send SMS to the user object. They wanted User as a MoC object.

Fix:
The Record owner sender id will be displayed.

6. Issue: Error message during upgrade on sandbox.
During Sandbox org upgrade from 1.55.7 to 1.60.24, we got below error message:
The user license doesn’t allow the permission: Manage All smagicinteract__Consent_Audit_History__c, Details: SMS_Interact_Permission_Set: The user license doesn’t allow the permission: Manage All smagicinteract__Consent_Audit_History__c

Fix:
We removed the View all, and Modify All permissions for the following objects: Compliance configuration audit, Consent Audit History, and Consents.


Patch 1.60.34

Date: June 03, 2020

Bug fixes

Issue: Non-admin users are unable to send SMS.Non-admin users are unable to send SMS. They see the error on the conversation component and also when using the ‘Send SMS’ button.

Error – ‘ObjObject name Organization does not have the permission to the field: read’.

Fix:
Commented security check for Organization object while checking for the namespace, so that non-admin users can send SMS.

Improvements

N/A


Patch 1.60.28

Date: May 12, 2020

Bug fixes

1. Issue: No automatic update of ‘complianceConsentList’ component.
For users with the compliance consent list component, embedded on their record detail page of contact, when a new record is created or an existing record is updated, it does not automatically reflect on the record detail page.They had to refresh the browser so that the new /updated record will be reflected on the record delta page.

Fix:
Compliance consent list components can be updated without a browser refresh. An additional button on the UI will refresh the list.

2. Issue: Consent record alignment.
Fixed consent record alignment issue due to additional refresh button on the record detail page.

Additional refresh button  & fixed alignment issue

3. Issue: Plan upgrade with existing active license.
Users were unable to change to a new plan when their existing license is active.

Fix:
Users can change to a new plan when their existing license is active. ie. If the user currently has a ‘ Start your conversation’ plan then they can change it to “ Grow Your Conversation Plan’.

4. Issue: Trial plans (Both) are reflecting in SF org, even after setting non-trial plan (Grow plan) from back-end.
Trial plans(Start your conversation, and Grow your Conversation plan), reflected in SF org, even after setting a non-trial plan(Grow plan) from the back-end.

Because of this issue, customers could only see the SMS Credits specific to the trial plan in their Salesforce org.

On the portal, the total number of available SMS credits as per the plan was displayed.

Fix:
If the plans are updated from the backend then that information will be updated to display the active plan on UI.

E.g. A ‘Grow your conversation’ trial plan is updated to any full plan, then it will be updated in the Plan manager section of Custom settings as well as on UI.

The following is the screen prior to fixing the bug:

5. Issue: Trial plans (Both) are reflecting in SF org, even after setting non-trial plan (Grow plan) from back-end.
The Client users were getting error messages when they clicked on the consent list view component, added on their lightning page.

Error messages:

I. No phone numbers are available on this record.
II. Component error message

The issue occurred when cross-referenced objects were using the consent list component.

In this case, while adding consent list component list on the Case object and then tried to set consent for the contact these error messages occurred.

Fix:
Fixed the issue with Consent lightning component, when fetching mobile number from lookup relation. No error message will be displayed, and the ‘Add Consent’ button will be clickable.

6. Issue: Image upload size limitation on SF Mobile app.
For SF mobile app, allowed images size is up to 2.5 MB. An error message should be shown if image size >2.5 MB.

(Error message for file size >2.5MB, before fix)
 (Error Message before the fix )

7. Issue: ‘Callout Exception’ error message for some of the messages.
Few of our customers have reported that their users intermittently faced an issue where a few messages were failed with an error message “Rejected from portal” or “Callout Exception error”.

Also, there was not enough information in error logs related to this issue, making the tracing of the cause difficult.

Workaround:
For any callout exception error message, an error log will capture more data using the system provided a function for troubleshooting than before so that the tracing actual reason(s) for the “Callout Exception Error“ will be easier.

The customer would need to set up a debug log of appropriate level in their salesforce org to get these extra logs.

ie. We are providing users with the enhanced error logging that will help us to trace the root cause. With this patch, a stack trace only for “Callout exception error ” is implemented when we sync with Portal API.

8. Issue: Unresolved templates for messages from SMS Magic Mobile app.
Templates are not resolving properly when the messages are sent from the SMS Magic Mobile application. When the user tries to send a message with a template attached to it, that includes the merge field, no data was available in the merge field.

Fix:
When messages are sent from any source, the template should resolve itself ie. merge field data will be available.

Security review changes
1. Removed jquery/angular libraries from the package as we are no longer using them.
2. Fixed Injection and CRUD/FLS bugs./SMI-6105

Improvements

N/A


Patch 1.60.24

Date: April 20, 2020

Bug fixes

1. Issue: Non-conversion of a few outgoing and incoming records.
Migration scripts for certain steps failed with an error message “ First error: Attempt to de-reference a null object” in debug log. That resulted in non-conversion of a few outgoing and incoming records. i.e leads were not converted into contact/Opportunity/Account.

Fix:
Fixed Data Migration issue for leads which were missed for being converted into contact/Opportunity/Account.

2. Issue: Converse app tasks failure with the message ‘No response from MessagingService’.
When the name of a custom object does not match with the name of the lookup relationship on the SMS history object, the converse app tasks fail with the message ‘No response from MessagingService’.

Eg. For a custom object named ‘xyz’, if the user creates a lookup on an SMS history object, with a different name ‘abc_xyz’. And, also creates a custom builder to create a converse app task whenever any field of the custom object is changed.

The Converse app task will be created with the error, message “No response from MessagingService”.

Fix:
No error message for the mismatch in the name of a custom object and that of used to create the lookup relationship on SMS history object.

3. Issue: Converse app task failure.
In the Master-Detail relationship between Salesforce objects, when a Standard Salesforce object was the Master, and a Detail object was a Custom object, the process builder showed an error message.

The automation failed when messages were sent from the detail record as a Detail custom object did not contain the field for the Master object.

This issue was only observed when the Master object was a Standard Salesforce object, not custom objects.

Fix:
The Master-Detail relationship will now work for standard objects as well to send the messages using Detail – custom objects.

Improvements

Supporting messaging to internal users with User Object(Limitation – SMS History records won’t be created)


Patch 1.60.22

Date: April 09, 2020

Bug fixes

1. Issue: A intermittently error message on UI
Fixed a UI intermittently error message:
“This page has an error. You might just need to refresh it [Action failed: aura: iteration$controller$itemsChange [Maximum call stack size exceeded]]”

on Converse setting on the selection of plan.

2. Issue: Wrong Consent mode was shown when the user sends SMS from a bulk SMS source.
Wrong Consent mode was shown when the user sends SMS from a bulk SMS source.
i.e. Global consent mode was shown when the user sent SMS from a bulk SMS source.

Eg. In the converse setting, users selected “Consent not required “ in the Consent method & Content section(as global consent) for their Marketing content. Also, selected “ Consent mode – Required “ for their Marketing content.

In the template for Marketing content the consent type appears as – required. But when the same template is selected for sending bulk messages, appears as “ Not applicable” i.e. same as global consent.

Fix:

Appropriate consent mode is now shown when the user sends SMS from Bulk SMS source. The consent mode appears as per the selection made only for the content-specific consent /SMI-5661

3. Issue: A blank space appears when MMS is received in the Facebook integration.
For Facebook integration, a blank space appears when MMS is received in the conversation window.

Fix:
Incoming images from Facebook are displayed in SF. (Converse desk, Conversation component ).

4. Issue: Auto append not working for messages from templates and Phone, and Phone +senderid combinations.
If a user sends messages using the template with opting for an Auto append, for Phone, and Phone +senderid combinations, the auto append messages were not included in the template messages.

This issue was observed only for the messages from templates and Phone, and Phone +senderid combinations.

Fix:
Auto append message will work for phone, and Phone+ sender id for the selected template while sending SMS. This can be confirmed from SMS history.

Improvements

1. Issue: Failed license allocation due to permission issues.
For a few customers, Due to some permission issues – License allocation is getting failed while installation of the package. But because of such restrictions, licenses can’t be added from an external interface. The only option remaining is un-installing & installing packages.

Solution:

Removed the restriction for support of license handling from the external interfaces and restricted the user from assigning multiple licenses to one user.

2. Issue: Guest users unable to send messages despite granting permission(s).
The converse app task is getting created with success status but the history record is not getting created.
Guest user from customer’s org was unable to send automated messages despite granting him following permissions:

  • Object and field-level permissions
  • created sharing rules on required objects
  • View All Custom settings
  • SMS License
  • custom settings, apex classes and custom metadata on at profile level

Solution:

Skipping Group object access check for non- standard/guest users allowing them to send automated messages.


Patch 1.60.17

Bug fixes


N/A

Improvements

Salesforce API version updated to 1.46, allowing user to add all objects in message configuration under converse settings.


Patch 1.60.14

Bug fixes

  • Fixed issue regarding only the text from the Template getting sent when Template is used in Campaign and extra text is added.
  • Fixed issue regarding missing fields in the conversation user permission set.
  • Fixed issue regarding the sender injection code.

Improvements

  • New compliance support for the campaign manager. For more information click here.
  • Added injection framework for supporting custom logic.

Patch 1.60.10

Bug fixes

  • Fixed issue with UI while sending single SMS when country set to all for MMS.
  • Fixed issue with record owner sender id not displayed in Bulk Campaign in Converse App.
  • Fixed issue with Utility bar where the message is displayed to two records.

Improvements

Patch for Salesforce Spring’20 Critical Update.
A critical update has been rolled out with the Spring ’20 release on January 3, 2020 and made globally available from February 17, 2020. After the critical update, users without the Customize Application permission can no longer access custom settings. You can read the detailed instructions here or please reach out to us at care@screen-magic.com with any questions you might have.


Patch 1.60.8

Bug fixes

Fixed new message UI to populate correct data in record detail page.

Improvements

N/A


Patch 1.60.7

Bug fixes

For Line & Facebook channel – Fixed issue with Conversation Id creation and Unformatted number population.

Improvements

Application available for use on Salesforce Professional Edition


Patch 1.60.3

Bug fixes
  • Fixed issue with expanded view of conversation component on alert notification of Incoming Message.
  • Fixed issue with facebook’s alphanumeric sender ID formatting on conversation view.
Improvements
  • Bulk SMS component load time improvements.
  • Optimisation for composer rendering on Send SMS button click.
  • Auto Reload of Conversations and ConversationView Components on community edition with push topics dependency removed.
  • Injection framework – Sender Id, Template, Incoming lookup Injection changes for customer.
  • Packaged dashboards are removed to handle installation blockers. We would be introducing native dashboards as a better way of analytics dashboards MIS. 
  • The converse app feature is made available for all from 1.60 version onwards.
  • MMS size limit is subjected to limits provided by Providers and carriers.



Version 1.58

Patch: 1.58.49

Date: 10th Aug 21

Bug fixes
  1. Issue: Customer was facing an Issue while using the Composer Component

Fix –
In the ComposerComponentController which is a js file, a condition was applied which was checking for a quick reply & if that condition was satisfied, the code was getting executed.

In the customers’ scenario, this condition was not getting satisfied as it was outside the managed package. To resolve this issue, the quick reply condition was tested and removed criteria from the quick reply section to resolve this issue.

Patch 1.58.48

Date: 18th June 2021

Bug fixes
  1. Issue – Users were receiving other user’s incoming messages

Fix –
The users were receiving other user’s incoming messages in their Converse inbox even after the global filter was set to ‘My’ and not ‘ALL’. All the users of the company were able to view the incoming messages of other users in their Converse Desk.

The incoming messages were auto refreshed on the Converse Desk via PushTopic subscription. Due to this, all messages were populated on the Converse Desk Inbox, irrespective of who the current user was.

To solve this issue, the ‘OwnerId’ filter was added while subscribing to the PushTopic. With this, users started receiving only those messages that were meant for them.

Patch 1.58.44

Date: 27th March 2021

Bug fixes

Issue – New field Permission- SMS History Object – Non-admin users were not able to send messages

Fix:
Customer had created custom fields on the SMS History object. The non-admin users were given only ‘read’ permission to these custom fields. Because of this, the non-admin users were not able to send messages.

The code was checking update permission for all the fields on the SMS History object which was causing this issue. To solve the issue, the code was changed to check the update permission only for the packaged fields and not for the customer-created fields

Issue – Unable to download content received via incoming messages (txt file)

Fix:
This was happening because only certain media files could be rendered on the UI. The customer was facing an issue downloading the non-media file (txt file) in the conversation view component (embedded on the record details page).

Previously the non-media file attempted to open in the same browser window which was causing the issue. To solve this, the code was changed to open the file in a new tab.

Patch 1.58.43

Date: 28th January 2021

Bug fixes

Issue – Misspelled text was getting saved while creating a template

Fix:
The customer was facing an issue with misspelled text while creating a template.

When a user was typing a wrong spelling, the correct word/spelling was suggested to them. While selecting the suggested correct spelling, the corrected spelling was not getting saved with the template text. The template was saved with the original wrong spelling.

The ‘onchange’ event was not captured on the text area, because of which, the text change via mouse selection was not getting captured. To solve the issue, the ‘onchange’ event was added on the text area of the composer component.

Patch: 1.58.42

Date:  18th Jan 2021

Bug fixes
  1. Issue: The customer was getting an error while using the time field in the template

Fix
The customer was getting an error while using the time field in the template. The error which customers were getting was ‘Failed to execute a query or some unknown error occurred’ on SMS History record while triggering SMS from automation – ‘SMS: VA PreHearing/Hearing Date Scheduled’ when they were using a time field ‘Hearing Time’ in the template ‘ VA Hearing Initial Text ‘ (a3L2g000000THJuEAO). 

While using the Time Datatype field in Template, it was not getting resolved. The conversion time datatype was not working properly in TemplateEngine class & SMSUtility class. 

To solve this issue ‘Date Time format’ was not converted using the Time field syntax as passed from Salesforce. 

Patch 1.58.40

Date:  18th Jan 2021

Date: 7th September 2020

Bug fixes

Issue – Integration with Outlook.

Fix:
The customer was getting an error while using the conversations component. To solve this issue, we implemented a null check condition. With this, the integration with Outlook happened properly.

Improvements

N/A


Patch 1.58.35

Bug fixes

  • Fixed Converse App error related to SMS Bulk Campaign.
  • Fixed an error related to Converse Desk Layouts.
  • Fixed UI for sync button in utility bar.
  • Fixed intermittent component error on utility bar.

Improvements

N/A


Patch 1.58.34

Bug fixes

Fixed BulkSMSComponent related to MMS when country was set to all.

Improvements

N/A


Patch 1.58.32

Bug fixes
  • Multiple refreshes for components fixed.
  • UI error fixed in conversation component
Improvements

N/A


Patch 1.58.29

Bug fixes

N/A

Improvements

Patch for Salesforce Spring’20 Critical Update.
A critical update has been rolled out with the Spring ’20 release on January 3, 2020 and made globally available from February 17, 2020. After the critical update, users without the Customize Application permission can no longer access custom settings. You can read the detailed instructions here or please reach out to us at care@screen-magic.com with any questions you might have.


Patch 1.58.28

Bug fixes
  • Component error fixed related to Conversation in Record Detail Page (Sandbox).
  • Component error fixed related to Utility Bar (Sandbox).
Improvements

N/A


Patch 1.58.26

Bug fixes
  • Message bubble setting reflects correctly now on converse desk.
  • Send bulk SMS template issue fixed.
  • Bugs fixed related to Converse app automation.
  • Conversation view from section issue resolved.
Improvements

Bulk SMS interface performance increased.


Patch 1.58.25

Bug fixes
  • Fixed bugs related to Converse App
  • Fixed conversations related to Utility Bar.
  • Send bulk SMS template issue fixed
Improvements

Desk performance increased.


Patch 1.58.17

Bug fixes

  • Fixed conversation trigger component.
  • Fixed converse desk loading for community.
  • Fixed Exception handling in updateRelatedList trigger.
  • Permission set as disabled for user for deleting conversations and message records.

Improvements

Increased file size upload limit to 2.5MB.


Patch 1.58.14

Bug fixes

Fixed activation of converse apps and navigation to automation/template in converse apps.

Improvements

N/A

Patch 1.58.13

Bug fixes

Migration Failure.

Improvements

N/A


Patch 1.58.12

Bug fixes

Unable to select the options of Template, Automation and Bulk Campaigns in Converse Apps and hence unable to add templates.

Improvements

The three options of Template, Automation and Bulk Campaigns were displayed successfully in both Classic and Lightning versions. While using Lightning, users must register their domain to view the options properly.


Patch 1.58.11

Bug fixes

NA

Improvements

New Links were added for Release Notes and Admin Guides (Post-installation Steps)

Patch 1.58.10

Bug fixes

Multiple Email notifications were being sent while Incoming message was being updated.

Improvements

Incoming Message Notifications were implemented




Version 1.55

Patch 1.55.29

Date: 18th Nov 2020

Bug fixes

1.Issue – Issue with the Emoticon Box; the width of the box was restricted to a specific value

Fix – 

The width of the emoticon box was confined to a specific value. Due to this when the count increased, all emoticons did not fit into the available area and expanded out of the box, thereby breaking the UI.

To solve this issue, the width constraint on the emoticon box area was removed so that the box automatically adjusts itself to fit all the available emoticons.

2.Issue – Impact of Winter ’21 Release

Fix

In Winter ’21 Release, Salesforce enforced the requirement of explicit permission for the apex classes having @auraenabled methods.

To cater to this enforcement, we added all the apex classes in the permission sets in our package. Thereby providing permissions for the required apex classes.


Patch 1.55.25

Date: July 07, 2020

Bug fixes

Issue: Error message error “ApexCPU Time Limit Exceeded”

Fix:
Fixed the issue when inserting bulk records into Converse App Task object failed with error “ApexCPU Time Limit Exceeded”

Improvements

N/A


Patch 1.55.25

Bug fixes

Issue: Auto-messages triggered for an incoming message which was a close match with the defined keyword.

In the converse app, auto-messages were triggered for an incoming message which was a close match with the defined keyword.

Eg. In converse apps, the auto message trigger keyword is ‘demo’, the incoming message reads as ‘demo1’, and auto-messages are sent.

Fix:

Autoreply will be triggered only for the message senders whose message matches the exact keyword. No auto-reply will be triggered otherwise.

Improvements

N/A


Patch 1.55.24

Bug fixes

N/A

Improvements

We have added a custom apex configuration option to show a filtered list of senderIds on Converse UIs as well during the message sending process.


Patch 1.55.21

Bug fixes


Fixed Issue with Campaign state if listview is having multi-pick list field.

Improvements

N/A


Patch 1.55.19

Bug fixes


Fixed issue with size of template dropdown in conversation component view.

Improvements

N/A


Patch 1.55.18

Bug fixes


N/A

Improvements

Patch for Salesforce Spring’20 Critical Update.
A critical update has been rolled out with the Spring ’20 release on January 3, 2020 and made globally available from February 17, 2020. After the critical update, users without the Customize Application permission can no longer access custom settings. You can read the detailed instructions here or please reach out to us at care@screen-magic.com with any questions you might have.


Patch 1.55.17

Improvements

N/A

Bug fixes

Fixed date formatting issue.


Patch 1.55.16

Bug fixes

SMS credits consumed displays correctly now.

Improvements

N/A


Patch 1.55.15

Bug fixes

Component error fixed.

Improvements

  • Converse desk incoming notification.
  • All conversations related to a record displayed in conversation view.

Patch 1.55.14

Bug fixes

Fixed Bulk Campaign operator related to Converse App.

Improvements

N/A


Patch 1.55.12

Bug fixes

N/A

Improvements

List view increased to 2000 records.


Patch 1.55.11

Bug fixes

Fixed multiple records update for SMS History in Portal search message component fixed

Improvements

Added bulk sms component for community users.


Patch 1.55.10

Bug fixes

The Disabled Button continued to be displayed in an enabled state despite user having clicked once. This made it difficult to understand if message is being submitted resulting in multiple clicks by the user. This led to the message being submitted multiple times.

Improvements

While sending a Bulk SMS the Send SMS button is disabled after the first use.


Patch 1.55.9

Bug fixes

  • An SOQL Limit exception was displayed (SOQL queries: 101′ error) on loading Converse App while multiple Automation messages (over 95) were in active state.
  • The Expanding the Utility Bar displayed a Component Error.

Improvements

Resolved the utility error and SOQL Limit exception


Patch 1.55.7

Bug fixes

The Streaming API usage is happening for all the users active on the conversation page. It should happen only for the conversation owners.

Improvements

Corrected the usage of Streaming API for both outgoing and Incoming messages.


Patch 1.55.5

Bug fixes

Templates were not displayed alphabetically in the template dropdown.

Improvements

All templates are being displayed in alphabetic order


Patch 1.55.4

Bug fixes

SMS History record is created in Salesforce but the message is not been forwarded to Portal. A possible root cause being that Multiple Queueable jobs are created in batch context due to which messages are not synced to the portal.

Improvements

SMS-History is being created and successfully and also being forwarded to Portal


Patch 1.55.3

Bug fixes

Partial SMS and those with Error status were not being sent out.

Improvements

Added callSMSAPI Callout after for loop in SMSUtility.


Patch 1.55.1

Bug fixes

isSearchable checks missing in Campaigns, Settings, Bulk messages and Conversation Composer.

Improvements

  • Implemented CLI changes
  • Added isSearchable checks

Patch 1.55

Bug fixes

Unable to use parent object name field & optout field in new message & in the Converse desk.

Improvements

Launched the Winter 19 Release.




Version 1.48

Patch 1.48.17

Date: August 31, 2020

Bug fixes

1. Issue – Formula field not working in SMS Template.

Fix:
Conversion of Time datatype field was not happing properly in TemplateResolver & template engine class. We were converting string given by salesforce into Date/time datatype. Solved this issue by using proper format (In Time Datatype format).

Improvements

N/A


Patch 1.48.16

Bug fixes

Issue: ‘Callout Exception’ error message for some of the messages.
Few of our customers have reported that their users intermittently faced an issue where a few messages were failed with an error message “Rejected from portal” or “Callout Exception error”.

Also, there was not enough information in error logs related to this issue, making the tracing of the cause difficult.

Workaround:
For any callout exception error message, an error log will capture more data using the system provided a function for troubleshooting than before so that the tracing actual reason(s) for the “Callout Exception Error“ will be easier.

The customer would need to set up a debug log of appropriate level in their salesforce org to get these extra logs.

ie. We are providing users with the enhanced error logging that will help us to trace the root cause. With this patch, a stack trace only for “Callout exception error” is implemented when we sync with Portal API.

Improvements

N/A


Patch 1.48.15

Bug fixes

N/A

Improvements

Patch for Salesforce Spring’20 Critical Update.
Critical update has been rolled out with the Spring ’20 release on January 3, 2020 and made globally available from February 17, 2020. After the critical update, users without the Customize Application permission can no longer access custom settings which will impact the SMS-Magic capabilities like sending messages, receiving incoming messages, etc. 

Through 1.48.13, We had given SMS-magic packaged permission set “SMS Interact conversation user” to give access to only SMS-magic custom settings which customers can assign to their users in order to overcome the issues arising due to Salesforce critical update. You can read the detailed instructions here.

But for those who don’t want their users to have delete permission on objects, we are releasing 1.48.15 by updating a SMS-magic packaged permission set “SMS Interact conversation user” to give access to only custom settings which customers can assign to their users . This will not only help the them in overcoming the issues arising due to salesforce critical update but also in having access permission control over objects.


Patch 1.48.14

Bug fixes

Fixed intermittent error related to send SMS button.

Improvements

N/A


Patch 1.48.13

Bug fixes

N/A

Improvements

Patch for Salesforce Spring’20 Critical Update.
A critical update has been rolled out with the Spring ’20 release on January 3, 2020 and made globally available from February 17, 2020. After the critical update, users without the Customize Application permission can no longer access custom settings. You can read the detailed instructions here or please reach out to us at care@screen-magic.com with any questions you might have.


Patch 1.48.12

Bug fixes

N/A

Improvements

Display more than 3000 messages in a conversation.


Patch 1.48.9

Bug fixes

Displayed error on rescheduling SMS.

Improvements

SMS was successfully rescheduled.