Version 1.60

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

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

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

Patch 1.54.1

Improvements

  • Resolved issues in Lightning View.
  • Resolved earlier Bugs.

Bug fixes

Need to display Automated SMS in a different color


Patch 1.54.2

Improvements

  • winter 19, back button on Desk & force:recordView
  • Resolved all the issues pending in Winter 19 release
  • Implemented a back button on Desk and force:recordView

Bug fixes

Winter 19 issues


Patch 1.54.3

Improvements

Added a title for topics

Bug fixes

Converse Desk was refreshed to display incoming messages meant for the User’s Inbox only.


Patch 1.54.4

Improvements

Converse Desk was refreshed to display incoming messages meant for the User’s Inbox only.

Bug fixes

Conversation of other user was being displayed in My > Inbox


Patch 1.54.5

Improvements

Comet Static Resource was made private

Bug fixes

None


Patch 1.54.6

Improvements

Bulk SMS was sent successfully for all objects including those with “/” in their name.

Bug fixes

Syntax for query in Includes statement was rectified for multiselect picklists.


Patch 1.54.7

Improvements

  • Push topic permissions provided to community users.
  • Added Bulk SMS component for community users.

Bug fixes

N/A


Patch 1.54.8

Improvements

N/A

Bug fixes

A fix for restricting the execution of excessive AsyncApex jobs through conversation controllers so the Salesforce limitation for customer Org’s AsyncApex jobs will not be reached quickly.




Version 1.52

Patch 1.52.1

Improvements

  • Allowed only one queueable job from batch.
  • Removed picklist field of Conversation Map from SetUp Wizard.

Bug fixes

  • Queueable job issue on campaign execution
  • The Picklist Field of Conversation Map needed to be removed from the Setup Wizard as the package did not include Conversation Map

Patch 1.52.2

Improvements

  • Resolved issues in Lightning View.
  • Resolved earlier Bugs.

Bug fixes

  • Display of the “Attempt to dereference null object” error in Converse Desk.
  • Error displayed when an outgoing Sender ID, that has been associated with an incoming number, is selected again for incoming number association.
  • Issue in Converse App task when the owner ID field is missing in the Object.

Patch 1.52.3

Improvements

Removed system.debug and console.log

Bug fixes

Need for Security Review.


Patch 1.52.4

Improvements

  • Resolved all CSRF and CLI issues
  • Resolved other issues.

Bug fixes

  • Error displayed while trying to create a Converse App
  • Missing Sequence Number while creating an Automation action
  • App Name and App Description fields on the Converse App edit page are blank and the Cancel Button redirects to the wrong URL
  • Display of error text at the bottom of the Composer window while trying to paste text.
  • Converse App UI Issues
  • Need to eliminate the insertion of a security setting while handling an auto event
  • Lightning CLI Issues

Patch 1.52.5

Improvements

Ensured that all IDs are alphanumeric and that all MMS URLs are redirecting to Screen Magic domains.

Bug fixes

Lightning Security changes


Patch 1.52.6

Improvements

Eliminated arbitrary redirection issue to URLs that are passed to the navigateToUrl function.

Bug fixes

Lightning Security changes


Patch 1.52.7

Improvements

Increased Campaign batch size from 1 to 50.

Bug fixes

Very poor Batch Speed owing to limited size


Patch 1.52.8

Improvements

Fixed SOSL issue for large lead count

Bug fixes

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


Patch 1.52.9

Improvements

Implemented professional edition of ProcessInstance object permission

Bug fixes

Process Instance Object should be checked before querying


Patch 1.52.10

Improvements

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

Bug fixes

Need to display Automated SMS in a different color


Patch 1.52.11

Improvements

  • winter 19, back button on Desk & force:recordView
  • Resolved all the issues pending in Winter 19 release
  • Implemented a back button on Desk and force:recordView

Bug fixes

Winter 19 issues


Patch 1.52.12

Improvements

N/A

Bug fixes

Fixed multiple records update for SMS History in Portal.


Patch 1.52.15

Improvements

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

Bug fixes

Component error fixed.





Version 1.51

Patch 1.51.1

Improvements

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

Bug fixes

  • 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

Improvements

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

Bug fixes

SMI-2832: To Change filter in embedded View.


Patch 1.51.3

Improvements

Corrected logic to get total conversation count

Bug fixes

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


Patch 1.51.4

Improvements

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

Bug fixes

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


Patch 1.51.5

Improvements

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.

Bug fixes

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

Improvements

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

Bug fixes

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


Patch 1.51.7

Improvements

Introduced a limit Clause of 5k records.

Bug fixes

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

Improvements

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

Bug fixes

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

Improvements

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

Bug fixes

  • 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

Improvements

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

Bug fixes

  • 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

Improvements

Summer 18 Lightning bug fixes.

Bug fixes

Summer 18 release made the Lightning components fail.


Patch 1.51.12

Improvements

  • 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

Bug 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

Improvements

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

Bug fixes

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


Patch 1.51.14

Improvements

Status of all outgoing SMS have been attributed to Bulk SMS

Bug fixes

Bulk SMS should share the same status as Outgoing SMS.


Patch 1.51.15

Improvements

Fixed SOSL issue for large lead count

Bug fixes

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


Patch 1.51.16

Improvements

Campaign Batch size increased to 50

Bug fixes

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


Patch 1.51.17

Improvements

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

Bug fixes

Need to display Automated SMS in a different color




Version 1.50

Patch 1.50.2

Improvements

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

Bug fixes

  • 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

Improvements

Fixed SOSL issue for large lead count

Bug fixes

SMI- 3036 – Make the find query selective in current 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.




Version 1.47

Patch 1.47.9

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.

Bug fixes

N/A




Version 1.46

Patch 1.46.20

Date: September 22, 2020

Bug fixes

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.

Improvements

N/A


Patch 1.46.19

Bug fixes

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

Improvements

Templates are displayed alphabetically in the template dropdown for selection.