Date: 13th Dec 21
- Issue: The customer was getting an error in the Converse App in version 1.60.79
Fix: The following error message was seen in the Converse app:
Invalid field OwnerId for Training__c
The customer was trying to send an SMS using a detail record from the Converse App, and the Owner ID was not existing for the detail record. Hence this issue was encountered.
To solve this issue, the RecordsSenderID() method of SenderService.cls was fixed, where “Owner ID” was explicitly added in the fieldName. Fixed the code, and checked if the object was detailed which then took Owner ID from the master object. The existing method MessageUtility.personObjectOwnerFldMap() was used.
- Issue: Incoming messages were not getting associated
Fix: There was an issue where the incoming SMSs were not getting attached to the Matter after the Lead was converted.
There was a SOSL query exception for reserved/special characters which could not be directly used for SOSL queries.
To solve this issue, added the method appendEscapeInPhoneForSOSL() to handle special characters in the SOSL query.
- Issue: Converse App Bulk campaign was getting stuck in running status
Fix: The user was trying to run a bulk campaign from the converse app and the campaign was getting stuck in Running status. The SMS History records were not being created as well.
Follow this step: Go to Converse App “Patient Marketing” Bulk campaign. Use the listView “Test Text-Marketing Only”.
List view contained subqueries as filters. It was fetching wrong object in query in parseSelectCondition() method of MetadataService.cls
To solve this issue, modified the List View query formation by adding ‘from’ + ‘object name’ while getting the where clause of the list view.
Date: 10th Aug 21
- Issue: Customer was facing an Issue while using the Composer Component
In the ComposerComponentController which is a js file, a condition was applied which was checking for a quick reply & if that condition was satisfied, the code was getting executed.
In the customers’ scenario, this condition was not getting satisfied as it was outside the managed package. To resolve this issue, the quick reply condition was tested and removed criteria from the quick reply section to resolve this issue.
Date: 18th June 2021
- Issue – Users were receiving other user’s incoming messages
The users were receiving other user’s incoming messages in their Converse inbox even after the global filter was set to ‘My’ and not ‘ALL’. All the users of the company were able to view the incoming messages of other users in their Converse Desk.
The incoming messages were auto refreshed on the Converse Desk via PushTopic subscription. Due to this, all messages were populated on the Converse Desk Inbox, irrespective of who the current user was.
To solve this issue, the ‘OwnerId’ filter was added while subscribing to the PushTopic. With this, users started receiving only those messages that were meant for them.
Date: 27th March 2021
Issue – New field Permission- SMS History Object – Non-admin users were not able to send messages
Customer had created custom fields on the SMS History object. The non-admin users were given only ‘read’ permission to these custom fields. Because of this, the non-admin users were not able to send messages.
The code was checking update permission for all the fields on the SMS History object which was causing this issue. To solve the issue, the code was changed to check the update permission only for the packaged fields and not for the customer-created fields
Issue – Unable to download content received via incoming messages (txt file)
This was happening because only certain media files could be rendered on the UI. The customer was facing an issue downloading the non-media file (txt file) in the conversation view component (embedded on the record details page).
Previously the non-media file attempted to open in the same browser window which was causing the issue. To solve this, the code was changed to open the file in a new tab.
Date: 28th January 2021
Issue – Misspelled text was getting saved while creating a template
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.
Date: 18th Jan 2021
- Issue: The customer was getting an error while using the time field in the template
The customer was getting an error while using the time field in the template. The error which customers were getting was ‘Failed to execute a query or some unknown error occurred’ on SMS History record while triggering SMS from automation – ‘SMS: VA PreHearing/Hearing Date Scheduled’ when they were using a time field ‘Hearing Time’ in the template ‘ VA Hearing Initial Text ‘ (a3L2g000000THJuEAO).
While using the Time Datatype field in Template, it was not getting resolved. The conversion time datatype was not working properly in TemplateEngine class & SMSUtility class.
To solve this issue ‘Date Time format’ was not converted using the Time field syntax as passed from Salesforce.
Date: 18th Jan 2021
Date: 7th September 2020
Issue – Integration with Outlook.
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.
- 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.
Fixed BulkSMSComponent related to MMS when country was set to all.
- Multiple refreshes for components fixed.
- UI error fixed in conversation component
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 email@example.com with any questions you might have.
- Component error fixed related to Conversation in Record Detail Page (Sandbox).
- Component error fixed related to Utility Bar (Sandbox).
- 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.
Bulk SMS interface performance increased.
- Fixed bugs related to Converse App
- Fixed conversations related to Utility Bar.
- Send bulk SMS template issue fixed
Desk performance increased.
- 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.
Increased file size upload limit to 2.5MB.
Fixed activation of converse apps and navigation to automation/template in converse apps.
Unable to select the options of Template, Automation and Bulk Campaigns in Converse Apps and hence unable to add templates.
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.
New Links were added for Release Notes and Admin Guides (Post-installation Steps)
Multiple Email notifications were being sent while Incoming message was being updated.
Incoming Message Notifications were implemented