The Developer Tools section of Sugar's Admin page contains various configuration menus that help you customize your instance to best suit your organization's needs. Developer Tools allow you to edit the look, feel, and functionality of your instance, including adding fields, changing layouts, adding automated processes, and creating entirely new modules.
The Developer Tools section contains the following menus:
|Studio||Modify fields, relationships, and layouts for existing modules|
|Module Builder||Create new modules to be deployed into this instance or exported to other Sugar instances|
|Module Loader||Upload and manage customization packages to your instance, such as additional modules or third-party integrations|
|Workflow Management||Manage automated processes in Sugar to optimize and streamline your company's business process|
|Rename Modules||Update the name of each module within Sugar|
|Display Modules and Subpanels||Hide or display modules and subpanels across the application|
|Configure Navigation Bar Quick Create||Configure which modules appear in the Quick Create menu on the navigation bar|
|Configure API Platforms||Manage platform identifiers for custom API integrations|
|Dropdown Editor||Manage dropdown lists to add new lists or edit existing lists|
Studio enables administrators to customize stock or custom modules by modifying fields, page layouts, and more. This allows Sugar to be modified to ideally fit your organization's needs and terminology. Please note that only users with administrator or developer access have the ability to make changes via Admin > Studio. For more information on how to utilize Studio, please refer to the Studio documentation.
Module Builder enables administrators to create, deploy, and maintain custom modules in Sugar. For your convenience, the custom modules are based on templates such as Basic, Person, Company, etc. Modules can then be deployed within your instance of Sugar so that users can utilize the new module in their daily process. In addition, modules can be exported for additional development or published and then imported to other Sugar instances. For more information on using Module Builder, please refer to the Module Builder documentation.
Module Loader is used to import packages into Sugar that make changes to core files. Examples of module-loadable packages include Sugar custom modules that were created in Module Builder, language packs, third-party integrations, or any other type of file that would make changes to Sugar's core file system. Module Loader provides a portal within the application where zip files can be easily uploaded and then installed. For more information on how to use Module Loader, please refer to the Module Loader documentation.
Sugar's Workflow functionality allows administrators to configure cause and effect type actions throughout Sugar and across multiple modules. Workflows can be used to update fields, send emails, or create records once certain sets of conditions are met. Workflows are a great way to configure automated processes within Sugar so that users do not need to remember manual steps and instead can focus on their primary tasks and job responsibilities. Administrators can create and manage workflows via Admin > Workflow Management. For more information on workflows, please review the Workflow Management documentation.
Depending on your business needs, it may be necessary to alter the display label to make the module's name (e.g. Contacts, Accounts, etc.) align with your various business components. Administrators can easily rename modules via Admin > Rename Modules. When editing a name, you are given the option to update both the singular and plural version of the word. This change will be reflected globally across Sugar so that every use of the given module name is updated to your preference, seamlessly to all users. You can also use the language dropdown list at the top of the page to rename the modules to a language other than English.
The following steps cover renaming the Contacts module as an example:
- Navigate to Admin > Rename Modules.
- Locate the module you wish to change and click the Pencil icon to the left of the module's name.
- Enter a new singular and plural name for the module then click the Pencil icon again to close the text boxes.
- Click "Save" to deploy your changes across your instance.
Display Modules and Subpanels
Administrators have the ability to control which modules and subpanels will appear in their instance via Admin > Display Modules and Subpanels. This option is useful as any unnecessary module(s) and subpanel(s) can be hidden to prevent users from accessing it. Please note that not every module and subpanel in Sugar is enabled by default when initially installed.
Once the "Display Modules and Subpanels" page is open, you will see the Displayed Modules, Hidden Modules, Displayed Subpanels, and Hidden Subpanels columns. To configure which modules are displayed on the navigation bar, drag and drop the module from the Hidden Modules column to the Displayed Modules column. To hide a module, simply drag and drop the module from the Displayed Modules column to the Hidden Modules column. To configure which subpanels appear in modules, drag and drop the module from the Hidden Subpanels column to the Displayed Subpanels column. To hide a subpanel, simply drag and drop the module from the Displayed Subpanels column to the Hidden Subpanels column. After making the necessary changes, click "Save" at the top of the page to deploy your changes or "Cancel" to revert back to your previous settings.
Please note that if a hidden module is related to a module that is visible in Sugar, it will display as a subpanel in the record view (for Sidecar modules) or detail view (for Legacy modules) of the related module. In addition, hidden modules continue to be available to users when viewing, creating, and managing reports via the Reports module. When a subpanel is hidden, users cannot view any related records from the record view (for Sidecar modules) or detail view (for Legacy modules) of the related module.
Users have the option to hide and display modules per their viewing preference via the User Profile. The list of available modules to display and hide in a user's account is based on the modules in the Displayed Modules column of the Display Modules and Subpanels page. To disable the users' ability to modify which modules are hidden or displayed on their navigation bar, uncheck the Allow users to select modules to appear in the navigation bar checkbox above the Displayed and Hidden Modules columns.
If you wish to prevent certain users from accessing specific modules in Sugar, you can keep the module enabled globally but assign a role to the user. For more information on creating and assigning roles, please refer to the Role Management documentation.
Configure Navigation Bar Quick Create
The Quick Create menu allows users to easily create new records from anywhere in Sugar. Simply click the quick-create button on the upper right of any Sugar page to access the menu. Administrators can easily configure the Quick Create menu via Admin > Configure Navigation Bar Quick Create menu to control which modules are enabled/disabled, as well as the order the modules will appear in the menu.
Once the "Configure Navigation Bar Quick Create" page is open, you will see the Enabled Modules and Disabled Modules columns. Modules that appear within the Enabled Modules column will display in the Quick Create menu. To enable a module to be displayed in the Quick Create menu, drag and drop the module from the Disabled Modules column to the Enabled Modules column. To disable a module, simply drag and drop the module from the Enabled Modules column to the Disabled Modules column. You can also change the order of the modules as they appear in the Quick Create menu by dragging and dropping the modules up-and-down within the Enabled Modules list. After making the necessary changes, click "Save" at the top of the page to deploy your changes or "Cancel" to revert back to your previous settings.
Note: The Quick Create menu can display a maximum of 10 modules at one time.
Configure API Platforms
Developers use the
platform parameter to distinguish their custom platform from other clients when using the Sugar API. For example, when a user accesses Sugar via the desktop client and the mobile client simultaneously without being logged out of either, it is because the API recognizes that they are different platforms due to their unique platform identifiers. The platform identifier also makes it easy for a Sugar administrator to configure which API platforms are allowed to access their instance via Admin > Configure API Platforms.
Note: To learn more about platform identifiers, please refer to the Dev Blog in SugarClub.
The API Platforms panel is a list of client IDs that have been given permission to interact with your Sugar instance. The panel will automatically display some standard platform identifiers required by every Sugar instance. The stock API platforms listed in the following table cannot be removed and must not be reused as platform identifiers for a custom integration.
|API Platform Identifier||Platform/Client|
|base||Sugar desktop client (default platform)|
|mobile||Sugar Mobile app|
|portal||Sugar Portal (Enterprise, Ultimate, Sell, Serve)|
|opi||Sugar Plug-in for Microsoft Outlook 2.x|
|lpi||Sugar Plug-in for IBM Notes|
To allow a new integration for your Sugar instance, find the package's
platform parameter, enter it in the text box below the API Platforms panel, and then click "Add". You may need to ask your developer to check the .custom/clients/platforms.php file for this information. To remove any custom API platforms from the list, click the Remove icon next to the API platform identifier that you wish to remove. Upon removing the platform, all integrations that relied upon it will stop working.
Alternatively, developers may choose to create a module loadable package to add custom identifier(s) via Sugar's Module Loader tool. To remove platform identifiers that were added via Module Loader, simply uninstall the package. More information on adding platform identifiers via Module Loader can be found on the Dev Blog in SugarClub and the Platforms documentation in the Developer Guide.
The Dropdown Editor allows administrators to view, modify, and create dropdown lists which can be added as fields in Sugar. Since dropdown lists are not module specific, they are stored and managed through the Dropdown Editor. Dropdown lists can only be associated with dropdown, multiselect, and radio-type fields via Admin > Studio. For more information on associating dropdown lists to the different field types, please refer to the Studio documentation.
Certain dropdown lists cannot be edited via the Dropdown editor as they are controlled by a separate area (e.g. Contract Types, Releases, etc.) of the Admin page. These include dropdown lists for the Forecasting, Bug Tracker, Contracts, and Products and Quotes modules. Please refer to the appropriate sections of the Administration Guide for more information regarding the fields and how they can be edited.
Adding Dropdown Lists
Dropdown lists can be created at any time and added to a Dropdown type field via Studio. When creating a list, please keep in mind that this list is not module specific, so be sure to properly name your list and any dropdown options to avoid any confusion in the future.
Use the following steps to create a dropdown list via Dropdown Editor:
- Navigate to Admin > Dropdown Editor.
- Click the Add Dropdown button, which is located above the list of existing dropdown lists.
- Enter a name for your dropdown list in the Name field (e.g. "account_manager_list").
- Note: The name must be alphanumeric and use the underscore character for spaces.
- To create the items that will appear in your dropdown list, enter an "Item Name" and a "Display Label". Click "Add" once you have populated both fields to add the value to the dropdown list.
- The item name is the backend system name for the list item and must be alphanumeric. An underscore or a period can be used for the item name.
- The display label defines what will be displayed in the actual dropdown. Please note that there are no character restrictions when entering the display label. Click "Add" once you have populated both fields to add the value to the dropdown list.
- Once all values have been added to your dropdown list, you can click one of the sort options to rearrange the values as desired. Lists can be sorted alphabetically in ascending or descending order based on the display label. You can also sort the list manually by dragging and dropping the values up-and-down the list.
Click "Save" at the top of the screen to complete and add your dropdown list. You will be directed back to the main dropdown editor page once the save completes.
Viewing Dropdown Lists
The Dropdown Editor displays all existing dropdown lists in two separate sections (Dropdowns list, Dropdown Editor) on the page. The Dropdowns list to the left of the page displays the dropdown lists in alphabetical order. The Dropdown Editor tab displays the dropdown lists in columns and allows you to view more of the lists at once instead of scrolling down a single list.
Once you locate the dropdown list you are looking for, click the list's name to open the Edit Dropdown tab to view and edit the list. The Edit Dropdown tab displays the name, the set language for the list, list values, and the item name. The list will be ordered as they appear in the dropdown list when added as a field to a layout. You can reorder the list if you wish by dragging and dropping the items into the desired positions.
If your organization uses Sugar in languages other than English, Sugar can display translated dropdown lists for each language used. For example, Sugar will display French dropdown items when a user is logged into Sugar in French. You must provide the translations for each language by specifying display labels for each dropdown item. First, finalize your list's items by adding or removing items; the item names (a.k.a. database values) and order of items will be consistent across all languages. Choose the desired language in the Language dropdown above the list. Then, click the pencil icon for each item and enter a translated display label. When all labels have been translated, click "Save" to preserve your changes. After saving, the list will automatically be displayed in English, but you can change the Language dropdown again to check your labels.
Editing Dropdown Lists
Dropdown lists can easily be modified via the Dropdown Editor by selecting the specific dropdown list which opens the edit layout. You can reorder the items in the list, add new values, remove unnecessary values, change the display label for a value, or change the display label language.
Please note that the name of the dropdown list cannot be changed once created. Also, dropdown lists cannot be deleted since they can span multiple modules in Sugar and cause important data to be lost if removed in error. Once the necessary modifications have been made, click "Save" on the upper right to preserve the changes made.
To sort the list alphabetically, you can simply click the Sort Ascending or Sort Descending button on the bottom left of the tab view. Please note that the sorting is based on the display label. You can also reorder the items in your list, by dragging and dropping the items into the desired position.
To add a new value, enter an item name and corresponding display label below the list of existing values then click "Add". Please note that the item name is the back-end system name and must be alphanumeric without any special characters other than an underscore or a period. The text in the display label defines how the value will be displayed in the dropdown list when viewed in the user interface. Please note that there is no character restriction for the display label.
To remove a value from the list, click the Minus icon to the far right of the item row. Once deleted, the item will show a strikethrough and will be removed from the list once saved.
The item name of a dropdown value cannot be edited, but you can update the display label via the Dropdown Editor. Simply locate the value in the list then click the Pencil icon to the far right of the item row. Enter the new value into the open text box then click anywhere on the page to close the edit.
Editing Sales Stages
The Opportunities module contains two fields that function unlike other fields in Sugar. When the Sales Stage dropdown field is updated, the corresponding probability updates in the Probability (%) field. This is a unique function to the Opportunities module and when any changes are made to the
sales_stage_dom list, you must consider the
sales_probability_dom list as well to ensure the relationship between the two fields remain intact. For example, if you add a new sales stage (e.g. Item Name: "review_stage", Display Label: "Review Stage") to the
sales_stage_dom list, then you must add a corresponding probability (e.g. Item Name: "review_stage", Display Label: "50") to the
sales_probability_dom list in order for it to populate properly in the opportunity. The two lists' item names and order must match.
The Dropdown Editor contains both the
sales_probability_dom lists. Both dropdown lists have the same item name for all values, but different display labels.
sales_stage_domlist is associated with the Sales Stage field and displays the various sales stages (e.g. prospecting, qualification, closed won, etc.).
sales_probability_domlist is associated with the Probability (%) field and displays the corresponding probability value (e.g. 10, 20, 100, etc.) for each sales stage.
Note: Both the
sales_stage_dom and sales_status_dom lists must have "Closed Won" and "Closed Lost" as item names in order for the Forecasts module to function correctly. Never remove or change the item names for these two options.
For sales_probability_dom list:
Users can create similar logic for custom fields using Sugar Logic in Studio.
Editing Time Intervals
The "After Time Elapsed" workflow triggers after a specified period of time has elapsed from when a record save occurs in Sugar. For more information on "After Time Elapsed" workflows, please refer to the Workflow Management documentation. When creating the conditions for the workflow, you have the option to specify the time interval (e.g. 0 hours, 4 hours, 1 day, 1 week, etc.) used by the system to execute the workflow. The available time interval values can easily be modified via the Dropdown Editor.
The Dropdown Editor contains the "tselect_time_dom" list, which allows administrators to configure the time intervals used for time elapsed workflows. To add new time intervals to the dropdown list, simply enter the "Item Name" and "Display Label", keeping in mind that the item name must display the number of seconds corresponding to the new time interval. The display label value should have the time as it relates to minutes, hours, days, etc. For example, if you are adding 2 hours to the time interval list, the item name value will be "7200" and the display label will show "2 hours".
Relate Fields Denormalization
Relate Fields Denormalization is a Sugar administration tool that can be used by customers with very large database tables to optimize the database structure for faster sorting and data load of relate-type field values on list view pages. The denormalization process will copy the values of stock Sugar relate fields from their own tables into a text field (e.g.,
denorm_field_name) in the table of the related module (i.e. the parent table) via cron job. The new text field is then used for sorting in list views. Then, a logic hook will continue to monitor any value changes made to the relate field, the source field that the relate field points to, and to the linked record ID. The logic hook will also react to changes made to the relationship.
As an example, you may want to denormalize the Account Name relate field for the Opportunities module so that when you sort by Account Name in the Opportunities list view, Sugar will query its search against the field value in the Opportunities table instead of against the JOIN table for accounts_opportunities.
Note: While denormalizing the data will speed up sorting in list views, it may increase the time it takes to update records in the denormalized module (1-5% degradation in the worst case).
To denormalize a relate field in your instance, use the following steps:
- Navigate to Admin > Relate Fields Denormalization, located in the Developer Tools section of the page.
- Choose the module that contains the relate field you would like to denormalize. Each module's name will display a number that indicates how many relate fields are eligible for denormalization in that module. The following criteria must be met in order for a field to be eligible for field denormalization:
- The field must be a stock relate-type field. Custom fields cannot be denormalized.
- The field must be configured as "Available" in the list view layout for the module. For more information on list view layouts, refer to the Studio documentation.
- The relate field must be sortable in the list view. This is not an admin configurable option, so we recommend confirming this before continuing.
- Click on the field name that you want to denormalize under "Field List" and drag and drop it to the "Denormalized Fields" section on the right.
- Click Save.
- Review the Pre-check Results window and take note of the estimated time to complete, which could take up to an hour depending on the table sizes. Click "Confirm" to continue. Alternatively, you may choose to copy the SQL shown in the window, click "Cancel", and execute the command manually if you would prefer not to initiate the cron job.
After confirming, the process will continue in the background and show its progress in the Work Status field. You may click on the refresh icon to update the latest progress until it is "Done".
You may click on the Remove (x) icon to remove your scheduled denormalization job from the job queue, but as best practice, it is recommended to allow an in-process job to fully complete without stopping it. Denormalization changes that have been applied to a field can be reversed by moving it from the "Denormalized Fields" side back to "Field List" and clicking "Save". Reversing a denormalization action will remove the related logic hook and Sugar will resume using the regular field, but the denormalized field will still exist in the database.
Last modified: 2020-10-22 22:08:43