Understanding Object Templates Five of the six object templates contain pre-built CRM functionality for key CRM use cases. These objects are “Company”, “Issue”, “Person”, “File”, and “Sale”. As their title denotes, each of these templates contain fields and application logic to describe entities similar to “Accounts”, “Cases”, “Contacts”, “Documents”, and “Opportunities”, respectively. Thus, a person wanting to create a Custom Module to track a type of account would select the “Company” template. For someone who would like to track human interactions would select “People”. For the media tracking use case, the user will use the object template “Issue” because inbound media requests have similarities to an incoming support case. In both examples, there is an inquiry, a recipient of the issue, assignment of the issue and resolution. The final object template is named “Basic” which is the default base object type. This allows the administrator to create their own custom fields to define the object. Figure 4: Object templates allow users to create custom modules based on common use cases, such as company, issue and person. Upon naming and selecting the Custom Module template named “Issue”, the user can further customize the module by changing the fields and layout of the application and creating relationships between this new module and existing standard or custom modules. This edit functionality allows user to construct a module that meets the specific data requirements of the Custom Module.
Copyright 2004-2008 SugarCRM Inc. Product License
Figure 4: Object templates allow users to create custom modules based on common use cases, such as company, issue and person.