Let the platform do the work

Sugar Sell 12.0.5 Release Notes

Overview

This document describes the changes and functionality available in Sugar® 12.0.5. Sugar 12.0.5 is only available for customers on the annual upgrade path. 

Note: This release is not available for SugarCloud customers.

Administrator and End User

Fixed Issues

Sugar 12.0.5 is a security update released to address certain security vulnerabilities identified during our routine QA checks.

For customers on the annual upgrade path, we strongly recommend that you install this update at the earliest opportunity. While we have not experienced any reported incidents relating to these vulnerabilities to date, failure to install this update could leave you exposed to malicious third-party attacks. For more information, please refer to the following Security Advisory announcements:

These vulnerabilities have been addressed in release 12.0.5, which is available for download from the Download Manager.

Administrators are strongly encouraged to upgrade their on-site Sugar instances running 12.0.4 or lower to version 12.0.5 to prevent potential exploitation of these weaknesses

The following issues have been resolved in this release. Case portal users can use the following links for more details about each issue:

  • 93986: The PDF Manager in Sugar may not work as expected and result in errors. 
  • 93444: In certain circumstances, customers may encounter PHP fatal errors in Sugar when using PHP 8.2.
  • 93315: Users may encounter unexpected issues when trying to use dashboard filters in Sugar.

Known Issues

Click the link below to expand or collapse the 12.0.5 known issues list.  

12.0.5 Known Issues

The following known issues are present in this release. Case Portal users can use the following links for more details about each issue: 

  • 93631: When new panels are added to the record view layout while configuring the dropdown-field-based views in Studio, changing the panel label may improperly update the label of the other new panels.  
  • 92477: DateTime fields may be calculated incorrectly in reports when accounting for daylight savings time (DST).
  • 91045: In certain circumstances, customers running Sugar on-site may be required to manually revalidate their license every few days.
  • 91023: The Search and Select Users drawer may not display the correct count of user records if there is an inactive user in the instance. 
  • 91003: When a report fails to run due to a 500 error, the error message that appears should be more meaninful and informative.
  • 90931: When role permissions are modified for a user, the changes do not get applied until the browser cache is cleared and the user logs out and back in to their account.   
  • 90615: When logged into Sugar using a non-English language (e.g., French), changing the classification value for the sales_stage_dom list in Admin > Dropdown Editor may improperly change the classification values for the other list items. As a workaround, log in to Sugar with the English (US) language and manually update the classification of the list items to the correct values. 
  • 90463: If the report contains three or more group-by fields, the report result may show incorrect data. 
  • 90322: Certain languages (e.g., Chinese, Japanese) with special characters display incorrectly in reports exported as a PDF or CSV file. 
  • 90059: In certain circumstances, sorting a related-record subpanel (e.g., Leads) using the Account Name field column may result in an unexpected error. Sort the subpanel using a different field column to stop the error and allow the subpanel to load. 
  • 89831: Exported reports do not respect the locale settings in Sugar and incorrectly displays the date using the YYYY-MM-DD format. 
  • 89641: Hint-related error messages are logged for some recently upgraded Sugar 12.0 instances that do not have Sugar Hint.
  • 89542: For instances wth a very large number of SugarBPM processes, trying to view the list of processes in the Process Management's list view may result in performance issues and fail to load. 
  • 89457: The search bar in SugarLive does not work in instances that include Hint (e.g., Sugar Premier instances).
  • 88957: In certain circumstances, performing a global search in Sugar may result in a 500 error.  
  • 88374: Attempting to reorder the columns in the Worksheet Columns Preview list view in Admin > Quotes Configuration does not work as expected. As a workaround, remove all the fields from the Worksheet Columns section then add the fields again to the section. 
  • 88206: In certain circumstances, installing packages in Module Loader may not work as expected and the package may get uninstalled with errors. 
  • 88188: Drilling through report charts may not work as expected for Summation-type reports filtered or grouped a certain way.  
  • 87880: The default system currency incorrectly displays "US Dollars" as the currency name even though the system currency is changed to a non-USD currency (e.g., AU Dollars) in Admin > Locale.
  • 87602: In Sugar Enterprise, portal customization settings for the following features in Admin > Sugar Portal > Theme Portal are available but not applicable to the portal: the search bar, the banner, and the dashboard.
  • 87601: In Sugar Sell, portal customization settings for the following features in Admin > Sugar Portal > Theme Portal are available but not applicable to the portal: the search bar, the banner, the New Case button, and the dashboard.
  • 87477: Removing the Discount Amount field then re-enabling the field in Admin > Quotes Configuration may cause the Discount Amount field to not display correctly when creating quoted line items on the quote worksheet. As a workaround, navigate to Admin > Quotes Configuration and click "Restore Defaults" under the Worksheet Columns section and be sure to have the Discount Amount field enabled.
  • 87018: Hard deleting note records via the Data Archiver module does not delete the record's file attachments in the upload directory as expected. 
  • 86849: In certain circumstances, refreshing the browser may improperly change the order of dashlets on the dashboard. 
  • 86285: In certain circumstances, users may experience unexpected behaviors when attempting to expland a subpanel or edit an empty Subpanel layout in Admin > Studio. For information on the workaround, refer to the defect's description on the bug portal.  
  • 85673: Installng a custom module that was built and exported from Module Builder may fail to install with an error.
  • 85342: When the Assignment Notification Emails template is customized using new variables (e.g. $account_name), the email notification does not pull in the relevant information as expected and display the variables in plain text instead. 
  • 85246: Errors may get logged in the system after upgrading or installing Sugar when certain license data is missing.  
  • 84692: Certain reports may not generate as expected if the last group-by field is a date (e.g. Opportunities > Week: Expected Close Date) and the report contains a chart (e.g. Horizontal Bar). 
  • 84684: In certain circumstances, saving the Preview View layout for modules (e.g. Accounts) via Admin > Studio may not work as expected and result in an error. 
  • 84426: The Meeting Type field in the Meetings module does not reflect new values added to the Meeting Type dropdown list in Admin > Dropdown Editor.
  • 83880: Changes made to role-based view layouts are not applied to users assigned to the role. As a workaround, perform a Quick Repair and Rebuild for the change to take effect. 
  • 83796: SugarBPM processes always run after module-level logic hooks and it is not possible to configure them to run before logic hooks.
  • 83716: Attempting to deploy a package via Module Builder or Module Loader may fail with an error.  
  • 83715: User assigned to the Service Console and/or Renewals Console does not have access to configure the console settings.
  • 83574: Editing contact records containing a duplicate portal name may result in a number of unexpected errors when saving the record. 
  • 83425: Custom Date fields in the PDF template may not respect the user's preferred date format. 
  • 83335: Performance issues may occur for instances that have a number of related calculated fields, legacy workflows, and SugarBPM processes that trigger at the same time. 
  • 82810: Fields based on non-existent or improperly defined custom field types may cause upgrades to fail.
  • 82361: Emails sent from SugarBPM's processes may not include the link to new lead records generated from a Web-to-Lead form even though the process email template contains a link variable. 
  • 82230: Exporting a Summation report may fail with an error if the computed derivative (e.g. Count, SUM) is missing in the Choose Display Summaries step.
  • 81382: Deleting a target list related to a large number of records may fail with an error. 
  • 81297: If a web-to-lead form gets submitted using an existing email address in Sugar, the email address may not be marked as "Primary" for the generated lead record. 
  • 80865: It is not possible to search by the Record Name column in Process Management.
  • 80759: In PDF templates that contain more than one href link, only the first link works.
  • 80001: Email messages sent via SugarBPM may display HTML formatting when records are created using SOAP/REST v4.1. It is recommended to use the latest version of the API.
  • 79009: When the targeted module contains a broken field, configuring an Action element in a process definition causes the Process Design canvas to time out.
  • 77738: Attempting to merge two records (e.g. accounts) may fail with an error if the record that is being merged to the primary record contains a large number of related records (e.g. contacts).
  • 77719: If a process definition contains a Wait event that is relative to a date field, the process does not adjust for changes that may occur to the date field after the Wait event's initiation.
  • 77287: Performing certain actions (e.g. import, mass update) in Sugar may result in performance issues if there are numerous calculated fields to be updated in related records. As a workaround, add the following line to the config_override.php file to disable the related calculation field updates: $sugar_config['disable_related_calc_fields'] = true;. But keep in mind that the affected calculated values will not be updated and running Recalculate Values on related records. 
  • 77249: Guests may not get imported to call or meeting records as expected.
  • 73566: Calculated or dependent fields containing a related() function may not get calculated until after save for activity-type modules (e.g. Notes).  
  • 68112: Matrix-type reports display incorrectly when exported to PDF.

Supported Platforms

For information on supported platform components, see Sugar 12.0.x Supported Platforms.