Date: 25th Jan 22
- Issue: The default Sender ID functionality was not working as expected
Fix: The non-admin users were getting the error message on the Converse Home screen which was reported in case#00107408. (Previously it was reported for the 1.68 version). The organization object did not have permission for the field(s).
The read access in the CheckIsSandbox() method of FMAUtility.cls was checked. In this case, the user did not have access and was receiving an error on the Converse Home page.
Here, there was a read check for the PermissionSetAssignment object. If the user did not have view setup and configuration permissions, it was throwing an error for this check.
To solve this issue, removed the check for reading access on organization access for the PermissionSetAssignment object.
Date: 13th Apr 22
Issue: The client did not have a license to send an SMS from the SMS tab on Salesforce or even to access the Converse Desk tab of SMS-Magic
Fix: One of the SMS-Magic users who held a Power License had a problem when they wanted to send an SMS from the SMS tab on Salesforce or even to access the Converse Desk tab of SMS-Magic. They were getting an error message: “You don’t have a license for this feature. This feature is part of Standard and Enterprise plans.” This happened to only one user with the power license, and the rest of the power license holders were not experiencing this issue.
There was an inactive license record present for this user which was of Basic type. While checking for a license, the code was fetching that inactive license.
To solve this issue, in the getLicenseType() method of LicenseService, a filter of smagicinteract__status__c was added while querying licenses for users.
Date: 27th Apr 22
- Issue: The customer requested customization that on the conversation component the conversation should be visible based on the mobile number that they select.
Fix: Conversations related to the “To” number were visible on the conversation component on the record page. The Conversations were to be changed if the “To” mobile number was changed.
To fulfill this customization, an injection point was created for a custom injection service to which a selected phone number or SenderID was provided as a parameter. The data received from the custom injection service was used to display on the UI in the message list component.
Date: 4th May 22
Issue: Customer was not able to select a plan from converse settings as it was giving an error ‘the list had no rows for assignment to SObject’ while selecting a plan.
Fix: The user was unable to select the plan from Converse settings as it was giving the following error: “List had no rows for assignment to SObject”
In the current version, we were fetching the active users whose profile name is ‘System Administrator’, which caused this issue.
To solve this issue, removed the Profile name criteria from GetActiveUserId() method.
Issue: The customer was receiving an error while adding a manual consent
Fix: The customer was facing an issue when creating manual consent.
Below is the error that the customer was receiving while creating manual consent:
For v1.68.23, the complianceNewConsentHelper.js file attribute was set to the Sender list.
To solve this issue, the profile name criteria were removed from GetActiveUser ID () method.
Date: 18th May 22
- Issue: Record Owners Sender ID option was not available to the customer
Fix: The customer was creating a Converse App automation on the message flow creation window and it was showing the Sender ID that was assigned to them. However, the option to select Record Owners Sender ID was not visible.
In the filterSenderID’ssFromSenderVisibility method, the Record-Owner Check was not added, hence this issue occurred.
To solve this issue, added the below condition in the filterSenderID’s FromSenderVisibility method of SenderService Class:
SenderInfoList[i].SenderID != Constants.RECORD_OWNERS_SENDERID)
Date: 3rd June 2022
1. Issue: The customer was facing license issues for Guest User
Fix: The customer had reported that the automated messages were not getting triggered and they were receiving an error “Required License not assigned to send SMS or MMS”. Also, the org-wide license was not supported.
To solve this issue, the ‘IsFeatureAccessble’ method was updated in the ‘LicenseManagerUtility’ class to support org-wide licenses for user types like community users, and guest users.
Date: 12th Oct 2022
1. Issue: The customer wanted to create a provision to change the owner of the ‘License Type’ records via ‘protectedSettings’ Visualforce Page page
The “License Type” object of the managed package is protected via a trigger interface which makes it impossible to update the records via UI. The records of such protected objects can be created/updated only via Apex.
Sometimes the owner of the records of such protected objects is a ghost user. This causes problems in the expected functionality of the package.
To resolve the problem, the owner of such records needs to be set as one of the internal users of the target org, but that is not possible via UI, thus the need for the provision to update such records of protected objects occur.
Created provision via “protectedSettings” VF page to update the owner of the records of protected objects by passing the user id of the desired user.
Date: 21st Dec 2022
1. Issue: The customer was unable to add a merge field
Fix: Whenever the user was trying to create a Converse Template with the primary object as “Service Appointment” and the “Assigned Resource” selected in the merge field, the merge field dropdown “AppAssistInfoURL” field was not getting displayed.
The managed package code was on API version 47 (Metadata PAI version). The assigned resource was a standard Salesforce object. The field AppAssistInfoURL was only available on API version 51.0 and later. Hence, this field was not populating in the merge field list.
To resolve this, the MessageUtility.cls-meta.xml and Security.cls-meta.xml was updated to API version 55.