Read our blog for the latest insights on sales and marketing Take Me There

Webinar: Use Sugar Data to Easily Generate Complex Documents Register

Webinar: Advanced Calendar Solution for Sugar Register

Sugar Summer ‘18 (8.1.0)

Released on July 10th, 2018


This document describes the changes and functionality available in Sugar® Enterprise For more information on the changes in this release, please refer to the What to Expect When Upgrading to 8.1 article.

Sugar is only available for Sugar cloud (Sugar-hosted SaaS) deployments.

Administrator and End User

Feature Enhancements

The following feature enhancements are included in this release:

  • Reporting 
    • Improved report distribution: Users can now schedule emailed reports for other users as well as for themselves via the new Scheduled Reports module.
    • Stock reports : Over 100 new stock reports are available in the Reports module.
  • Advanced Workflow 
    • Faster imports and exports: Email templates and process business rules will automatically export as part of their related process definition's .bpm file, streamlining the import process.
    • Gateway improvements: Event-based gateways can now detect whether a form activity has been completed before a condition has been met or within a set period of time.
    • Start event support for "All" or "Any" related records : When more than one related record may be affected by a process definition's Start event, the administrator can specify if the criteria must be true for all related records or just one or more of the related records.
  • Data Privacy
    • Email opt-in link : Users can generate a link to send to customers which, when clicked, will mark the opted-out email address as opted-in.
    • Data erasure for activity streams : Erasing personal information via the Data Privacy module now removes the erased values from activity stream posts. 
  • Emoji support : The Emails module can now display emojis used in message content, and users can use emojis in Sugar text fields.
  • Additional information at login : Sugar's login screen now includes an image and the ability to display notifications from SugarCRM. Admins have the option to disable this via Admin > System Settings > Enable additional login screen content. Instances with customized login screens will have this option disabled automatically when upgraded to 8.1.

Fixed Issues

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

  • 81026 : Users may be unable to login to Sugar or may be unable to use global search due to an error caused by Elastic Search settings being absent from config_override.php.
  • 81001 : In the REST API version 4.1, calling get_entry_list on the Contacts module fails to return valid account_name and account_id values.
  • 80915 : LDAP users may be unable to log into Sugar due to the presence of 'authenticationClass' => '' in config.php.
  • 80886 : LDAP users may be unable to log into Sugar when LDAP is configured to use anonymous binding.
  • 80866 : Reports may fail to return correct results when the Optional Related Modules option is used.
  • 80860 : Campaigns' email marketing records are not able to be edited.
  • 80851 : List views may fail to load when multiple custom relationships have been created between modules.
  • 80813 : The SOAP API and is not available for use, rendering applications which use SOAP unable to connect to Sugar.
  • 80808 : Records views may fail to load when the Actions menu has been customized using non-sequential button ordering.
  • 80671 : Prepared statements built using Doctrine's SQL builder class do not appear in slow query logging as expected.
  • 80605 : Integrations and customizations using the REST v4.1 API may no longer work as expected for instances running on PHP 7.1.
  • 80477 : While importing records, choosing "Salesforce" as the data source results in an error.
  • 80475 : When building a workflow alert template, users are not able to insert field variables based on related modules.
  • 80469 : The "Clean up unused combinations of teams" repair does not remove unused sets of teams from Sugar's database as expected.
  • 80349 : Global search does not return results when team-based permissions are enabled.
  • 80163 : Modules using the legacy user interface experience degraded performance when Sugar's tracker tables grow very large.
  • 80094 : Legacy workflows which use a checkbox field in their trigger conditions may not function as expected.
  • 800837995679251 : List view filters which are applied before the list view finishes loading may not be respected by the displayed results.
  • 79785 : While importing records, clicking "Undo Import" removes the imported records from Sugar but errantly allows the records to appear as results in global search.
  • 79643, 72456 : Inbound emails containing emojis may not get imported into Sugar as expected.
  • 79166 : Session locking may cause performance issues in Sugar.
  • 78555 : Reports which attempt to display the Knowledge Base module's Active Revision field result in an error.
  • 78339 : Global search does not return results matching search strings which are portions of field values and greater than 16 characters long.
  • 78278 : Reports which attempt to filter on multiselect fields created via Module Builder do not return results as expected.
  • 78224, 73891 : Attempting to reorder subpanels in the module's record view may not work as expected when logged into Sugar using Chrome on Windows touchscreen devices. As a workaround, disable the "Enable Touch Events" option for Chrome and users should be able to drag and drop subpanels accordingly.
  • 77979 : Using the v4 SOAP API to retrieve lists of records may experience performance issues when tags are heavily used in the instance.
  • 77330 : Report filters cannot be created based on the Product Catalog module's Product Category field.
  • 77314 : List views sorted by custom fields may experience degraded performance for modules containing a large number of records.
  • 76000, 75999 : Setting the Collation option to "utf8mb4_general_ci" via Admin > Locale may cause unexpected errors.
  • 73282 : Forwarding an email from within Sugar does not include the body of the original email in the newly sent message.

Known Issues

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

  • 81152 : Event-based gateways improperly consider activity elements to be complete if the activity gets reassigned to another user via "Select New Process User".
  • 81151 : Report chart drill-through may not work as expected when the report is filtered by a checkbox field.
  • 80730 : Reports without charts are improperly available to select in the Saved Reports Chart dashlet. 
  • 80681 : Making changes to a report's relationship-based filters may result in an error when running the report. As a workaround, re-create the report with the desired filter without making any changes to it.
  • 80583 : Attempting to erase fields (e.g. Description) marked as "Personal Information" from the Opportunities module do not work as expected and result in a 500 error. 
  • 80376 : Uninstalling custom modules from Sugar may not delete the associated workflows as expected. As a workaround, remove the affected workflow via the database. 
  • 80250 : Receive Message events configured for a record related to the process definition's target module may not behave as expected.
  • 80246, 78121 : In certain circumstances, having calculated fields that are marked as required may cause unexpected behavior in the record.
  • 80091 : Creating a dashboard may not work as expected and result in an error for users without private teams. Navigating to Admin > Repair and running "Repair Teams" will help resolve the issue. 
  • 80002 : Generating PDFs using previously existing PDF templates may not display data as expected after upgrading to Sugar versions 7.9 or higher.
  • 79947 : Calculated fields may not populate when the record has multiple calculated fields using the related() function to the same module (e.g. related ($accounts, field1) and related($accounts, field2)). 
  • 79888 : Email accounts configured as a group inbound mailbox may not be used to send emails even though the "Allow users to send emails using the "From" Name and Address as the reply to address" option is enabled.
  • 79777 : The billing address and shipping address for quotes created via the "Quotes (Bill To)" or "Quotes (Ship To)" subpanel may appear incorrectly if the related record's (e.g. Accounts) billing and shipping address is different.
  • 79763 : The Account Name field does not get populated as expected for quoted line items related to a quote. 
  • 79752 : When using Internet Explorer 11 with Advanced Workflows, columns cannot be deleted from process business rules in the Rules Builder. As a workaround, please use another supported browser.
  • 79716 : The Contracts list view, record view, and subpanel do not have the option (star icon) to designate records as favorites.
  • 79715 : The Follow button does not appear in the Contracts record view as expected. 
  • 79712 : The "Sign" and "Get latest" links do not appear as expected in the Documents subpanel of the Contracts module. 
  • 79709 : Single sign-on authentication may fail when attempting to log into Sugar using Internet Explorer.  
  • 79704 : When logged into Sugar with certain languages (e.g. Russian), the list view's Record Actions menu may not appear as expected for some modules (e.g. Dashboards).
  • 79686 : The List Order field in the Contract Types, Manufacturers, Tax Rates, and Shipping Providers modules does not control the order in which the options are listed in the corresponding fields (Type Name, Manufacturer Name, Shipping Provider, Tax Rate) for the Contracts, Quotes, and Product Catalog modules.
  • 79492 : Setting the log level to "Error" may result in multiple relationship errors being written to the log file.
  • 79469 : When a web-to-lead form is created without including a redirect URL, the visitor may improperly get directed to an error page upon submitting the form.
  • 79453 : Emails that were previously archived to contact records, as well as newly archived emails to contacts, may not appear in the related account's Emails subpanel after upgrade to 7.9.x. As a workaround, select the related account when archiving an email to a contact using the Outlook plug-in. 
  • 79368 : Values cannot be set for custom relate fields or custom relationship fields when configuring the Add Related Record action for a process definition in Advanced Workflow.
  • 79344 : The quoted line item total may not respect the user's preferred currency as expected. 
  • 79318 : When a user has team-based permissions enabled for their default team (i.e. "Additional Permissions Enabled"), the setting may not be respected when creating a new record.
  • 79244 : Certain stock modules may be improperly hidden after converting from Sugar Professional to Sugar Ultimate
  • 79186 : When searching for records that contain an apostrophe (e.g. Johnny's) in the name via SugarCRM Mobile or the desktop version of Sugar, the search result may improperly display the tag (e.g. Johnny's) in the record's name.
  • 79173 : When attempting to navigate away from the module or save the record, the Unsaved changes warning message may unexpectedly appear for modules containing custom dependent fields.
  • 79156 : When a Summation Report with Details is printed to PDF, there may be missing display columns (e.g. Name) on the PDF file.
  • 79131 : When the "Listview items per page" setting in Admin > System Settings contains a large value (e.g. 50 or greater), it may cause an issue with rendering the "Download PDF" and "Email PDF" options in the record view's actions menu. Changing the "Listview items per page" setting to "20" may help resolve the issue. 
  • 79108 : When editing a record via the list view preview on the intelligence pane, the Resolve Conflict drawer may appear unexpectedly upon save.  
  • 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.
  • 78890 : Updating composer in instances with custom modules deployed from module builder may cause unexpected errors.
  • 78885 : An Advanced Workflow process may be prematurely considered complete when part of the process remains unexecuted in job queue.
  • 78850 : The Saved Reports Chart dashlet may not render the chart as expected for certain reports when the Bar chart value placement field is set to an option other than "None" or "Total". Selecting "None" or "Total" for the Bar chart value placement field will render the charts properly in the dashlet.
  • 78845 : Attempting to add a code library to Sugar may cause the composer update process to fail and not update as expected. 
  • 78790 : Performing certain actions that rebuild the cache files (e.g. clearing the cache directory) may cause unexpected errors in the system.
  • 78736 : Out-of-the-box dashboards may incorrectly be recreated after deleting it from the home page or intelligence pane. 
  • 78719 : Users may encounter an unexpected behavior when accessing Sugar if the Date Modified field in the user account contains the same value as another user. 
  • 78709 : Users assigned a role with Delete, Edit, or Export permission set to "Owner" may improperly be restricted from downloading and emailing PDFs.
  • 78668 : In certain circumstances, the tooltip (e.g. Create) may continue to persist improperly while navigating through Sugar. Reloading the web browser will clear the tooltip from the screen.     
  • 78667 : Attempting to scroll in Sidecar modules (e.g. Meetings) may not work as expected when logged into Sugar on iPad.
  • 78600 : Special characters are improperly allowed to be entered in dropdown lists' item names.
  • 78582 : Process definitions do not enforce the requirement that multiple paths must converge before an End event.
  • 78580 : Saving a record without completing the Salutation field which is marked as required in Admin > Studio may result in unexpected behavior. 
  • 7857078509, 7850776151 : When accessing Sugar using Internet Explorer or Firefox, attempting to clear a saved filter from the list view or subpanel search may not work as expected. As a workaround, select the All "Module Name" option from the Filter options list to clear the applied filter.
  • 78547 : When creating a meeting or call assigned to another user, removing the current user from the Guests panel may not remove the user as expected upon saving the record. 
  • 78541 : Dropdown fields set with ReadOnly dependencies may improperly be allowed to be edited if the field contains a dependent visibility formula. 
  • 78527 : Inline editing a TextArea field via the subpanel may not work as expected. Reloading the web browser will resolve the issue and allow the user to inline edit the field properly. 
  • 78487 : When renaming modules via Admin > Rename Modules, only the most recent changes will remain and any previous updates to module names will be incorrectly removed after save. 
  • 78471 : Setting the default date format in the user's profile to "mm/dd/yyyy" may cause the time periods on the Forecasts Settings page to incorrectly display "Invalid date".
  • 78334 : Performing certain actions in records containing calculated fields with rollup functions (e.g. rollupSum) and a large number of related records may cause performance issues in Sugar.   
  • 78315 : The same Process ID may be used for multiple processes if a process definition's Start condition is triggered by simultaneous events.
  • 78272 : Populating an amount field during record creation via the REST version 10 API causes the record to fail to appear in listview as expected when filtering on the amount field's value. As a workaround, update the currency_id field to "-99" via the REST API, trigger a save event via the user interface, or update the field directly via the database. 
  • 78229 : Downloading the import file template may take longer than expected for module's containing a large number of records.
  • 78198 : Activity stream posts may incorrectly display system labels for instances where the system default language is set to a non-English language. As a workaround, navigate to Admin > Locale and change the language to "English (US)", perform a "Quick Repair and Rebuild", then switch the default language back to your desired language.
  • 78153 : Changing the default value for the Popup Reminder Time field for calls or meetings may not work as expected and continue to display the old value.
  • 78128 : For dropdown list values, a value's Display Label will improperly revert to a blank value if its Item Name is 0 (zero).
  • 78093 : Reports filtered by date/time fields (e.g. End Date) may generate incorrect results if the user's timezone has changed. 
  • 78065 : Moving a stock field between the columns (e.g. Hidden, Available) for the List View and Subpanel layouts in Studio may result in unexpected behavior. 
  • 78031 : Setting a default value for a field during the import process may not preserve the value in the field as expected.
  • 77820 : The Visibility Editor window may not load as expected and display an error if there is a large number of dropdown dependencies defined in the visibility editor.
  • 77792 : Enabling Full Text Search for the Date Created field in a module (e.g. Leads) may cause unexpected errors when performing a global search filtered by the module.
  • 77780 : Instances using MS SQL may see unexpected behavior due to a lack of ORDER BY clause in the list view query. 
  • 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.
  • 77648 : Removing the Name field from layouts in Studio may cause the hyperlink attribute ('link' => true,) to get removed from the field. To resolve the issue, add 'link' => true, to the Name field array in the relevant layout file within your custom directory, then perform a quick repair and rebuild.
  • 77609 : Generating reports with empty relate fields may not include the associated record in the report result as expected if the related record has been deleted.
  • 77601 : Advanced Workflow cannot add related records when the target module is on the "one" side of a one-to-many relationship. 
  • 77596 : The Emails subpanel may not display more than five email records for Sugar instances running on MSSQL databases. 
  • 77549 : Users may experience performance degradation when user records are modified. 
  • 77539 : Changing the boost value for a field (e.g. Name) may not affect the relevancy of the field for full text search, resulting in unexpected behavior. 
  • 77516 : The My Processes dashlet may display processes that have already completed.
  • 7737277612 : When logged into Sugar using the Chrome browser, highlighting/selecting text in certain fields (e.g. Description, Name) may cause issues loading the browser and display an error. As a workaround, edit the field without highlighting any text to make the necessary changes. 
  • 77302 : Upgrades may fail due to queries posted by the upgrade exceeding the max_allowed_packet database setting.
  • 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.
  • 77205 : Viewing a page (e.g. list view) in Sugar without performing any actions for a period of time (e.g. 3 minutes) may cause an error message (Request Timeout: The server is not responding. Check your internet connection.) to appear unexpectedly.
  • 77162 : When Sugar is deployed on a Linux OS, uploading packages in Module Loader may fail with an error when .PNG files are detected by the package scanner.
  • 77087 : When a record is assigned to the user's default private team, changing the Teams field from the private team to another team (e.g. Global) may incorrectly display the team name with the user's last name appended to the end (e.g. Global Smith).   
  • 77055 : Attempting to mass update the user's outbound email client via Admin > User Management may not work as expected. 
  • 76985 : When performing a global search, filtering by a module then hitting the Enter key after entering the search term may cause a 500 error to occur.
  • 76783 : When a record view panel with a Sugar Logic dependency formula contains a required Date field, the field may improperly default to 01/01/1970 when the panel appears.
  • 76730 : Field-level validations may not work as expected to trigger field validation messages upon saving the record. 
  • 76524 : Dependent fields may not appear in the layout (e.g. Record View) as expected if the parent field (e.g. parent dropdown) is not present.
  • 76401 : The data in the report chart may be inconsistent between the report chart dashlet and the Reports module. 
  • 76126 : When entering a dependency formula for a DropDown-type field, clicking the Cancel button on Studio's formula builder may not close the window as expected and result in an error.
  • 76114 : When importing products, the defined currency on the import file may not be respected properly and cause the currency values to be calculated incorrectly.
  • 76014 : Mass-updating a large number of records that trigger the start event on one or more process definitions will result in a PHP timeout error. Additionally, any processes created before PHP timed out may be corrupt.
  • 75398 : Workflow alert may not trigger as expected if the processing order for the workflow is set to "Actions then Alerts". As a workaround, changing the workflow's processing order to "Alerts then Actions" may help resolve the issue.  
  • 75258 : Mass updating or importing records (e.g. cases) that are related to records (e.g. accounts) with large datasets may result in PHP memory errors.
  • 75254 : Printing reports (e.g. Summation With Details report) to PDF may not work as expected when logged into Sugar via a mobile browser.
  • 74919 : Performing certain actions (e.g. Quick Repair and Rebuild) in Sugar that rebuild the cache files may cause unexpected issues in the system if there are multiple users logged in and utilizing Sugar. As a workaround, perform such actions during off-hours where users are not utilizing the system.
  • 74912 : In the Process Business Rules module, it is possible to create a business rule that exceeds the maximum SQL query length, resulting in a Javascript error and blank screen on save.
  • 74893 : Opportunities with expected closed dates prior to a certain time period (e.g. 1/1/1970) may cause the Forecast Bar Chart dashlet to not display as expected.
  • 74887 : When there are a large number of filters (greater than 20) created by the same user for a module (e.g. Accounts), the corresponding list view dashlet may not behave as expected.
  • 74713 : Designating an email address as the "Reply to" address in the user's profile may not save as expected to preserve the settings.
  • 74628 : Certain workflows using a Relate-type field in the condition may fail to load as expected and result in errors after upgrading to 7.6.x.x. As a workaround, run the following query in the instance's expressions table:
    UPDATE expressions
    SET    exp_type = "id"
    WHERE  exp_type = "relate"
           AND lhs_field = "assigned_user_id"
  • 74539 : Custom fields may not display as expected when previewing call and meeting records via the intelligence pane.
  • 74416 : Creating a Summation-type report that is grouped and sorted by a certain field (e.g. Month: Expected Close Date, Quarter: Expected Close Date) in a related module (e.g. Opportunities) may cause the run-time filter to not work as expected. 
  • 74382 : The Case Summary dashlet may not work as expected and cause an internal server error if the account record has a large number of related cases.
  • 74354 : Pie charts may not display properly in report results if there are labels with a large number of characters.
  • 74350 : An unexpected error may occur when saving a record if there is an issue with the user's default team in the database. As a workaround, run the following query in the instance's team sets table. The affected users will then need to edit their profile to configure their default teams again.
    UPDATE team_sets
    SET    deleted = 1
    WHERE  id NOT IN ("select team_set_id from team_sets_teams where deleted = 0")
           AND deleted = 0
  • 74349 : Creating and saving a record assigned to a team that the current user is not associated to may display an error even though the record gets created successfully.
  • 74097 : Changing the instance's opportunity model from "Opportunities and Revenue Line Items" to "Opportunities" may cause data to not display correctly when viewing the campaign's ROI.
  • 73912 : Certain reports may not generate as expected if the last group-by field is a date (e.g. Opportunities > Month: Expected Close Date) and the chart type is set (e.g. Horizontal Bar). As a workaround, do not use the date field as the last grouping in the Define Group By step or change the chart type to "None".
  • 7372972956: Populating a target list by selecting a report for a module (e.g. Accounts) may not add all records as expected if the report contains a large amount of data.
  • 73689 : When users adjust the list view or subpanel column widths, the user's preferred column size may not be preserved if the browser window is resized.
  • 73569 : Attempting to add a row to an existing quote record may not work as expected when accessing Sugar via certain browsers (e.g. Chrome, Safari) on iPad.
  • 73566 : Calculated or dependent fields containing a related() function may not get calculated until after save for activity-type modules (e.g. Notes).
  • 73468 : Time-elapse workflow may not trigger as expected when a date field (e.g. Expected Close Date) in the condition is set to a date in the future.
  • 73434 : Custom entrypoints which require authentication may not work as expected when using session tokens.
  • 73346 : URLs generated for iFrame or URL fields may improperly include special character encoding when the record was created via an API call.
  • 73301 : Attempting to edit Sugar Logic formulas with too many lines in the formula may cause an error ("Formula Builder: Error Loading Content") in Studio's formula builder. As a workaround, edit the formula to remove any line breaks.
  • 7318770389: Tabbing while inline editing the address block in the record view does not work as expected as it does not tab through all the fields (e.g. state, postal code) within the address block.
  • 72962 : Dependent fields containing a related() function may cause the data to not display as expected in the module's list view.
  • 72906 : Non-admin users who have developer-level role access to Sugar modules do not have access to the Advanced Workflow panel on the Admin page. These users may navigate to Process Management via the Processes module tab menu.
  • 72810 : Filtering the list view search using custom checkbox fields may not work as expected.
  • 7262571848 : When a large number (e.g. 60) of PDF templates are available in a module, users may not be able to scroll through the full list of templates via the "Download PDF" or "Email PDF" options in the record view. As a workaround, changing the screen resolution or reducing the number of templates may help resolve the issue.  
  • 72590 : The Due Date field may not be available to select when mass updating in the Tasks module. To resolve the issue, navigate to Admin > Studio > Tasks > Fields and disable the Mass Update option for the Due Date field then enable it again.
  • 72581 : Attempting to merge records in modules containing required dependent fields may not work as expected. 
  • 72409 : When generating a report, labels may improperly overlap in the chart (e.g. Vertical Bar chart) causing the labels to be unreadable.
  • 72286 : The Opportunity module's amount fields cannot accept negative values.
  • 72264 : Clicking on the opportunity's name in the Quotes detail view after downloading the quote to PDF improperly redirects to the home page instead of the opportunity's record view. As a workaround, right-click on the opportunity name after downloading the quote to PDF and the opportunity's record view will open accordingly.
  • 72022 : The Projects module is incorrectly available to select via Admin > Mobile.
  • 71950 : Adding TinyMCE to a TextArea-type field (e.g. Description) may cause the field to not display properly in record view when accessing Sugar via certain browsers (e.g. Firefox).
  • 71835 : The Reset Password option in Admin > User Management may not work as expected and fail to send the system-generated password message to users with an email address from a domain consisting of 5 or more characters.
  • 71733 : Printing archived emails via the browser's print option may not display correctly.
  • 71446 : For opportunities, changes made to labels via Studio > Opportunities > Labels do not affect list view labels. Make changes to labels via Studio > Opportunities > Layouts > List View to modify list view layouts.
  • 70940 : Attempting to disable the SAML authentication via Admin > Password Management may not work as expected if the authenticationClass property in config.php has been set to SAMLAuthenticate.
  • 70935 : When text is highlighted to change the font size in the compose email window, selecting the same font size (e.g. 12pt) twice in consecutive order may incorrectly reset the font back to the default size (8pt).
  • 70542 : The "Show Completed Meetings, Calls, and Tasks" option is not available in Calendar > Settings, which can cause performance issues in the Calendar module for users who have a large number of activity records. Setting Admin > System Settings > vCal Updates Time Period to "-1" will relieve the performance delay, however, this will prevent user availability information from appearing when scheduling a call or meeting.
  • 70024 : Scheduled reports may have incorrect or missing charts in the emailed PDF. Select "Print as PDF" from the report's Actions menu to see the updated chart.
  • 69985 : If a custom module has a relationship with an individual Activity-type module (e.g. Tasks), this related module may not be available to select when creating a workflow action to create a record in a module (Tasks) associated with the target module (e.g. custom module). As a workaround, create a one-to-many relationship between the custom module and the Activities module, and the appropriate Activity-type module (e.g. Tasks) will be available to select when creating the workflow action
  • 69982 : Old Value variables (e.g. {::past::Opportunities::sales_stage::}) inserted in workflow alert templates may not display the correct value in the email as expected.
  • 69957 : Large number of activity stream records may cause performance issues.  
  • 6991869801 : Changing the style attributes for table tags, image tags, etc. on email templates via HTML may result in parts of the code getting removed upon save.
  • 68985 : Custom relationships created between a module and the Activities module via Admin > Studio cannot be deleted as expected.
  • 68975 : Changing the order of subpanels via Admin > Display Modules and Subpanels does not preserve the order upon save.
  • 68461 : Searching by non-primary email addresses in the module's list view (e.g. Accounts) does not pull up results as expected.
  • 68112 : Matrix-type reports display incorrectly when exported to PDF.
  • 68024 : The Case Number, Date Created, and Created By field values for the Cases module may not get populated in workflow alerts that are triggered on first save.
  • 67886 : During lead conversion, the newly created opportunity record does not get associated to the Revenue Line Item, causing the lead conversion to not complete successfully. As a workaround, create the opportunity record during lead conversion then manually associate the opportunity to the Revenue Line Item.
  • 67875 : Attempting to insert old value variables for related modules in workflow alert templates may not work as expected.
  • 67186 : The View Change Log in module records (e.g. Quotes, Opportunities) may incorrectly reflect the original system currency (US Dollar) for currency fields even though the default system currency has been changed (e.g. Euro) in Admin > Locale.
  • 66995 : The Display server response times option is improperly available to select via Admin > System Settings.
  • 66910 : The notification for Cases module does not include the case number as expected when triggered via the workflow.
  • 66900, 67294 : Resetting the forecast time period does not set the current time period correctly and causes various issues in the application.
  • 66842 : Relate fields cannot be sorted as expected in the list view.
  • 66086 : Embedded images may not display properly in archived emails.
  • 64880 : Certain fields (e.g. email address, phone) in the Users module may not be available to add as field variables in PDF templates.
  • 61338 : When test entries are deleted from the campaign, the related campaign emails that are sent to targets may not be viewable and display an error (Error retrieving record. This record may be deleted or you may not be authorized to view it).


The following changes in this release may affect developers:

  • A db logger channel has been added to allow for more fine-grained control over log messages related to the database. For example, the following config option will cause related debug messages to be written to the log file regardless of the global Sugar log setting: $sugar_config['logger']['channels']['db']['level'] = 'debug';
  • The format for database-related log messages has changed. 
    Previous format:
    Tue 03 Jul 2018 01:27:39 PM PDT [23772][1][INFO] Query: SELECT name
    FROM users
    WHERE id = 1
    New format:
    Tue 03 Jul 2018 01:27:39 PM PDT [23772][1][INFO] Query: SELECT name\n FROM users\n WHERE id = 1
    For development purposes, the original multi-line message can be restored using sed 's/\\n/\n/g' sugarcrm.log
  • The SugarCache implementation has been refactored to support PSR-16 cache interface and encrypted storage for multi-tenant cache use.
    As part of these changes, cache backends that extend SugarCacheAbstract are deprecated and will be removed in a future Sugar release. Cache implementations from Sugarcrm\Sugarcrm\Cache\Backend namespace should be used instead.
    Usage of the characters reserved by PSR-16 in cache keys such as ()/@: are no longer supported. Currently, these characters are converted to - and warnings are logged in sugarcrm.log.
  • The following Sugar Config parameters have been added for SugarCache:
    • cache.backend is a string that can be used to define which caching backend class that should be used.
    • cache.multi_tenant is a boolean that can be used to enable multi-tenant cache behavior.
    • cache.encryption_key can be used to define the encryption key for use in multi-tenant mode. This key will be generated automatically and doesn't need to be specified manually.
  • When using Sugar with Elasticsearch 6.x, Sugar will create one search index per module.
  • The following PHP libraries were updated or added in this Sugar release:
    • The Elastica library was upgraded from v5.3.0 to v6.0.1. Please refer to the Elastica changelog for more details if you have custom code that calls Elastica library directly.
    • AWS SDK for PHP (aws/aws-sdk-php) v3.55.3 was added in this Sugar release. For more information on this SDK, please visit the Amazon website.
  • Slow queries created using Doctrine QueryBuilder are now logged as FATAL errors when "Log slow queries" is enabled via Admin > System Settings. The associated boolean SugarConfig setting is dump_slow_queries.
  • Monolog channels no longer support non-PSR logging levels like "fatal". For more information on PSR compliant logging levels, refer to the PSR-3 Logger page of Sugar's Developer Guide.
  • An option has been added to module loadable package manifests that will allow Module Loader to ensure all traces of previously installed package versions (including packages that have been upgraded multiple times) are removed.
      'uninstall_before_upgrade' => true,
    Custom pre- or post-install scripts that remove old versions of the package when upgrading may no longer be necessary when using the new uninstall_before_upgrade option.
  • Sugar can now be configured to use Amazon Elasticsearch Service. This requires some different AWS specific configuration as seen in the example below.
    'full_text_engine' => array (
      'Elastic' =>
      array (
          'transport' => 'AwsAuthV4',
          'aws_access_key_id' => '',
          'aws_secret_access_key' => 'aws secret access key',
          'aws_region' => 'aws region',
          'host' => 'aws ES server host',
  • Filter API performance has been significantly improved in this release by optimizing how the API queries the database. Instead of running a single complex SQL query, Filter API requests are now implemented using two simpler SQL queries. This change should significantly improve list view performance for modules with many records and complex team security rules.
  • The following authentication-related files were removed:< >sugarcrm/modules/Users/authentication/EmailAuthenticate/EmailAuthenticate.phpsugarcrm/modules/Users/authentication/EmailAuthenticate/EmailAuthenticateUser.phpsugarcrm/modules/Users/authentication/LDAPAuthenticate/LDAPAuthenticate.phpsugarcrm/modules/Users/authentication/LDAPAuthenticate/LDAPAuthenticateUser.phpsugarcrm/modules/Users/authentication/LDAPAuthenticate/LDAPConfigs/default.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/SAMLAuthenticate.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/SAMLAuthenticateUser.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/SAMLRequestRegistry.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/index.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/saml.phpsugarcrm/modules/Users/authentication/SAMLAuthenticate/settings.phpsugarcrm/modules/Users/authentication/SugarAuthenticate/SugarAuthenticate.phpsugarcrm/modules/Users/authentication/SugarAuthenticate/SugarAuthenticateExternal.phpsugarcrm/modules/Users/authentication/SugarAuthenticate/SugarAuthenticateUser.php
  • SAMLAuthenticate has been replaced by IdMSAMLAuthenticate.LDAPAuthenticate has been replaced by IdMLDAPAuthenticate.SugarAuthenticate has been replaced by IdMSugarAuthenticate.SugarAuthenticateExternal has been replaced by ExternalLoginInterfaceThe clipboard.js v2.0.0 library has been added to Sugar.
  • In order to support importing and displaying emails that contain emoji, MySQL databases now use the utf8mb4 character set and the utf8mb4_general_ci collation. The character set and collation will be set automatically for new instances of Sugar and updated during the upgrade of existing instances of Sugar. Upgrading instances are not anticipated to experience issues, but upgrade testing is recommended.
    Tables with very large row sizes (e.g. custom tables with a large number of custom fields) may be unable to be automatically upgraded. The upgrade script will notify you if a table would exceed the single-row size supported by MySQL (65,535 bytes) upon conversion to utf8mb4. In order to reduce the row size, we recommend the following:
    • Remove fields that are not being used.
    • Reduce the lengths for char/varchar fields (e.g. size of longest existing value plus some padding).
    • Replace large varchar fields with text fields. Text fields are roughly 10 bytes, so significant size reduction exists when text fields can replace large varchar fields (e.g. VARCHAR(255).
  • The EmailMarketing::time_start property has been removed in this release. The start time of an email campaign should be derived by parsing the EmailMarketing::date_start attribute.
  • The function View.Views.Base.HistorySummaryHeaderpaneView._getParentModelName is now deprecated.
  • The translatable template string TPL_HISTORICAL_SUMMARY stored in sugarcrm/include/language/en_us.lang.php now uses unescaped values. Please ensure you are NOT using this template in combination with Handlebars.SafeString as this would make your code vulnerable to XSS attacks.
  • The Sugar login page has been updated to display content from SugarCRM. The content will not display on any window smaller than 1024px (this includes most phones and tablets). We recommend testing that any customizations you have made to the Sugar login page continue to work on both large and small screens.
    The following sidecar views have been added:< >MarketingExtrasViewMarketingExtrasView has been added to LoginLayoutMarketingExtrasView has been added to ForgotPasswordLayoutAdmins can choose to disable the SugarCRM content from appearing on the login page via Admin > System Settings > Enable additional login screen content. The marketing_extras_enabled boolean SugarConfig setting has been added in this Sugar release. Setting this value to false will disable the custom content from SugarCRM on the login page.

« Back to Releases