Date: July 07, 2020
Issue: Error message error “ApexCPU Time Limit Exceeded”
Fixed the issue when inserting bulk records into Converse App Task object failed with error “ApexCPU Time Limit Exceeded”
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.
Autoreply will be triggered only for the message senders whose message matches the exact keyword. No auto-reply will be triggered otherwise.
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 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 firstname.lastname@example.org with any questions you might have.
Fixed date formatting issue.
SMS credits consumed displays correctly now.
Component error fixed.
- Converse desk incoming notification.
- All conversations related to a record displayed in conversation view.
Fixed Bulk Campaign operator related to Converse App.
List view increased to 2000 records.
Fixed multiple records update for SMS History in Portal search message component fixed
Added bulk sms component for community users.
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.
While sending a Bulk SMS the Send SMS button is disabled after the first use.
- 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.
Resolved the utility error and SOQL Limit exception
The Streaming API usage is happening for all the users active on the conversation page. It should happen only for the conversation owners.
Corrected the usage of Streaming API for both outgoing and Incoming messages.
Templates were not displayed alphabetically in the template dropdown.
All templates are being displayed in alphabetic order
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.
SMS-History is being created and successfully and also being forwarded to Portal
Partial SMS and those with Error status were not being sent out.
Added callSMSAPI Callout after for loop in SMSUtility.
isSearchable checks missing in Campaigns, Settings, Bulk messages and Conversation Composer.
- Implemented CLI changes
- Added isSearchable checks
Unable to use parent object name field & optout field in new message & in the Converse desk.
Launched the Winter 19 Release.