v7.1 SP2 Release Notes

Transcription

1 v7.1 SP2 Release Notes

2 Copyright 2012 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 Sage CRM v7.1 SP2 Release Notes Introduction... 2 Who can install this release?... 2 Date of Release... 2 Version Numbers... 2 CRM Document Version Code for these Release Notes... 2 Documentation... 3 Issues List... 4 Rolled Up Fixes Known Issues Supplementary Information for Documentation More Notes on this Release Mail Merge () Method in.net API Customizing Sage CRM Updated Documentation for Documents/Reports Settings Viewing the Full Report from a Classic Dashboard Chart Location of New Sample Mail Merge Templates Updated Sage CRM Twitter Component Cross-Browser Compatibility and Safari Sage CRM 7.1 SP2 Release Notes Page 1 of 16

4 Introduction 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. Who can install this release? The install options available for 7.1 SP2 are as a full install or as a patch. The full install can be used for: A new install of 7.1 SP2 An upgrade from 7.0 SP1 It is recommended that the patch is applied to: 7.1 GA 7.1 SP1 Date of Release April 2012 Version Numbers Release Version: 7.1 SP2 DLL Version: Doc Plugin: Outlook Plugin: CTI Plugin: CRM Document Version Code for these Release Notes SYS-REA-ENG Sage CRM 7.1 SP2 Release Notes Page 2 of 16

5 Documentation The following new/updated documentation is available with this service pack: Description Release Notes What s New Guide Software Support Matrix User Guide System Administrator Guide Context Sensitive User Help Context Sensitive System Admin Help Installation and Upgrade Guide Version Code SYS-REA-ENG SYS-REL-ENG IMP-MAT-ENG USE-MAN-ENG SYS-MAN-ENG USE-HLP-ENG SYS-HLP-ENG IMP-UPG-ENG The PDFs of the above are available on the Sage CRM Ecosystem web site ( The following new product videos are available with this service pack: Description What s New in Sage CRM v7.1 SP2 Creating and Sharing a Mail Merge Template Getting Started with Sage CRM Version Code REL-VID-ENG TPL-VID-ENG QSG-VID-ENG All product videos are available on the Sage CRM Ecosystem web site ( Sage CRM 7.1 SP2 Release Notes Page 3 of 16

6 Issues List The following cases have been addressed in Sage CRM version 7.1 SP2. Note: The message 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 Address Linking The Address Linked check box on the People panel in the Addresses tab was not checked as expected after creating a new company and selecting the Business check box on the Addresses panel. The check box was still not selected after clicking the Change button and selecting the Address Linked check box manually QA Address Linking Using "Select Address To Copy" option was not displaying the expected number of addresses QA Call Handling "Got Through" button was re-appearing during outbound call and, if clicked on, creating inaccurate statistics for the call lists QA Campaign Management Script error when using the Date/Time picker while creating a new appointment from an outbound call QA Cases Invalid Column Name error when a field was added to the Case Progress screen which did not exist on the Case QA Cases After creating a new case within a demo company, 3G Homes, the phone numbers were split across two lines instead of displaying on one. This issue is by design. Note: If fields on the case table need to be tracked then a corresponding field should be added to the case progress table. Fields should be added to the case table first QA Companies / People QA Companies / People QA Companies / People QA Companies / People Part of a company name contained within double quotes was cut off when using the company dedupe screen. A user with a security profile which allowed them to insert everything expect People and Companies was logged out of CRM when they tried to add an address. Incorrect address was displaying when adding a new person from the web picker of the appointment screen. A new multi-select field added to the Person screen was giving the message "you may be entering a person that already exists in the database" when you selected Update Record Anyway, and the changes were not saved. This issue has been fixed. Sage CRM 7.1 SP2 Release Notes Page 4 of 16

7 Ref ID Area Description Status QA Companies / People The message "The field is already matched" was displayed after adding a new person and then trying to select a company. This was on a customized screen using the pers_companyid field. This is by design. This issue was caused by the same SSA field (pers_companyid) being displayed on the person entry screen. This caused the conflict. Removing this field from the PersonEntryScreen and using the default one in the PersonWebPicker fixes the problem QA Core Product A company was not being fully deleted after a communication had been created for it as a result of an Export To File action on a group QA Core Product Not possible to convert a task to an appointment. This issue is by design QA CTI Script error after blanking out the CTI Internal Number Length field QA Customization A customization using Advanced Search Select for Products and Product Families was not working as expected QA Customization Continue button on Cases tab in Custom Entity not behaving consistently QA Customization ClientSide script files were not being included as part of a customization QA Customization A button group customization on the Addresses tab was not working as expected QA Customization A default value on OrderItemsSummary screen, set using a field-level script customization, was not displaying as expected QA Customization An error was produced when using a lookup family which had entries wider than 15 characters on a custom Intelligent Select field QA Customization The format of a custom check box on the company summary screen was displaying differently in view and edit modes QA Dashboard A report which did not include the entity ID was not displaying on the Interactive Dashboard QA Database Communications tab slow to load where lots of communication had been added to a person in the CRM demo data QA Data Upload Dates from an XLS or XLSX file where not being uploaded in the correct format QA Data Upload Errors on a data upload from XLS file in a German system. Sage CRM 7.1 SP2 Release Notes Page 5 of 16

8 Ref ID Area Description Status QA Comms/Diary User in different timezone from server was seeing previous day's calendar when clicking on the View Today button in the Calendar QA Comms/Diary Changing the person linked to a task from the task screen was reverting to the original person when you went back into the task QA Comms/Diary If you linked a task to a company, but removed the default person link, then the company link was also being removed QA Comms/Diary It was not possible to change the account from an existing task QA Comms/Diary An SQL error occurred when trying to view the calendar after applying patch 7.1c QA Comms/Diary Communication "owner" was not being saved on existing communication QA Comms/Diary Error after comm_location was removed from CustomCommunicationDetailBox screen QA Comms/Diary Not able to change the company on an existing task QA Comms/Diary Task was changed from being assigned to one user to "none", but was still appearing in the My CRM list of the original user QA Client Unable to resize inline image in QA E-Marketing (SageCRM) Translated values were not displaying in E-marketing templates QA Integration English translation of a German title was appearing on a contact in Outlook after synchronization QA Integration An HTTP error occurred when trying to sync with the server QA Integration Phone number was splitting across area code and country in CRM even though these settings were not in use QA Integration When using Outlook 2007 and Server 2007 SP3, some columns of a contact's address in Outlook were not displaying correctly QA Export Data Error when exporting a file to CSV with German special character in file name QA Export Data 404 error when trying to export companies in increments of QA Export Data Not able to change date format in exported XLS report. Sage CRM 7.1 SP2 Release Notes Page 6 of 16

9 Ref ID Area Description Status QA Manager editor was not loading when working in a new language, which was added from Admin Customization Translations QA Find / Advanced Find Search criteria was lost after scrolling to second page of search results on iphone. This issue if fixed. See also QA and QA QA Hosting There was an error on a cross-tab report where the sort order was set to user, and the sorting options "By Translation" or "By Caption Order" were selected QA Install / Upgrade QA Install / Upgrade QA Install / Upgrade QA Install / Upgrade An error was generated when trying to export a report to Excel which was larger than 1500 KB. The length of customized CRM phonedata fields was reset after updating with a patch. addresses were missing for some records after upgrade had warned of potential duplicate Person phone numbers. Advanced Search Select was not returning any results after upgrading from v6.1 to v QA Soap Integration Although phone types were correctly populated in the link table and there are no sync or UI errors, an extra type column was added to the phone and tables following the sync of the schema QA Interactive Dashboard Person entity not available on Interactive Dashboard after setting "Use Individuals" to "Yes" QA Interactive Dashboard When a user did not have security access to Leads, they were unable to create a gadget for tasks on the Interactive Dashboard QA Interactive Dashboard Error on gadgets on Company Dashboard in CRM on Oracle QA Keyword Search Keyword search screen not displaying correctly after performing a keyword search which included a special character QA Dashboard (Interactive) Field translation "Interactive/Classic Dashboards Level" misleading because available for ChartBlocks even though these are not supported on the Interactive Dashboard. A more specific translation is displayed for this scenario QA Dashboard (Interactive) Incorrect translations in Interactive Dashboard for Dutch system QA Dashboard (Interactive) Workflow dialog on Interactive Dashboard was only displaying first six workflow actions QA Dashboard (Interactive) No drill-down on Chart on Classic Dashboard. A new icon appears on the header of dashboard block allowing users to replicate the drill-down functionality. Sage CRM 7.1 SP2 Release Notes Page 7 of 16

10 Ref ID Area Description Status QA Leads It was not possible to select the Company Summary tab after entering a Lead (Sage 200) QA Leads Lead upload date not populated if "Make a Group" was not selected QA Leads When a lead without an address was updated to change the "Opt out of E-marketing" check box, other leads without addresses were also being updated with the same change. This issue is by design QA Library and Templates Not able to edit an existing MS Word template. This issue is closed. This feature has been redesigned in SP QA Mobile Error when trying to customize a communication list for the iphone QA Mobile Pagination on iphone was showing incorrect number of companies QA Mobile List of all people displayed when scroll to second page on iphone. See also QA and QA. See also QA and QA QA Dashboard (Classic) Top content context not refreshed when navigating away from Company Dashboard tab (classic dashboard) QA Dashboard (Classic) Javascript error when select View All on list of leads on classic dashboard QA Notification No reminder message was being sent after a new task was created when #cmli_comm_userid# was being used in the To field QA Opportunities Clicking a section of the case, leads or opportunities pipeline deselected any existing selection/highlight and removed the filter instead of filtering the section that was clicked QA Order Entry / Products QA Outlook Integ - Classic QA Outlook Integ - Classic QA Outlook Integ - Classic QA Outlook Integ - Classic Shipping/Billing addresses on an order were not autopopulating. Documentation on Use Area Code and Use Country Code was unclear. The session of user logged in to Sage CRM via Outlook was not ended when the user closed Outlook. When filing an from a secondary account in Outlook, the From address was used, instead of the To address, which meant the communication was filed against the incorrect person record in Sage CRM. Outlook was not synchronizing with CRM for one user. The descriptions of these fields in the System Administrator Help/Guide have been updated. This is by design. A workaround is to copy the into the Sent Items of the primary account and file it from there. Sage CRM 7.1 SP2 Release Notes Page 8 of 16

11 Ref ID Area Description Status QA Outlook Integ - Classic The Classic Outlook plugin did not work on a cloud install when the install had not been deployed on the cloud server QA Outlook Integ A user with no address was not able to install the Outlook Plugin on a Windows 2008 Terminal Server. This is by design. A CRM user s address must match their Outlook address QA Outlook Integ QA Outlook Integ QA Outlook Integ QA Outlook Integ QA Outlook Integ QA Outlook Integ - The Install CRM Outlook Integration button was not available from My CRM Preferences after upgrading from a Sage CRM install that was not using Outlook Integration from v7.0 to v7.1. When trying to install Integration, an error message displayed stating that Office 2003, 2007 or 2010 should be installed, even though Outlook 2003 is no longer supported. There was an error when filing an which had double quotes in the subject. An error occurred when trying to file an from a sender not in Sage CRM when the Use Companies option in Administration System System Behavior was set to No. Every time a phone number was edited in Sage CRM, two spaces were added in front of the original number. File in the Outlook plug-in for was not taking the user's territory into account correctly. This issue is fixed - Outlook 2003 has been removed from the error message QA Document Plugin It was not possible to use the document drop facility to attach s that had Cyrillic writing in the Subject field QA Document Plugin An error occurred when filing a document when either the company or the account contained special characters QA Quotes / Orders QA Quotes / Orders QA Quotes / Orders QA Quotes / Orders A Header Record Delimiters error occurred when performing a mail merge. The Hyperlink To property was not working on new Search Select Advanced fields added to Quote Items Grid. Selecting the Opportunity hyperlink from the top content area brought the user to the Company Summary, rather than the Opportunity Summary, screen. An SQL error occurred after the quot_billaddress field was added to the Quote summary screen. The mail merge functionality has been changed for v7.1 SP2. Sage CRM 7.1 SP2 Release Notes Page 9 of 16

12 Ref ID Area Description Status QA Soap Quotes / Orders When creating a new web quote in Sage 200, the billing and shipping addresses were not defaulting to the data in the billing and shipping fields. There is a new hidden system parameter called 'AlwaysDisplayAddresses ForQuote'. The default setting is 'Y' QA Reports It was not possible to export to file when Sage CRM was running under port QA Reports An error occurred when trying to run a report from the Classic Dashboard QA Reports Data in report output was truncated when running reports containing comm_note QA Reports When running a report containing a newly added alias column, the new column header displayed in square brackets QA Reports When using the totalling functions on alias fields within reports the output was displayed as QA Reports Charts were not displaying on reports QA Reports Charts weren't rendering on newly created ASP pages QA Reports Reports containing Key Attribute data could not be run by anyone other than system administrators or info managers QA Reports A company that was updated so that it was in the "Agriculture" Segment no longer displayed in the Company List by Segment report QA GCRM Accounts When adding a new case on a Sage CRM system integrated with Sage 200 and trying to select an address from the Select Address From List hyperlink, the addresses for the wrong company were returned and the Type column was blank QA GCRM Integration The quot_shipmethod was not mapped to shipmethod QA GCRM Integration Table-level scripts were not executed during synchronization QA GCRM Integration TLS scripts were not executed correctly when a new Line item was inserted and the pricing service was switched on QA SData Provider SData gadget based on a custom view was not displaying correctly after upgrade to 7.1 SP QA Solutions It was not possible to delete a saved search on the Solution entity QA E-Marketing (Swiftpage) An E-marketing mail blast to a group based on a view that allowed duplicate records did not exclude the duplicates, and exceeded the SwiftPage daily send limit. Sage CRM 7.1 SP2 Release Notes Page 10 of 16

13 Ref ID Area Description Status QA Groups / Target Lists QA Groups / Target Lists QA Groups / Target Lists QA Groups / Target Lists Two new fields - Beitrag and Beitragstyp - were added to the Company screen, and a new group was created based on company and a view that contained the two new fields. However, the Beitrag column on the group was empty. The Save button was missing from the Static Group screen, so no changes could be made to the group. The Save button was no longer available when editing a group after upgrading to 7.1c - only the Save As button was available. After changing the name of an empty static group, the group was populated with a number of records. This is by design. Users should only see a Save As button on dynamic groups, whereas on static Groups, users should see both the Save and Save As buttons QA Security Management The caption for a security profile name was not updating correctly QA Translation (English prod) There was a typo in the output of a German report QA Translation (English prod) HTML was injected into a caption text box when editing any field with inline translation mode enabled. This is by design. There are two suggested workarounds: 1. Remove the HTML from the caption. 2. Rename the column in the view that the report is based on so that the original translation is no longer used in the report QA User Interface After clicking the ellipsis on the tab menu and changing the number of tabs displayed then navigating to a new Company, the only tab available was the Summary tab QA User Interface The TABOFFRIGHT style was used in the recent area, which caused issues when trying to customize this area QA User Interface The ellipsis tab did not contain a TABOFFRIGHT cell, which was causing an issue with themes that don't have a continuous blank tab running across the screen after the tab group QA Web Services When adding a new record into the NewProduct table, and then trying to add another product with the same product name but a different product code, the original product was overwritten QA Web Services An error occurred when trying to use the web services on Company demo data QA Workflow An HTML worked properly when created manually using a template, but did not work when using a new escalation. Sage CRM 7.1 SP2 Release Notes Page 11 of 16

14 Ref ID Area Description Status QA Workflow After creating two primary rules for a custom entity, only one of them worked QA Workflow In a workflow rule with both a Display Field for Amendment action and a Reset Column Value action that was based on the field of the Set Column Value, the reset was not retrieving the new value. Rolled Up Fixes Fixed cases for 6.2m and 7.0h are rolled up to this service pack. Please refer to the 6.2 and 7.0 Patch Release Notes respectively for the full lists. Sage CRM 7.1 SP2 Release Notes Page 12 of 16

15 Known Issues The following known issues exist with Sage CRM version 7.1 SP2. Ref ID Area Description Status Document Drop The Add Attachment button is displayed in the New Task screen during Outbound Call Handling, however it does not work as expected when you click on it. Known issue. This issue will be addressed in a future patch. If you need to add attachments to tasks in 7.1 SP2, please do this outside of the context of Outbound Call Handling, following the steps in the User Help SData Provider SData gadget based on a custom view was not displaying correctly after upgrade to 7.1 SP2. Known issue. The workaround is to go to the gadget edit screen, click the Next button on steps 1 through 4 and then the Finish button on step 5. This has the effect of resetting the xml for the gadget on the DB Outlook Integration - Errors occurred when working with the Outlook Integration Plug-in for when adding a contact and using Send And File. Known issue when working with Outlook The workaround is to upgrade to Outlook 2007 SP2 or above. Supplementary Information for Documentation The following cases provide supplementary information to the Documentation and Help shipped with Sage CRM version 7.1 SP2. Ref ID Area Description Status Documentation Descriptions for the Admin Documents/Reports settings: Reports Admin Override and Desktop Size Limitation (Kb), must be updated. The descriptions are included in the 7.1 SP2 release notes. They will be updated in the core help/documentation in the next patch Documentation Add documentation of a new icon to view the full report from a Classic Dashboard chart block QA Core Product To rename an existing workflow rule, you need to go to Administration Translations, search for the rule and update the name in all languages required. The description is included in the 7.1 SP2 release notes. It will be available in the core help/documentation in the next patch. The core System Administrator Help/Guide will be updated with this information in the next release. Sage CRM 7.1 SP2 Release Notes Page 13 of 16

16 More Notes on this Release The following notes provide supplementary information to the Documentation and Help shipped with Sage CRM version 7.1 SP2. Mail Merge () Method in.net API The Mail Merge () method in the.net API is no longer available in SP2. Customizing Sage CRM Sage CRM is both flexible and powerful in its customization capabilities. When customizing via the API, it is critical to understand that only the documented customization capabilities are supported. Please refer to for full listings. While new technologies are often incorporated into Sage CRM to give the user the best possible experience of working with the system, unless they are explicitly documented in the Sage CRM Developer Guide or Developer Help, the customization of these new technologies is not supported. Updated Documentation for Documents/Reports Settings The descriptions for Administration and Documents Documents and Reports Configuration Reports Admin Override and Desktop Size Limitation have been updated. The updated descriptions will be available with the core help and documentation with the next release. Field Reports Admin Override Desktop Size Limitation (Kb) Description There is a restriction in place on the size of reports anybody can run. With this option set to Yes, administrators can run any size report. Set to No, and the Desktop Size Limitation setting is taken into account when the report is run. If you regularly run large reports, it is recommended that this is set this to No. The size limit in Kb of the report for desktop clients. It is an approximation, as it is counting the size of the XML and not the resulting HTML. This is to stop very large reports being run and taking all of the bandwidth, especially for dial-up clients. If you regularly run large reports, it is recommended that this is set to 60 MB ( Kb). Note: This setting must not exceed 120 MB ( Kb). Sage CRM 7.1 SP2 Release Notes Page 14 of 16

17 Viewing the Full Report from a Classic Dashboard Chart There is a new View Full Report icon on Classic Dashboard chart blocks. This replaces the prev7.0 functionality which allowed users to open the report by clicking on the chart. Classic Dashboard Chart Block Location of New Sample Mail Merge Templates New HTML and Word document templates have been created to complement the updates to the Sage CRM mail merge feature. The new templates will be added to the default library folder automatically for new installs, full upgrades and for upgrades via a patch. If your system has been set up to use a network share for your mail merge templates instead of the local library folder, you may need to copy the new template files across to this network share manually. Updated Sage CRM Twitter Component The Sage CRM Twitter component has been updated for SP2. Please note that current customers who already have the Sage CRM Twitter component installed will need to re-run the component on upgrade. The updated component can be downloaded from: The standard terms and conditions, which apply to all add-ons downloaded from Ecosystem, also apply to this updated component. Sage CRM 7.1 SP2 Release Notes Page 15 of 16

18 Cross-Browser Compatibility and Safari Safari 5 on OSX is compatible with the Main Menu area in Sage CRM. The following are not supported in Sage CRM v7.1 SP2: Safari on Windows OS IOS Installations of Sage CRM on Apple Macs (on OSX) If you are working with Sage CRM from an ipad, it is recommended that you use the tablet theme available for download from the add-ons area of the Ecosystem: This is a Beta version and, as with all add-ons, is subject to the standard terms and conditions for add-ons. Sage CRM 7.1 SP2 Release Notes Page 16 of 16