Sage CRM. Sage CRM 2014 R1 Patch Release Notes

Transcription

1 Sage CRM Sage CRM 2014 R1 Patch Release Notes

2 Copyright 2014 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.

3 Contents Overview... 2 CRM Document Version Code for these Release Notes... 2 Sage CRM 2014 R1.2 Issues List... 3 Changes to supported software... 4 Core Sage CRM update... 4 Social media add-ons update... 8 Sage CRM 2014 R1.1 Issues List... 9 Sage CRM 2014 R1 Release Notes 1

4 Overview This document provides details about Sage CRM Patch Releases for Cloud version 2014 R1. The latest version is 2014 R1.2.1 These release notes are for Sage OpCos, Sage CRM partners, and Sage CRM customers. Please note that while the document refers to Sage CRM, CRM, or the CRM system throughout, regional products may use different brand names. CRM Document Version Code for these Release Notes SYS-REA-ENG Sage CRM 2014 R1 Release Notes 2

5 Sage CRM 2014 R1.2.1 Issues List Note: The message This issue could not be reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Ref ID Area Description Status QA Core Product When creating a Company record, duplicates were created for some fields in the database. For example, Business QA Reports A user was unable to upload their own logo for PDF reports. The Panoply logo was displayed instead QA Custom Entities It was not possible to enter a name in the Company field in the context of a Sage CRM Builder entity record. Sage CRM 2014 R1 Release Notes 3

6 Sage CRM 2014 R1.2 Issues List Note: The message This issue could not be reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Changes to supported software All versions of Office 365 are now supported. Core Sage CRM update Ref ID Area Description Status QA Campaign Some reports had duplicate Management rows QA Companies / People The Company team tab was not available in the context of Company for Essentials users QA Core Product When you create a new status for workflow, there was no GIF icon set for the new status QA Companies / People An Essentials user was unable to access the Company Team tab for companies QA Core Product There was an issue with the Holiday set option for SLAS when the option "No Holiday Set Items" was set QA Core Product It was impossible to see the statistics for opportunities in the Opportunities tab when all stages were selected QA Currency Multi-currency quotes displayed the main currency only QA Customization If the name of a custom entity built using Sage CRM Builder contained an accented letter, Sage CRM removed that letter from the entity name. For example, Matériel became Matriel. If an icon for a status is missing, a default "unknown" icon is displayed. Sage CRM 2014 R1 Release Notes 4

7 QA Customization In the context of workflows, it was not possible to write JavaScript conditions that were more than 255 characters long QA QA QA Customization Wizard Customization Wizard Custom Entities A user was unable to create a new custom entity record by right-clicking New, then <custom entity name> from My CRM. From the Case entity, a user was unable to create a new Payee record, where Payee was a custom entity. On an install with multicurrency enabled, it was not possible to update the Currency fields on custom entity records built with Sage CRM Builder QA Data Upload Selection list entries containing the '&' character and/or spaces were duplicated during upload QA Data Upload In the context of a custom entity created with the Sage CRM Builder, it was not possible to change a field to Not Required. This also caused issues when performing a data upload for the custom entity QA Data Upload A user was unable to perform a People data upload, because of an issue around required fields QA Data Upload It was possible to upload data for a custom entity created with the Sage CRM Builder, even if required fields (for example, User) were blank QA Comms/Diary When the From field of an was left empty, the The character max length limit was removed. This issue could not be reproduced. Data upload for custom entities now respects the required fields settings. In the log files you can see which records failed, and also we've introduced the ability to let you know which fields were blank. This is by design. This is because the From field in Sage CRM 2014 R1 Release Notes 5

8 was marked as sent from the logged on user QA Comms/Diary After editing a Communication record and clicking Back, the user was taken to a different customer and/or company context QA Comms/Diary The Subject field of is required by default, and can't be left blank QA Comms/Diary When creating a new Communication from the context of a company, the Person SSA field wasn't filled with the correct default Person QA Hosting Cloud Platform When a user exported a report to PDF, the logo and the legend for the chart were not displayed in the PDF QA Leads A custom field to check a Lead Updated Date was updated each time the Lead record was viewed, instead of being updated when a change to the record was made QA Leads When the lead_opened field is set to Date only, a user who lives in a different time zone than the server machine sees the incorrect date for their time zone QA Opportunities The Forecast feature did not display any figures in the "Closed" column for a user. the reminder template was set to None, and in the Workflow configuration, the "From User" and "From " settings were also not set. s are sent from the logged on user when the From field is set to None in the template and/or the workflow. This is by design. The workaround is to delete the field from the screen, and then add it back to the screen again. This is by design. The DateOnly field always takes the server time and never adjusts for time zones or Daylight Saving Time. Sage CRM 2014 R1 Release Notes 6

9 QA Opportunities The Opportunity pipeline didn't display the correct figures for "All Opportunities" QA Opportunities On French instances of Sage CRM, there was a missing translation on the Opportunity pipeline when a user filtered opportunities to All Stages QA Outlook Integ When sending an attachment via using the Outlook plug-in, the pop-up window stayed open after the message was sent QA Outlook Integ Using the Classic Outlook plug-in, a Dutch language user was unable to synch an appointment from Sage CRM to Outlook QA Outlook Integ A user was unable to reinstall the Outlook plug-in QA Outlook Integ A single sign on check box was displayed on the installer for the Outlook plug-in. This needed to be hidden QA Reports When a user exported a report to PDF, paragraph breaks were missing and the information was displayed in one block QA Sage 50 Integration QA Sage 50 Integration QA Translation (English prod) A user kept being logged out of Sage CRM. On a Sage 50 Accounts integrated account, a user was unable to click into any of the records tabs in Sage CRM. There was an issue with the French translation of "Building in progress" for the Sage CRM Builder User Interface The "Contact Support" functionality was available on trial instances of Sage CRM. This issue is fixed (duplicate). This issue could not be reproduced. The translation was amended to "Construction en cours". This functionality is only available to paying customers. Sage CRM 2014 R1 Release Notes 7

10 QA User Management A user wanted to run Log Activity reports to measure how much time sales reps were using Sage CRM. However, the log and duration reports did not seem to display the correct data Web to Lead A user asked for the web2lead logs to be updated in order to make it easy to know on which fields data insertion was failing QA Workflow Deleting a workflow state or rule from the list of states/rules resulted in an unexpected error which deleted the whole workflow. This can't be fixed. This is because when a user closes their browser window without clicking Log Off first, then Sage CRM cannot detect that the user is no longer using Sage CRM until that user tries to log on again. Social media add-ons update The following cases were fixed for the social media add-ons: Ref ID Area Description Status QA Facebook The Facebook tab on Company records was not displayed correctly QA Facebook A user was unable to access Facebook profiles on Company screens QA Twitter A user was unable to access the Twitter tab in My CRM and from Company records QA Yammer A user was unable to work with the Twitter and Yammer add-ons on. Sage CRM 2014 R1 Release Notes 8

11 Sage CRM 2014 R1.1 Issues List Note: The message This issue could not be reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Ref ID Area Description Status QA Core Product A user received a Recreate Views Manually error on the Opportunities tab Customization A user had an issue with Mail Merge customizations, following an upgrade QA Customization It was not possible to change the value of select and multiselect fields for a custom entity after it had been created QA Find / Advanced Find If a multi-select field was added to a Search screen for any core entity, no records were returned if the --All-- option was selected on the multi-select field QA Hosting Cloud Platform There was an issue with the Buy Now page, if it was accessed from the Interactive Dashboard in trial instances of Cloud QA Mail Merge Mail Merge fields were not populated for quotes QA Mail Merge There was an issue with Mail Merge and exchange rates when an opportunity and its quote used different currencies. Sage CRM 2014 R1 Release Notes 9