Patch 1.51.1

• While searching for conversations by the parent name displayed correct results.
• New Conversations are not created while sending notifications to users.

• SMI-2823: The “Invalid Field” error message is displayed while searching in Converse Desk.
• SMI-2824: An Automated Send SMS Conversation in Converse Desk is displayed under the History object
• SMI-2825: For Message Flow “Notification to User” is not working when notifying same user for second time

---

Patch 1.51.2

Filter for embedded view was changed from MY > INBOX > UNREAD to
MY > INBOX > ALL

SMI-2832: To Change filter in embedded View.

---

Patch 1.51.3

Corrected logic to get total conversation count

SMI-2834: Total Conversation count for embedded view was incorrect.

---

Patch 1.51.4

Filtered Conversation records by adding primary object lookupField clause in query.

Time limit exceeded for Bulk messaging (Batch & 200).
This issue was not reported by QA in Converse.

---

Patch 1.51.5

A check was implemented to verify the direction of push topics (incoming and outgoing). For outgoing SMS push topics will be received till a defined time frame after which only 1 API call will be performed.

Push topic for outgoing SMS was not being Bulkified. When a campaign was run each inserted record would call unread count API. Lightning would group multiple API calls causing them to reach governor limits.

---

Patch 1.51.6

A change was implemented in ConversationService. Maps were used to build association in order to reduce time complexity to O(n).

Time limit exceeded for Bulk messaging (200). This issue was not reported by QA in Converse.

---

Patch 1.51.7

Introduced a limit Clause of 5k records.

Incoming from Unknown number was not being pushed to Salesforce as there were over 50k Conversation records.
This issue was not reported by QA in Converse.

---

Patch 1.51.8

• Cached unrelated objects API result from MOC to reduce time.
• Removed message with source 1360 & 1490 from creating conversation.
• Resolved problem in incoming data migration on enabling Salesforce to Salesforce.

Calling unrelated objects API multiple times which increases processing time.

Incoming data migration problem when Salesforce to Salesforce is enabled in org.

---

Patch 1.51.9

• Resolved issue for SenderId profile map showing extra user as default
• Resolved bug in information object when no unrelated object is configured for primary object.

• Duplicate conversations were getting created when messages sent to the same Lead.
• Improvements SMI-2855
• Showing default sender is assigned to user when “null” keyword is present in their name, or email, or username.

---

Patch 1.51.10

• Identified fix for using 3 mobile fields in Classic bulk.
• Identified fix for sending Incoming MMS.

• SMI-2839: Sending classic bulk using 3 mobile fields.
• When the Single object is enabled and there is an incoming MMS, it forwards the message to the mobile number.

---

Patch 1.51.11

Summer 18 Lightning bug fixes.

Summer 18 release made the Lightning components fail.

---

Patch 1.51.12

• Resolved Conversation Migration
  Modified query to let Platform License owners send SMS
• Cached getAccountInfo callout to avoid time limit exception
• Resolved bug for URL redirects
• Removed the unused libraries that were being added while creating Conversation Page for Lead/Contact

Resolved the Scheduler with i18 fixes

• Data sanity issues while migrating Conversations.
• Platform License users unable to send out messages.
• Moved bugs fixed in other releases.

---

Patch 1.51.13

Checks are implemented for user access to Campaign object prior to checking for the container in order to build associations.

Checks for all Campaigns and Converse Apps were hard coded and hence displayed errors for Platform license.

---

Patch 1.51.14

Status of all outgoing SMS have been attributed to Bulk SMS

Bulk SMS should share the same status as Outgoing SMS.

---

Patch 1.51.15

Fixed SOSL issue for large lead count

SMI- 3037 – Make the find query selective in current release

---

Patch 1.51.16

Campaign Batch size increased to 50

Need to Increase the Batch size for Campaign to 50 to improve Batch speed

---

Patch 1.51.17

• Resolved all the issues pending in Winter 19 issues
• Implemented a change in color for automated SMS

Need to display Automated SMS in a different color

Patch 1.50.2

While scheduling bulk messages , the date being displayed on  the interface displayed the correct date irrespective of the machine date.
The fix replaced the Javascript date object with Salesforce standard date as given by the component.

Modified query to suit the requirements of the client’s large dataset.
Fixed critical bugs

• SMI-2894 – While scheduling bulk messages, the date being displayed was incorrect.
  A possible explanation for this was that the query being run used a Javascript Date object to get a date from a string. This date was based on machine time. 
• Changed the query for Conversation without modifying the logic.
• Verified URL changes.

---

Patch 1.50.3

Fixed SOSL issue for large lead count

SMI- 3036 – Make the find query selective in current release

Patch 1.48.17

Date: August 31, 2020

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

N/A

---

Patch 1.48.16

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.

N/A

---

Patch 1.48.15

N/A

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

Fixed intermittent error related to send SMS button.

N/A

---

Patch 1.48.13

N/A

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

N/A

Display more than 3000 messages in a conversation.

---

Patch 1.48.9

Displayed error on rescheduling SMS.

SMS was successfully rescheduled.

Patch 1.47.9

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.

N/A

Patch 1.46.20

Date: September 22, 2020

1. Issue: The return URL not getting validated correctly.

Fix:
Due to a critical update, the return URL was not getting validated correctly. To solve this issue, we added checks for Hostname URL.

N/A

---

Patch 1.46.19

Create Patch for current release (1.46) to order templates alphabetically (Case number: 00013648)

Templates are displayed alphabetically in the template dropdown for selection.

Overview

Release 1.60 was mainly focused on following things:

1. Changes related to prebuilt dynamic dashboard

SMS magic 1.59 version has prebuilt dynamic dashboards giving insights on compliance, team and agent productivity etc. In salesforce, every enterprise edition organization can have up to 5 dynamic dashboards and unlimited edition organisation can have up to 10 dynamic dashboards. 

Based on the organisation edition, customers were facing issues with installation of 1.59 version where the dynamic dashboard limit was exceeding. So through release 1.60 we are taking out the packaged dynamic dashboards outside of the main package and giving it as an add-on for those who need it / who’s org can support it. [To get the add-on package version link, please reach out to us at care@screen-magic.com]

2. Patch for Salesforce Critical Update rolled out on February 17, 2020

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.60, we are giving a SMS-magic packaged permission set “SMS Converse conversation user” to give access to only SMS-magic custom settings which you can assign to your users. You can read the detailed instructions here or please reach out to us at care@screen-magic.com with any questions you might have. 

3. Custom Apex Code Injection Capability

Sender ID selection, template selection and incoming lookup selection can now be customised as per business process with custom development.

4. Bug fixes & Improvements

Through 1.60, we are coming up with a few more bug fixes & enhancements as listed below.

Improvements

1. Bulk SMS component load time improvements.
2. Optimization for composer rendering on Send SMS button click.
3. Auto reload of Conversations and ConversationView Components on community edition with push topics dependency removed.
4. MMS file size limit increased to 2.5MB from 500Kb.
5. The converse app is made available for all from 1.60 version onwards.
6. Application available for use on Salesforce Professional Edition.
7. New compliance support for the campaign manager. For more information click here.
8. Salesforce API version updated to 1.46, allowing user to add all objects in message configuration under converse settings.

Bugs

1. Fixed issue with expanded view of conversation component on alert notification of Incoming Message.
2. Fixed issue with facebook’s alphanumeric sender ID formatting on conversation view.
3. Fixed issue with Conversation Id creation and Unformatted number population for Line & Facebook channel.
4. Fixed new message UI to populate correct data in record detail page.
5. Fixed issue with record owner sender id not displayed in Bulk Campaign in Converse App.
6. Fixed issue with Utility bar where the message is displayed to two records.
7. Fixed issue with UI while sending single SMS when country set to all for MMS.
8. Fixed issue regarding only the text from the Template getting sent when Template is used in Campaign and extra text is added.
9. Fixed issue regarding missing fields in conversation user permission set.