Skip to main content
  • 299 Accesses

Abstract

Up to this point, you’ve looked at ways to customize SugarCRM using the standard developments tools, such as Studio, Workflows, and Logic Hooks. These tools are generally considered the easiest way to customize SugarCRM, since it is the most supported and most common way to customize your instance. Sometimes SugarCRM doesn’t achieve the level of customization you may need. Perhaps you need to alter some of the default behaviors of the application or maybe the GUI tools you looked at in Chapter 6 just don’t do exactly what you need. At this point, code level customization is truly the only option.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 16.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2009 John Mertic

About this chapter

Cite this chapter

Mertic, J. (2009). Overriding Existing Code. In: The Definitive Guide to SugarCRM. Apress. https://doi.org/10.1007/978-1-4302-2440-2_8

Download citation

Publish with us

Policies and ethics