Sage CRM71 SP2 Release Notes

18
v7.1 SP2 Release Notes

description

With Sage CRM v7.1 Service Pack 2 (SP2) fully tested and ready to go, we’re proud to announce that the theme of this release is Cross Browser Compatibility. We have been aware for some time that Cross Browser compatibility is a major customer requirement. This is even reflected on our ideas hub – you’ll see it’s one of the top requested features. In an effort to deliver Cross Browser Compatibility to you as soon as possible, we have included it in the upcoming service pack rather than asking you to wait until our end of year release. Cross Browser Compatibility - what are the end user browser options in SP2?As most of you are aware, previous versions of Sage CRM were optimised for Internet Explorer. The options listed below will be available to end users in SP2. Cross browser compatibility is focused on the end user experience, i.e. the Main Menu area. The user experience and functionality throughout the Main Menu is consistent across Firefox, Chrome, Safari, and Internet Explorer (IE). End User Supported Browsers in Sage CRM v7.1 SP2IE – versions 7, 8 and 9 (as per Sage CRM v7.1 SP1)Safari – latest version Safari browser on OSX (Apple MAC). Note that the Tablet theme is recommended for use with iPad – IOS is not in scope)Chrome – latest versionFirefox – latest versionMail Merge and Document FilingThe Mail Merge and Document Filing features required special attention when it came to making them work across different browsers. Both features depended on an Active X plugin, which meant that the features only worked on IE and that end users needed to install the plugins themselves. Focusing on these features meant that we could make them work effectively across different browsers and also enhance their feature sets.

Transcript of Sage CRM71 SP2 Release Notes

Page 1: Sage CRM71 SP2 Release Notes

v7.1 SP2 Release Notes

Page 2: Sage CRM71 SP2 Release Notes

© 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 onany 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 Agreementenclosed 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 orregistered trademarks of their respective owners.

Page 3: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 1 of 16

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 ....................................................................................................................................... 12

Known Issues .......................................................................................................................................... 13

Supplementary Information for Documentation ................................................................................... 13

More Notes on this Release ................................................................................................................... 14

Mail Merge () Method in .NET API ........................................................................................................ 14

Customizing Sage CRM ........................................................................................................................ 14

Updated Documentation for Documents/Reports Settings .................................................................... 14

Viewing the Full Report from a Classic Dashboard Chart ..................................................................... 15

Location of New Sample Mail Merge Templates ................................................................................... 15

Updated Sage CRM Twitter Component ............................................................................................... 15

Cross-Browser Compatibility and Safari................................................................................................ 16

Page 4: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 2 of 16

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: 7.1.0.6

Doc Plugin: 7.1.0.3

Outlook Plugin: 7.1.0.5

CTI Plugin: 7.1.0.1

CRM Document Version Code for these Release Notes SYS-REA-ENG-712-1.0

Page 5: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 3 of 16

Documentation The following new/updated documentation is available with this service pack:

Description Version Code Release Notes SYS-REA-ENG-712-1.0

What’s New Guide SYS-REL-ENG-712-1.0

Software Support Matrix IMP-MAT-ENG-712-1.0

User Guide USE-MAN-ENG-712-1.0

System Administrator Guide SYS-MAN-ENG-712-1.0

Context Sensitive User Help USE-HLP-ENG-712-1.0

Context Sensitive System Admin Help SYS-HLP-ENG-712-1.0

Installation and Upgrade Guide

IMP-UPG-ENG-712-1.0

The PDFs of the above are available on the Sage CRM Ecosystem web site (http://community.sagecrm.com/user_community/m/sage_crm_v71/default.aspx).

The following new product videos are available with this service pack:

Description Version Code What’s New in Sage CRM v7.1 SP2 REL-VID-ENG-712-1.0

Creating and Sharing a Mail Merge Template

TPL-VID-ENG-712-1.0

Getting Started with Sage CRM QSG-VID-ENG-712-1.0

All product videos are available on the Sage CRM Ecosystem web site (http://community.sagecrm.com/p/productvideos.aspx)

Page 6: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 4 of 16

Issues List The following cases have been addressed in Sage CRM version 7.1 SP2. 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

0-141964-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.

This issue is fixed.

0-142381-QA Address Linking

Using "Select Address To Copy" option was not displaying the expected number of addresses.

This issue could not be reproduced.

0-141575-QA Call Handling "Got Through" button was re-appearing during outbound call and, if clicked on, creating inaccurate statistics for the call lists.

This issue is fixed.

0-141401-QA Campaign Management

Script error when using the Date/Time picker while creating a new appointment from an outbound call.

This issue could not be reproduced.

0-141697-QA Cases Invalid Column Name error when a field was added to the Case Progress screen which did not exist on the Case.

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.

0-142605-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 could not be reproduced.

0-139545-QA Companies / People

Part of a company name contained within double quotes was cut off when using the company dedupe screen.

This issue is fixed.

0-139550-QA Companies / People

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.

This issue has been fixed.

0-140092-QA Companies / People

Incorrect address was displaying when adding a new person from the web picker of the appointment screen.

This issue is fixed.

0-141931-QA Companies / People

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 is fixed.

Page 7: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 5 of 16

Ref ID Area Description Status

0-141978-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.

0-139678-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.

This issue could not be reproduced.

0-141380-QA Core Product Not possible to convert a task to an appointment. This issue is by design.

0-138603-QA CTI Script error after blanking out the CTI Internal Number Length field.

This issue is fixed.

0-137742-QA Customization A customization using Advanced Search Select for Products and Product Families was not working as expected.

This issue is fixed.

0-139269-QA Customization Continue button on Cases tab in Custom Entity not behaving consistently.

This issue is fixed.

0-139751-QA Customization ClientSide script files were not being included as part of a customization.

This issue is fixed.

0-141094-QA Customization A button group customization on the Addresses tab was not working as expected.

This issue could not be reproduced.

0-141382-QA Customization A default value on OrderItemsSummary screen, set using a field-level script customization, was not displaying as expected.

This issue is fixed.

0-141929-QA Customization An error was produced when using a lookup family which had entries wider than 15 characters on a custom Intelligent Select field.

This issue is fixed.

0-142284-QA Customization The format of a custom check box on the company summary screen was displaying differently in view and edit modes.

This issue is fixed.

0-141597-QA Dashboard A report which did not include the entity ID was not displaying on the Interactive Dashboard.

This issue is fixed.

0-143403-QA Database Communications tab slow to load where lots of communication had been added to a person in the CRM demo data.

This issue is fixed.

0-138871-QA Data Upload Dates from an XLS or XLSX file where not being uploaded in the correct format.

This issue is fixed.

0-140739-QA Data Upload Errors on a data upload from XLS file in a German system.

This issue could not be reproduced.

Page 8: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 6 of 16

Ref ID Area Description Status

0-135644-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.

This issue could not be reproduced.

0-139305-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.

This issue could not be reproduced.

0-139996-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.

This issue is fixed.

0-140094-QA Comms/Diary It was not possible to change the account from an existing task.

This issue is fixed.

0-141966-QA Comms/Diary An SQL error occurred when trying to view the calendar after applying patch 7.1c.

This issue could not be reproduced.

0-141999-QA Comms/Diary Communication "owner" was not being saved on existing communication.

This issue could not be reproduced.

0-142078-QA Comms/Diary Error after comm_location was removed from CustomCommunicationDetailBox screen.

This issue is fixed.

0-142475-QA Comms/Diary Not able to change the company on an existing task. This issue could not be reproduced.

0-142534-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.

This issue is fixed.

0-127987-QA E-mail Client Unable to resize inline image in e-mail. This issue could not be reproduced.

0-142264-QA E-Marketing (SageCRM)

Translated values were not displaying in E-marketing templates.

This issue is fixed.

0-139161-QA Exchange Integration

English translation of a German title was appearing on a contact in Outlook after synchronization.

This issue is fixed.

0-140982-QA Exchange Integration

An HTTP error occurred when trying to sync with the Exchange server.

This issue is fixed.

0-141507-QA Exchange Integration

Phone number was splitting across area code and country in CRM even though these settings were not in use.

This issue is fixed.

0-142586-QA Exchange Integration

When using Outlook 2007 and Exchange Server 2007 SP3, some columns of a contact's address in Outlook were not displaying correctly.

This issue is fixed.

0-136431-QA Export Data Error when exporting a file to CSV with German special character in file name.

This issue could not be reproduced.

0-142336-QA Export Data 404 error when trying to export companies in increments of 50.

This issue could not be reproduced.

0-142612-QA Export Data Not able to change date format in exported XLS report. This issue is fixed.

Page 9: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 7 of 16

Ref ID Area Description Status

521-133175-QA

E-mail Manager

E-mail editor was not loading when working in a new language, which was added from Admin | Customization | Translations.

This issue is fixed.

0-143168-QA Find / Advanced Find

Search criteria was lost after scrolling to second page of search results on iPhone.

This issue if fixed. See also 0-142363-QA and 0-142355-QA.

0-144053-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.

This issue is fixed.

0-141741-QA Install / Upgrade

An error was generated when trying to export a report to Excel which was larger than 1500 KB.

This issue is fixed.

0-142063-QA Install / Upgrade

The length of customized CRMemailphonedata fields was reset after updating with a patch.

This issue is fixed.

0-142414-QA Install / Upgrade

E-mail addresses were missing for some records after upgrade had warned of potential duplicate Person phone numbers.

This issue is fixed.

0-143392-QA Install / Upgrade

Advanced Search Select was not returning any results after upgrading from v6.1 to v7.1.

This issue is fixed.

0-141573-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 email tables following the sync of the schema.

This issue is fixed.

0-139705-QA Interactive Dashboard

Person entity not available on Interactive Dashboard after setting "Use Individuals" to "Yes".

This issue is fixed.

0-141868-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.

This issue is fixed.

0-143067-QA Interactive Dashboard

Error on gadgets on Company Dashboard in CRM on Oracle.

This issue is fixed.

0-142053-QA Keyword Search

Keyword search screen not displaying correctly after performing a keyword search which included a special character.

This issue is fixed.

0-140841-QA Dashboard (Interactive)

Field translation "Interactive/Classic Dashboards Level" misleading because available for ChartBlocks even though these are not supported on the Interactive Dashboard.

This issue is fixed. A more specific translation is displayed for this scenario.

0-141363-QA Dashboard (Interactive)

Incorrect translations in Interactive Dashboard for Dutch system.

This issue is fixed.

0-141642-QA Dashboard (Interactive)

Workflow dialog on Interactive Dashboard was only displaying first six workflow actions.

This issue is fixed.

0-142691-QA Dashboard (Interactive)

No drill-down on Chart on Classic Dashboard. This issue is fixed. A new icon appears on the header of dashboard block allowing users to replicate the drill-down functionality.

Page 10: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 8 of 16

Ref ID Area Description Status

0-141004-QA Leads It was not possible to select the Company Summary tab after entering a Lead (Sage 200).

This issue could not be reproduced.

0-142238-QA Leads Lead upload date not populated if "Make a Group" was not selected.

This issue is by design.

0-142468-QA Leads When a lead without an e-mail address was updated to change the "Opt out of E-marketing" check box, other leads without e-mail addresses were also being updated with the same change.

This issue is fixed.

0-140129-QA Library and Templates

Not able to edit an existing MS Word template. This issue is closed. This feature has been redesigned in SP2.

0-141029-QA Mobile Error when trying to customize a communication list for the iPhone.

This issue is fixed.

0-142355-QA Mobile Pagination on iPhone was showing incorrect number of companies.

This issue is fixed. See also 0-143168-QA and 0-142363-QA.

0-142363-QA Mobile List of all people displayed when scroll to second page on iPhone.

This issue is fixed. See also 0-143168-QA and 0-142355-QA.

0-143355-QA Dashboard (Classic)

Top content context not refreshed when navigating away from Company Dashboard tab (classic dashboard).

This issue is fixed.

0-143406-QA Dashboard (Classic)

Javascript error when select View All on list of leads on classic dashboard.

This issue is fixed.

0-142052-QA Notification No e-mail reminder message was being sent after a new task was created when #cmli_comm_userid# was being used in the To field.

This issue is fixed.

0-141174-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.

This issue is fixed.

0-142193-QA Order Entry / Products

Shipping/Billing addresses on an order were not auto-populating.

This issue is fixed.

0-141864-QA Outlook Integ - Classic

Documentation on Use Area Code and Use Country Code was unclear.

This issue is fixed. The descriptions of these fields in the System Administrator Help/Guide have been updated.

0-141894-QA Outlook Integ - Classic

The session of user logged in to Sage CRM via Outlook was not ended when the user closed Outlook.

This issue is fixed.

0-142452-QA Outlook Integ - Classic

When filing an e-mail 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.

This is by design. A workaround is to copy the e-mail into the Sent Items of the primary account and file it from there.

0-143802-QA Outlook Integ - Classic

Outlook was not synchronizing with CRM for one user. This issue is fixed.

Page 11: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 9 of 16

Ref ID Area Description Status

530-143658-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.

This issue is fixed.

0-142171-QA Outlook Integ A user with no e-mail address was not able to install the Outlook Plugin on a Windows 2008 Terminal Server.

This is by design. A CRM user’s e-mail address must match their Outlook e-mail address.

0-140944-QA Outlook Integ - Exchange

The Install CRM Outlook Exchange 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.

This issue is fixed.

0-141202-QA Outlook Integ - Exchange

When trying to install Exchange Integration, an error message displayed stating that Office 2003, 2007 or 2010 should be installed, even though Outlook 2003 is no longer supported.

This issue is fixed - Outlook 2003 has been removed from the error message.

0-142396-QA Outlook Integ - Exchange

There was an error when filing an e-mail which had double quotes in the subject.

This issue is fixed.

0-142653-QA Outlook Integ - Exchange

An error occurred when trying to file an e-mail from a sender not in Sage CRM when the Use Companies option in Administration | System | System Behavior was set to No.

This issue is fixed.

0-143484-QA Outlook Integ - Exchange

Every time a phone number was edited in Sage CRM, two spaces were added in front of the original number.

This issue could not be reproduced.

0-144152-QA Outlook Integ - Exchange

File E-mail in the Outlook plug-in for Exchange was not taking the user's territory into account correctly.

This issue is fixed.

0-125167-QA Document Plugin

It was not possible to use the document drop facility to attach e-mails that had Cyrillic writing in the Subject field.

This issue is fixed.

0-142448-QA Document Plugin

An error occurred when filing a document when either the company or the account contained special characters.

This issue is fixed.

0-136953-QA Quotes / Orders

A Header Record Delimiters error occurred when performing a mail merge.

This issue could not be reproduced. The mail merge functionality has been changed for v7.1 SP2.

0-138609-QA Quotes / Orders

The Hyperlink To property was not working on new Search Select Advanced fields added to Quote Items Grid.

This issue is fixed.

0-139076-QA Quotes / Orders

Selecting the Opportunity hyperlink from the top content area brought the user to the Company Summary, rather than the Opportunity Summary, screen.

This issue could not be reproduced.

0-141668-QA Quotes / Orders

An SQL error occurred after the quot_billaddress field was added to the Quote summary screen.

This issue could not be reproduced.

Page 12: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 10 of 16

Ref ID Area Description Status

0-142478-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.

This issue is fixed. There is a new hidden system parameter called 'AlwaysDisplayAddressesForQuote'. The default setting is 'Y'.

0-138730-QA Reports It was not possible to export to file when Sage CRM was running under port 8080.

This issue is fixed.

0-139320-QA Reports An error occurred when trying to run a report from the Classic Dashboard.

This issue is fixed.

0-139748-QA Reports Data in report output was truncated when running reports containing comm_note.

This issue is fixed.

0-140323-QA Reports When running a report containing a newly added alias column, the new column header displayed in square brackets.

This issue could not be reproduced.

0-140756-QA Reports When using the totalling functions on alias fields within reports the output was displayed as 0.00.

This issue is fixed.

0-140819-QA Reports Charts were not displaying on reports. This issue is fixed.

0-141324-QA Reports Charts weren't rendering on newly created ASP pages. This issue is fixed.

0-141916-QA Reports Reports containing Key Attribute data could not be run by anyone other than system administrators or info managers.

This issue is fixed.

0-143536-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.

This issue is fixed.

0-140980-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.

This issue is fixed.

0-142010-QA GCRM Integration

The quot_shipmethod was not mapped to shipmethod. This issue is fixed.

0-142277-QA GCRM Integration

Table-level scripts were not executed during synchronization.

This issue is fixed.

0-142819-QA GCRM Integration

TLS scripts were not executed correctly when a new Line item was inserted and the pricing service was switched on.

This issue is fixed.

0-144110-QA SData Provider SData gadget based on a custom view was not displaying correctly after upgrade to 7.1 SP1.

This issue is fixed.

0-139141-QA Solutions It was not possible to delete a saved search on the Solution entity.

This issue is fixed.

0-141492-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.

This issue is fixed.

Page 13: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 11 of 16

Ref ID Area Description Status

0-140716-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.

This issue is fixed.

0-140962-QA Groups / Target Lists

The Save button was missing from the Static Group screen, so no changes could be made to the group.

This issue is fixed.

0-141917-QA Groups / Target Lists

The Save button was no longer available when editing a group after upgrading to 7.1c - only the Save As button was available.

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.

0-143674-QA Groups / Target Lists

After changing the name of an empty static group, the group was populated with a number of records.

This issue is fixed.

0-144283-QA Security Management

The caption for a security profile name was not updating correctly.

This issue is fixed.

0-139101-QA Translation (English prod)

There was a typo in the output of a German report. This issue is fixed.

0-141703-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.

0-139322-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.

This issue could not be reproduced.

0-139800-QA User Interface The TABOFFRIGHT style was used in the recent area, which caused issues when trying to customize this area.

This issue is fixed.

0-139803-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.

This issue is fixed.

0-139594-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.

This issue is fixed.

0-139734-QA Web Services An error occurred when trying to use the web services on Company demo data.

This issue is fixed.

0-124840-QA Workflow An HTML e-mail worked properly when created manually using a template, but did not work when using a new escalation.

This issue is fixed.

Page 14: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 12 of 16

Ref ID Area Description Status

0-138881-QA Workflow After creating two primary rules for a custom entity, only one of them worked.

This issue is fixed.

0-139291-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.

This issue is fixed.

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.

Page 15: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 13 of 16

Known Issues The following known issues exist with Sage CRM version 7.1 SP2.

Ref ID Area Description Status

543-144790 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.

328-145259 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.

506-145215 Outlook Integration - Exchange

Errors occurred when working with the Outlook Integration Plug-in for Exchange when adding a contact and using Send And File.

Known issue when working with Outlook 2007. 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 52-144595 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.

52-144597 Documentation Add documentation of a new icon to view the full report from a Classic Dashboard chart block.

The description is included in the 7.1 SP2 release notes. It will be available in the core help/documentation in the next patch.

0-141379-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 core System Administrator Help/Guide will be updated with this information in the next release.

Page 16: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 14 of 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 https://community.sagecrm.com/developerhelp/ 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 | E-mail 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 Description Reports Admin Override 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.

Desktop Size Limitation (Kb) 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 (60 000 Kb). Note: This setting must not exceed 120 MB (120 000 Kb).

Page 17: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 15 of 16

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 pre-v7.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:

https://community.sagecrm.com/add_on_store/m/sage_crm_downloads/default.aspx

The standard terms and conditions, which apply to all add-ons downloaded from Ecosystem, also apply to this updated component.

Page 18: Sage CRM71 SP2 Release Notes

Sage CRM 7.1 SP2 Release Notes Page 16 of 16

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: https://community.sagecrm.com/add_on_store/m/sage_crm_downloads/default.aspx

This is a Beta version and, as with all add-ons, is subject to the standard terms and conditions for add-ons.