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

Transcription

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

2 Copyright 2015 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed, or otherwise duplicated on any medium without prior written consent of Sage Technologies Limited. Use of the software programs described herein and this documentation is subject to the End User Licence Agreement enclosed in the software package, or accepted during system sign-up. Sage and the Sage logo are registered trademarks or trademarks of The Sage Group PLC. All other marks are trademarks or registered trademarks of their respective owners. Sage CRM Patch Release Notes Page 2 of 19

3 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 Issues addressed in patch A 19 Sage CRM Patch Release Notes Page 3 of 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 Documentation and help To view context-sensitive Help, click the Help button in Sage CRM 7.3. For online User Help, online System Administrator Help, and all PDF documentation for this release, go to Sage CRM Patch Release Notes Page 4 of 19

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: %ProgramFiles(x86)%\Sage\CRM\CRM\WWWRoot Sage CRM Patch Release Notes Page 5 of 19

6 Patch C Release date Files included August 2015 eware.dll version Outlook plugin Document plugin CTI plugin 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 QA.Net There was an issue installing the Sage CRM SDK QA 3rd Party Software Group is being sent to MailChimp remained on screen after the group was successfully sent QA Campaign The User Guide incorrectly stated that a broker rule called Distributed Among Team Users was available when scheduling an internal telesales activity QA Cases Incorrect values were returned for an Advanced Find search QA Cases An incorrect SQL statement was used to search records QA Comms/Diary The User field for a deactivated user showed the user s ID instead of the user s name QA Comms/Diary An communication was not saved against a case QA Comms/Diary The End Date value in an appointment wasn t dynamically updated when a user changed the Start Date value. Sage CRM Patch Release Notes Page 6 of 19

7 QA Comms/Diary It was possible for two users to edit a communication record at the same time QA Companies / People QA Companies / People QA QA Component Component Phone numbers and s were not displayed on the Person Find screen. A user was unable to merge Person records on an integrated system. A user was unable to record a field deletion using the Component Manager. A component script was incorrectly deleted QA Configuration A user was unable to sort a list using two columns 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 QA Core Product Internet-facing instances of Sage CRM were indexed by Google QA Core Product The User Log Date field displayed an incorrect date 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 QA Core Product The thousand separator didn t appear in numeric fields QA Core Product A user was able to return information about a Sage CRM installation using an SQL injection QA Core Product A cross-site script that was sent to Sage CRM didn t work as expected QA Core Product A user who was restricted from viewing certain tabs could access these tabs using the relevant URLs QA Core Product An incorrect error message was displayed when a user repeatedly entered the wrong password and was eventually locked out. Sage CRM Patch Release Notes Page 7 of 19

8 QA Core Product An internal IP address was included in a response QA Core Product Parameters passed through GET and POST requests were interchangeable QA Core Product An Info Manager was unable to create new users QA Customization When using workflow, the Territory field didn t default to the user s home territory QA Customization Values in a selection list didn t persist as expected QA Customization Checkbox values were not displayed when a user printed a screen using a custom Print button QA Customization Top content for a custom entity incorrectly appeared twice on the custom entity screen QA Customization When a button caption included an apostrophe, the button didn t work as expected QA Dashboard (Classic) The User Guide did not clearly state that the classic dashboard is available for upgrade customers only QA Data Upload An error occurred when a user performed a data upload using date information only QA Database Date only fields in a newly created database appeared as text fields on the User Interface QA Database The interactive dashboard didn t load when using Latin1_General QA Document Drop A document was incorrectly saved to the last viewed opportunity rather than to the current opportunity QA Documentation The User Guide didn t clearly explain that a limited number of initial results may be returned for a keyword search. Sage CRM Patch Release Notes Page 8 of 19

9 QA Client When a user replied to an or forwarded an , the Subject field appeared empty QA Client When a user created a new based on an template, the From address specified in the template didn t appear QA Client The left navigation bar disappeared when a user clicked Cancel on a new pop up window QA QA QA QA QA QA QA QA QA E-Marketing (MailChimp) E-Marketing (MailChimp) E-Marketing (MailChimp) E-Marketing (MailChimp) Exchange Integration Exchange Integration Exchange Integration Find / Advanced Find Find / Advanced Find 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. 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. 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. Sage CRM Patch Release Notes Page 9 of 19

10 QA QA QA QA QA QA QA QA Install / Upgrade An incorrect message was displayed during the installation of Sage CRM Express. Install / Upgrade The mapping component didn t work as expected. Interactive Dashboard Interactive Dashboard Interactive Dashboard Interactive Dashboard Interactive Dashboard Key Attribute Data 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 multiserver installation with a hardware Load Balancer. A dashboard gadget displayed incorrect fields. A user was unable to change the values of Key Attribute fields QA Leads Company information wasn t copied to a new Lead record when a user clicked Ignore warning and enter Company QA Library and Templates Document drop did not work as expected on Internet Explorer QA Licensing An error message was displayed when a user entered a valid Sage CRM license key QA Mobile The User Agent field for a mobile device was too short QA Mobile An incorrect label was displayed on the French version of the Mobile theme QA Navigation There were font and layout issues when using the Sage theme on an integrated system. Sage CRM Patch Release Notes Page 10 of 19

11 QA Notification The value in Notification Display Count was incorrectly incremented by QA Opportunities The date value in the Opened and Closed fields on a new opportunity or case was not saved correctly QA Opportunities An wasn t filed against the relevant opportunity QA Order Entry / Products The Products drop-down list was empty QA Outlook Integ An error occurred when a user filed an using the Classic Outlook plug-in QA Performance / Scalability The IP address was displayed in the log on screen source view QA Reports The legend on a chart was truncated in a standard report that was exported to Excel QA Reports The Sum function didn t work as expected in an Account report that was exported to Excel 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 QA SData Provider An SData HTTP request incorrectly returned Personcollection QA QA QA Security Soap Integration Soap Integration Users with no access rights to Marketing information could open the Marketing tab and view Marketing information. The ID of a deleted account was not available to be reused by a new account. On a Sage 200 integration, there were spacing issues with the Integration quick link that s displayed on the User Interface QA User Interface A user was unable to create a follow-up task on an ipad Mini. Sage CRM Patch Release Notes Page 11 of 19

12 QA User Interface On Internet Explorer 11, form submission didn t work as expected when a user resized the browser QA User Interface The <My Profile> button wasn t displayed when using the Contemporary theme QA User Interface The <My Profile> button wasn t displayed when using the Contemporary theme QA QA User User The value of the Default Address field reverted to the default value instead of maintaining the new value set by the user. An Info Manager was unable to disable and reassign users QA Workflow A link in a new escalation rule didn t support HTTPS QA Workflow There were layout issues with workflow states on the Advanced Customization Workflow screen QA Workflow The Negotiating stage caption for a progressed opportunity was truncated QA Workflow A user was unable to send an from the Opportunity workflow. Sage CRM Patch Release Notes Page 12 of 19

13 Known issues in patch C Issue ID Area Description 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 -edge-drop-files-from-explorer-to-browser-does-not-work-asexpected. WORKAROUND Use any other supported web browser. Sage CRM Patch Release Notes Page 13 of 19

14 Patch B Release date Files included June 2015 eware.dll version Outlook plugin Document plugin CTI plugin 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. Issue ID Area Description Status QA.NET In certain cases, a field value was not automatically set to the expected default value QA Campaign When a user clicked Create Campaign on the MailChimp Campaigns tab in Sage CRM, an error showed up 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 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 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. Sage CRM Patch Release Notes Page 14 of 19

15 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 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 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 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 QA Customization Wizard When a user double-clicked a custom entity to view its summary, an internal error occurred QA Dashboard (Classic) On the Classic Dashboard, a List gadget configured to display a saved search returned an error message QA Dashboard (Interactive) A Dashboard Gadget showed incorrect information when the date was manually changed on the Sage CRM server QA Client templates were corrupted on a computer with Microsoft Office Word 2010 installed. Sage CRM Patch Release Notes Page 15 of 19

16 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 QA E-Marketing (SageCRM) When a user enabled the Let users pick plain-text or HTML s option in MailChimp, a misleading error message appeared in Sage CRM QA Exchange Integration A Resource user in Sage CRM wasn't displayed as a required attendee in appointments synched from Sage CRM to Exchange Server QA Exchange Integration After an appointment was synched from Sage CRM to Exchange Server, it showed the incorrect time zone in Microsoft Outlook QA Find / Advanced Find When a user clicked New on the Find screen, a newly-created template was missing from the Templates list that opened 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 QA Interactive Dashboard When a user accessed Sage CRM from a mobile device, the dashboards on the Dashboard tab didn't load up properly QA Mail Merge A mail merge performed on a custom entity failed to fill in all merge fields as expected QA Mobile A user with no permissions to view specific communications could view those communications when accessing Sage CRM from a mobile device. Sage CRM Patch Release Notes Page 16 of 19

17 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 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 QA Mobile An appointment created in the Sage CRM iphone app showed incorrect time after synchronization with the Sage CRM server QA Opportunities On a Sage 200 integration, when a user created a quote using the CRM form, the Total Quote Value wasn't updated QA Outlook Integration - Classic When a user replied to all recipients of an message filed in Sage CRM, some of the recipients were not included in the reply 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 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. Sage CRM Patch Release Notes Page 17 of 19

18 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 QA Reports When a user ran a report where entries were sorted by caption order, an SQL error occurred. This issue is fixed QA QA 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. SData Provider In Sage CRM integrated with an ERP system, a table-level script updated data that should have been left intact. SData Provider An ERP integration component failed to install QA Translation (English prod) Renaming a team didn't automatically update the US Translation field value with the new team name QA User Interface An attempt to open Sage CRM from within Office Line failed, returning a script error QA User A user logon name containing an apostrophe (') caused errors during logon QA User 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 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. Sage CRM Patch Release Notes Page 18 of 19

19 Patch A Release date Files included February 2015 eware.dll version Outlook plugin Document plugin CTI plugin 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. Issue ID Area Description Status QA Core Product An incorrect product version number was displayed on the Sage CRM splash screen QA Advantage ProSeries Integ On a Sage 300 ERP integration, display issues occurred when a user changed the Sage CRM theme QA Security Sage CRM security has been enhanced. This is an enhancement QA Licensing MailChimp was incorrectly available for users with a standard license QA Quotes/Orders On a Sage 200 integration, a user was unable to save a Web quote or order in Sage CRM. This behavior is by design 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 Patch Release Notes Page 19 of 19