This is a developer’s manual on SugarCRM. The book focuses on customizing SugarCRM. It provides you with an overview of the architecture of the application and the database. It also shows essential steps for hooking your module into the SugarCRM infrastructure.
Chapter 1—This chapter is a smooth introduction to customizing Sugar CRM.
Chapter 2—You will start to customize the SugarCRM application itself, and you will be able to add your own components in the form of module tabs and dashlets.
Chapter 3—You will learn how to modify the look and feel of SugarCRM. This chapter also shows how to add new fields to SugarCRM.
Chapter 4—This chapter looks at the interfaces, and how to use them effectively in your customizations.
Chapter 5—This chapter includes database schematic diagrams, showing the relationships between each table in the database.
Chapter 6—In this chapter we have covered complete database schematics for the SugarCRM application, providing full details on each table.
Chapter 7—You will learn in this chapter how to develop, test, and use SugarCRM in a safe environment using a development server, a test server, and a live server.
Chapter 8—You will learn to incorporate third-party modules into your site and develop your own modules from scratch.
Chapter 9—This chapter deals with developing a custom workflow within SugarCRM.
Chapter 10—You will see various techniques in this chapter for optimizing the performance of SugarCRM implementations, and a few more ways of extending the application.
The book is for PHP developers working with SugarCRM, who want to extend its capabilities. Readers should have basic knowledge of SugarCRM as the book does not provide any instructions on installation and usage.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
There are three styles for code. Code words in text are shown as follows: "We can include other contexts through the use of the include directive."
A block of code will be set as follows:
[default] mkdir -p modules/TestApp/language touch modules/TestApp/language/en_us.lang.php touch modules/TestApp/Forms.php touch modules/TestApp/index.php
When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:
insert into fields_meta_data
( id,
name,
label,
help,
custom_module,
data_type,
ext1,
default_value,
date_modified,
mass_update
)
New terms and important words are introduced in a bold-type font. Words that you see on the scre]en, in menus or dialog boxes for example, appear in our text like this: "clicking the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply drop an email to <[email protected]>, making sure to mention the book title in the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Visit http://www.packtpub.com/support, and select this book from the list of titles to download any example code or extra resources for this book. The files available for download will then be displayed.
The downloadable files contain instructions on how to use them.
Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the Submit Errata link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
You can contact us at <[email protected]> if you are having a problem with some aspect of the book, and we will do our best to address it.