Addressed issues

CRMS-504

When a system administrator customized the SLA Severity field in | Administration | Customization | Cases to set Default to any value and then selected Save, an "UnexpectedEvent" error occurred.

CRMS-628

When a user created a new case, the Team field was not populated with the default value defined for the Case entity.

For example, this issue occurred when the default value of the case_channelid field was set to Current User's Default Team.

CRMS-645

When a system administrator or info manager edited the case_primarypersonid field and selected Save, an "ErrorSavingEntryDetails UnexpectedEvent" error occurred.

CRMS-693

• Cases

• Companies
  

• People
  

• Email

• Workflow

When a workflow rule was configured to automatically send emails, the emails were not added to the Communications tab for the related case record.

For example, this issue occurred in the following scenario:

• You had a workflow rule configured to send emails whenever a user created a new case.

• The email was to be sent to the user who was assigned the case and the person (client) for whom the new case was raised.

As a result, the email was added to the Communications tab for the user and person, but not the case because the related comm_caseid field value was set to NULL in the database.

CRMS-582

• Classic Outlook plugin

• Lite Outlook plugin

CRMS-740

• Companies

• People

Sage CRM failed to correctly wrap the values of multiline text fields. As a result, long values were not fully displayed in the user interface.

For example, you could observe this issue on the Communications tab when the subject or details of a communication contained a long value.

CRMS-703

The User Help did not mention the following behavior: 

When a user merged a source company that had associated custom entities, Sage CRM copied the custom entities over to the destination company.

CRMS-760

A custom element was not displayed in the Administration area in the Sage CRM user interface if the SQL field in the element properties contained a SQL statement with an EXISTS clause.

This issue occurred if a system administrator did the following:

1. Went to | Administration | Advanced Customization | System Menus.

2. Edited the Admin tab group contents to add a new custom element.

3. Populated the SQL field in the element properties with a statement containing an EXISTS clause, for example:

   EXISTS(SELECT * from Custom_SysParams where parm_name='Escalation' and parm_Value='Y')

4. Saved the changes.

As a result, the new custom element wasn't displayed in the Administration area, but it was still present in the left-hand side panel.

CRMS-461

• Customization

• Workflow

Sage CRM displayed wrong workflow actions when a user selected the Action icon () in an interactive dashboard gadget of type List.

This issue occurred when: 

• The interactive dashboard gadget was configured to display workflow anchor columns.

• The related workflow rule was restricted to a specific team or had a custom JavaScript condition configured.

CRMS-674

• Database

• User interface

When a system administrator went to | Administration | Advanced Customization | Tables and Databases, selected the Change button (), and then selected Save without changing any values, the following error occurred:

"Unable to connect to database."

CRMS-673

• Database

• User interface

When a system administrator added a new database connection in | Administration | Advanced Customization | Tables and Databases, the connection did not appear on the screen.

CRMS-436

Sage CRM behaved unexpectedly when a user created a new person and the person's name was identical to a name existing in the system:

• With deduplication enabled, Sage CRM did not prompt the user to select the existing person.

• With deduplication disabled, Sage CRM still prompted the user to select the existing person.

This issue affected integrated systems only.

CRMS-842

Documentation

The Getting client ID and secret for Outlook web app topic in the Administrator Help provided incorrect redirect URI.

The redirect URI provided in the topic included uppercase letters. However, the URI must be all lowercase.

CRMS-724

CRMS-739

When a company had several associated persons sharing the same email address, each email message sent to that address caused Sage CRM to create a communication for each person regardless of the person status in Sage CRM.

The expected behavior in this case is that a communication should be created only for the persons whose status is Active or blank.

CRMS-540

When a user created an email using a preconfigured template containing some merge fields in the subject, Sage CRM did not replace the merge fields with the actual values.

This issue occurred when a user created a new email in the context of a custom entity record and the custom entity was configured as follows:

CRMS-481

When a system administrator changed a password in | Administration | Email and Documents | Advanced Email Management Server Options, the Email Management service stopped working and following error was written to the Sage CRM log:

"Invalid eWare username or password."

CRMS-452

When a user sent an email to a company using an email template whose body contained the #comp_name# merge field, the field was not replaced with the actual company name.

This issue occurred when the target company had no default person set.

CRMS-615

• Mail merge

• Quotes/orders

CRMS-527

When a user selected the Send to Mailchimp button on a group, the values in the comp_idcust field were unexpectedly set to NULL in the Company table of the Sage CRM database.

This issue affected only those groups whose comp_idcust field was populated.

CRMS-495

When a user ran a report, a SQL error occurred. Also an "Invalid column name addr_city" error was written to the Sage CRM log file.

This happened when the report was configured as follows:

Report Contents
Company : Company Name
Opportunity : Total Quote Value
Opportunity : Details
Opportunity : Close By
Opportunity : Reason For Loss
Opportunity : Assigned To

Search Criteria
Opportunity : Total Order Value
Opportunity : Reason For Loss

Sort On
Opportunity : Total Order Value

Group By
Opportunity : Status
Opportunity : Assigned To

Advanced Find
The report was set up to use the following query:

Address : City Begins With <value>

OR

Cases : SLA = <value>

AND

Cases : Opened By = <value>

AND

Cases : Product = <value>

AND

Cases : Person

CRMS-630

When a user deleted a company address, the address was removed from the user interface but not from the Sage CRM database.

As a result, an HTTP request sent to the RESTful API would return the deleted company address.

CRMS-636

• Search

• Quick find

When a system administrator used a SQL query to filter the records displayed in the drop-down list for an advanced search select field (), the drop-down list failed to open.

For example, this issue occurred when a system administrator did the following: 

1. In | Administration | Customization | Communication, selected comm_opportunityid.

2. Entered a statement in Search SQL.

3. Saved the changes.

CRMS-848
CRMS-849
CRMS-851

• Security management

• Third-party components

Sage CRM used a third-party component Apache Log4j whose versions 2.0.0 - 2.14.1 contained vulnerabilities that allowed an attacker to execute malicious code.

These vulnerabilities are logged in the NIST National Vulnerability Database under the following IDs:

• CVE-2021-45046

• CVE-2021-45105

• CVE-2021-44228

• CVE-2021-44832

You also can find the detailed descriptions of these vulnerabilities on the Apache Log4j Security Vulnerabilities page.

CRMS-698

• User interface
  

• Interactive dashboard

When a user set a comma (,) as a decimal point and a dot (.) as a thousand separator in | Preferences, these changes were not applied to reports in the interactive dashboard.

As a result, the reports used the incorrect separators: a dot (.) as a decimal point and a comma (,) as a thousand separator.

CRMS-773

• Users

• Groups