SugarCRM SupportProduct GuidesSugar Versions10.010.0 ServeSugar Serve 10.0.0 (Q2 2020) Release Notes

Sugar Serve 10.0.0 (Q2 2020) Release Notes


This document describes the changes and functionality available in Sugar® Serve 10.0.0 (Q2 2020). Sugar 10.0.0 is available for both SugarCloud (Sugar-hosted SaaS) and On-Site deployments. 

Customers who are upgrading to 10.0.0 (Q2 2020) from 9.3 (Winter '20) should refer to the following sections:

For information about this release's changes to existing functionality, please refer to the What to Expect When Upgrading to 10.0 article.

Administrator and End User

Feature Enhancements When Upgrading From 9.3 (Winter '20)

The following feature enhancements are available in 10.0.0 (Q2 2020) when upgrading from the 9.3 (Winter '20) release:

Sugar Serve Features (9.3.x to 10.0.x)

For features included in other products for 10.0.x, please see the release notes for Sugar SellSugar UltimateSugar Enterprise, and Sugar Professional.

  • Edge browser support : Sugar is now supported for use in the Edge browser.
  • Cookie consent : The first time you log in, Sugar will ask you to consent to the use of cookies in the application.
  • Record View Features
    • Field name placement : Users now have the option in their profile to configure where field names are placed in relation to their field values; the default is "Beside Field Value" and provides a more compact record view than the alternative layout, which shows labels "Above Field Values".
    • Empty field pills : Record view is now more compact with empty fields represented by a single empty field pill instead of a field name and a blank value.
  • Viewing long record names : Hovering over a truncated record name will now display the full text as a tooltip.
  • Quick-create cases : Users can now create cases from any page in Sugar using the Quick Create menu.
  • Product Catalog : The Product Catalog, Product Category, Product Types, and Manufacturers modules, which were previously admin-only, will be globally visible for all users on upgrade. Administrators can restrict user access to these modules via standard team and role restrictions. Audit Log functionality has also been added for the Product Catalog module.
  • Exporting Users reports : Regular users can now export reports that target the Users module.
  • Dashboard limit : The maximum number of dashboards that can be listed under the Home module tab has increased from 20 to 50 dashboards.
  • Portal Help link : A Help link to the portal user documentation has been added to the portal user menu.
  • Tile View Features
    • Sticky filters : A filter applied to the tile view will automatically apply to the module's list view and vice versa and will continue to apply as you toggle between the Tile View tabs, switch between the list view and tile view, or navigate away from the module.
    • Custom field support : Both stock and custom fields are now available to add to the Tile Options Header and Tile Options Body fields to be displayed in tile view.
    • Re-ordering column headers : The left-to-right order of the tile view column headers can be changed in Tile View settings.
    • Field validation : Field validation rules for records are now enforced when moving tiles from one column to another in tile view.
    • RTL support : Tile View is now compatible with right-to-left (RTL) languages.
  • Console Management Features
    • Default sort order : Administrators can now designate the field column(s) to be sorted in descending or ascending order when configuring the module tab lists to modify the list's sort order.
    • Restore default console : The console configurations can be restored back to the default out-of-the-box settings by clicking the Restore Defaults link at the bottom of the Console Settings window.
  • SugarBPM Features
    • Process sequencing : It is now possible to assign a sequence for processes with the same target module running at the same time by using the Run Order field.
    • Portal Name in email templates : The Portal Name field on the Contacts module is now available in the Fields Selector tool when designing process email templates.
  • General Administration Features

Fixed Issues When Upgrading From 9.3 (Winter '20)

The following issues are resolved in version 10.0.0 (Q2 2020) when upgrading from the 9.3 (Winter '20) release. Case portal users can use the following links for more details about each issue:

  • 84156 : In certain circumstances, creating revenue line items may fail with an error.
  • 83989 : An error may occur when using a process email template that contains a link to a related module if the record that triggered the process does not have a related record of that type. 
  • 83820 : When creating reports using the Product Categories module, generating the SQL queries may not display correctly when previewing the report.
  • 83765 : Deleting a user from the Cloud Settings console may not delete the user record from the Sugar application as expected if the organization has exceeded its license limit.
  • 83709 : Stock Change Timer reports in Sugar Serve that use averages perform incorrect average calculations.
  • 83679 : Users may be unexpectedly logged out with an error when logged into a SugarIdentity-enabled instance with a non-English language (e.g. French) and the English (US) language is disabled in the system. 
  • 83564 : Sugar instances with a Sugar Serve-only license type may improperly prevent admin users from accessing the System Email Settings on the Admin page.  
  • 83277 : Sugar licenses that are not revalidated after a renewal or upgrade to version 9.1.0 may cause users and admins to not be able to access certain areas (modules, dashboards) of the Sugar application.
  • 83225 : The filter(s) applied to the tile view is not preserved when toggling between the two group-by options (e.g. Opportunities by Time, Opportunities by Sales Stage) in the Opportunities tile view.
  • 83111 : In certain circumstances, dependent dropdown fields may not populate correctly when creating new records.  
  • 83056 : Custom dependencies in the Opportunities module may cause the Tile View to not display as expected.
  • 82897 : The dashboard metadata from a previous version of Sugar may not be compatible after upgrading to version 9.1.0 causing a 500 error to occur in certain circumstances. 
  • 82850 : Dragging and dropping a tile to a column in tile view may not update the record as expected if the column's dropdown value contains a numeric value (e.g. 1) in the Item Name.  
  • 82779 : In certain circumstances, downloading a PDF file via the module's record view (e.g. Accounts) may improperly generate multiple PDFs at once and result in PHP errors.  
  • 82690 : When the forecasting worksheet's current (uncommitted) numbers are higher than the most recent commit, it may not be reflected correctly in the forecast's summary and commit history. 
  • 82647 : Sorting on a relate field (e.g. Account Name) in the list view may improperly remove a record from the list view if the currently logged in user does not have access to view the related record due to team memberships.
  • 82589 : Setting the default date format in the admin's profile to "mm/dd/yyyy" may cause the time periods on the Forecasts Settings page to incorrectly display "Invalid date".
  • 82565 : The Product Catalog dashlet may not display the scrollbar as expected when accessing Sugar using Firefox.
  • 82455 : Quoted Line Items subpanels on record views of modules with no currency fields may not load as expected.
  • 81699 : Creating or linking a record via a subpanel (e.g. Notes) may improperly direct the user to the top of the record view instead of remaining in the current subpanel view. 
  • 81221, 78536 : Users may experience an unexpected error when utilizing Sugar if the instance contains a large number of calculated fields.
  • 80752 : When changing a date field that is marked for "Audit", the audit log may show an incorrect old/new value for the field if the user's current time zone reflects a different date than UTC.  
  • 8060074539 : The changes made to certain module's (e.g. Calls, Meetings) record view layouts in Admin > Studio may not be respected when previewing the record via the intelligence pane.  
  • 79925 : Email messages that have been archived to Sugar and contain embedded or inline images show empty containers instead of images in the email's record view and preview.
  • 79763 : The Account Name field does not get populated as expected for quoted line items related to a quote. 
  • 79618 : In certain circumstances, users may experience performance issues when running reports in instances with a large dataset.
  • 78802 : Using REST API endpoints to filter on teams using $equals may not return exact matches as expected. 
  • 75154 : Sugar may improperly truncate long record names/subjects and not display the full value in the field as expected.
  • 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 report contains a chart (e.g. Horizontal Bar). 
  • 67886 : During the lead conversion process, creating a new opportunity record does not automatically get associated with the revenue line item (if enabled) causing issues completing the lead conversion.

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:

  • 84236, 84076 : In certain circumstances, users may run into unexpected errors when trying to access certain modules and/or notice modules missing from the navigation bar. 
  • 84014 : When an opportunity's expected close date is updated from tile view, the Sales Stage and Expected Close Date fields are improperly updated on related revenue line items that are already closed. 
  • 83994 : In certain circumstances, campaign emails sent by regular users may not send as expected and result in unexpected errors. As a workaround, send the campain as an Admin user or do not click the Delete Test Entries button when sending the campaign as a regular user. 
  • 83985 : When the "Field Name Placement" user preference is set to "Beside Field Value", some labels will remain above the field value for the Calls and Meetings modules.
  • 83839 : Changing a user's license type from Sugar Enterprise to Sugar Sell and/or Sugar Serve may cause the user to be unable to log into Sugar.
  • 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. 
  • 83510 : In certain circumstances, PHP warning errors may occur for certain SugarCloud instances.  
  • 83461 : Sugar licenses that are not revalidated after purchasing additional seats or a renewal may result in unexpected behavior with list view filters. As a workaround, re-validate the license via Admin > License Management. 
  • 83328 : Generating reports may result in a database error for Sugar instances using MySQL 5.7 if the ONLY_FULL_GROUP_BY setting is enabled. As a workaround, disable sql_mode=only_full_group_by in the MySQL server configuration.  
  • 83301 : In certain circumstances, the tooltip (e.g. Create) may continue to persist improperly while navigating through Sugar. As a workaround, reloading the web browser will clear the tooltip from the screen. 
  • 83178 : When administrating Sugar Portal, enabling or disabling the "Enable search before opening a case" option does not update the user interface as expected. As a workaround, a Quick Repair and Rebuild must be run for the change to take effect.
  • 83091 : Report chart drill-through may not work as expected and display incorrect data for users in different timezones. 
  • 82970 : Deactivating the default admin user (user id = '1') via the Cloud Settings console may not work as expected and the user's status incorrectly remains "Active" in Sugar.
  • 82914 : Running reports in instances with a large number of team sets may fail to generate for non-admin users and result in performance issues. 
  • 82899 : Peforming a recipient search using an email address does not return any records as expected for SugarBPM's Send Message events. As a workaround, manually enter in the full email address and press "Enter" or use the selection option to choose the recipient.
  • 82840 : Date and datetime fields do not respect the user's preferred format when included on PDFs.
  • 8281381877 : Performing full-text search re-indexes from the command line or via Admin > Search may run out of memory when run on very large data sets.
  • 82810 : Fields based on non-existent or improperly defined custom field types may cause upgrades to fail.
  • 82756 : Upgrades fail when a filter exists for a module that has been removed.  
  • 82693 : When importing contacts mapped to new accounts, users may experience unexpected behavior if the system detects an error on the file. As a workaround, import the new accounts into Sugar first then import the contacts.  
  • 82584 : Custom user fields and stock fields which do not appear in SugarIdentity cannot be imported in Sugar instances using SugarIdentity as the Import Users option is not available. 
  • 82581 : An unexpected error message may appear when attempting to import in a person-type module (e.g. Contacts, Leads) after upgrading to Sugar 9.0.0. Users can close the error message to proceed with the import.    
  • 82559 : Certain customizations in Sugar may cause the upgrade to fail.
  • 82495 : Adding quoted line items to a quote incorrectly sends an assignment notification to the current user who created and is assigned to the record. 
  • 82493 : Users may be unable to send outbound emails if the "Allow users to use this account for outgoing email" option is disabled via Admin > System Email Settings.
  • 82486 : Upgrades may fail when a custom field has conflicting field types defined.
  • 82484 : Attempting to undo an import may not work as expected and fail for modules containing custom fields. 
  • 82468 : Custom decimal fields may prevent upgrades from completing and result in invalid alter queries being generated. As a workaround, use the queries described in the defect's description on the bug portal to convert the decimal fields.
  • 82454 : Entering duplicate email addresses with different capitalizations (e.g., into a record (e.g. Contacts) may result in adverse behaviors. 
  • 82451 : Removing the currency field from the Quotes record view layout may cause an unexpected error when viewing a quote and the Unit Price field to display blank for the quoted line items. 
  • 82437 : Drilling through report charts from the Saved Reports Chart dashlet may not work as expected and return incorrect results if the report has a run-time filter applied.
  • 82384 : Deleting note records created from email attachments may not work as expected and continue to persist in the upload directory. 
  • 82377 : SugarBPM module field evaluations improperly allow the selection of the "changes", "changes to", and "changes from" operators when "All Related Records" is enabled. To avoid unexpected behavior, utilize the "is", "is not", or other non-change operators when evaluating all related records in process criteria.
  • 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. 
  • 82254 : Emails may fail to send as expected if it uses an email template containing an attachment that is already attached to an existing note record. As a workaround, add the code described in the defect's description or delete the existing email template and create a new one with a fresh upload of the file attachment.
  • 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.
  • 82050 : Web logic hooks may not trigger as expected after save when new records are created.  
  • 82038 : Clicking on a Home page tab (e.g. Sales) or attempting to sort by a field column on the Legacy dashboard may not work as expected and result in an error.  
  • 81999 : Users may be unexpectedly logged out when requests with out-of-date user_hash data are sent to the server in close succession.
  • 81929 : Report chart drill-through may not work as expected and display an error message (No data available) for reports using the Product Catalog module.
  • 81722 : Sorting the fields by the column header (e.g. Name) in Admin > Studio or Module Builder may result in CSRF errors being written to the log file.
  • 81382 : Deleting a target list related to a large number of records may fail with an error. 
  • 81339 : Generating a report (e.g. Summation with Details) grouped by "Fiscal Quarter" for a custom date field (e.g. Fiscal Quarter: Booking Date) may result in a database failure error. 
  • 81335 : Importing records in Sugar may fail with a PHP error if the upload directory is not set to the default upload folder in config.php.
  • 81328 : Changes made to custom relate fields that are marked as "Audit" in Admin > Studio do not get recorded in the audit log as expected.
  • 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. 
  • 81276 : When there are multiple group-by fields in a Summation With Details report, generating the report with a chart or trying to view a dashboard containing the saved report chart dashlet may result in performance issues. 
  • 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.
  • 81121 : In certain circumstances, the Gantt chart in the Projects module may display an incorrect year of "1907" for the date range if the date format in the user's profile or system locale settings is set to "MM/DD/YYYY". As a workaround, change the date format in the user's profile or system locale settings to "YYYY-MM-DD", "YYYY/MM/DD", or "YYYY.MM.DD".
  • 81051 : If a calculated Date field is set to null, the value is incorrectly displayed as an invalid date in reports.
  • 81021 : Creating report schedules via duplication copies the related user recipient, preventing users from copying other users' report schedules for themselves.
  • 80968 : It may not be possible to disable SAML authentication via the user interface after certain actions have been performed on your Sugar instance.
  • 80936 : When importing records makes changes to an existing record, the Date Modified field is not updated.
  • 80884 : Viewing a shared dashboard containing the Forecast Bar Chart dashlet may display a "Loading..." message.
  • 80865 : It is not possible to search by the Record Name column in Process Management.
  • 80799 : Upgrading to Sugar 8.0.x may fail if you set the acl_actions table to MyISAM. As a workaround, set the acl_actions table to InnoDB before upgrading. 
  • 80759 : In PDF templates that contain more than one href link, only the first link works.
  • 80730 : Reports without charts are improperly available to select in the Saved Reports Chart dashlet. 
  • 80726 : Dropdown lists created in Module Builder incorrectly allow certain special characters in the item name; modules containing such a list cannot be deployed.
  • 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. 
  • 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.
  • 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.
  • 79752 : When working with SugarBPM process business rules on Internet Explorer 11, you cannot delete columns from rules in the Rules Builder. As a workaround, please use another supported browser.
  • 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. 
  • 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).
  • 79698 : When merging records, fields that are required under certain conditions are required even if the conditions have not been met.
  • 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.
  • 79640 : The Home (Sugar cube) icon shifts position in the navigation bar when "Allow users to select modules to appear in the navigation bar" is enabled.
  • 79510 : Email addresses are not shown on the import summary screen even though they were properly imported.
  • 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.
  • 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 : A SugarBPM process may be prematurely considered complete when part of the process remains unexecuted in job queue.
  • 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.   
  • 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. 
  • 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. 
  • 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.
  • 78128 : For dropdown list values, a value's Display Label will improperly revert to a blank value if its Item Name is 0 (zero).
  • 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.
  • 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.
  • 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.
  • 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.
  • 76401 : The data in the report chart may be inconsistent between the report chart dashlet and the Reports module. 
  • 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.
  • 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.
  • 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"
  • 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.
  • 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
  • 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.
  • 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.
  • 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.  
  • 72581 : Attempting to merge records in modules containing required dependent fields may not work as expected. 
  • 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).
  • 71733 : Printing archived emails via the browser's print option may not display correctly.
  • 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.
  • 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.


Developer Notes for Upgrading From 9.3 (Winter '20)

The following changes in this release may affect developers in version 10.0.0 (Q2 2020) when upgrading from the 9.3 (Winter '20) release:

  • Relate Fields Denormalization : Administrators with very large database tables can optimize their database structure for faster sorting and data load on list view pages.
  • ExpressionEngine REST API endpoint update : Currently, records with many SugarLogic related-value formulas can cause the URI to become too long using GET, causing a 414 error. Therefore, the existing GET endpoint for the ExpressionEngine's related-values API (/ExpressionEngine/:record/related) has been deprecated. It has been replaced with a POST endpoint of the same name. For more information and a sample request, please refer to the Sugar 10.0 (Q2 2020) Customization Guide.
  • REST API : The 10.0 (Q2 2020) Sugar release uses the v11.8 REST API version.
  • Module Loader REST API : The following new REST Endpoints have been added for working with Module Loadable Packages. For complete details on parameters and usage guidelines, please refer to the Sugar 10.0 (Q2 2020) Customization Guide.
    • /Administration/packages/:unFile
    • /Administration/packages/:id/disable/
    • /Administration/packages/:id/enable/
    • /Administration/packages/:file_install/install/
    • /Administration/packages/
    • /Administration/packages/installed/
    • /Administration/packages/staged/
    • /Administration/packages/:id/uninstall/
    • /Administration/packages
  • LessJS theme variables : The following theme-related LessJS variables have been removed in this release. For more information, refer to the Adding Custom Color Variables to a Theme SugarClub post.
    • @moss: #33800d;
    • @stone: #0f7799;
    • @cider: #7e6017;
    • @rose: #ebaaaa;
    • @cream: #fdf8ee;
    • @mint: #18e7d2;
    • @brightBlue: #1202f5;
  • Performance improvement : PHP Classes which extend SugarWidgetEnumField and override the _get_column_select method should now accept an optional $shouldIfNull parameter (bool) in order to avoid a PHP warning.
  • labelsOnTop viewdef has been deprecated : An option has been added to allow users to designate whether field labels in record views will appear beside the field or above the field. This could affect your customized layouts as it is per-user and therefore one user's record view may now differ from another's. Field label placement will be set to "Beside Field Value" by default for all users upon upgrade. This setting overrides labelsOnTop viewdef which is deprecated as of this release.
    • Note: Every user will see their preferred label placement regardless of ANY other settings because there is no code option to set this value. It can only be changed from the User's profile settings. To override this setting globally, a developer would need to create a custom record template using custom CSS to undo the side-label formatting.

Supported Platforms

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

Upgrade Paths

Sugar Serve and Sugar Sell Upgrade Paths
Package From Version(s) MySQL SQLServer
New Installs
9.3.0-to-10.0.0 9.3.0

Last modified: 2021-04-08 22:07:20