Version 1.48

Patch 1.48.9

SMS was successfully rescheduled.

Displayed error on rescheduling SMS.

---

Patch 1.48.12

Display more than 3000 messages in a conversation.

N/A

---

Patch 1.48.13

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

N/A

Fixed intermittent error related to send SMS button.

---

Patch 1.48.15

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.

N/A

---

Patch 1.48.16

N/A

Issue:

Users faced an issue where a  few messages were failed and the error message was  “Callout Exception Error“.

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

Fix:

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