Sugar Enterprise 13.0 (Q2 2023) Release Notes

Feature Enhancements When Upgrading From 12.0.x (Q2 2022)

The following feature enhancements are new in Sugar Enterprise On-Site 13.0.0 (Q2 2023) when upgrading from the 12.0.x (Q2 2022) release:

Fixed Issues When Upgrading From 12.0.x (Q2 2022)

The following issues are newly resolved in version 13.0.0 (Q2 2023) when upgrading from the 12.0.x (Q2 2022) release. Case portal users can use the following links for more details about each issue:

• 91558: Creating a case record may fail to save with an error if the Cases module contians a calculated field using the related() function.
• 91488: Uploading packages via Admin > Module Loader may fail with an error.  
• 91456: Line charts in reports incorrectly display the date values (e.g., start date in months) in alphabetical order instead of in chronological order. 
• 91452: The subject of the calendar event may not display correctly when viewing the calendar in Sugar.
• 91427: The Geocoder Resolver scheduler may timeout and fail to geocode the queued account records if there are customizations (e.g., calculated fields, process definitions, custom logic hooks) applied to the records. 
• 91414: Empty addresses are not validated on records and improperly get geocoded.  
• 91363: Not all Sugar Automate-related packages get uninstalled automatically on upgrade to 12.3, causing record views to fail to load in Sugar.
• 91320: When configuring the Record View dashlet tabs in the Focus Drawer, the tab label may be translated incorrectly when logged into Sugar with the German language. 
• 91307: Sugar login fails with an error for Admin users with an invalid license type.
• 91297: Process email templates that insert values from a related record may fail to process all subsequent variables after encountering a variable that targets an empty relationship. 
• 91223: In certain circumstances, performance issues may occur in the Revenue Line Items module resulting in a 500 error.
• 91201: As you scroll in the Sugar Hint panel, the dashlets may disappear from view behind the Sugar Hint header on top.  
• 91182: In certain circumstances, email alerts for legacy workflows may have formatting issues and render the email content incorrectly. 
• 91071: The Export PDF option for reports is available to select for users who do not have permission to access the report.  
• 91060: Attempting to import contacts from Google may not work as expected due to field mapping issues. 
• 91052: When using Sugar version 12.0 and higher with PHP 8.0, a PHP fatal error may occur when a SugarBPM process is triggered.
• 91045: In certain circumstances, customers running Sugar on-site may be required to manually revalidate their license every few days.
• 91028, 90597: Calculated fields set as required behave incorrectly in Smart Guides.
• 91008: Users assigned a role with Export permission set to "None" for a module (e.g., Contacts) are not prevented from exporting the module data from reports.
• 90993: In certain circumstances, users may not see the standard layout as expected in a record (e.g., accounts), and the modules' customized dropdown-field-based record view layout may display instead.
• 90912: In certain circumstances, the resolve conflict error may improperly appear when editing account, contact, or lead records.   
• 90884: Clicking an external hyperlink in the Knowledge Base article may not open the link in a new tab as expected. 
• 90869: In certain circumstances, reports with more than one filter group may fail to run and display a permission error.   
• 90853: For Sugar instances using Sugar Maps, enabling the Distance field for search in Admin > Studio does not work as expected.
• 90851: Certain dashboards may break after upgrading to 12.2 depending on how they are stored in the database. 
• 90816: After upgrade, attempting to access the Admin > System Settings page fails to load with an error when logged into Sugar with the English US or English UK language.
• 90769: Reassigning users' records in Sugar may not work as expected and result in an error when using Sugar with PHP 8.0. 
• 90752: The primary admin user (ID = 1) is required to be assigned to the Sugar Maps license in order for the "Geocoder Resolver" and "Geocoder Maps" schedulers to work even though the organization has the Sugar Maps license.
• 90727: Generating a summation-type report for a module with a large number of records may fail to render any data and result in an error.
• 90710: Legacy modules (e.g., Users, Campaigns, Schedulers) fail to load with an error when runnning Sugar using MySQL 8.0.31
• 90697: The axis label on bar charts may be incorrect for Summation With Details reports containing more than one display summaries (e.g., AVG: likely, MIN: likely).  
• 90657: Invalid MIME Type errors may get logged in Sugar when creating Summation-type reports.  
• 90640: If an instance has a large number of purchases or purchased line items, deleting an account with relationships to one or both of those modules can have performance issues.
• 90602: When a report has multiple run-time filters for the same field (e.g., Accounts name), changing the filter value (e.g., ABC Company) in the report's Filters panel may not return the correct results.  
• 90595: Changing the filter value for a run-time filter using the "Is Between" operator may not return the correct set of data in the results. 
• 90572: Reports containing a "Is Between" run-time filter for a DateTime field may not properly respect the system date format setting and result in an error when running the filter.  
• 90555, 90554: For instances using Cloud Drive, the Cloud Drive dashlet may not display folders in Microsoft OneDrive as expected. 
• 90547: In certain circumstances, changing the list view filters may result in unexpected performance issues. 
• 90538: When a field column is sorted on a generated report, it does not preserve the change as expected and the data is no longer sorted when acessing the report later.
• 90495: In certain circumstances, a PHP fatal error may occur when using Sugar with PHP 8.0.  
• 90474: After upgrade, certain modules may be missing in Sugar due to some unexpected issues in the database. 
• 90463: If the report contains three or more group-by fields, the report result may show incorrect data. 
• 90437: Chart sorting on the Report Dashlet does not work as expected for charts in reports with multiple group-by fields (e.g., matrix-type reports) or for charts sorted on a function value (e.g., SUM: Likely).
• 90433: When a user is assigned a role restricting their ability to edit a report, any layout changes they make to the report's results view does not get preserved and reverts back to the previous layout when they leave the report or refresh the browser.
• 90414: The bar graph in reports incorrectly display a total percentage value of 100% instead of the actual total percentage.
• 90407: The Accessed On field for reports does not update as expected to reflect the date that the report record was last accessed.  
• 90402: When logged in to Sugar with non-english languages (e.g., German, Spanish), the report chart labels may incorrectly display "undefined" in report results and dashlets.
• 90396: Attempting to remove a previously unlinked user from a team may not work as expected and fail.
• 90379: Changes made to the user's time zone in Sugar may not be respected properly in reports and display the time values incorrectly in the report results.
• 90366: Long field values in reports do not wrap around or truncate in the field column, but instead overlaps to the next field on the right. 
• 90360: The link to the Sugar record (e.g., opportunity name) does not display as a hyperlink in reports if there is a custom date field preceding the record name field in the display columns.  
• 90357: Adding a relate field to a report incorrectly builds the link to the record using the wrong module causing the record link and focus drawer to break. 
• 90351: Line charts in reports incorrectly display the date values (e.g., start date in months) in alphabetical order instead of in chronological order. 
• 90349: Funnel charts may appear very large in reports and dashlets and require scrolling to view the full chart.
• 90348, 90345: When using Sugar version 12.0 and higher with PHP 8.0, unexpected errors may occur when referencing specific records in the activity stream or opening a custom dropdown field in a module's record view.
• 90347: Non-admin users that are not assigned to a report may be unable to modify certain runtime filters. 
• 90337: When the display label (e.g., Test) on a dropdown list matches the name of a dropdown field (e.g., Test) added to the report filter, the corresponding dropdown option displays "Array" instead of the correct display label (e.g., Test).  
• 90325: Reports containing multiple run-time filters for the same field (e.g., Date Created) may not preserve the run-time filter value as expected when the browser is refreshed or the user navigates away from the page. 
• 90320: Special characters display incorrectly for record names on exported CSV files even though the import/export character set is set as "UTF-8".
• 90318: Summations and Summation with Details reports containing no group-by fields display no results and show the "No data available" message. 
• 90303: User names do not appear as clickable hyperlinks in reports for version 12.1.0.  
• 90289: In certain circumstances, Doc Merge may fail to generate documents and result in an error.
• 90257: The Filters panel in reports does not properly respect the user's preferred date format and shows the date using the YYYY-MM-DD format.
• 90244, 90209, 89965: Performing certain actions (e.g., editing custom dropdown fields, importing) in Sugar may result in a PHP fatal error when running Sugar using PHP 8.0.  
• 90235: Modifying a note record in the Notes list view via mass update, inline edit, etc. may improperly cause any attachments to be deleted. 
• 90231: When certain SugarBPM processes run, it may cause unexpected performance issues in Sugar.
• 90192: The report's Advanced Filters drawer does not correctly display all the filters applied to the report.
• 90178: Exporting reports may not work as expected and display an error if the report is sorted by a display column field (e.g., Last Name). 
• 90173: The display label for a dropdown list item containing a forward slash may not display correctly when editing the corresponding dropdown list and unexpected issues may occur when drilling through report charts with this dropdown value. 
• 90165: Grouping a Summation-type report by week may not display the data as expected in the report results. 
• 90128: Actions Buttons do not work as expected with any activity-type modules (e.g., Meetings) that have been renamed in Sugar.
• 90093: Exporting reports does not respect changes made to run-time filters and incorrectly displays data with the original run-time filter.
• 90074: Report charts may be sorted incorrectly in certain circumstances.  
• 90000: Attempting to reduce the height of a resized dashlet may not work as expected and break the dashlet.  
• 89985: In certain circumstances, uploading and installing a custom package in Module Loader may result in an error. 
• 89979: Revalidating the license key does not work as expected and result in an error for Sugar instances configured to work with a proxy server.
• 89944: SugarBPM Receive Message events that wait for a specific state in an activity-type module record (e.g., meeting, note) are not triggered as expected.
• 89932: If a SugarBPM process creates multiple related records, any subsequent relationship change processes will only be triggered for the first related record.
• 89923: Downloading merged record data as PDF documents using Doc Merge fails with an error if the record contains an ampersand character. 
• 89915: Clicking the Dropbox file name in the Cloud Drive dashlet does not display the preview of the file and opens a blank page instead.  
• 89894: Emails fail to send when the SMTP timelimit is set to 2 seconds.  
• 89821: In certain circumstances, editing and saving a record containing a large number of fields in the layout may fail to save with an error.
• 89660: Using the Action Button to automatically create a call related to the current record may fail with an error when the calculated Start Date uses the now() function. 
• 89642: Attempting to schedule advanced reports for email delivery does not work as expected. 
• 89623: The Pending Processing field is incorrectly set to "true" on cases when outbound emails related to the case record are sent. 
• 89587: When performing a quick repair and rebuild, executing a mismatched query improperly returns you to the Admin page without executing the queries.
• 89551: Attempting to download the Sugar Plug-in for Outlook from the Downloads tab in user preferences results in an error.
• 89483: When a report is grouped by a multi-select field, drilling through the report chart results in a 500 error.  
• 89465: During upgrades, the health check may not pass as expected for certain custom modules.   
• 89445: Removing a user as a guest from a meeting does not remove the meeting from the user's calendar as expected. 
• 89441: The option to delete an activity is incorrectly hidden in the Smart Guide template editor when disabled via the Disabled Activity Actions field.
• 89368: Multiple SugarBPM processes triggered by a single action in Sugar (e.g., field update) may cause events to be executed more than once. 
• 89328: Filtered subpanels in the modules' record view (e.g., Cases) cannot be reverted to show all related record subpanels as expected.
• 89308: When logged in to Sugar with the Spanish language, certain labels in the Calendar module are not translated to the default language.  
• 89300: When logged in to Sugar with the French or Spanish language, renaming a module improperly causes the accent marks to be removed from the module names. 
• 89290: Users assigned a role with the "Admin & Developer" access cannot access the Administration page as expected. 
• 89269: Scheduling Summation With Details reports to be delivered as both a PDF and CSV file causes the scheduled report to become disabled. 
• 89259: The More option does not appear in the Case Timeline dashlet as expected to allow users to expand and see the full content.
• 89243: Users may improperly receive assignment notification emails for the MobileDevices module when the mobile app's push notification is enabled.
• 89241: Process Definitions with an action to start a Smart Guide fail to start additional Smart Guides after the first trigger.
• 89227: When an instance is configured to use Opportunities with Revenue Line Items and a user is assigned a role restricting access to the Forecasts module, the user will be prevented from creating opportunities or converting leads in Sugar.
• 89170: In certain circumstances, changes to user roles may not get applied until a Quick Repair & Rebuild is performed in Sugar. 
• 89167: In certain circumstances, duplicate numbers may improperly appear in the X and Y-axis of the report chart.
• 89121: Using dropdown-conditional record view layouts may cause calculated fields to break in the record.
• 89114: Funnel charts may not display properly when viewed in reports and dashlets.  
• 89084: In certain circumstances, scheduled reports may unexpectedly become deactivated.
• 89048: The Calendar module does not properly respect the Date format and Time format in the user's locale settings.
• 89045: In certain circumstances, cases may not be created from inbound emails as expected if the Cases module contains a custom logic hook.
• 89024: In certain circumstances, adding custom text fields to the Users module's edit and detail view layouts incorrectly displays the user's last name in the field. 
• 88989: Using a calculated field in a related or rollup function causes the calculation to be performed, and thus the record to be saved, even if no changes were made to the relevant field during the record save.
• 88986: Merged documents created via Doc Merge do not appear in the record's related subpanels (e.g., Documents) for custom modules.   
• 88911: Calendars added to the User and Team calendar may not appear as expected in the users' calendar view.   
• 88869: Mass record creation causes SugarBPM processes to overload and return errors resulting in missing processes.
• 88798: Creating reports using the "After" date range filter for Date fields may generate the report data incorrectly.   
• 88770: Holidays related to business centers are not respected properly causing incorrect Follow Up Dates to be calculated. 
• 88755: The role-based dropdown list improperly prevents a user from viewing a dropdown value that is restricted from their role even though the value was already selected for the record they are viewing. 
• 88746: Dependent fields that are created with dependency and required formulas containing the not() function may not work as expected and improperly display as a required field.
• 88736: Uploading a new language pack via Admin > Module Loader does not display the package in the Uploaded Packages panel to install.
• 88725: The README text when installing a package Module Loder is difficult to read.
• 88720: When two users modify the same quote record and save, the second record save overwrites the first change instead of displaying the conflict resolution screen.
• 88714: When creating a process definition, trying to select the Assigned To user for the related module (e.g., Contacts) from the Module Field Evaluation panel incorrectly opens the Search and Select drawer displaying a list of process definitions instead of users to choose from.
• 88706: Archiving emails via the Sugar Email Archiving service improperly creates a new blank case for emails that include the case macro (e.g., [CASE:1234]) in the subject line. 
• 88699: The "Relate to current record" option may not be available and/or functional in the List View dashlet depending on where (e.g., List View > Focus Drawer, Record View > Focus Drawer) the dashlet gets added.  
• 88695: The Advanced Search functionaity in the Users module is broken and does not work as expected.   
• 88641: Attempting to filter reports using the Service End Date field for the Revenue Line Items or Purchase Line Items modules does not work due to missing filter options.
• 88624: Creating notes with attachments in the Sugar Portal may fail and result in an error if the default value for the "Display in Portal?" field is set to "false" for the Notes Modules.
• 88600: Using "email1" in a related() formula does not return the email address as expected in the calculated field. 
• 88550: In certain circumstances, having calculated fields based on the Project Tasks module may cause 500 errors in Sugar.  
• 88532: When sending emails using an email template containing an attachment, the attachment does not get included in the email as expected.
• 88500: Attempting to copy a customized role-based record view layout in Admin > Studio may not work as expected and result in an error. 
• 88450: Calculated date fields containing a maxRelatedDate() function may incorrectly show the current date even though the field should be blank.
• 88370: When creating a Process Definition, adding a Gateway element for the Users module's "Reports to" field may not work as expected. 
• 88358: Installing packages via Module Loader may fail with a PHP fatal error.  
• 88241: When logged into Sugar using a non-English language, the meeting invitations sent to guests do not contain the meeting details and appear blank.   
• 88229: Triggering a SugarBPM Relationship Change event when creating a new record and relating it to another record may cause a 500 error that prevents the process from advancing.
• 88228: SugarBPM processes that have been deleted or disabled may still execute in certain circumstances. 
• 88206: In certain circumstances, installing packages in Module Loader may not work as expected and the package may get uninstalled with errors. 
• 88191: Active Subscriptions and Purchase History dashlets may behave differently in Record View dashboards and in the Renewals console.
• 88188: Drilling through report charts may not work as expected for Summation-type reports filtered or grouped a certain way.
• 88031: When importing leads to Sugar, the View Import Results step of the import wizard does not display the list of lead records that were created even though the import is complete. 
• 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.
• 87870: AutoIncrement fields are not available to define as a search filter in Admin > Studio. 
• 87854: When performing an import using a CSV file with duplicate "sync_key" entries, the import result provides misleading information.
• 87739: When runnning Sugar using MySQL version 8.0.19 and higher, performing a quick repair and rebuild after creating a new Integer field with Max Size value greater than 11 may result in a database vardef mismatch.
• 87539: Sugar fails to import inbound emails that only contain recipients in the BCC field and in turn fails to import all subsequent emails in the same batch. 
• 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. 
• 87349: When adding an Add Related Record action to the process definition, if the target module has fields that are conditionally required, the setting may be prevented from saving due to incorrect field validation.
• 87318: In certain circumstances, web logic hooks may not pass the same arguments as standard logic hooks.
• 87306: The Date Installed column in Module Loader incorrectly displays the published date instead of the actual date the package was installed.
• 87141: Hard deleting document records via Data Archiver does not remove the document revision records from the database. 
• 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. 
• 86740: Dependent fields do not display the data as expected in certain views such as the modules' list view and Record View dashlet.  
• 86663: Adding more than one Product Catalog dashlet on the dashboard may cause one of the dashlets to break and not work as expected.
• 86185, 78851: In certain circumstances, the sequence connector lines connecting the elements of a process flow may be missing in the process definition's design view.
• 85880: Users cannot authorize their default outgoing email account when the "Allow users to use this account for outgoing email" option is disabled in Admin > Email Settings.
• 85751: The errors related to SugarBPM in the Sugar log file incorrectly reference "Process Management" in the error message instead of "SugarBPM".
• 85673: Installing a custom module that was built and exported from Module Builder may fail to install with an error in Module Loader.
• 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. 
• 85320: In certain circumstances, the SugarBPM process approval form may not display values as expected for certain calculated fields.  
• 85158: When a Datetime field is contained within a tab in the module's record view (e.g., Contacts) layout, the date picker may not display properly in the view making it hard to select the date value. 
• 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). 
• 84691: Uninstalling a package containing relationships in Admin > Module Loader causes invalid modules to become available for Sugar Portal.
• 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. 
• 84464: SugarBPM processes with a Parallel gateway are not triggered multiple times for the same record.
• 83880: Changes made to role-based view layouts are not applied to users assigned to the role.  
• 83716: In certain circumstances, attempting to deploy a package via Module Builder or Module Loader may fail with an error.  
• 83652: Setting the "1000s separator" field with an empty separator does not get respected properly for Integer and Decimal type fields.    
• 83574: Editing contact records containing a duplicate portal name may result in a number of unexpected errors when saving the record. 
• 83236: In certain circumstances, ordering the quoted line items does not preserve the new order as expected.
• 83097: Triggering a web logic hook generates different sets of data between the admin user and regular user who triggered it.  
• 82757: Variables for relate fields in process email templates do not get populated with a value in SugarBPM emails.
• 82657: Process definitions with an Add Related Record action to create a record in a two-away module related to the target module (e.g., Calls, Meetings) results in an error when validated. 
• 82372: For inbound emails sent from certain email providers (e.g., Outlook), extra spaces may incorrectly display in the body of the email message when viewing or replying to the email in Sugar.
• 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.
• 81235: Drilling through report charts may not work as expected for reports containing dropdown fields that have multiple dropdown options using the same display label.  
• 81029: When logged into Sugar using a non-English language (e.g., Portuguese), configuring an Action element in a process definition using the Run Time option fails to save with an error.
• 80759: In PDF templates that contain more than one href link, only the first link works.
• 80681: Making changes to a report's relationship-based filters may result in an error when running the report.
• 80629: Decimal fields with a NULL value in the database incorrectly display 0.00 instead of an empty value when included in reports.  
• 80624: Report charts may not display correctly in chronological order when the report is grouped by date fields (e.g., Date: Start Date) using the Year, Month, and Day format in Sugar.
• 80478: SugarBPM processes may fail to send email notifications as expected to group users.
• 80448: Deleting a note with an attachment via the import process does not delete the file attachment in the Uploads directory. 
• 80420: The Account Name field is not sortable in the Quotes list view.
• 80379: SugarBPM processes may improperly send multiple assignment notifications to users when records are reassigned to them. 
• 79930: The Forecast view breaks and does not load as expected when there are any users that have an @ symbol in their username. 
• 78392: Filtering reports using two DateTime fields may cause unexpected issues for the second DateTime field run-time filter.
• 78302, 77738: Merging records (e.g., Accounts) containing a large number of related records (e.g., Cases) may result in unexpected behaviors/errors.
• 78121: When required calculated fields are left blank, the field does not get highlighted in red upon saving the record to indicate that the field has an error.  
• 76484: The Recalculate Values option does not appear in the Meetings list view's Mass Actions menu even though the module contains calculated fields. 
• 75461: The domain entered in the "No Auto-Reply to this Domain" field for group mail accounts improperly receive auto-replies even though it should be excluded from receiving automatic email responses.
• 74635: A Summation report that displays the SUM of decimal fields incorrectly rounds the total on the chart to a whole number instead of displaying numbers with decimal places.

Sugar Enterprise Upgrade Paths

The following upgrade paths apply to Sugar Enterprise: