Sugar Professional Release Notes Version 6.0.0

Introduction

This document describes the requirements, new features, enhancements, and known limitations in Sugar Professional 6.0.0.

Please continue to provide feedback on this release as we continue to develop Sugar functionality. The SugarCRM Development Team is closely monitoring your feedback and is making every effort to fold it into upcoming releases.

For more information on a bug or to provide feedback, use the SugarCRM Bug Tracker which is accessible through http://bugs.sugarcrm.com. Check the Bug Tracker for known issues prior to submitting bugs. When creating a bug for a new issue, use “6.0.0” to designate new bugs found in this release. You can also update existing bugs with additional information.

For information on downloading Sugar Plug-ins as well as Sugar installation, upgrade, and conversion packages, see this Knowledge Base article.

Topics include:

•	Requirements

•	Upgrade Guidelines

•	Compatibility Matrix

•	New Features, Enhancements, and Changes in 6.0.0

•	Upgrade Considerations

•	Fixed Bugs in 6.0.0

Requirements

Requirements for 6.0.0 are as follows:

•	Increase the value of the memory_limit parameter in the php.ini file as follows:

•	MySQL Server: 96M or higher

•	MS SQL Server: 96M or higher

•	To install Sugar 6.0.0 successfully, ensure that the Multibyte String (mbstring) module is installed in your PHP libraries.

•	If you are using MySQL, install version 5.0 or higher to use with Sugar 6.0.0.

•	If you are using Microsoft Exchange, use versions 2000 and higher.

•	To successfully upload the Upgrade zip file, before upgrading, navigate to the php.ini file on your system and change the post_max_size and upload_max_filesize settings to at least 60MB. Restart Apache and then begin the upgrade process.

Upgrade Guidelines

You can upgrade from Sugar versions 5.5.0, 5.5.1, 5.5.2, 5.5.3, and 5.5.4 to Sugar 6.0.0. To upgrade from 5.5.1, 5.5.2, 5.5.3 and 5.5.4, use the same upgrade package: SugarPro-Upgrade-5.5.1-to-6.0.0.zip. Similarly, to upgrade from 6.0.0 RC1, RC2, and RC3, use the same upgrade package: SugarPro-Upgrade-6.0.0RC1-to-6.0.0.zip.

Note:

It is strongly recommended that you test 6.0.0 on a copy of your production system before you upgrade it.

Guidelines are as follows:

•	The process of upgrading can take up to an hour. If you are using the IIS Web server, you need to ensure that the CGI application does not time out. To do this, on IIS, set the CGI script timeout to more than 300 seconds, which is the default value.

•	If op-code caching is enabled in the PHP configuration file, you will need to disable it before upgrading your Sugar installation. You can enable it after the upgrade process is complete.

Compatibility Matrix

SUGAR BUILDING BLOCKS	SUPPORTED VERSIONS	COMMENTS
PLATFORMS		Sugar runs on any OS that runs PHP
• Linux	Red Hat 4.x, 5.x (Advanced Server, Enterprise Server) Oracle Enterprise Linux 5.1 CentOS 4.x, 5.x
• Windows	XP, 2003, 2008, Vista
• Mac	OS X
PHP
PHP	5.2.1- 5.2.6, 5.2.8 - 5.2.13, 5.3.0-5.3.2	The PHP setting, MBstring.func_overload =7 is supported
DATABASES
• MYSQL	5.0x, 5.1	Strict mode is supported for MYSQL
• MS  SQL Server	2005, 2008
WEB SERVERS
•    Apache	1.3x, 2.0x, 2.2x	Supports any version that runs PHP
•    IIS	6.0, 7.0
MAIL SERVERS • Exchange
• QMail
• GMail
• Yahoo
SUGAR PLUG-INS
• Sugar Plug-In for Microsoft Outlook	Outlook 2003, 2007
• Sugar Plug-in for Microsoft Word	Word 2003, 2007, XP
• Sugar Plug-in for Microsoft Excel	Excel 2007
• Client (Browser)	Firefox 2.0, 3.0, 3.5, 3.6 IE 7.0, 8.0 Safari 4.0
MULTIMEDIA
• Adobe Flash	7.0 and above
RECOMMENDED STACKS
Linux Stack
• PHP version	5.2.8
• Apache	2.0.63, 2.2.4
• RedHat Enterprise	Workstation 4
Preferred Databases
MySQL	5.1
SQL Server	2005
Windows Stack
• Windows	2003
• PHP version	5.2.8
• IIS	6.0
Preferred Databases
MySQL	5.1
SQL Server	2005

New Features, Enhancements, and Changes in 6.0.0

With each revision of the Sugar application, significant advances are made in both the feature set and usability of the software.

In 6.0.0, the Sugar User Interface has been extensively redesigned and several features have been added or enhanced to improve user experience and performance. Enhancements and fixes have been made in Studio and Module Builder to allow for deeper customization of Sugar to fit your business needs and processes.

Some of the major changes are listed below.

Getting Started

•	A new Admin Wizard guides administrators through branding Sugar for their organization.

•	A new User Wizard guides users through configuring their user profile and preferred settings in Sugar.

UI Changes

•	An updated Sugar theme features a cleaner design with larger fonts and brighter icons.

•	The Shortcuts menu has been removed, and the module action links have been moved to the Actions list in the module tab menus.

•	The Last Viewed links have been moved into Module tabs to enable you to quickly access records in other modules without navigating away from your current page.

•	A slider bar hides global links that you do not access frequently.

•	A new Shortcut Bar enables you to access Quick Create Forms from any page.

•	Global Search has been enhanced to display initial results within your current page. The search results are module-weighted and display results from the current module first, followed by results from other modules.

•	Basic Search has been simplified to search only by record name. For contacts, you can search by first, last, or full name.

•	The default page layouts for Edit View and Detail View have been redesigned to display fields in more logical groupings.

•	List View has been modified as follows:

•	The Edit icon has been moved to the left.

•	The Information icon has been moved to the right.

•	Buttons for actions such as Merge, Export, Delete, and Email have been removed, and these options have been moved to the Actions menu.

•	The Mass Update panel does not display on the page by default. The Mass Update option is now listed in the Actions menu.

•	For all Datetime fields, when you enter a date value, you must also enter the time value.

•	The following field labels in the Opportunities module have been changed as follows: “Amount” has been changed to “Opportunity Amount”. “Amount USD” has been changed to “Amount”.

•	The name of the record, module, and system now appear in the browser tab.

•	The Grouped Modules feature has been removed. All modules set to be displayed will appear in the navigation bar.

•	The Quick Create Form that displayed below the Shortcuts menu has been removed and will no longer appear in any Sugar theme.

•	The Sitemap is not available in the new Sugar theme, but is available in the “Classic” theme.

•	The “Enter Business Card” feature has been removed from the Contacts module.

Module Consolidations and Enhancements

•	The Dashboard module has been consolidated with the Home module. Dashboard pages appear in the Home module next to the Home pages in both new and upgraded instances.

•	The Calendar module has been consolidated with the Activities module, and is the default view of the Activities module.

•	The User Settings page has been redesigned to display panels as tabs for easier navigation.

Studio and Module Builder Enhancements

•	You can edit properties for standard fields including field lengths and whether the field is required or audited.

•	You can customize Quick Create forms for custom modules.

•	You can customize the Convert Lead form to add new fields and new related modules.

•	You can customize “Select” pop-up windows.

•	You can revert from customized layouts to the default layouts.

•	You can specify the next number in Quotes, Cases, and Bug Tracker, as well as in custom modules created using the Issue template.

•	You can display layout panels as tabs.

•	You can set the Address field as a required field.

•	You can set Email Address as a required field.

•	You can add custom fields to Sugar Dashlets and to Sugar Dashlet Search.

•	New field types, “DateTime” and “Image”can be added to page layouts. DateTime creates a field to enter the date and time. Image creates an image field to upload an image to display in a record.

•	Custom modules based on the Person template now displays an Email option in the Actions drop-down list in the List View. Users can use this option to compose emails without navigating away from the page.

•	Relationship labels can be localized.

Upgrade Considerations

•	Upon upgrade, the new Sugar theme will display in the user interface.

•	Custom themes will need to be updated to correct any display issues.

•	Customizations to Sugar made through Studio and Module Builder are preserved.

•	Page layouts that have not been customized will inherit the new default layouts including any new fields that have been included to them.

•	Non-standard, code-customized layouts may have display issues.

•	Page layouts that you have customized will change as follows:

•	The Date Created and Date Modified fields will be added to EditView and DetailView layouts of Accounts, Contacts, Leads, Opportunities, Calls, Meetings, Notes, Cases, Bugs, Contracts, Campaigns, and Targets.

•	The Picture field will be added to the Edit View and Detail View layouts of Users, Employees, and Contacts.

•	The Website field will be added to the Edit View and Detail View layouts of Leads.

If you do not want these fields in your customized layouts, the system administrator can remove them.

•	Code customizations in Sugar Dashlets are preserved. For existing out-of-the-box Sugar dashlets, the upgrade replaces existing Search and List definitions with the default out-of-the-box definitions in 6.0. This may alter previous layouts and functionality.

•	Pre-upgrade Lead Conversion forms are preserved if:

•	The code-customized Lead Conversion pages are located in the custom/directory. If the customized pages are in the main module folder, then they are ignored and the new default Lead Conversion pages will replace the pre-upgrade Lead Conversion form.

•

The pre-upgrade Lead Conversion form contains custom fields. Prior to 6.0, custom fields were automatically added to the Lead Conversion form. In order to switch to the Lead Conversion page, a system administrator would need to customize the Lead Conversion form in Studio. A Lead Conversion form that is customizable in Studio does not contain, by default, any of the custom fields in the default modules. A system administrator would need to add any custom fields that are needed.

Fixed Bugs in 6.0.0

Bug 37136

Importing contacts with account names does not work unless the “account_name” column is the last column in the CSV file.

Bug 38449

A new breadcrumb stack is created on every request resulting in slower performance.