This guide provides an overview of product features and related technologies. In addition, it contains recommendations on best practices, tutorials for getting started, and troubleshooting information for common situations.
Topics
- Introduction
The Sugar application code is based on a modular framework with secure entry points into the application (e.g. index.php or soap.php). All modules, core or custom, must exist in the /modules/ folder. Modules represent business entities or objects in Sugar such as Contacts, and the object has fields or attributes that are stored in the database, as well as a user interface (UI) for the user to create and modify records. A module encompasses definitions for the data schema, user interface, and application functionality.
- ACL
ACLs and restricting access.
- Administration Links
Managing administration links.
- AjaxUI
Overview of the AjaxUI features and design considerations.
- Authentication
- Charts
- Connectors
- Dashlets
- Databases
All five Sugar editions support the MySQL and Microsoft SQL Server databases. Sugar Enterprise and Sugar Ultimate also support the DB2 and Oracle databases. In general, Sugar uses only common database functionality, and the application logic is embedded in the PHP code. Sugar does not use database triggers or stored procedures. This design simplifies coding and testing across different database vendors. The only implementation difference across the various supported databases is column types.
- Entry Points
- File Caching
An Overview of how caching works within SugarCRM
- Global Control Links
Managing global control links.
- Helper Classes
- Job Queue
- Language
- Loggers
- Module Builder
- Module Loader
- Performance
- Portal
- Quicksearch
Sugar uses a type-ahead combo box system called QuickSearch that utilizes components from the YUI framework.
- Schedulers
- SugarBean
- SugarPDF
- Teams
- Themes
An overview of the theme framework
- TinyMCE
- Uploads
- Web Services
|
