Skip navigation
All Places > Developer > Blog > 2019 > January
2019

Hey Sugar devs!

 

Just like clockwork, it is time for another Sugar cloud quarterly release. If you are on-premise, then you will get these features and many more in the upcoming Sugar 9.0 release in the Spring.

 

Check out the official release announcement for information that your end users will care about.

 

For Developers, we recently hosted a developer webinar we gave an overview of the important changes developers need to know:

 

 

The slides from the webinar are available here.

 

Here's a quick overview of what developers can expect in Winter '19 release.

  • We've added a bunch of new great features like the Comment Log and Product Catalog Quick Picks dashlet
  • We've enhanced the export options available in Reports module
  • We've also made a number of enhancements to Advanced Workflow including the ability to use old and new values in email templates
  • We've put in groundwork for future PHP 7.3 support
  • We've also upgraded to jQuery 3.3.x
  • And our REST API version increased to 11.4 with some additional API endpoints

 

Check out the below resources that have the rest of the details.

 

We hope you’re as excited about this release as we are!

Hello Sugar Devs!

 

My name is Patrick Sullivan and I am SugarCRM’s Escalation Manager. I live in Pennsylvania, USA and began my career at SugarCRM in 2015 as part of the Support team. As the Escalation Manager, my job is to drive resolution of critical customer issues by working across all departments at SugarCRM, especially Technical Support, Technical Account Management, Professional Services, and Product teams. In short, I make sure problems are solved and stuff gets done.

 

Back in the Sugar Fall '17 release (also known as 7.10) we introduced a brand new Emails module built using the Sidecar framework. While the new Emails module introduced a lot of new functionality, we did not include an existing feature related to Outbound Email Accounts, specifically Group Mail Accounts, that some existing Sugar customers relied on.

 

Per our documentation, group inbound email accounts allow multiple users, such as team members, to view emails from an external mail account.  We often see customers configure group inbound mail accounts for support, sales, and similar functions. In Fall ’17 and later versions of Sugar, it is very easy to set up group mail accounts for incoming email and allow many users the ability to access the inbound email.  For outbound email, the outbound email accounts must be configured for each individual user separately, providing for more granular access control.

 

Some of you missed the ease of deploying outbound email account configuration to multiple Sugar users at once. If we are talking about you then have no fear! Enrico Simonetti, Senior Technical Account Manager, has created an open source solution to allow Sugar administrators the ability to deploy outbound email accounts to entire teams with just a few clicks of the mouse. Go Enrico!

 

Accessing the Code

You can find the code for this solution in the Sugar Labs github account at:

 

https://github.com/sugarcrmlabs/OutboundEmailsDeployer

 

All you need to do is download the files, compile it into a module loadable package, and install it to your Sugar instance via Module Loader!

 

Please note that this code is provided as-is under the Apache 2.0 license.

 

Using the Deployer

Once you have installed the code, you will need to clear your browser cache.  After doing so, you will see a new section in your instance’s Admin panel called Outbound Group Email Account Deployer:

 

Opening the deployer will take you to a new page where you have several dropdown lists for selecting the applicable email account, the team to which you want to deploy the email account, and a list of all of your currently-deployed accounts.

 

For more instructions, you can find the deployer’s documentation at:

 

https://github.com/sugarcrmlabs/OutboundEmailsDeployer

 

If you have any questions, feel free to comment on this blog post, but please remember that this solution is being provided as-is.

 

Roadmap

This feature is under consideration to be included as a standard fully supported feature in a future Sugar release. Please leave feedback below if you find this feature useful!

As of this writing, all current Sugar versions (7.9 extended, 8.0, and Sugar cloud) supports and uses PHP 7.1. This PHP version was released in 2016 and entered security support on December 1st 2018. While we’ve made great strides in supporting newer PHP versions over the last few years, we have tended to be a couple years away from the latest and greatest.

 

So what is today’s latest and greatest? Well PHP 7.3 was just released on December 6th 2018. Therefore PHP 7.3 will be the next version that Sugar will support. Over the last few months our engineers have been laying the groundwork for that support in our upcoming Sugar 9.0 release.

 

Some of that work involves adding cumulative code compatibility changes for PHP 7.2 and PHP 7.3. The details of these changes can be found in the PHP 7.2 migration guide and the PHP 7.3 migration guide.

 

However, our intent is to certify support for PHP 7.1 and PHP 7.3 for Sugar 9.0. We have no plan to support PHP 7.2 now or in future. By skipping 7.2, we are able to spend more time innovating while still allowing you all to access the latest and greatest features and performance that new PHP versions offer.

 

Library updates in Sugar Winter ‘19 release

In the upcoming Sugar Winter ‘19 release, the following PHP libraries are updated. Many of these were updated to newer versions that were compatible with PHP 7.3.

 

  • doctrine/dbal: 2.7.1 → 2.8.0 (changelog)
  • ramsey/uuid: 2.9.0 → 3.8.0 (changelog)
  • symfony/{cache,console,framework-bundle,security-core,security-csrf,translation,validator}: 3.4.8 → 3.4.16 (changelog)
  • tedivm/jshrink: 1.1.0 → 1.3.1 (changelog)
  • onelogin/php-saml: v2.11 → v3.0 (changelog)

 

Additionally, we are making minor changes to the following vendored libraries for PHP 7.3 compatibility:

 

  • Smarty
  • XTemplate
  • HTMLPurifier

 

If you have custom code that uses any of the above libraries, you should verify that your customizations are still compatible.

 

Looking ahead to PHP 7.3

Finally, here are some additional PHP resources that you can review today to help you get ready to use PHP 7.3.

 

 

Let us know what you think in the comments below!