Spring ’18 and Sugar 8 Are Now Available

Just in time for Spring ’18, SugarCRM offered their third quarterly release for what was previously known as Sugar On-Demand, now, Sugar Cloud. Last year, Sugar took the route of a quarterly and annual release schedule to ensure a consistent and structured upgrade process. Not to mention, this is the yearly release for on-premises clients.

As many of you have been preparing for the General Data Protection Regulation (GDPR), you’ll be delighted to see and utilize all the updated data privacy features to ensure compliance with the GDPR. For instance, some of the new privacy features include:

  • A Data Privacy module (Review data privacy requests, share requests, complete requests, reject requests, view audit log. View latest values for all fields and value sources for personal data.)
  • Data Privacy Manager role (View and add data privacy requests from the person’s record)
  • Opt-out new email addresses by default
  • View and permanently erase personally identifiable information (PII)
  • Disable activity streams
  • Monitor additional context in audit logs
  • Mark fields to label them as (PII)

The GDPR is based upon more protections for personal information such as pictures, social links, IP addresses, email addresses, mailing addresses and more. In addition, it affects any company that has customers who are EU residents. Sugar offers more simplicity in terms of privacy data requests and supports the right to erasure.

The effective date of the regulation is May 25, 2018. Failure to comply can result is massive fines of up to $20 million or 4% of annual revenue–whichever sum is higher.

With the GDPR, it’s all about having the ability to track changes–especially involving customer data. Sugar 8.0.0. was designed accordingly. In fact, there are also updates with the audit data model so that you can track information and changes more efficiently.


Another updated feature is the implementation of Sugar’s semantic versioning for the REST API. Also introduced is v11.1. You may remember that v11 was released in the Fall ’17. Previously, the API version was specified just through the URL. Now, it is also specified with an HTTP header.

The benefit is, no matter the API version, resource URLs can be viewed as unique identifiers. The result is better alignment with RESTful architectural principles. Here are the attributes that make a service RESTful:

  • It is stateless
  • Cacheable
  • A client-server architecture
  • Layered system
  • Uniform interface
  • Code-on-demand

With v11.1, you get a semantic versioning policy with MAJOR.MINOR format. It’s always critical to adopt the latest REST API version to ensure you receive all the newest features–especially when building new Sugar integrations or clients. This REST API version is a property of the Sugar REST API.

Referring back to the GDPR, if you get a data privacy request, all these fields are audited by default and marked as personal information making it easier to track if an erasure is needed.

  • salutation
  • first_name
  • last_name
  • title
  • facebook
  • twitter
  • googleplus
  • phone_home
  • phone_mobile
  • phone_work
  • phone_other
  • phone_fax
  • primary_address_street
  • primary_address_street_2
  • primary_address_street_3
  • primary_address_city
  • primary_address_state
  • primary_address_postalcode
  • primary_address_country
  • alt_address_street
  • alt_address_street_2
  • alt_address_street_3
  • alt_address_city
  • alt_address_state
  • alt_address_postalcode
  • alt_address_country
  • assistant
  • assistant_phone

Furthermore, you can now configure API platforms within the Admin interface. This means you no longer need to create a custom module loadable package when registering custom platforms. Instead, you can register your custom platforms right in the Admin interface.

Not to mention, emails addresses are always viewed as personal information. You can’t turn it off through a metadata setting. Plus, a new method was added to the SugarBean class. To make data unrecoverable, the method will erase data for these fields from the audit log.

Within the audit log, a new Audit\EventRepository class has been added for more detailed tracking. Within the REST API, the audit endpoint has also been updated to show change sources. Sweet!


Here, we would like to discuss supported platforms for the 8.0.0 release. Of course, any platform that supports PHP from http://php.net is supported–this includes Mac OS, Unix, and Linux. Although, this release does not support any specified SAN or NAS devices. It is also supported on these platforms:

  • Windows, Windows Server 2012 R2
  • MySQL 5.7
  • PHP 7.1
  • Oracle 12 (only for Sugar Ultimate and Enterprise)
  • SQLServer 2014 SP2 (Only with Windows server environments)
  • IIS 8.5
  • Apache 2.4

The end user requirements are as follows:

  • Firefox 59
  • Safari 11
  • Google Chrome 65
  • Internet Explorer 11

Sugar 8.0.0 no longer supports PHP 5.6 and Elasticsearch 1.7.5

You’ll also notice improved performance since many of the SugarAutoloader functions no longer do anything. Moreover, the ./cache/file_map.php has been removed. If you want to further enhance performance, simply disable the ‘block_nested_loop’ optimization in MySQL.

Other updated features

The Product Catalog Dashlet is also now readily available. You can create pre-populated line items from an opportunity or account record.

Advanced Workflow, now has runtime execution. Automated actions can be executed depending on execution time. You can incorporate a wide variety of time and date elements into your workflows.

And, the new user interface offers a more seamless experience in alignment with Sugar mobile. You even have drill-view charts where you can pull up a list view of any report set you need. You can even make in-line edits directly from the list view.

Here are some more expansive thoughts from SugarCRM’s co-founder Clint Oram on SugarCRM’s commitment to data privacy.