Version 1.60

Patch 1.60.46

Date: July 28, 2020

Bug fixes

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

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.

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



Patch 1.60.45

Date: July 27, 2020

Bug fixes

Issue: Utility Bar Notification Not Working.

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.



Patch 1.60.44

Date: July 23, 2020

Bug fixes

1. Issue: ApexCPU Time out error.

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.

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”.

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.



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.

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.

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.



Patch 1.60.38

Date: June 30, 2020

Bug fixes

1. Issue: Component error.

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.

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.

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



Patch 1.60.37

Date: June 26, 2020

Bug fixes

Issue: Intermittent issue for notification in Utility bar.

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


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.

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:

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.

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.

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.

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

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’.

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



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.

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.

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.

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.

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.

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.

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



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.

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”.

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.

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


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.

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.

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.

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.


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.

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

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

Patch 1.60.17

Bug fixes



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.


  • 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.


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 with any questions you might have.

Patch 1.60.8

Bug fixes

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



Patch 1.60.7

Bug fixes

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


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.
  • 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.

Was This Article Helpful?