Do you need a new module in your SugarCRM application to incorporate a new business requirement? Many businesses repurpose within standard modules to facilitate implementation of a new requirement. In this session we will discuss best practices on when to repurpose vs. when to create a new custom module. We will then learn how to create a new module, set up fields, edit page layouts and establish relationships to other modules. This session is a MUST for anyone who is looking to expand their Sugar application beyond what is standard/out of the box and for anyone looking to become a master Sugar Admin.

1. Sugar U.
Building Custom Modules in SugarCRM

2. Bryan Leung
SugarCRM Professional Services Consultant
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 2

3. Custom Modules – What, When and How
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 3

4. Objectives
 Understand what custom modules are
 Identify when custom modules should be created
 Learn how to create a custom module
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 4

5. What is a custom module?
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 5

6. What is a custom module?
 A module is a container that holds a specific set of
data in the SugarCRM application
 A custom module is a custom container that a system
administrator can build to house a specific set of data
 Allows for importing
 Allows for reporting
 Compliments other modules
 Can be related standard or other custom modules
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 6

7. When should I create a
custom module?
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 7

8. Custom modules should be created when…
 Business requirements dictate
 There aren’t any standard modules in the SugarCRM
application that can appropriately house the
information needed
 An existing standard module cannot be repurposed
 You want to extend related custom data to existing
modules
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 8

9. How do I create a custom
module?
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 9

10. Components
 Package
 Module Templates
Basic
Company (Accounts)
File (Documents)
Person (Contacts)
Issue (Cases)
Sale (Opportunities)
 Fields
 Layouts
 Relationships
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 10

11. Package Buttons Defined
 Save
 Duplicate
 Deploy
 Delete
 Publish
Creates a zip file to install into another SugarCRM instances
Ready to be deployed
The destination instance will not have the package in Module Builder
The package is considered as completed
The installed “published” package is deployed immediately in the
destination instance
 Export
Creates a zip file to install into another SugarCRM instance
Not ready to be deployed
Additional work to be continued
The package and custom module(s) appear in Module Builder
The package is not yet deployed
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 11

12. Demonstration
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 12

13. Q&A
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 13

14. Custom Module Best Practices
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 14

15. Best Practices
 Fully gather and understand the Business
Requirement before starting
 Start small and expand
 Studio level configurations are overwritten each time
a package is redeployed
Tweet: #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 15

16. Submit Session Feedback
Select the SugarCon Mobile App:
1) Tap on this session
2) Tap on survey
3) Submit your feedback
*iPad prizes for attendees who submit session feedback using the Mobile App
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 16

17. #SCON12
4/24/2012 ©2012 SugarCRM Inc. All rights reserved. 17