Sugar Serve 14.0 (Q2 2024) Release Notes

Fixed Issues When Upgrading From 13.3 (Q1 2024)

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

• 94404, 93369: When Sugar's email settings is configured to use Google mail via OAuth2, emails may fail to send because the refresh token is not returned from Google. 
• 94297: If the Users list view is customized, it may be blank or formatted incorrectly after upgrading to 13.3.
• 94216: When sharing a link to the record (e.g., Accounts) via email, the Cancel, Save Draft, and Send buttons may be misaligned on the Compose Email window.
• 94193: When activities in a Smart Guide contain sub-activities, the assigned user's avatar image does not display as expected for the sub-activities.
• 94059: Geocoding a record (e.g., Meeting) containing calculated address fields that pull address data from the related record (e.g., Accounts) may not work as expected. 
• 94037: For instances that do not use SugarIdentity, enabling the LDAP or SAML authentication in Admin > Password Management does not expose the "LDAP Authentication Only" or the "SAML Authentication Only" checkbox option in the Advanced tab of the user's record. 
• 94036: For Sugar versions 13.3.0 and higher using PHP 8.2, creating a one to many relationship between a custom module and another module (e.g., Accounts) does not display a subpanel for the related module in the custom module's record view as expected.
• 93960: Quotes downloaded as PDFs may not be formatted correctly for Sugar versions 13.3.0 and higher. 
• 93957: Clicking an Action Button to open a URL may result in a 500 error if the record contains a calculated field containing a related() function.
• 93954: In certain circumstances, creating a recurring meeting or call may result in a 500 error.
• 93894: In certain circumstances, multiple fatal errors may get logged in the sugarcrm.log file when accessing legacy modules (e.g., Users, Teams, Schedulers) in Sugar.
• 93849: When the Smart Guide Points field value has been changed for a task in the Smart Guide, the Scoring field value in the parent Smart Guide stage does not reflect the correct total until the stage is saved.   
• 93846: When fetching records via the Filter API, the next_offset and the number of records may not be accurate.
• 93843, 93803: Users assigned a role with Admin & Dev access to the Users/Teams/Roles module are improperly restricted from viewing data in the Users modules and see an error.
• 93756: In certain circumstances, users may experience unexpected behavior when accessing certain views (e.g., Audit Log, Historical Summary, Search and Select drawer) in Sugar.
• 93751: When executing a process, the process' record view may not properly display the record (e.g., Opportunities) if that module's record view layout is displayed using tabs.
• 93665: The Smart guide due date calculation does not work as expected when the minus (-) sign is used in the Due Days value to subtract the number of days from the Due Date field.
• 93653: When paginating between pages of results on a module's list view, clicking the Refresh button may cause unexpected issues. 
• 93543: When a report is generated as a PDF, any line breaks in TextArea fields may get removed improperly. 
• 93444: In certain circumstances, customers may encounter PHP fatal errors in Sugar when using PHP 8.2. 
• 93372: When logged in to Sugar with the French language, the Distribution Method field label is translated incorrectly in Admin > Inbound Email.
• 93237: In certain circumstances, filtering the report using a date field (e.g., Date Created) that is using the YYYY-MM-DD format may return no results in the report.
• 93160: The quote's grand total amount does not get calculated correctly when a quoted line item is removed from the quote.
• 93115: When logged in to Sugar with the Chinese language, the Define Calendar Day dialog box in the Calendar module may display incorrect translations. 
• 93021: When Action Buttons are used to create a new record and the target module (e.g., Opportunities) contains a conditionally required field, the required field may appear blank even if it was configured to have a default value. 
• 93003: Modifying an email template may cause the content in the Body field to be deleted.   
• 92964: Fetching comment log entries using the RelateAPI may return empty results even if there are entries.
• 92911: Sugar does not support the French Canadian language for Pendo Guide messages and displays the message in English.
• 92790: When logged in to Sugar with the French language, the run-time filter text string that appears when adding a new filter in the Dashboard Filters panel is translated incorrectly.
• 92765: When creating a Data Archiver job, filtering by the date field (e.g., Date Created) using the "More than _ days ago", "Last_days", "Next_days" or "More than_days in the future" incorrectly shows a date field to populate instead of an integer field.
• 92759: When a dashlet (e.g., Opportunity dashlet) in the Focus Drawer is filtered to only display records related to the current record, the applied filter does not get preserved as expected when the page is refreshed.   
• 92571: Sugar Automate continues to remain enabled in Sugar even though the Sugar Automate license has been removed from the user.
• 92133: When the Cases module's record view layout is customized in Studio using the dropdown-field-based views, the portal may use this layout instead of using the portal record view layout for cases.
• 91301: When editing the Currency field on a module's record view, the names of the available currencies are cut off in the dropdown list and does not display the full name.
• 91128: Drilling through a report chart of opportunities grouped by their fiscal quarter expected close date may use the default fiscal year instead of the time period defined in the forecast configuration.
• 90470: When a Customer Journey Template is copied and there are tasks, meetings, or calls using the Assignee Rule set to "Specific Activity Completed", the duplicated template will use the original template's Assignee Rule Activity, which causes the assignment rule to fail.
• 89727: The SugarBPM process sends all emails using the system email account's email address instead of the email address of the user specified in the Send Message event.  
• 89432: If a custom text field in the module has a display label with a large number of characters (e.g., 800), no tooltip appears when you hover over the field.
• 89194: Users are improperly allowed to edit calculated fields in Focus Drawers. 
• 87908: For instances that use SugarIdentity, the Reset Multi-Factor Auth option improperly appears during a user impersonation session.
• 87346: When generating a quote from an opportunity's Revenue Line Items subpanel, attempting to edit the line item in the Quotes record view does not work as the fields (e.g., Quantity) are read-only. 
• 86790: When creating a Process Email Template and using the Fields Selector tool, the First Name and Last Name fields are not available to select for the related Users module's fields.
• 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. 
• 80970: When the Start event criteria for a process definition is set to evaluate that an Integer field is not null, a value of "0" in the field will incorrectly evaluate as a null value and cause the process to not trigger.
• 80488: Resetting the list view filter for a date field (e.g., Date Created) does not work as expected. 
• 78153: The Default Value setting is available to configure for the Calls/Meetings Email Reminder Time and Popup Reminder Time fields in Studio even though the default is determined by the user in their User Preferences. 

Sugar Serve and Sugar Sell Upgrade Paths

The following upgrade paths apply to Sugar Serve and Sugar Sell Premier, Advanced, and Essentials: