Sage CRM 7.3 Patch Release Notes. Revision: SYS-REA-ENG-73c-5.0 Updated: August 2015

(1)

Sage CRM 7.3

Patch Release Notes

(2)

(3)

Sage CRM 7.3 - Patch Release Notes Page 3 of 19

Overview

4 Latest patch and eWare.dll

4 Documentation and help

4 Steps to install a patch

5 Patch C

6 Issues addressed in patch C

6 Known issues in patch C

13 Patch B

14 Issues addressed in patch B

14 Patch A

19

(4)

Overview

This document provides details of all patches released for Sage CRM 7.3. Installing the most recent patch ensures that you get all of the fixes included in earlier Sage CRM 7.3 patches.

Latest patch and eWare.dll

Item Version

Sage CRM patch 7.3c

eWare.dll 7.3.0.3

Documentation and help

To view context-sensitive Help, click the Help button in Sage CRM 7.3.

(5)

Steps to install a patch

1. Make sure you have Sage CRM 7.3 installed.

You can view the product version number at the bottom of the Sage CRM splash screen. 2. Before installing a patch, back up the following items:

● Microsoft SQL Server database used by Sage CRM. ● eWare.dll file.

● eware.css file (only if you have customized your style sheets).

● LogonTranslations.txt file (only if you have customized your translations). 3. Run the CRM7.3.<PatchLetter>.exe file supplied in the patch distribution package. 4. Complete the setup wizard that starts.

On the Database Server Login step of the wizard, type the credentials of an account that has sufficient permissions on the Sage CRM database in Microsoft SQL Server.

5. If you backed up the eware.css and LogonTranslations.txt files in step 2 of this procedure, restore them to their original locations.

Note: You can find the eWare.dll, eware.css, and LogonTranslations.txt files in the Sage

CRM installation folder.

The default locations of these files are as follows: ● On a 32-bit (x86) system:

%ProgramFiles%\Sage\CRM\CRM\WWWRoot ● On a 64-bit (x64) system:

(6)

Patch C

Release date Files included

August 2015 ● eWare.dll version 7.3.0.3 ● Outlook plugin 7.3.0.1 ● Document plugin 7.3.0.1 ● CTI plugin 7.3.0.1

Issues addressed in patch C

After installing patch C, clear the Web browser cache on each user's computer. This is required to make sure the Interactive Dashboard will work properly after patch C installation.

Issue ID Area Description Status

0-164242-QA .Net There was an issue installing the Sage CRM SDK.

This issue is fixed.

0-163495-QA 3rd Party Software

Group is being sent to MailChimp remained on screen after the group was successfully sent.

0-163729-QA Campaign Management

The User Guide incorrectly stated that a broker rule called Distributed Among

Team Users was available

when scheduling an internal telesales activity.

0-161876-QA Cases Incorrect values were returned for an Advanced Find search.

0-163371-QA Cases An incorrect SQL statement was used to search records.

0-163409-QA Comms/Diary The User field for a

deactivated user showed the user’s ID instead of the user’s name.

0-163947-QA Comms/Diary An email communication was not saved against a case.

0-164365-QA Comms/Diary The End Date value in an appointment wasn’t

dynamically updated when a user changed the Start Date value.

(7)

0-164524-QA Comms/Diary It was possible for two users to edit a communication record at the same time.

0-164553-QA Companies / People

Phone numbers and emails were not displayed on the

Person Find screen.

0-164811-QA Companies / People

A user was unable to merge Person records on an integrated system.

0-164454-QA Component Management

A user was unable to record a field deletion using the Component Manager.

0-164617-QA Component Management

A component script was incorrectly deleted.

0-163882-QA Configuration A user was unable to sort a list using two columns.

0-163189-QA Core Product When a user tried to log on to Sage CRM, an error message appeared incorrectly stating that the user was already logged on.

0-163747-QA Core Product Internet-facing instances of Sage CRM were indexed by Google.

0-164101-QA Core Product The User Log Date field displayed an incorrect date.

0-164289-QA Core Product An SQL error occurred when a user opened a company record where the Person and Lead Last Name fields are empty and non-required.

0-164672-QA Core Product The thousand separator didn’t appear in numeric fields.

0-164825-QA Core Product A user was able to return information about a Sage CRM installation using an SQL injection.

0-164869-QA Core Product A cross-site script that was sent to Sage CRM didn’t work as expected.

0-164871-QA Core Product A user who was restricted from viewing certain tabs could access these tabs using the relevant URLs.

0-164872-QA Core Product An incorrect error message was displayed when a user repeatedly entered the wrong password and was eventually locked out.

(8)

0-164874-QA Core Product An internal IP address was included in a response.

0-164875-QA Core Product Parameters passed through GET and POST requests were interchangeable.

0-164899-QA Core Product An Info Manager was unable to create new users.

0-164021-QA Customization When using workflow, the

Territory field didn’t default

to the user’s home territory.

0-164035-QA Customization Values in a selection list didn’t persist as expected.

0-164118-QA Customization Checkbox values were not displayed when a user printed a screen using a custom Print button.

0-164366-QA Customization Top content for a custom entity incorrectly appeared twice on the custom entity screen.

0-164712-QA Customization When a button caption included an apostrophe, the button didn’t work as expected.

0-163513-QA Dashboard (Classic)

The User Guide did not clearly state that the classic dashboard is available for upgrade customers only.

0-164673-QA Data Upload An error occurred when a user performed a data upload using date information only.

0-162287-QA Database Date only fields in a newly created database appeared as text fields on the User Interface.

0-163951-QA Database The interactive dashboard didn’t load when using Latin1_General.

0-160627-QA Document Drop A document was incorrectly saved to the last viewed opportunity rather than to the current opportunity.

0-164510-QA Documentation The User Guide didn’t clearly explain that a limited number of initial results may be returned for a keyword search.

(9)

0-163525-QA E-mail Client When a user replied to an email or forwarded an email, the Subject field appeared empty.

0-163946-QA E-mail Client When a user created a new email based on an email template, the From email address specified in the template didn’t appear.

0-164238-QA E-mail Client The left navigation bar disappeared when a user clicked Cancel on a new email pop up window.

0-164358-QA E-Marketing (MailChimp)

An error occurred when a user sent a group to MailChimp.

A new segment wasn’t created when a user sent a group with a long name to MailChimp.

The Sage CRM database wasn’t automatically updated when a contact

unsubscribed from a MailChimp campaign.

An incorrect error message was displayed when completing MailChimp campaign fields in Sage CRM.

0-163490-QA Exchange Integration

Company name and Person name weren’t displayed on external appointments.

An appointment that was created in Outlook Exchange and then synched to Sage CRM was displayed in My

CRM but not in Team CRM.

A user was unable to install the Microsoft Exchange Lite plug-in.

0-164159-QA Find / Advanced Find

There were style issues with Advanced Search Select fields on Internet Explorer 11.

An Advanced Find search used to generate a report wasn’t saved against the relevant entity.

(10)

0-163878-QA Install / Upgrade An incorrect message was displayed during the installation of Sage CRM Express.

0-164456-QA Install / Upgrade The mapping component didn’t work as expected.

0-162277-QA Interactive Dashboard

Action icons on interactive dashboards didn’t work as expected.

When a user created a new dashboard and tried to add a list gadget, an unnecessary authorization window appeared.

An error occurred when a user added a report

containing key attribute data to a list gadget.

Interactive dashboards weren’t displayed when HTTPS was used on a multi-server installation with a hardware Load Balancer.

A dashboard gadget displayed incorrect fields.

0-163677-QA Key Attribute Data

A user was unable to change the values of Key Attribute fields.

0-163537-QA Leads Company information wasn’t copied to a new Lead record when a user clicked Ignore

warning and enter Company.

0-163999-QA Library and Templates

Document drop did not work as expected on Internet Explorer 11.

0-164610-QA Licensing An error message was displayed when a user entered a valid Sage CRM license key.

0-163743-QA Mobile The User Agent field for a mobile device was too short.

0-164572-QA Mobile An incorrect label was displayed on the French version of the Mobile theme.

0-163512-QA Navigation There were font and layout issues when using the Sage theme on an integrated system.

(11)

0-163448-QA Notification The value in Notification

Display Count was

incorrectly incremented by 1.

0-163386-QA Opportunities The date value in the

Opened and Closed fields

on a new opportunity or case was not saved correctly.

0-163467-QA Opportunities An email wasn’t filed against the relevant opportunity.

0-160064-QA Order Entry / Products

The Products drop-down list was empty.

0-164272-QA Outlook Integ An error occurred when a user filed an email using the Classic Outlook plug-in.

0-163471-QA Performance / Scalability

The IP address was displayed in the log on screen source view.

0-163547-QA Reports The legend on a chart was truncated in a standard report that was exported to Excel.

0-163628-QA Reports The Sum function didn’t work as expected in an Account report that was exported to Excel.

0-164296-QA Reports My CRM menu options were

not displayed in the

Contemporary theme when a user created a report category title that included an apostrophe.

0-163948-QA SData Provider An SData HTTP request incorrectly returned Personcollection.

0-163877-QA Security Management

Users with no access rights to Marketing information could open the Marketing tab and view Marketing information.

0-154749-QA Soap Integration

The ID of a deleted account was not available to be reused by a new account.

0-163338-QA Soap Integration

On a Sage 200 integration, there were spacing issues with the Integration quick link that’s displayed on the User Interface.

0-162444-QA User Interface A user was unable to create a follow-up task on an iPad Mini.

(12)

0-163826-QA User Interface On Internet Explorer 11, form submission didn’t work as expected when a user resized the browser.

0-163827-QA User Interface The <My Profile> button wasn’t displayed when using the Contemporary theme.

0-164012-QA User Interface The <My Profile> button wasn’t displayed when using the Contemporary theme.

0-162557-QA User

Management

The value of the Default

Email Address field

reverted to the default value instead of maintaining the new value set by the user.

0-163944-QA User

Management

An Info Manager was unable to disable and reassign users.

0-163791-QA Workflow A link in a new escalation rule didn’t support HTTPS.

0-163961-QA Workflow There were layout issues with workflow states on the

Advanced Customization | Workflow screen.

0-164262-QA Workflow The Negotiating stage caption for a progressed opportunity was truncated.

0-165128-QA Workflow A user was unable to send an email from the

Opportunity workflow.

(13)

Known issues in patch C

Issue ID Area Description

0-163637-QA Comms/Diary When a user accesses Sage CRM using the Microsoft Edge web browser, drag and drop does not work as expected. This is a known issue in Microsoft Edge.

For more information and status updates, see the issue description published by Microsoft at

https://connect.microsoft.com/IE/feedback/details/1544800/ms -edge-drop-files-from-explorer-to-browser-does-not-work-as-expected.

WORKAROUND

(14)

Patch B

June 2015 ● eWare.dll version 7.3.0.3

● Outlook plugin 7.3.0.1 ● Document plugin 7.3.0.1 ● CTI plugin 7.3.0.1

Issues addressed in patch B

After installing patch B, clear the Web browser cache on each user's computer. This is required to make sure the Interactive Dashboard will work properly after patch B installation.

0-162322-QA .NET In certain cases, a field value was not automatically set to the expected default value.

0-163521-QA Campaign Management

When a user clicked Create

Campaign on the

MailChimp Campaigns tab

in Sage CRM, an error showed up.

0-162409-QA Comms/Diary A user was unable to save a new task when the

comm_isalldayevent field

was set to Required in

Administration | Customization | Communication.

0-162704-QA Comms/Diary When a user created a new appointment for a company, saved it, and then refreshed the Communications tab, a duplicate appointment appeared in the list of communications.

0-163637-QA Comms/Diary Drag and drop didn't work for appointments on the

Calendar tab.

This issue only showed up in the Internet Explorer and Firefox web browsers.

(15)

0-162597-QA Configuration An SQL filter configured on a button in the Sage CRM user interface didn't work as expected.

As a result, the button was visible in situations where it should have been hidden.

0-162626-QA Customization A parameter entered in the

CreateScript text box for an

entity screen (Administration |

Customization |

<EntityName> | Screens | <ScreenName>) didn't work

as expected:

The entered parameter value displayed in the entity description field.

0-162664-QA Customization When a user right-clicked a Main Menu button on the left-hand side of the Sage CRM screen, the context menu that opened contained duplicate items.

0-162788-QA Customization The Search select

advanced fields grid size

option in Administration |

System | System Behavior

didn't work as expected in the Chrome web browser.

0-163678-QA Customization Wizard

When a user double-clicked a custom entity to view its summary, an internal error occurred.

0-162727-QA Dashboard (Classic)

On the Classic Dashboard, a List gadget configured to display a saved search returned an error message.

0-163503-QA Dashboard (Interactive)

A Dashboard Gadget

showed incorrect information when the date was manually changed on the Sage CRM server.

0-160259-QA E-mail Client Email templates were

corrupted on a computer with Microsoft Office Word 2010 installed.

(16)

0-159796-QA E-Marketing (SageCRM)

On an e-marketing

campaign, the following tabs provided incorrect information: ● E-marketing Campaign Analysis ● E-marketing Wave Activity Summary ● E-marketing Wave Activity Analysis

0-163500-QA E-Marketing (SageCRM)

When a user enabled the Let

users pick plain-text or HTML emails option in

MailChimp, a misleading error message appeared in Sage CRM.

A Resource user in Sage CRM wasn't displayed as a required attendee in

appointments synched from Sage CRM to Exchange Server.

After an appointment was synched from Sage CRM to Exchange Server, it showed the incorrect time zone in Microsoft Outlook.

When a user clicked New

Email on the Find screen, a

newly-created email template was missing from the Templates list that opened.

0-163638-QA Groups / Target Lists

When a user created a Group and added an

Intelligent Select field to the

Search Criteria for the Group, an SQL error occurred.

When a user accessed Sage CRM from a mobile device, the dashboards on the

Dashboard tab didn't load

up properly.

0-160495-QA Mail Merge A mail merge performed on a custom entity failed to fill in all merge fields as expected.

0-158548-QA Mobile A user with no permissions to view specific

communications could view those communications when accessing Sage CRM from a mobile device.

(17)

0-162071-QA Mobile Even though the Use

Individuals option was set

to No in Administration |

System | System Behavior,

users who accessed Sage CRM from mobile devices were still able to create new individuals.

0-163444-QA Mobile When a user accessed Sage CRM from a mobile device and created a new entity, the

Save button was missing on

that entity.

0-163756-QA Mobile An appointment created in the Sage CRM iPhone app showed incorrect time after synchronization with the Sage CRM server.

0-158676-QA Opportunities On a Sage 200 integration, when a user created a quote using the CRM form, the

Total Quote Value wasn't

updated.

0-163964-QA Outlook Integration - Classic

When a user replied to all recipients of an email message filed in Sage CRM, some of the recipients were not included in the reply.

0-162630-QA Outlook Integration - Exchange

When a user added a new contact to Sage CRM from Microsoft Outlook, the plus sign (+) prefix was

unexpectedly removed from the contact's phone number. The plus sign (+) prefix was added back to the phone number in Sage CRM only after the next synch run.

0-162931-QA Quotes / Orders When the Line Item Screen

Position option in Preferences was set to Popup, the popup window

displayed the entire Sage CRM screen and not just the line item.

(18)

0-162613-QA Reports A report showed incorrect data in the Classic/ Interactive Dashboard. This issue occurred when the Chart Options of the report were configured as follows:

- Show Chart was selected. - Show Legend was selected.

- Multi-Bar was set to Yes.

0-162537-QA Reports When a user ran a report where entries were sorted by caption order, an SQL error occurred.

This issue is fixed

0-163796-QA SData Provider In a table-level script, the UpdateRecord function was unexpectedly called several times in situations where it should have been called just once.

0-164226-QA SData Provider In Sage CRM integrated with an ERP system, a table-level script updated data that should have been left intact.

0-164257-QA SData Provider An ERP integration

component failed to install.

0-162973-QA Translation (English prod)

Renaming a team didn't automatically update the US

Translation field value with

the new team name.

0-164133-QA User Interface An attempt to open Sage CRM from within Office Line failed, returning a script error.

0-162507-QA User

Management

A user logon name

containing an apostrophe (') caused errors during logon.

0-162640-QA User

Management

When a system administrator selected the same team in the Primary Team and

Display Team fields on the User Details tab and saved

the changes, the Display

Team field remained blank.

0-160113-QA Workflow Workflow action buttons didn't work correctly in some cases.

For example, workflow action buttons didn't open the Sage CRM screens they were expected to open.

(19)

Patch A

February 2015 ● eWare.dll version 7.3.0.2 ● Outlook plugin 7.3.0.1 ● Document plugin 7.3.0.1 ● CTI plugin 7.3.0.1

Issues addressed in patch A

After installing patch A, clear the Web browser cache on each user's computer. This is required to make sure the Interactive Dashboard will work properly after patch A installation.

0-163250-QA Core Product An incorrect product version number was displayed on the Sage CRM splash screen.

0-163314-QA Advantage ProSeries Integ

On a Sage 300 ERP integration, display issues occurred when a user changed the Sage CRM theme.

0-163384-QA Security Management

Sage CRM security has been enhanced.

This is an enhancement.

0-163462-QA Licensing MailChimp was incorrectly available for users with a standard license.

This behavior is by design.

0-163506-QA Quotes/Orders On a Sage 200 integration, a user was unable to save a Web quote or order in Sage CRM.

0-163529-QA Opportunities When using Sage CRM on an iPad that was synced with Sage 200, a user was unable to create a new opportunity.

Sage CRM 7.3 Patch Release Notes. Revision: SYS-REA-ENG-73c-5.0 Updated: August 2015

Sage CRM 7.3

Patch Release Notes

Contents

Overview

4

Latest patch and eWare.dll

4

Documentation and help

4

Steps to install a patch

5

Patch C

6

Issues addressed in patch C

6

Known issues in patch C

13

Patch B

14

Issues addressed in patch B

14

Patch A

19

Overview

Latest patch and eWare.dll

Documentation and help

Steps to install a patch

Patch C

Issues addressed in patch C

Known issues in patch C

Patch B

Issues addressed in patch B

Patch A

Issues addressed in patch A