Addressed issues
The following is a list of customer cases addressed in this release.
|
Issue ID |
Area |
Description |
Status |
|---|---|---|---|
|
CRMS-1643 |
Calendar, |
When the time zone in Sage CRM and on the Windows server hosting Sage CRM was set to (UTC -07:00) Mountain Time (US & Canada), a quick appointment created in the Sage CRM calendar showed the wrong time. |
Fixed |
|
CRMS-1825 |
Communications |
A communication that was created by an escalation rule mentioned the wrong person in the Person column. For example, this issue occurred when an escalation rule was configured to create a communication about an opportunity. |
Fixed |
|
CRMS-1769 |
Communications |
An escalation rule didn't work properly: Instead of sending emails about modified opportunities to the users that had the opportunities assigned, the rule sent all such emails to one user only. This issue occurred when you used the oppo_assigneduserid field to identify a user. |
Fixed |
|
CRMS-1728 |
Communications |
In some situations, an email linked to an opportunity as a communication mentioned the wrong company not related to the opportunity. This issue occurred when escalations rules were enabled. |
Fixed |
|
CRMS-507 |
Core product |
The Apache Tomcat service installed and used by Sage CRM unexpectedly stopped running. |
Fixed |
|
CRMS-1869 |
Core product |
After upgrading to Sage CRM 2024 R1, the following error occurred: "SQLError: String or binary data would be truncated (ALTER TABLE Lead ALTER_COLUMN Lead CompanyWebSite NVARCHAR(100);)" |
Fixed |
|
CRMS-1864 |
Customization |
After upgrading to Sage CRM 2024 R1, an Advanced Search Select field that provided a list of users stopped working: When a user selected the magnifying glass icon, the field constantly displayed "Please wait..." |
Fixed |
|
CRMS-710 |
Customization |
In some situations, Search Select Advanced fields displayed wrong values. This issue occurred only when Sage CRM was configured to use an external database. |
Fixed |
|
CRMS-1806, |
Customization |
When a user opened a custom entity record, the following error occurred: "You are currently not logged in, or eCRM is not correctly registered." This issue affected the custom entities that had Find, Communication, Library, and Workflow. |
Fixed |
|
CRMS-1495 |
Documentation |
The documentation fails to mention that Sage CRM doesn't prompt the system administrator to change their password when demo data is installed. |
By design |
|
CRMS-1548 |
Documentation |
The topic titled Configuring OAuth 2.0 for Exchange Online (Office 365) in the System Administrator Help contained the following wrong URL that contained a full stop at the end: https://outlook.office365.com/EWS/Exchange.asmx. |
Fixed |
|
CRMS-213 |
Documentation |
The Sage CRM UI and documentation used the wrong term (SData 2.0) for the Sage CRM RESTful API. |
Fixed |
|
CRMS-1542 |
|
An escalation rule configured to sent emails failed to do so. |
Fixed |
|
CRMS-1879 |
Email management |
When Email Management was configured to use HTTP rather than HTTPS, the following error was written to the logs: "Exception connecting to Mail Server: Error connecting with SSL." |
Fixed |
|
CRMS-1523 |
Email management |
Use TLS TLS for SMTP checkbox wasn't available in |
Fixed |
|
CRMS-1590 |
Installation, |
When a system administrator selected to opt out of web analytics, Sage CRM still tried to make calls to the web analytics API. |
Fixed Web analytics code is now completely removed from Sage CRM setup. |
|
CRMS-1480 |
Mail merge |
When the Default download folder option in user preferences specified a local folder, Sage CRM still didn't save files in the specified folder. |
Fixed This option has been removed from user preferences. Because of the changes in JavaScript and web browsers, it is no longer possible to configure the default download folder. |
|
CRMS-1809 |
Mailchimp |
When a user selected Send To to send a group to Mailchimp, an "Invalid Resource" error occurred. |
Fixed |
|
CRMS-254 |
Mailchimp |
When you switched from standard to premium subscription in Mailchimp, the Mailchimp Integration stopped working. |
Fixed |
|
CRMS-1124 |
Mailchimp |
When the name of a Mailchimp campaign contained an apostrophe ('), it was not possible to close the campaign: Selecting Close Campaign didn't have any effect. |
Fixed |
|
CRMS-1022 |
Mailchimp |
When a segment of a Mailchimp campaign was created by a user, the Created By field still showed that the segment was created by the system administrator. |
By design The Created By field has been removed from the UI to avoid confusion. This field always shows that a segment was created by the system administrator. This happens because technically a segment is created by an automated action that uses the system administrator account. |
|
CRMS-910 |
Mailchimp, |
When a user sent a group to Mailchimp, some records in the group weren't actually sent and Sage CRM displayed no errors in this case. |
Fixed |
|
CRMS-1743 |
Opportunities |
The oppo_description field length in the OpportunityProgress database table was limited to 50 characters. This caused issues when a user modified an existing Opportunity record. |
Fixed The oppo_description field length has been increased to 128 characters. |
|
CRMS-1444 |
Reports |
When a user configured advanced search in a report and then edited and saved the report, the advanced search configuration was lost. |
Fixed |
|
CRMS-1329 |
RESTful API |
The GET operations in the RESTful API returned incorrectly ordered data in some scenarios. |
Fixed |
|
CRMS-1788, |
RESTful API, |
When IIS auto login was enabled in Sage CRM, it was possible to use the RESTful API to view, edit, and delete data without providing a password. |
Fixed |
|
CRMS-1895 |
Security |
Apache Solr 8.11.2 used by Sage CRM contained security vulnerabilities. |
Fixed Apache Solr has been upgraded to version 8.11.3. |
|
CRMS-925, |
Security management |
The Log4j libraries used by Sage CRM contained security vulnerabilities. |
Fixed Log4j libraries have been upgraded. |
| Administration | Email and Documents | Email Management Server Options