Below is a message from Ticomix, an Advanced SugarCRM Partner, about a monthly webinar series focused on the Sugar Developer/Admin hosted by one of our most active Sugar Developer community members Jeff Bickart.

SugarCRM Power Hour with Jeff Bickart

Webinar Series Overview:
We know how hard it can be to get the dedicated, interactive support you need, so we’re here to offer help. Each month, we’ll deliver a unique perspective to the common (and sometimes uncommon), everyday technical issues you face with the administration of SugarCRM. Each hour-long webinar will contain valuable information plus a live Q&A session to answer any burning questions you have. The initial schedule of topics is below.

The first webinar is happening March 11th @ 1:00PM ET. In the webinar, Jeff will unveil helpful hints for setting up your development environment and installing Sugar. Even if you’ve already setup your Sugar environment, you’ll find valuable tips for optimizing your install of Sugar.

Also, Jeff welcomes questions prior to the webinar. Click here to access Jeff’s webinar question form »

Click here to register for one or all webinars »

UPCOMING POWER HOUR SCHEDULE (all webinars begin at 1:00PM US Eastern Time):

  • March 11th: How to Set Up Your Development Environment & Install Sugar
  • April 8th: Building Custom Dashlets
  • May 13th: Using the SugarJobQueue & the SugarCRM Directory Structure
  • June 10th: Workflows, LogicHooks & Deploying Packages
  • July 8th: Layouts, Views and Building a Wizard

About Jeff:

Jeff Bickart, CRM Evangelist at Ticomix, has been developing in Sugar since 2004 (the same year SugarCRM was founded) and is one of the foremost experts in SugarCRM development. He writes a popular SugarCRM Developers Blog (SugarCRM: Developers’ Guide), is a frequent contributor on the Sugar community forums, and has made vast contributions towards Sugar’s code base. Jeff invites you to connect with him in several ways:

Twitter: @bickart

Have you discovered the new Sugar Community yet? The new Sugar Community launched about a year ago and right now it has over 4,500 conversations and over 3,000 members. It is a great resource for learning about Sugar and the names and faces behind Sugar. Most importantly, it’s great for getting your questions answered!

Registration is easy – just visit the Community and click ‘Register’ on the top right.

Some of the most popular topics on the Community are the ones that matter most to Sugar Developers. In fact, Sugar Developer topics account for majority of the conversations on the community!

The Community categories that I use the most are the Sugar 7 Category and the Development Best Practices Category. They’re both very active with lots of great discussions and questions. Do you also have Sugar Development questions? Or maybe some answers of your own?

UnCon is back again!

Matthew Marum —  February 19, 2015 — Leave a comment

Sugar Engineering is excited to announce that we are hosting another Sugar Developer exclusive event this year at SugarCon 2015.  UnCon is back again and better than ever!  We listened to your feedback and are changing up the format a bit this year.  We will have two concurrent tracks during UnCon – a hackathon contest and roundtable discussions.  This will allow us to maximize the value of UnCon for any Sugar Developer of any experience level.

Join us at UnCon to learn how sweet it is to be a Sugar Developer! UnCon is a great chance for novice to ninja-skilled Sugar developers to hack side-by-side with our core engineers, and learn from the brightest stars in Sugar Engineering and the Sugar Developer community at Unconference-style roundtable discussions. Oh, and we will have beer too.

UnCon 2015 website

Stay tuned for more details that will follow in coming weeks!  We hope to see you at SugarCon 2015!  Your conference registration includes access to UnCon.


Here are two free plug-in tools that make it painless for Sugar 7 users to get a quick glimpse into critical history items.

Continue Reading...

If you want to use namespaces following the PSR-0 standard for your custom code, it is now possible with the SugarAutoLoader in sugar7. Now you don’t have to insert require statements all over the place.


SugarAutoLoader::addNamespace('Fbsg\\', 'custom/include/Fbsg');

Sugar’s autoloader will now map requests for the class Fbsg\Example\Test to the file “custom/include/Fbsg/Example/Test.php”.

Post From Faye Business Systems Group Director of Development Matthew Strickland

Contact Jesse Heller

When you work with something everyday, eliminating tedious and repetitive tasks not only improves your productivity but also helps your sanity. With Sugar, there are certain things we as developers are constantly doing; in some cases, over and over again. How many times have you run quick repair and rebuild?

Luckily, we program things. We write scripts that make our lives in that moment a tad bit easier. But it’s easy to lose track of these things; we might even write the same tool over and over again.

In this series of posts, we’re going to build a command line utility tool whose only purpose is to make life more beautiful. If you’ve ever used the laravel framework, you are familiar with the “artisan” tool which is built with the symfony console component. We are going to do the same thing.

The general idea here is to be able to call commands like these:

$ sugarcli admin:repair
$ sugarcli manifest:validate

Let’s get started.

We are going to be using symfony console composer, so if you aren’t familiar be sure to read-up on it. The first thing, we need to do is pull in our symfony console dependency in composer.json.

    "require": {
        "symfony/console": "v2.4.4"

    "autoload": {
        "psr-4": {
            "Fbsg\\": "src"
$ composer install

Notice that we are using psr-4 for are auto-loading our classes, as we will be using psr compliant namespaces.
Now that we have our dependencies installed to the vendor folder, we are ready to start.

In the next post, we’ll be building the quick repair/rebuild command.

You can view the github repository here.

Post From Faye Business Systems Group Director of Development Matthew Strickland

Contact Jesse Heller


Editor’s Note: This blog post comes from Bill Convis of SierraCRM, and talks about how his team worked with our top notch engineering team to find a way to add action menu items across multiple modules. Big thanks to Bill for the writeup, and Peter DeMartini of SierraCRM, and David Wheeler of SugarCRM for helping form the solution.

With the release of SugarCRM 7 came new challenges and opportunities for SugarCRM technology partners. An entirely new paradigm was offered for solution providers to add new features to the power of SugarCRM. Process Manager Enterprise (PM) from SierraCRM, a workflow solution that augments SugarCRM’s existing workflow, was being updated to take advantage of the new architecture.

One of the features to be added to the new release of PM was the ability to see all the processes for a single object. Our intent was to show both processes that had been completed and process that were currently active.

After reviewing the options, a decision was made to add an “action item” to a record view to display a drawer with a listing view of the processes for that record.

We approached John Mertic at SugarCRM and asked him if there was an extensible framework for action buttons, as we wanted to build a solution that was both upgrade safe and would be global across all modules. He suggested we meet with the engineers at SugarCon.

At the SugarCon 2014 conference in San Francisco, Sierra’s senior developer, Peter DeMartini, met up with SugarCRM Engineer David Wheeler at one of the hacker sessions.

David suggested an approach in which we would keep the ./custom/clients/base/views/record/record.php which would define the button for every record. Then a new file that would enable us to include the javascript code behind the button click event in every module in SugarCRM that displays the record view.

This new file would be ./custom/clients/base/layouts/record/record.php.

In record.php we injected our custom layout, pm-record-logic, into the baseline record view. This pm-record-logic layout was the key to ensure that custom javascript code was guaranteed to be present for the modules record view and this javascript would be available on the click event of the new action button.

The final file that was created with the help from David (this was the most important piece for us) was the pm-record-logic.js file. David suggested we extend the initialize function , call the _super method and then bind our code to the click event for the button created above. The code snippet is:

We will now present the code in its entirety with instructions for other solution providers to accomplish the same thing:

The first file is record.php and lives in ./custom/clients/base/views/record/record.php

This file adds the action button to the action menu. The ‘name’ => ‘pm_record_reports’ will map to a file ./custom/clients/base/views/pm-record-logic/pm-record-logic.js with an initialize function that will set this buttons name to a click event function.

The next file is also named record.php and lives in ./custom/clients/base/layouts/record/record.php

What is key in this file is the ‘layout’ => ‘pm-record-logic’. Which allows us to inject our custom view into every record view.

Our first file is:


And our handle bars file ./custom/clients/base/views/pm-record-logic/pm-record-logic.hbs

And finally our pm-record-logic.js file which makes the api call to Process Manager to retrieve all the processes for the given object:


The remaining files used in this customization are the view and layouts for the actual data returned by Process Manager to be shown in the drawer.

What was key to this customization, and what we learned from the outstanding support from John and David, was the ability to be able to guarantee that our new action button click event function in javascript would be placed on the action menu for most modules (excluding Leads) and that we had confidence that the javascript functions on the click event would also be present.