Data Privacy Enhancements

New features to support data privacy practices, including adherence to the EU’s GDPR, have been added in this release as follows:

• Data Privacy module : The new Data Privacy module allows users to record and track data privacy requests (e.g. data subject request to be forgotten) and events (e.g. gaining consent from the data subject).
• Data Privacy Manager role : A new out-of-the-box role provides regular users the ability to close data privacy records and permanently erase personal information.
• Personal information fields : Fields can now be designated as personally identifying information which enables them to be permanently erased and included in the record’s View Personal Info option.
• Permanent erasure : Users in the Data Privacy Manager role now have the ability to immediately and permanently erase personal information fields from their Sugar database via an erasure request in the Data Privacy module.
• View Personal Info screen : The new View Personal Info option displays the record’s personal information fields along with the current field value, source of the value, and date the value was set.
• Consent tracking : The gaining or loss of consent can be tracked via the Data Privacy module. Users can record the business purposes to which an individual has consented in the new Business Purposes Consented For field on person-type modules (e.g contacts).
• Email opt-out default : Using the new option available via Admin > System Email Settings, admins can configure whether new email addresses added to Sugar records default to opted-in or opted-out.
• Opt-in via web-to-lead forms : An opt-in checkbox now gets added to web-to-lead forms containing email address fields to allow visitors to explicitly indicate that they wish to receive marketing emails.
• Disabling activity streams : Admins now have the ability to stop activity streams from displaying or storing new entries via Admin > System Settings.
• Record change log enhancements : Sugar’s change log is now called “Audit Log” and includes the following improvements:
  • Logging from creation : Audit logs now capture the setting of fields starting at record creation.
  • Source column : Audit log now captures the source (e.g. Sugar user, Web to Lead) from which each field change originated.
  • Email address audit log : Email addresses now have a separate audit log which records when the address is marked as opted-out or invalid.
  • Audit Log for the Targets module : Users can now view a history of changes to audited fields for target records.
  • Audit log header enhancement : The audit log header now displays the name of the current record to better identify which record’s audit log you are viewing.

Additional Enhancements

Enhancements to other areas of the application have been made as follows:

• Product Catalog dashlet enhancements : The following improvements have been made for the Product Catalog dashlet:
  • Product Catalog dashlet available in other views : The Product Catalog dashlet can now be added to other Sidecar modules, as well as the home page, and will be read-only.
  • Usability improvements : For a better user experience, enhancements have been made to the dashlet including the addition of a scroll bar (for Chrome), a cursor that changes when hovering over actionable elements, and an updated font style to match Sugar’s new look.
• Saved Reports Chart dashlet enhancement : The Select a Report field now allows users to search and select their desired report when adding/editing the Saved Reports Chart dashlet.
• Configure API Platforms user interface : Administrators now have the ability to add or remove custom API platform identifiers via Admin > Configure API Platforms.

Data Privacy Enhancements

New features to support data privacy practices, including adherence to the EU’s GDPR, have been added in this release as follows:

• Data Privacy module : The new Data Privacy module allows users to record and track data privacy requests (e.g. data subject request to be forgotten) and events (e.g. gaining consent from the data subject).
• Data Privacy Manager role : A new out-of-the-box role provides regular users the ability to close data privacy records and permanently erase personal information.
• Personal information fields : Fields can now be designated as personally identifying information which enables them to be permanently erased and included in the record’s View Personal Info option.
• Permanent erasure : Users in the Data Privacy Manager role now have the ability to immediately and permanently erase personal information fields from their Sugar database via an erasure request in the Data Privacy module.
• View Personal Info screen :The new View Personal Info option displays the record’s personal information fields along with the current field value, source of the value, and date the value was set.
• Consent tracking : The gaining or loss of consent can be tracked via the Data Privacy module. Users can record the business purposes to which an individual has consented in the new Business Purposes Consented For field on person-type modules (e.g contacts).
• Email opt-out default : Using the new option available via Admin > System Email Settings, admins can configure whether new email addresses added to Sugar records default to opted-in or opted-out.
• Opt-in via web-to-lead forms : An opt-in checkbox now gets added to web-to-lead forms containing email address fields to allow visitors to explicitly indicate that they wish to receive marketing emails.
• Disabling activity streams : Admins now have the ability to stop activity streams from displaying or storing new entries via Admin > System Settings.
• Record change log enhancements : Sugar’s change log is now called “Audit Log” and includes the following improvements:
  • Logging from creation : Audit logs now capture the setting of fields starting at record creation.
  • Source column : Audit log now captures the source (e.g. Sugar user, Web to Lead) from which each field change originated.
  • Email address audit log : Email addresses now have a separate audit log which records when the address is marked as opted-out or invalid.
  • Audit Log for the Targets module : Users can now view a history of changes to audited fields for target records.
  • Audit log header enhancement : The audit log header now displays the name of the current record to better identify which record’s audit log you are viewing.

Additional Enhancements

Enhancements to other areas of the application have been made as follows:

• New look and feel : Updated colors and shapes appear throughout Sugar’s Sidecar user interface.
• Preview user interface : Record previews in the intelligence pane have a more usable layout and updated look and feel.
• Emails user interface : The Emails module now uses the Sidecar interface. It has been redesigned to store copies of email messages sent from Sugar or archived via one of the various email archiving options. Users can view and work with email records much like they view and work with records in other Sidecar modules.
• Outgoing email accounts : Users can configure multiple SMTP accounts to send email from Sugar.
• Unlink emails : Explicitly related emails can be unlinked from the Emails subpanel of related records.
• Drill-through report charts : Users can now click on a segment of a report’s chart from the Reports module or Saved Reports Chart dashlet to view a filtered list view of records belonging to that segment and perform various actions (e.g. edit, mass update, refresh).
• Sharable dashboards : Dashboards can now be shared with teams of users, pulled into their views by users, and pushed to teams of users by system admin users.
• Copying quote records : Users can create quote records via duplication. The original quote’s line items, groups, comments, and related account and opportunity data will carry over to the new quote.
• Product Catalog dashlet : The Product Catalog dashlet is now available to access from the following views:
  • Product Catalog dashlet for building quotes : Easily find and add products directly from the Product Catalog dashlet as you create and edit quote records.
  • Product Catalog dashlet in other views : The Product Catalog dashlet can be added to other Sidecar modules, as well as the home page, and will be read-only.
• Saved Reports Chart dashlet enhancement : The following improvements have been implemented for the Saved Reports Chart dashlet:
  • Search and select reports : The Select a Report field now allows users to search and select their desired report when adding/editing the Saved Reports Chart dashlet.
  • View Report option : The View Report option has been added to the Saved Reports Chart dashlet allowing users to access the originating report’s detail view.
• Contracts user interface : The Contracts module now uses the Sidecar user interface.
• Contract Types user interface : The Contract Types module now uses the Sidecar user interface.
• Currencies user interface : The Currencies module now uses the Sidecar user interface.
• Products- and Quotes-related modules user interface : The Manufacturers, Shipping Providers, and Tax Rates modules now use the Sidecar user interface.
• Configure API Platforms user interface : Administrators now have the ability to add or remove custom API platform identifiers via Admin > Configure API Platforms.
• SAML configuration enhancement : Additional configuration options have been added for configuring SSO using SAML.
• Teams filter : Multiple team selection is now supported when filtering based on the Teams field in Sidecar modules.
• Elasticsearch 5.4 support : Elasticsearch version 5.4 is now supported.

• 80579 : Logic hooks with class and function names matching in text, but not in case sensitivity, result in PHP fatal errors.
• 80489 : If Sugar’s notification delay is set to exceed the limit of 35791 minutes, it may cause unexpected errors in the system.
• 80237 : When sending emails from a custom module’s Emails subpanel, the related email record may not appear in the Emails subpanel as expected.
• 80160 : Users are prevented from sending transactional email messages via the Emails module to recipients who have opted out from marketing campaigns.
• 80113 : Filtering the Knowledge Base module using the Body field may cause a 500 error to occur.
• 79807 : When viewing knowledge base article attachments via the Notes module, the Related To field may display the incorrect label name (KBContentsAttachments) for the Knowledge Base module and not include the related knowledge base record.
• 79717 : The View Change Log option is not available in the Contracts record view actions menu.
• 79705 : Report charts do not respect user preferences for number formatting, currency symbol, or date and time formatting.
• 79486 : Attempting to edit the Shipping field for existing quote records may not work as expected if the record contains a calculated or dependent field.
• 79268 : Modules (e.g. Task) that have a custom relationship with the Activities module may not display email records as expected when emails are sent via the Emails subpanel.
• 79254 : An unexpected error may display while installing Sugar on a Windows server on PHP 7.1.
• 78808 : Downloading PDF templates containing ampersands may not work as expected and result in a 500 error.
• 78714 : Emailing a meeting record as a PDF file via the Email PDF option may improperly remove the meeting’s relationship to the related account record.
• 78568 : Calculated fields containing the countConditional(), rollupConditionalSum(), or rollupSum() functions may improperly update and display incorrect values each time additional records are loaded in the related module subpanels.
• 78532 : In certain circumstances, the record’s creation date may improperly default to 01/01/1970.
• 78496 : Report chart values may not render correctly for Integer fields when using a period as the 1000s separator and a comma as the Decimal Symbol in the user’s profile.
• 77764 : Attempting to scroll in Legacy modules (e.g. Campaigns) may not work as expected when logged into Sugar on iPad.
• 73026 : Workflow alert templates containing new and old value variables (e.g. {::future::Contacts::do_not_call::}, {::past::Contacts::do_not_call::}) for checkbox fields may not display the correct field values as expected in the email notification.

• 80579 : Logic hooks with class and function names matching in text, but not in case sensitivity, result in PHP fatal errors.
• 80489 : If Sugar’s notification delay is set to exceed the limit of 35791 minutes, it may cause unexpected errors in the system.
• 80237 : When sending emails from a custom module’s Emails subpanel, the related email record may not appear in the Emails subpanel as expected.
• 80160 : Users are prevented from sending transactional email messages via the Emails module to recipients who have opted out from marketing campaigns.
• 80124 : Attempting to log into Sugar may fail with an error for instances using LDAP if the LDAP configuration (e.g. password) contains any HTML special characters (e.g. <>, &).
• 80116 : An error in the language file may cause MySQL errors.
• 80113 : Filtering the Knowledge Base module using the Body field may cause a 500 error to occur.
• 80099 : The RT GSync integration version 3.7 and higher may not pass the health check as expected.
• 80056 : When creating a workflow action to create a record in a module associated with the target module (Leads), “Calls” may not be available to select from the modules dropdown list.
• 79972 : Comments added to a group on the quote worksheet may improperly sort to the bottom of the worksheet after save.
• 79969 : Changes made to a comment may not preserve as expected when adding another comment in edit mode.
• 79943 : SAML authentication may not work as expected after upgrade for instances configured with an ADFS server.
• 79914 : When logged into Sugar with the Spanish (Latin) language, the Accounts, Contacts, Notes, Reports, and Tasks module names display with lowercase characters (e.g. cuentas) on the navigation bar after upgrading to 7.10.0.0.
• 79906, 79859 : Summation with Details-type reports containing an ampersand character (&) in the name may not render the report charts or results as expected.
• 79816 : Accessing quote records via the REST API may not work as expected.
• 79807 : When viewing knowledge base article attachments via the Notes module, the Related To field may display the incorrect label name (KBContentsAttachments) for the Knowledge Base module and not include the related knowledge base record.
• 79801 : The RT SalesMap integration version 4.3 and higher may not pass the health check as expected.
• 79734  : Drill through is not supported for report charts which are grouped by a relate field.
• 79717 : The View Change Log option is not available in the Contracts record view actions menu.
• 79707 : Clicking a URL link from an archived email’s record view may cause the email body to improperly render blank. Navigating back to the email’s record view will display the email body again.
• 79705 : Report charts do not respect user preferences for number formatting, currency symbol, or date and time formatting.
• 79486 : Attempting to edit the Shipping field for existing quote records may not work as expected if the record contains a calculated or dependent field.
• 79450 : Creating a call with a start date time (e.g. 9:10 am, 10:35 am) that is not available in the dropdown list may not block out the time period in the user’s schedule as expected.
• 79329 : Outlook Plug-in version 2.4.0 may not connect to certain Sugar versions (7.9.1.0, 7.10.0.0).
• 79302 : Filtering on Decimal fields in list view search may not return search results as expected and result in a 500 error.
• 79268 : Modules (e.g. Task) that have a custom relationship with the Activities module may not display email records as expected when emails are sent via the Emails subpanel.
• 79254 : An unexpected error may display while installing Sugar on a Windows server on PHP 7.1.
• 79222 : If two modules contain calculated fields containing a related() function that point to each other, deleting one record may cause a new blank record to get created improperly.
• 79204 : Creating multiple quotes from a related module’s Quotes subpanel (e.g. from an account record) incorrectly duplicates the original quote’s line items as line items in each subsequent quote.
• 79076 : The quoted line item’s Unit Price field in the Quotes module is uneditable.
• 78860 : Sugar SSO fails to connect to SAML login URL’s containing an ampersand (&).
• 78808 : Downloading PDF templates containing ampersands may not work as expected and result in a 500 error.
• 78714 : Emailing a meeting record as a PDF file via the Email PDF option may improperly remove the meeting’s relationship to the related account record.
• 78620 : The related record (e.g. Account Name field) links in a module’s record view (e.g. Contacts) may incorrectly be disabled for users assigned a role with View permission set to “Owner”.
• 78568 : Calculated fields containing the countConditional(), rollupConditionalSum(), or rollupSum() functions may improperly update and display incorrect values each time additional records are loaded in the related module subpanels.
• 78537 : Editing the run-time filter in reports may not auto-complete to pull up matches as expected.
• 78532 : In certain circumstances, the record’s creation date may improperly default to 01/01/1970.
• 78496 : Report chart values may not render correctly for Integer fields when using a period as the 1000s separator and a comma as the Decimal Symbol in the user’s profile.
• 78364 : Sugar improperly attempts to establish an SSL/TLS connection when “Use SMTP Authentication” is unchecked.
• 78306 : When importing calls or meetings, the current user performing the import is improperly added as a guest to the call/meeting.
• 77764 : Attempting to scroll in Legacy modules (e.g. Campaigns) may not work as expected when logged into Sugar on iPad.
• 77736 : User records may not be clickable from the Organization Chart dashlet to access the Employees detail view.
• 77658 : Adding a custom time format in the config_override.php file may not work as expected and display the time values incorrectly.
• 77481 : Manually clearing the cache directory may cause unexpected errors in the system if the Users module contains a custom field.
• 77410 : After upgrading to Sugar version 7.7.1.0+, performing an import using the pre-set import settings may not map the Email Address field to the corresponding field (Email) as expected.
• 77291 : Downloading PDF templates containing bold and/or italic text may not display the text in the correct font format.
• 77255 : When resetting a password via the Reset Password email, including an ampersand character (&) in the new password may cause login issues for subsequent login attempts.
• 77012 : When creating a custom module in module builder, adding a many-to-one relationship may incorrectly create a duplicate relationship field to the module after saving/deploying the package.
• 76620 : Users assigned a role with “Access Type” set to “Admin & Developer” for “Users, Teams, and Roles” may not be able to reset passwords for other users as expected.
• 76538 : When accessing Sugar using a device (e.g. laptop) with touch screen enabled, the date picker may not work as expected.
• 76428 : Sugar may improperly truncate the attachment name from inbound emails if it contains special characters in the name.
• 76183 : Sugar improperly attempts to send auto-reply emails using the Admin user’s (id=1) email address instead of the system email address defined in Admin > Email Settings.
• 75571 : Enabling the “Delete related notes & attachments with deleted emails” option may not delete the related note record as expected when an email is deleted.
• 75471 : Sugar may not behave as expected and result in an error if the Sugar license is either expired or due to expire.
• 73026 : Workflow alert templates containing new and old value variables (e.g. {::future::Contacts::do_not_call::}, {::past::Contacts::do_not_call::}) for checkbox fields may not display the correct field values as expected in the email notification.
• 72921 : Setting the email client in the user’s profile to “External Email Client” may not be respected properly as the Sugar email client continues to be used when replying to emails in Sugar.