Addressed issues

CRMS‑857

Calendar

This issue occurred when Sage CRM had a root territory and one or more subterritories configured.

When a system administrator created a new user that had all rights on the root territory, and then the user created an appointment for a company in a subterritory, the appointment wasn't shown to the user in the calendar.

CRMS-1040

Component management

Sage CRM logged out a user unexpectedly. This issue occurred in the following scenario:

1. A system administrator used the Component Manager to create a new custom entity that had cases.

2. A user created a new custom entity record, and then created a new case for the record. After this step, Sage CRM logged out the user.

CRMS-982

Customization

When a user edited a record on a custom screen and then saved the changes, the Sage CRM logon screen opened.

CRMS-928

• Customization

• Document drop

Sage CRM logged out a user after they attached a document to a custom entity record or updated an existing document attached to it.

CRMS-752

• Customization

• Quotes and orders

When a user selected a non-default status for a Quote record and saved the changes, the status was unexpectedly reset back to the default one.

This issue occurred when the selected status used a custom translation and code.

CRMS-969

Document drop

When a user attached a file to a Company record on the Documents tab, the Regarding field showed the wrong description.

This issue occurred when a user performed the following steps: 

1. Opened an Opportunity record.

2. Opened Keyword Search, searched for a Company record, and opened it.

3. Opened the Documents tab of the Company record and attached a file.

CRMS-929

Documentation

The Hardware and Software Requirements document did not cover scenarios where the database server used by Sage CRM required more hardware resources.

CRMS-822

Email

When a user sent an email using an email template with an attachment added, the email failed to be sent.

This issue occurred only when the attachment name contained a diacritic (â, ê, î, and so on).

CRMS-912

Exchange Integration

When a system administrator enabled a Sage CRM user mailbox for synchronization with Exchange on the User Mailbox Management tab in | Administration | Email and Documents | Exchange Server Integration | Connection Management, the synchronization operation failed with an error stating that the Sync Engine failed to connect to an Exchange mailbox.

This issue occurred if the system administrator did not have an Exchange Online mailbox configured for their administrator account in Office 365.

CRMS-751

Exchange Integration

When a user edited an appointment or task synchronized from Sage CRM to Exchange Online, the time of the appointment or task unexpectedly changed.

This issue occurred in the following example scenario:

1. A system administrator configured bidirectional synchronization for appointments and tasks between Sage CRM and Exchange Online.

2. A user created an appointment in Sage CRM and set the appointment time to 4:00 PM – 5:00 PM of the current date.

3. When the appointment was synchronized to Exchange Online, the user edited the appointment in Microsoft Outlook without changing the appointment time.

4. When the user saved the modified appointment, its time unexpectedly changed to 3:00 PM – 4:00 PM.

CRMS-460

Leads

With the Web to lead feature enabled and a lead workflow configured, when a user created a new lead, Sage CRM assigned the wrong values to the lead_status and lead_stage fields of the lead.

CRMS-878

• Leads

• Opportunities

An error "No company or person was selected. Cannot continue with conversion." occurred when a user tried to convert a lead to an opportunity.

This issue was observed only if the website address specified for the related company exceeded 40 characters.

CRMS-874

Opportunities

When a system administrator changed Order by Desc to Yes in | Administration | Customization | Secondary entities: Opportunity Progress | Lists | OpportunityProgressList, this change was not applied to the last column on the Tracking tab of an Opportunity record.

CRMS-896

Reports

When a user edited a report on opportunities to sort records by the Opportunity: Company field, this change did not have any effect.

CRMS-879

Reports

Sage CRM failed to generate a report in the Microsoft Excel format when the currency rate specified in | Administration | Data Management | Currency exceeded 999.

CRMS-926

Security management

Apache Tomcat 9.0.33 supplied with Sage CRM contained the following security vulnerabilities: 

• CVE-2021-30639

• CVE-2021-41079

CRMS-786

Self service

ISSUE 1

When a user opened a Case record, a 500 HTTP error occurred. This issue showed up when a system administrator configured the Case entity as follows: 

1. Opened  | Administration | Cusomization | Cases.

2. On the Screens tab, selected the ssCaseEntry screen.

3. Selectd the case_referenceid field.

4. In the CreateScript box, added Required=true.

ISSUE 2

When a user tried to modify and save a Case record, a 500 HTTP error occurred. This issue showed up when a system administrator configured the Case entity as follows:

1. Opened <My profile> | Administration | Cusomization | Cases.

2. On the TableScripts tab, selected New.

3. In the Table-level script box, entered a script.

4. Saved the changes.

CRMS-804

Territories

The Document Territory field of an attached file was reset to a blank value when a user performed the following steps: 

1. Opened a Company record.

2. Added a file on the Documents tab.

3. Set the Document Territory field of the attached file to Default.

4. Saved the changes.

5. Opened the attached file on the Documents tab and observed the value of the Document Territory field.

CRMS-979
CRMS-850

Translation

When the Opportunities pipeline was enabled in a non-English version of Sage CRM, the legend below the pipeline and some of the user interface text were still displayed in English.

CRMS-875

User interface

When a user entered a telephone number in Sage CRM without specifying a country code, and then clicked that telephone number to dial it, the telephone number was dialled with a country code.