Select Yes to enable users to import a value into the field.
Select No to prevent users from importing a value into the field.
Select Required to make it a required field during import.
¢
|
Duplicate Merge. From the drop-down list, specify one of the following options for the Duplicate Merge functionality that allows users to merge records from a record’s Detail View.
|
l
|
Enabled: The field will appear on the Merge Duplicates page, but will not be available as a filter condition on the Find Duplicates page.
|
l
|
Disabled: The field will not appear on the Merge Duplicates page, and will not be available as a filter condition on the Find Duplicates page.
|
l
|
In Filter: The field will appear on the Merge Duplicates page and will also be available in the Find Duplicates page.
|
l
|
Filter Only: The field will not appear on the Merge Duplicates page, but will be available on the Find Duplicates page.
|
l
|
Default Selected Filter: The field will be used for a filter condition by default on the Find Duplicates page, and will also appear on the Merge Duplicates page.
|
4.
|
Click Save to create the field.
|
The new field is listed in the Custom section. The system appends the field name with ‘_c’ to indicate that it is a custom field. You can now add the field to the desired layout of a module.
To edit fields in Studio
1.
|
Select the module and click fields to navigate to the Edit Fields page.
|
The Edit Fields page displays custom fields in the Custom section and default fields in the Default section.
2.
|
Click the field to view its properties in the Field Editor.
|
3.
|
Edit the properties as needed and click Save.
|
You can view the updated field in the module’s records.
To manage fields
•
|
To duplicate the field, click Clone, enter a new name, and click Save.
|
•
|
To delete the field, click Delete. You must also remove the field from any layout to which it was added.
|
Editing Subpanels
Every record’s Detail View displays sub-panels for related records from other modules. You can add or remove fields for these sub-panels depending on the information that you want to display to users. You can also rename a sub-panel if needed.
To edit a sub-panel
1.
|
Select the module and then click Subpanels.
|
Sugar displays the sub-panels for the selected module on the page.
2.
|
Select the sub-panel that you want to edit.
|
The page displays the list of default fields and a list of fields that are available for display.
3.
|
To change the sub-panel’s name, enter the new name in the Title field.
|
4.
|
To add a field to the sub-panel, select it from the Hidden column and drag it to the Default column.
|
5.
|
To remove a field from the sub-panel, select it from the Default column and drag it to the Hidden column.
|
6.
|
To save and display your changes in the module, click Save & Deploy.
|
7.
|
If you do not want the changes that you made, click Restore Default to change back the layout to its original form.
|
Note:
|
You cannot use the Restore Default button to restore the default title of the sub-panel.
|
8.
|
To view a list of time stamps for changes that were made to the sub-panel, click View History.
|
You can view changes that were made at a particular time on a certain date and reinstate those changes if needed. For more information, see To preview and restore changes.
Editing Layouts for Sugar Modules
You can edit the page layouts for modules in Sugar. You can move fields, add fields, and remove fields. You can also change the tabbing order to move from field to field.
The breadcrumbs to navigate back to Studio display above the layout. The Toolbox stores fields that are not currently displayed in the layout. It also provides new rows to add to the view and a list of available fields that you can add.
You can edit the following layouts for a module:
•
|
List View
|
•
|
Detail View
|
•
|
Edit View
|
•
|
Convert Lead form for the Leads module
|
•
|
Quick Create form
|
•
|
Sugar Dashlet
|
¢
|
List View
|
¢
|
Search
|
•
|
PopupView
|
¢
|
ListView
|
¢
|
Search
|
•
|
Search
|
¢
|
Basic Search form
|
¢
|
Advanced Search form
|
•
|
Sub-panels
|
List View Layout
When you select List View, the system displays separate columns of fields that are currently displayed in the view, fields that are available for display, and hidden fields. You can click and drag a field from one column to the other depending on what you want to display to users.
Detail View, Edit View, and Quick Create Form Layouts
When you select Detail View or Edit View, the system displays the various sections of the current layout, along with the fields in each section. You can click and drag a field to a different location within the layout.
For Edit View, Detail View, and Quick Create forms, you can also change the order in which the user tabs from field to field. For example, when users create a new account, they can tab from the Account Name field to the Websitefield and so on. You can change the tabbing order to so that users tab from account name to email.
To edit List View
1.
|
In Studio, select the module.
|
2.
|
Click Layouts, and then click ListView.
|
To edit a Sugar Dashlet List View, navigate to Layouts > Sugar Dashlet > Sugar Dashlet ListView.
To edit the List View for a Pop-up window, navigate to Layouts > PopupView > Popup ListView. Sugar displays the Pop-up window when you click Select in the sub-panel of a related module in a Detail View.
Sugar displays the List View page on the screen. The Default column lists fields that currently display in the User Interface. TheAvailable column lists fields that are available to users through Advanced Search. Users can search for and add any of these fields that they want to view in the search results. The Hidden column lists fields that you do not want users to view when they perform an advanced search.
3.
|
To display a field in List View, select and drag the field from the Available or Hidden column and drop it into theDefault column.
|
4.
|
To remove a field from List View, select and drag the field from the Default column and drop it in the Availablecolumn.
|
5.
|
To hide a field from users, drag it from the Default or Available column and drop it in the Hidden column.
|
6.
|
To move a field within the layout, drag and drop it into its new location.
|
7.
|
Click Save & Deploy to display the updated List View in the User Interface.
|
8.
|
Click View History to view a list of previous changes along with the date and time of each change.
|
a.
|
To preview the changes made at a particular time, click the adjacent Preview button.
|
b.
|
To restore the previous version of the List View, click the adjacent Restore button.
|
9.
|
To revert back to the default layout, click Restore Default.
|
To edit a Detail View, Edit View, or Quick Create form
1.
|
Select the module in Studio.
|
To edit the Detail View layout, navigate to Layouts > Detail View
To edit the Edit View layout, navigate to Layouts > Edit View
To edit the Quick Create form layout, navigate to Layouts > Quick Create.
To edit a layout for Sugar Mobile and Sugar Mobile for iPhone, navigate to Layouts > Mobile Layouts, and select the layout of your choice.
2.
|
You can edit a layout as follows:
|
¢
|
To add new fields or replace existing ones with blanks, drag the filler row under New Row and drop it into the layout. You can then drag a field from the Toolbox into the filler row.
|
Note:
|
In the Edit View layout of the Leads module, the First Name and Last Name fields are used to input the lead’s name. Sugar concats these two values to display the lead’s name in the Detail View.
|
¢
|
To remove an existing field, drag it to the Recycling Bin in the Toolbox. The field is removed from the layout, but is not deleted from the system.
|
¢
|
To replace an existing row in the layout with another one, drag the new field from Available Fields and drop it on the field that you want to replace.
|
¢
|
To create a panel or row, drag New Panel or New Row into the Current Layout.
|
¢
|
A new panel or row contains two blanks fields. To add more fields to the panel or row, drag New Panel or New Row into the panel again.
|
¢
|
To enter or edit a field label, click the Edit icon within the field and enter the label in the Properties panel; clickSave to create the label.
|
¢
|
To move a field to a different location, drag it to the desired location on the page.
|
¢
|
To edit the tabbing order, click the Edit icon within the field and enter a numeric value in the Tab Order field of the Properties panel; click Save. The tabbing order for each field is represented by numbers such as 1, 2, and 3. You can change one or more numbers to change the order in which users tab to those fields.
|
¢
|
To display each panel as a separate tab instead of displaying all panels on one page, select the Display Tabs as Panels option located next to the Restore Default button.
|
3.
|
Click Save to save your changes.
|
4.
|
Click Save & Deploy to display the updated view in the Sugar User Interface.
|
5.
|
Click View History to view a list of previous changes along with the date and time of each change.
|
a.
|
To preview the changes made at a particular time, click the adjacent Preview button.
|
b.
|
To restore the previous version of the view, click the adjacent Restore button.
|
6.
|
To revert back to the default layout, click Restore Default.
|
Copy/Sync Edit and Detail Views
Modifications made to the Edit View in Layouts can be copied to the Detail View. The Layouts Detail View can also be synced with the Edit View so that any changes made to the Edit View are automatically reflected in the Detail View.
To copy/sync Edit and Detail Views
Follow the steps listed below to sync modifications made to the Edit View of Layouts of a module, for example Accounts, to the Detail View of the Layouts of the same:
1.
|
Click Studio in the Developer Tools section of the Administration page.
|
2.
|
Select Layouts under Accounts in the Modules section.
|
3.
|
Click EditView in the Accounts Layouts pane.
|
4.
|
Drag and drop items between the Toolbox and Layout sections.
|
5.
|
Select the Sync to DetailView checkbox.
|
6.
|
Click Save and Deploy.
|
7.
|
Go to the Accounts module in Sugar to verify that the changes have been deployed
|
To edit the Search form
1.
|
To edit the Search form for the module, click the module, navigate to Search, and select Basic Search or Advanced Search.
|
To edit the Search form of the module’s Sugar Dashlet, navigate to Sugar Dashlet > Sugar Dashlet Search.
To edit the module’s Popup View Search form, navigate to PopupView > Popup Search.
The fields in the current Search form are listed in the Default column, and the available fields are listed in the Hidden column.
2.
|
To remove an existing field from the search form, drag it from the Default list to the Hidden list.
|
3.
|
To add a field to the search form, drag it from Hidden column to the Default column.
|
4.
|
To save your changes, click Save & Deploy.
|
5.
|
To revert back to the default layout, click Restore Default.
|
To preview and restore changes
1.
|
Click View History to view a list of time stamps for changes that were made to a layout, a Search form, or a sub-panel.
|
2.
|
To preview the changes for a timestamp, click the adjacent Preview button.
|
The Preview page provides a Restore button that corresponds to each timestamp. You can use this button to restore the changes made for a specific timestamp. Alternatively, click a timestamp to restore the layout that existed before the changes made at that time.
To edit the Convert Lead form
1.
|
In Studio, select the Leads module and navigate to Layouts.
|
2.
|
Select Convert Lead to view the Convert page.
|
This page displays a list of related modules, such as accounts, opportunities, notes, and so on. Users can create these related record during the process of converting a lead to a contact. You can add and remove related modules as needed.
3.
|
If you want the user to create a record in a related module during lead conversion, select the Required box corresponding to the module. The user will then have to create the related record in order to successfully convert the lead to a contact.
|
4.
|
To copy values from fields that exist in both Leads and a related module to the newly created records, select theCopy Data box corresponding to the related module. The fields must have the same name in both modules. For example, if you add a custom field called Category to both Leads and Notes, and then enable the Copy Data option for the Notes module, the Category field in Leads will be copied into any new Notes created during the convert Lead process.
|
5.
|
To select a record from a module that has a one-to-one relationship, or a one-to-many relationship with the Contacts module (that is, many contact records associated with one record in the related module), select the Allow Selection box. By default, only the Accounts module has a relationship with the Contacts module, hence the Allow Selection box is selected for Accounts.
|
6.
|
To edit a module’s page layout, click the Edit icon, make the necessary changes, and click Save.
|
7.
|
To remove the relationship with a related module, click the Delete icon, and click OK to confirm the removal.
|
The deleted module no longer displays in the list of related modules in the Convert Lead form.
Exporting Module Customizations
You can export a module’s customized layouts, fields, and field labels from one Sugar instance to other Sugar instances. To do this, you will need to package the customizations in Studio, export it to your local machine, and upload it into another Sugar instance. The system applies the customizations to the appropriate layouts, fields, and field labels.
To publish a customized module
1.
|
On the Studio home page, click Export Customizations.
|
The Export Customizations page displays a list of customized modules and the type of customization, such as customized layouts, fields, or labels.
2.
|
Enter the following information:
|
Package Name. Enter a name for the export package. The package will contain the customizations that you select.
Author. Enter your name as the author.
Description. Enter a brief description of the package.
3.
|
Select the customizations you want to export.
|
4.
|
Click Export.
|
The system creates a zip file and displays a dialog box that allows you to open the file or save it to a disk.
5.
|
Select Save to Disk and click OK.
|
On Windows, the system saves the zip file in the Downloads directory.
6.
|
Open the other Sugar instance, upload and install the zip file using Module Loader. For more information, seeModule Loader.
|
Embedding Links and IFrames in a Layout
A Link field allows you to store a URL in a record such as a customer’s website or a link to a related internal or external system. TheURL can either be entered as a normal field in an Edit View, or it can be dynamically generated based on other fields in the record. For example, you can automatically generate a link to a Google map of an account’s address. To do this, click the Generate URLcheck box and insert the following in the Default Value field:
http://maps.google.com/?q=
Next, select billing_address_postalcode from the drop down above the Default Value field and click the Insert Field button.
The default value now reads:
http://maps.google.com/?q={billing_address_postalcode}
You can also embed a view of the website itself in the layout rather than as a link by using the IFrame field. IFrames support regular URLs as well as generated URLs.
You cannot edit generated URLs in a record’s Edit View. You can only change them in the Module Builder or Studio. You can edit regular URLs in a record’s Edit view.
To embed a manually entered URL
1.
|
From the Data Type drop-down list, select IFrame or URL.
|
2.
|
Enter a name for the field.
|
3.
|
Enter the desired max size.
|
4.
|
If using an IFrame, enter the desired height in pixels for the view.
|
5.
|
Click Save to create the field.
|
To embed a dynamically generated URL
1.
|
From the Data Type drop-down list, select IFrame or URL.
|
2.
|
Enter a name for the field
|
3.
|
Click the Generate URL checkbox.
|
4.
|
Insert the base URL into the Default Value field.
|
5.
|
Select a field you wish to include in the URL from the dropdown and click Insert Field.
|
6.
|
Click Save to create the field.
|
Creating Relationships
Typically, a Sugar module has relationships with other Sugar modules. For example, Accounts is related to Contacts, Leads, Opportunities, and several other modules. Related records from these modules display in fields or sub-panels on an account’s detail page. You cannot edit these pre-defined relationships.
In Module Builder, you can create relationships between undeployed modules, and between undeployed modules and deployed modules. If you want to change a relationship after you have deployed the module, you can redefine or delete the relationship and then re-deploy the module package.
In Studio, you can create relationships only between deployed modules. After you deploy a relationship in Studio, you cannot change it.
You create one relationship at a time from the Relationship Editor. When you create a relationship for a module, it is considered to be the primary module and the module that you relate it with is the related module. Depending on the relationship type, the relationship is expressed with sub-panels and related-to fields. When you create a new relationship between two modules, the system automatically creates the necessary sub-panels, related-to fields, and metadata relationships.
Note:
|
It is recommended that you use a Relate field to create a one-way relationship between modules. To create a two-way relationship between modules, use the Relationship Editor.
|
You can also create a relationship between a module and itself. In this case, the relationship becomes a parent-child relationship. For example, you can create a relationship from Accounts to Accounts in order to create sub-accounts within the primary account.
In Module Builder, you can select Activities as the related module but not its sub-modules such as Tasks, Calls, and Meetings. The relationship is automatically reflected in these sub-modules.
In Studio, you can select a sub-module of Activities when you create a relationship. So, when you select Activities as a related module in the Module Builder, you can use Studio to define the relationship further for its sub-modules.
Relationship types
The relationship types are as follows:
One-to-one: Records in the primary module and the related module are uniquely related to each other. For example, an account can be associated with only one contact and a contact can be associated with only one account. This account value will display in the contact’s Detail View, and the contact value will display on the account’s Detail View.
One-to-many: A record in the primary module can have relationships with many records in the related module. For example, an account can be associated with many contacts, and many contacts can be associated with the same account. The Detail View of the primary module will display a sub-panel for the related module, and the Detail View of the related module will display a Related-to field containing a link to the related record.
Many-to-one: Records in the primary module can have a relationship with one record in the related module. For example, an account can be associated with one contact. The Detail View of the primary module will display a field for the related module from which you can select a record, and the Detail View of the related module will show a sub-panel for the primary module from which you can create or select records.
Many-to-many: In this relationship, records in both the primary module and the related module can have relationships with multiple records in each module. For example, an account can be associated with many bugs, and a bug can be associated with many accounts. The Accounts Detail View will display a Bugs sub-panel. Similarly, the Bugs Detail View will display an Accounts sub-panel.
The type of relationship that you can create depends on your choice of primary and related modules. This is because only a module with sub-panels can have a one-to-many or a many-to-many relationship with another module. A sub-panel is needed to show all the related records from the other module.
For example, with Accounts as the primary module and Knowledge Base as the related module, you can create only a one-to-one relationship between them. This is because Knowledge Base lacks a sub-panel. Therefore, Accounts cannot display related records from Knowledge Base. However, if Knowledge Base is the primary module and Accounts is the related module, you can create a one-to-many relationship between them because Accounts has sub-panels and, therefore, Knowledge Base can display related records from Accounts.
If you are creating a relationship between a custom module and a Sugar module, then you can choose any relationship type because all custom module types include at least one sub-panel.
Sub-panel types
Sugar provides many sub-panel types for your use. When you create a relationship that involves sub-panels, Sugar displays all sub-panel types available for that module for your selection. A sub-panel can display different sets of fields depending on the primary module to which it is related. For example, there are several types of sub-panels for Contacts. The Contacts sub-panel that appears under Accounts contains different fields than the Contacts sub-panel that appears under Cases.
The Default type of sub-panel contains the most commonly used fields in the module. Every module has a Default type that contains a set of fields to display as a sub-panel. Select Default if you want to display the most commonly used fields in the sub-panel in the relationship that you create.
For example, if you create a one-to-many relationship between Calls and Accounts, you can select a sub-panel type for the Accounts sub-panel in the Calls Detail View. To use a sub-panel consisting of the most commonly used fields from Accounts, select the Defaultsub-panel type; to use the Accounts sub-panel from the email’s Detail View, select ForEmails.
You can create relationships in Module Builder as well as in Studio. However, there are some differences, which are noted in the table below:
Relationship in Module Builder
|
Relationships in Studio
|
You can create relationships with other Sugar modules as well as other modules within any undeployed package.
|
In Studio, you can create relationships only between deployed modules.
|
If you want to change a relationship after you have deployed the module, you can redefine or delete the relationship and then re-deploy the module package.
|
You can delete a relationship after you deploy it, but you cannot redefine it.
|
You can select Activities as the related module but not its sub-modules such as Tasks, Calls, and Meetings. But the relationship is automatically reflected in these sub-modules.
|
You can select a sub-module of Activities when you create a relationship.
So, when you select Activities as a related module in the Module Builder, you can use Studio to further define the relationship for its sub-modules.
|
To create a relationship in Module Builder
1.
|
Click the custom module to view its details.
|
2.
|
Click View Relationships.
|
Sugar displays existing relationships, if any, on the page.
3.
|
Click Add Relationship.
|
4.
|
To localize the relationship label, select the language pack from the Language drop-down list.
|
5.
|
Select the relationship from the Type drop-down list.
|
If you select a One-to-One relationship, you can choose a related module. Sugar displays the related module as a field in the primary module, and the primary module as a field in the related module.
If you select a One-to-Many relationship, you can select a related module. Sugar displays sub-panels of the related modules in the Detail View of the primary module. The sub-panel options vary depending on the related module that you select.
If you select a Many-to-One relationship, you can select a related module. Sugar displays a the primary module as a sub-panel in the Detail View of the related module.
If you select a Many-to-Many relationship, you can select sub-panels for the primary module as well as the related module.
6.
|
From Related Module drop-down list, select the module you want to relate to the primary module.
|
7.
|
From the Subpanel field for the related module, select the sub-panel type that you want displayed on the detail page of the primary module.
|
8.
|
From the Subpanel field for the primary module, select the sub-panel that you want displayed on the detail page of the related module.
|
9.
|
Click Save to create the relationship.
|
The new relationship displays under the Add Relationship button in the middle panel. Sugar appends it with an asterisk to denote a custom relationship.
To create a relationship in Studio
1.
|
Select the module in Studio and click Relationships.
|
Sugar displays a list of existing relationships for the primary module on the page.
2.
|
To create a relationship, click Add Relationship.
|
The Relationship Editor displays on the page.
3.
|
Follow the process described in To create a relationship in Module Builder.
|
To manage a relationship
1.
|
To edit a relationship, in Module Builder, click its name in the Relationships list and make the necessary changes in the Edit Relationship tab and save it.
|
You cannot edit or delete relationships in Studio.
2.
|
To delete a relationship, click Delete.
|
History Subpanel
By default, the History subpanel of account record will include emails associated with any of the account’s related contacts. This functionality provides a fuller view of the interactions related to the current account record. The same functionality is also available on the Cases and Opportunities modules with it being enabled for cases by default in addition the Accounts module. The History Subpanel administration section allows administrators to enable or disable the inclusion of related contact records’ emails for the Accounts, Cases, and Opportunities modules.
To enable or disable a module to include related contacts’ emails in its History subpanel, follow these steps:
- Navigate to Admin > History Subpanel.
- To enable a module to include related contacts’ emails in its History subpanel, click to check the corresponding box. To disable a module, click to uncheck the corresponding box
- Click Save.
Rename Modules
Rename Tabs is now labeled Rename Modules. With this feature, module names are displayed in singular and plural form, depending on their use. For example, if the module name is Contact (for singular) and Contacts (for plural), the module tab is displayed asContacts and options in the Actions bar display as Create Contact, View Contacts, and so on. This also applies to every instance of the module name across the system.
You can also change the names of the modules appearing within the application using singular and plural labels for the module names. For example, Contact can be modified to Person and Contacts can be modified to People.
To rename modules
1.
|
In Developer Tools, click Rename Modules link.
|
This displays the Administration » Rename Modules page.
2.
|
Click the Edit icon located next to the module name.
|
This displays the Singular Label and Plural Label fields.
3.
|
Input the information in the fields to define the singular and plural names of the module.
|
4.
|
Click Save.
|
Display Module Tabs and Subpanels
This option enables you to hide or display selected module tabs and sub-panels from users and reorder them as needed.
When you hide a module tab from users, it is not visible to the users when they log into Sugar. However, if the hidden module is related to a module that is visible to users, it displays as a sub-panel in the Detail View of the related module. So users can still access related records of the hidden module from the Detail View of the related module.
Note: Use roles to block users completely from accessing a module. For more information, see Role Management.
When you hide a sub-panel, users cannot view related records from the Detail View of a related module.
You can allow users to configure tabs for modules that they can access from their User Preferences page. This will enable users to override the global settings that you set with this option.
By default, the following modules are hidden:
- Projects
- Bug Tracker
Note: You cannot hide the Home tab.
Follow the steps listed below to configure module tabs and subpanels:
- Go to Developer Tools and select Display Module Tabs and Subpanels.
This displays all the module tabs and sub-panels on the Select Module Tabs and Subpanels page. - To hide a module, drag it from the Displayed Tabs column and drop it in the Hidden Tabs column; to display a module, drag it from the Hidden Tabs column and drop it in the Displayed Tabs column.
- To rearrange the display order of a tab, drag and drop it into the desired position.
- To prevent users from configuring module tabs, deselect the Allow users to configure tabs option.
- To hide a sub-panel, drag it from the Displayed Subpanels column and drop it into the Hide Subpanels column. To display a sub-panel, drag it from the Hidden Subpanels column and drop it in the Displayed Subpanels column.
- Click Save to save the configuration; click Cancel to exit the page without saving your changes.
Configure Shortcut Bar
Use this option to select the modules for which Quick Create forms would be available on the Shortcut bar. By default, Cases, Bug Tracker, Documents, and Targets are disabled, hence icons for these modules do not display in the Shortcuts bar.
To enable or disable Quick Create forms for a module
1.
|
To enable the Quick Create form for a module, select the module from the Disabled Modules list and drag it to theActive Modules list.
|
To disable the Quick Create form for a module, select the module from the Active Modules list and drag it to the Disabled Modules list.
2.
|
Click Save to update the settings.
|
Configuring Grouped Modules
You can use the Configure Grouped Modules feature to organize modules within groups. Users can select these groups to view the modules within those groups. For example, you can group the Contacts, Leads, and Opportunities modules under a Sales group, and the Cases, Bug Tracker, and Products modules under a Support group. Users can then select either the Sales group or the Support group to view the corresponding set of modules.
You can add the same module to multiple groups. For example, Contacts can be part of the Sales group as well as the Marketing group.
The system provides following group tabs:
•
|
Sales
|
•
|
Marketing
|
•
|
Support
|
•
|
Activities
|
•
|
Collaboration
|
You can change the labels for any of these tabs and also add new groups, if needed.
Users have the ability to change the configuration to grouped modules or ungrouped modules from their User Preferences page.
To configure and manage grouped modules
1.
|
In Developer Tools, click Configure Grouped Modules.
|
Sugar displays the default groups on the Configure Grouped Modules page. The associated modules are listed below each group tab.:
2.
|
To edit the name of a group tab, click the Edit icon, located beneath the group name, and enter the new name in the text field; click Save.
|
Sugar displays the new group name.
3.
|
To remove a module tab from a group tab, place the cursor on the name and drag it to the Remove Module from Group bucket on the left.
|
The module no longer displays under the group tab.
4.
|
To add a module to a group tab, select it from the Modules list on the left, drag and drop it into the Group list, just below the Edit and Delete icons.
|
Under a group tab, you can rearrange the order of the module tabs by selecting a tab name and dragging it to a different location in the list.
5.
|
To save your changes and make them available for users, click Save & Deploy.
|
To add a new group tab
1.
|
Click Add Group.
|
This displays the New Group page.
2.
|
To name the new group tab, click the Edit icon, enter the name in the text field, and click Save.
|
3.
|
To add a module tab under the new group tab, select it from the Modules list and drop it in the group, below theEdit and Delete icons.
|
4.
|
To save your changes and make it available for users in the Sugar User Interface, click Save & Deploy.
|
Dropdown Editor
Most modules display at least one drop-down field containing a list of values from which users can choose. For example, when users create an account, they can choose a specific industry type and an account type in the respective drop-down fields.
As the administrator, you can use the Dropdown Editor to create new drop-down lists, and to edit values of a drop-down list to suit your organization’s needs. When you create a new drop-down field in Studio, you must associate it with an existing drop-down list.
Note:
|
You cannot use a custom Stage drop-down list when you create a quote.
|
To create a drop-down list
1.
|
Scroll down to the Developer Tools section on the Administration home page, and select Dropdown Editor.Alternatively, on the Studio home page, click the Dropdown Editor tab located at the bottom of the page.
|
Sugar displays the Dropdown Editor page, which contains existing drop-down lists.
Note:
|
You can also add a drop-down list in the process of creating a custom field with the DropDown data type in Studio.
|
2.
|
Click Add Dropdown.
|
Sugar displays fields to add a new drop-down listin the Edit drop-down tab.
The Name field displays the name that you specified. The system automatically appends _list to the drop-down name to identify the data type in the database. You can use your own data type naming convention if needed.
3.
|
From the Language drop-down list, select a pre-installed language pack of your choice.
|
4.
|
In the Item Name field, enter a name for the item.
|
5.
|
This is the name that is saved in the Sugar database.
|
6.
|
In the Display Label field, enter a label name for the item.
|
This is the label that displays to users.
7.
|
Click Add.
|
The name of the item displays above the Item Name field. This is the name that displays in the User Interface. To add additional items, click Add and repeat the process.
8.
|
To display the items in ascending order, click Sort Ascending; to display them in descending order, click Sort Descending.
|
9.
|
Click Save to save the drop-down list.
|
The list displays in the dropdown list on the Edit Field tab of a module.
To edit an existing drop-down list
1.
|
Select an existing drop-down field from the Dropdown Editor.
|
2.
|
To change an item’s display label, click the corresponding Edit icon and enter the new label.
|
3.
|
To remove an item, click the corresponding Delete icon.
|
4.
|
To add a new item, enter the item name and display label in the fields below; to add additional items, click Add and enter values for the next item.
|
5.
|
Click Save to save your changes; to undo your changes, click Undo; to redo your changes, click Redo.
<<Back |
