empty
| 
Sugar Community Edition 5.2 Documentation
Sugar Community Edition Release Notes
Version 5.2.0j
|
|
|
Introduction
This document describes the requirements, new features, enhancements, and known limitations in Sugar Community Edition 5.2.0j.
You can upgrade from Sugar versions 5.0.0x, and 5.1.0 to Sugar version 5.2.0j. All Sugar 5.1.0 plug-ins and extensions are compatible with Sugar 5.2.0j.
|
Note:
|
Please continue providing feedback on this release as we continue to develop Sugar functionality for the upcoming releases. We will continue to work to incorporate your feedback into the development process. 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 Portal which is accessible through http://bugs.sugarcrm.com. Use “5.2.0j” to designate new bugs found in this release. You can also update existing bugs with additional information.
|
Note:
|
If you are running PHP 5.2.9, and you are upgrading from Sugar 5.2.0c or earlier versions, turn off PHP notices in php.ini before upgrading to Sugar 5.2.0j to ensure that the Upgrade Wizard does not fail. If you are planning to upgrade to PHP 5.2.9, it is recommended that you do so after you upgrade to Sugar 5.2.0j.
|
|
•
|
|
•
|
To install Sugar 5.2.0 successfully, ensure that the MB String module is installed in your PHP libraries.
|
|
•
|
Before upgrading to 5.2.0, navigate to the php.ini file on your system and change the post_max_size and upload_max_filesize settings to more than 20MB. Restart Apache and then begin the upgrade process.
|
|
•
|
The process of upgrading to 5.2.0 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.
|
|
•
|
In order to better support multi-byte character storage with Microsoft SQL Server, you can configure Sugar to use FreeTDS driver. For more information, see “Installation Prerequisites and Guidelines” in the Sugar Community Edition Installation and Administration Guide. The supporting files are in a zip file, sugarcrm-MB-mssql.zip at http://www.sugarforge.org/frs/?group_id=6.
|
Connector to External Data Sources.
Sugar provides a connector to LinkedIn. Additional connectors to other data sources can be obtained and installed using Module Loader
Sugar Feed enables users to be informed as soon as a user creates a new contact, lead, opportunity, or case. Users can add a My Sugar Feed dashlet on their Home page so that when a user performs any of these actions, a message displays in the dashlet on their Home page. Users can also be notified when a lead is converted, when a case is closed, and when an opportunity is closed.
Additionally, users can post status updates, external links, images, and YouTube videos for other users to view within the dashlet.
Sugar provides a My Portal dashlet that presents product information and news about SugarCRM on your Home page. You can add additional My Portal dashlets to view information from external web sites and applications directly within your Sugar instance.
When you create or edit a drop-down list, you can now sort items in ascending or descending order.
|
•
|
Some entry points were changed in Sugar 5.1. Hence, a custom file created in 5.0, unless you manually updated it with the new entry point in 5.1, may fail in 5.2 with the error message “Not a valid entry point”.
|
For example, if you have customized vCard, navigate to custom\modules\<modulename>\metadata\detailviewdefs.php and replace <name="vcard" action="vCard.php>"
<name="vcard" action="index.php">
|
•
|
If you had renamed module tabs prior to Sugar 5.2.0g, and then used the Silent Upgrader to upgrade to Sugar 5.2.0g, your changes will be lost during the upgrade. After upgrading to 5.2.0h, you will have to rename your module tabs again.
|
|
Sugar runs on any OS that runs PHP
|
||||
|
Red Hat 4.x, 5.x (Advanced Server, Enterprise Server)
|
|||
|
||||
|
||||
|
5.1.0 - 5.1.2, 5.1.4, 5.1.6, 5.2.1-5.2.6, 5.2.8 - 5.2.10
|
||||
|
||||
|
||||
|
Supports any version that runs PHP
|
||||
|
Supports any version that runs PHP
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
•
|
You can now select any pre-installed language pack to display tab group labels when you group modules tabs on the Configure Tabs Group page. You can select the language from the Tab Group Language drop-down list on this page.
|
|
•
|
The Configure Tabs Group page now provides the option to disable the “Other” tab in Grouped Tabs configuration. When you enable this option, modules that are not part of any grouping do not display under “Other”, which is located under the extended module tab icon (>>) in the Navigation bar.
|
|
•
|
Several new configuration options have been added to the config.php file. For more information, see:
|
When you select the Grouped Modules option and choose to display eight or fewer module tabs, the “Other” option located under the extended module tab icon (>>) in the Navigation bar displays an “undefined” error message instead of displaying modules that are grouped under the “Other” option.
The Opportunities sub-panel in a contact’s Detail View does not display the Rem link that enables users to remove the link between the contact and a related opportunity.
If you use your IDs when creating records instead of using Sugar-generated UIDs, you may not be able to retrieve linked files that have the same record IDs.
When you attempt to respond to an email from the Detail View of a related record, the Compose Email page does not display your default signature, if one exists.
Relationships between existing custom modules and Sugar modules are duplicated in Sugar 5.2x after upgrading from Sugar 5.0x.
When responding to an email, if you select “Reply All”, Sugar copies the recipient on CC list. As a result, the provides a receives an extra copy of the email.
If the timezone on your web server is not set to UTC, the time intervals specified in the Scheduler may be disrupted. As a result, the Scheduler may run jobs in an inconsistent manner.
|
Note:
|
After applying the 5.2.0i patch, to ensure that jobs are processed successfully, navigate to the Create Scheduler option from the Administration Home page, select Advanced options, and ensure that the date specified in the Date & Time End field has not already passed.
|
In some instances, the 5.2.0h patch may rewrite custom language files incorrectly causing the application to use an older version of dropdown definitions.
Some instances encounter issues such as empty module tabs and empty drop-down lists as a result of applying the 5.2.0g patch.
|
•
|
In the Lead Conversion form, you can now enter a value in the Country field instead of having to select it from a drop-down list. This enables you to enter the country name of your choice.
|
|
•
|
In the Module Builder, custom module names display in the Related Module window instead of the module labels.
The number of closed opportunities displayed in the “My Closed Opportunities Gauge” dashboard is incorrect.
Lead conversion form shows the Country field as a drop-down field instead of a text field. As a result, if the country entered in the Lead record does not match any country in the drop-down list, it is not converted to a new contact record.
If the Users table contains invalid 'reports_to’ IDs, then silentUpgrade.php fails with the misleading error message “Allowed memory size of [X] bytes exhausted (tried to allocate [Y] bytes)”.
When using the MySQL database, setting the precision for a decimal field for a custom module results in a SQL error.
When using MS SQL database, if you edit a custom date file in a module and subsequently edit other fields in the module, the Change Log displays several entries for the date field even though it was edited only once.
Using the Repair option to repair the database after installing Sugar generates the wrong SQL scripts.
If a contact record has the same ID as a record that you are currently viewing in a different module, the Contacts column in the module’s History sub-panel displays the contact with the same ID even if it is not the right record.
The .htaccess file support for Apache 1.3 web servers has been repaired.
|
•
|
When you create a case through inbound email, the person sending the email is now automatically associated with the case as a contact.
|
|
•
|
If you associate two or more target lists with a newsletter campaign, subscriptions to the newsletter are not applied correctly.
When importing data that includes a custom Flex Relate field, the system displays an “Undefined Index” warning during the import process.
The string ‘Please Select’ is hard-coded in two locations in the Selector.php file instead of calling a label from a corresponding language file to allow for localization.
When importing records with qualified fields, field values beginning with multi-byte characters are truncated.
Search returns incorrect results if you use a relationship within the same module as a search filter.
The Bug Tracker dashlet displays values for the Priority drop-down list as P1, P2, and P3 instead of Urgent, High and Medium.
In a Newsletter Campaign, users can view all newsletters even if they are not members of the team assigned to the campaign.
Sugar does not display a warning if you delete an email template that is used in an active email campaign.
When you select a field containing a Checkbox value as a search filter, Sugar does not retain the value after returning the search results.
When you create an Alert email template with a non-English language pack, Sugar displays the module name in English.
When you use single quotes or double quotes to perform a global search by full name, the system treats the full name as a last name and returns too many results.
When you attempt to apply an email template to a blank outbound email containing an attached file, Sugar deletes the attachment.
When using a non-English language pack, if you add a new IFrame or Link field in Studio, the “Generate URL” string is not translated.
Apache Web Server users can delete dashlets from the Home page even if the administrator has locked the Home page to prevent such actions.
When you add a custom Checkbox field to a module’s layout in Studio, Sugar does not update existing records with the new field. Hence, searching for records using the new field as a filter produces incomplete search results because only records that were created after the new field was added to the layout are displayed.
If a lead and a contact have the same email address, only the contact’s address is populated in email templates.
Apache Web Server users can circumvent patterns that the .htaccess file uses to prevent access to protected files.
When you add the “Member of” field to the Accounts List View to view parent-child relationships, the List View reverses such relationships and displays the parent account as the child account.
In 5.2.0d, Group users were included in the number of licensed users. Hence, if the number of users exceeded the number allotted under your license because of Group users, the system displayed a warning.
|
•
|
A new Repair option named “Repair Non-Lowercased Fields” allows you to use mixed-case field names when searching for records.
|
|
•
|
Two new icons have been added in the Emails module. The “Assign To” icon enables users to assign emails to other users., and the “Mark” icon enables users to mark emails as Flagged, Unflagged, Read, and Unread.
|
The get_relationships function fails for custom modules.
Fields referencing a custom drop-down list that was not created through the Module Builder do not load properly in Module Builder when exported and loaded on another system, and hence cannot be edited in the new system.
When you click an email address in the Employees List View to compose an email, the “To” field does not display.
When using a SQL Server database, when you sort a paginated Accounts List View by a custom field, the system displays an “incorrect syntax” error if you click the Next button to navigate to the next page.
The value Amount of an opportunity is not converted correctly from EUR to USD for a contract with a default currency of EUR.
When installing Sugar 5.2.0 with MS SQL database, an error prompts Sugar to create a new MSSQL user.
When composing an email, personal and group email addresses are not differentiated in the “From” drop-down list.
If you do not have the latest Sugar version, the Configure Sugar Updates page displays strange characters.
When you click an email address from the Leads List View, the To field does not display the email address of the lead.
The My Pipeline By Sales Stage dashlet displays wrong total sum value if the user’s default currency is different from the system default currency.
Bar charts do not work if the user’s default currency is different from the system default currency.
When you run a cron job from the Sugar User Interface, or cron.php from the command line, the tracker table is populated when Tracker Actions is the only box selected on the Tracker Settings page.
Sugar now provides a new setting, vCal Updates Time Period, in the Advanced section of the System Settings Page. Administrators can use this setting to specify the number of months in advance of the current date that Free/Busy information for calls and meetings is published. The minimum value is one month, and the maximum value is 12 months. To turn off Free/Busy publishing, enter “0”.
|
•
|
In Studio, the Contact field has been removed from the Edit View of the Calls module and the Meetings module.
|
Attempting to import drop-down list values with a language pack other than English results in an import error.
While importing data, if you undo the last import, the system unlinks the updated contacts from the related accounts.
When users select the Show Full Name option on the My Account page, Sugar Feed and User Feed entries do not display users’ full names.
After you create a custom relate field in Studio, Sugar creates a new column in the Sugar database whenever you save the field.
In Studio, field labels do not warp around if they extend past the width setting resulting in an increase in page width.
If you use the Firefox browser to log into Sugar and choose the “Remember Now” option to remember your Sugar password, and then enable the Self Service Portal option, when you edit a contact record with blank portal name and password fields, the system populates these fields with your Sugar user name and password.
If you create custom fields in the Module Builder using a non-English language pack, and then change to the English language pack, Sugar does not display the custom field labels in English.
When you create a currency field in Studio and add it to the List View layout, the layout displays only digits before the first thousand separator.
In Studio, if you remove the “Any Email” field from a layout and deploy your changes, you cannot add the field back to the layout later on because it is no longer available.
When a user who does not have access to the Contacts module attempts to specify an email address for a lead, Sugar starts checking if the email address already exists in the system but does not complete the process.
When you log into Sugar using a language pack that is not the default, you cannot delete items from drop-down lists in Developer Tools.
In the Settings window of the Emails module, the Folders tab displays multiple sets of personal folders for all users.
When you undo an import that updated records, Sugar deletes the updated records instead of restoring the previous version.
Pipeline graphs display currency values in US dollars when the system default is set to a different currency.
When you import data into the Accounts module, any updated record is assigned to the user who updated it instead of the user who was originally assigned to the record.
When the default currency for a user is different from the system default currency, currency conversions that display on the user’s dashboard may be incorrectly calculated.
When a user sends out an email, Sugar uses the “From” address set in the inbound email account as the “reply-to” address instead of the “reply-to” address specified on the My Account page.
After you create and deploy a custom module using the “File” template, when you view a record in the module, the Last Viewed tracker does not display the record name.
Users assigned to a role that does not have permissions to edit records in the Accounts module can still create accounts.
Users assigned to a role that does not have permissions to edit records in the Accounts module can still use the Quick Create form to create accounts.
When you import data for notes from a .csv file, the first field in a row may be appended to the last field in the previous row. As a result, Sugar imports only the first row data.
Custom fields added through Studio in a non-English language are not updated to English on “Edit Label” page when you change to the English language pack.
An attempt to use the Silent Upgrader or Upgrade Wizard to upgrade from 5.0 to 5.1.0c fails with an error message.
You can successfully import data into the Notes module from a .csv file but Sugar displays a “Undefined Property” error message.
|
|
|
|
Copyright 2004-2009 SugarCRM Inc.
Community Edition License
