Book Review: SugarCRM Developer’s Manual
The following is a review of the book SugarCRM Developer’s Manual: Customize and extend SugarCRM by Dr. Mark Alexander Bain. The book's publisher is Packt Publishing.
Editor's note: Originally this book review was intended to be a joint effort between myself and Chris Harrick, Senior Director of Product Marketing at SugarCRM. I sent Chris a few questions to get his take on the book from the perspective of a Sugar expert. What I got in return was the following, comprehensive review. So except for a small excerpt at the end, this review was generously provided by Chris Harrick, to whom we extend our thanks. -James Gray
With a CRM system that has grown to be as diverse and feature-rich as SugarCRM, creating an encompassing developer’s manual is no small task. The open-source nature of SugarCRM makes it a highly flexible application set, and the huge community around the product makes tracking all that is possible with Sugar, well, nearly impossible. However, Dr. Mark Alexander Bain comes pretty close in his SugarCRM Developer’s Manual, from Packt Publishing.
Written with PHP developers of all skill sets in mind, the book’s coverage area ranges quite widely in scope. The book quickly takes off from simple field-name changes in the application, all the way to customizing dashlets (areas of the interface with pockets of CRM data) and creating workflows from scratch. The heart of the book deals with the database schematics of SugarCRM. Bain does a good job of charting the relationships between each table in the database, as well as provides strong details on the individual tables themselves.
A good portion of the book is also dedicated to testing and optimizing the performance of the product. While less is included about customization that alters the way users approach CRM, there are some helpful hints designed to optimize a user's experience with the application. Some of the tuning tips might be helpful to PHP developers in general looking to speed up other applications built on PHP, not just Sugar.
The book spends some time dealing with third party modules, and bringing them into the application. The book seems to glaze over the process of adding third party modules via SugarForge.org or SugarExchange.com, but this is understandable. There are literally hundreds of extensions and third-party applications to be found on these Web communities, and an exhaustive explanation and guide could never be amassed for such a large inventory. The book does, however, present a nice introduction to creating custom modules from Sugar’s core business objects.
The main drawback of the book is that, given SugarCRM’s accelerated development model, some of the information is a little out-of-date. As Sugar is presently releasing version 5.0 of its product, there is a lot more customization and other features not covered. For example, while the book gives great visual examples of customizing fields and workflows, the new Module Builder tool in Sugar 5.0 allows a lot of this to be done without code-level changes. And from a security perspective, the new field-level ACLs in 5.0 open up a lot of opportunity for roles-based customizations not covered in Bain’s text.
But as SugarCRM evolves as a product and application platform, it is including a lot of Web 2.0 and Visual Studio environments in its construction. So, while Bain’s book leaves out a lot of these new features (through no fault of its own – simply a timing issue here), a lot of what is new from a customization standpoint is aimed at business users and not necessarily developers. SugarCRM is democratizing the concept of customization, so a more business-level manual for Sugar’s Module Builder might be in order soon as well.
All told, this is a fine start for someone new to the application and with a decent background in PHP. The book uses many great screen shots to illustrate its points and takes the reader through many core customization tasks in a close, step-by-step manner. And for developers, the book is valuable for its data dictionaries and database table schematics alone. It is definitely a must-read for anyone looking to learn how a highly customizable CRM application is architected.
About the author
Dr. Mark Alexander Bain began working with CRMs back in the 1990s when he started using Clarify CRM while at the Vodafone Cascade Project in the UK. He says that his team turned it into a "radio base station planning application, complete with a workflow engine for passing jobs between the different departments involved in the planning building and implementation of a radio network." Since then he has been a lecturer at University of Central Lancashire (also in the UK) and now is a freelance editor covering Linux and Open Source for various publications, including Linux Journal.
SugarCRM Developer's Manual: Customize and extend SugarCRM
by Dr. Mark Alexander Bain
Copyright 2007, Packt Publishing
First published, June 2007
You can learn more at Packt Publishing's Web site: http://www.packtpub.com
James Gray is Products Editor for Linux Journal.
- Epiq Solutions' Sidekiq M.2
- Android Browser Security--What You Haven't Been Told
- Readers' Choice Awards 2013
- The Many Paths to a Solution
- Nativ Disc
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Synopsys' Coverity
- Tech Tip: Really Simple HTTP Server with Python
- Securing the Programmer
- Returning Values from Bash Functions
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide