empty
| 
Free Trial
Demo
Buy NowSugar Enterprise 5.2 Documentation
Sugar Enterprise Installation and Administration Guide
Version 5.2
|
|
|
|
Chapter 2 Administering Sugar : System
The options listed under this section allow you to configure system-wide settings that apply to all users in your organization.
Use this option to configure the system-wide settings according to your organization’s specifications. Users can override some default settings, such as the datetime format, on their My Accounts page.
Listview items per page. Enter the maximum number of records you want displayed in the list view. The system paginates lists that contain more than the specified number of records.
Listview items per page (Wireless). Enter the maximum number of records you want displayed in the list view when users log in from a wireless device such as a Smart phone. The default is 10 records per page. The system paginates lists that contain more than the specified number of records.
Display server response times. By default, the footer on every page displays the time taken to respond when users attempt to perform an action, such as logging in or opening an item, in Sugar. Deselect this box if you do not want to display the response time.
Prevent user customizable Homepage layout. Select this box if you want to prevent users from moving Sugar Dashlets on the Home page. However, users can still create additional Sugar Dashlets and pages.
Maximum number of Sugar Dashlets on Homepage. Enter the maximum number of Sugar Dashlets you want displayed on the Home page. Users will not be able to add more than the number of Sugar Dashlets that you specify. The default value is 15.
Subpanel items per page. Enter the maximum number of records you want displayed in the List View. The system paginates lists that contain more than the specified number of records.
Subpanel items per page (Wireless). Enter the maximum number of records you want displayed in the list view when users log into Sugar from a wireless device. The default is 3 records per page. The system paginates lists that contain more than the specified number of records.
Display tabs on login screen. By default, the Login page displays the Sugar module tabs on the Login page. Deselect this box if you do not want to display these tabs on the Login page.
Prevent user customizable subpanel layout. Select this box if you want to prevent users from dragging and dropping sub-panels to a different location in their Detail View layout.
Show Full Name (not Login). Select this box if you want the full name for users displayed instead of their login names.
System Name. This field displays your system name.
|
2.
|
|
3.
|
To restore the default settings, click Restore; to exit the page without saving your changes, click Cancel.
|
You can upload your organization’s logo to display in the Sugar User Interface and in PDF copies of quotes.
Current logo. Displays your current organization’s logo that displays in the User Interface.
Upload new logo. Enter the path to the location of the logo that you want to upload from your local machine. Or, click Browse to navigate to the location of the logo on your local machine. The dimension should be 212 X 40, with the standard transparent background color, in PNG or JPG format.
Logo used in Quotes. Displays your organization’s logo at 85% of the default size that displays in PDF copies of quotes.
Upload new Quotes Logo. Enter the path to the location of the logo that you want to upload from your local machine. Or, click Browse to navigate to the location of the logo on your local machine. The system displays this logo in PDFs of quotes that your users create. This file must be in JPG format.
|
2.
|
|
3.
|
To restore the previous settings, click Restore; to exit the System Settings page without saving your changes, click Cancel.
|
If your organization has implemented LDAP or Active Directory authentication, you can also enable authentication in Sugar. When your users attempt to log into Sugar, the application authenticates them against your LDAP directory or Active Directory. If authentication is successful, the user is allowed to log into Sugar. If you are using LDAP with SOAP, you will need to specify the encryption key for the system and forward the key to your users.
If your users are using the Sugar Plug-in for Microsoft Outlook, they will need to enter this key number in Outlook. The Sugar Plug-in for Microsoft Outlook uses this key to encrypt user passwords before forwarding them to Sugar for authentication. Sugar decrypts the password with the same key and forwards the user names and passwords to the LDAP server for authentication. If authentication is successful, the users are allowed to access Sugar through the Sugar Plug-in for Microsoft Outlook.
|
1.
|
In the LDAP Authentication Support sub-panel, select the Enable LDAP box and enter the following information:
|
Server. Enter the LDAP server name.
Port Number. Enter the server’s port number.
Base DN. Enter the base DN name.
Bind Attribute. Enter the attribute name that is used to bind the user’s name in LDAP.
Login Attribute. Enter the attribute name that is used to search for the user in LDAP.
Authenticated User. Enter the user name.
Authenticated Password. Enter the user’s password.
Auto Create Users. Select this option check the Sugar database for the user name and add it if it does not exist in the database.
Encryption Key. If you are using LDAP with SOAP, enter the encryption key to encrypt user passwords in the Sugar Plug-in for Microsoft Outlook.
|
2.
|
|
3.
|
If you are using a proxy server to connect to the Internet, you will need to enter the information here to allow the system to check for Sugar updates and to validate license keys as described in “License Management” on page 24.
Use proxy server. If you want to connect to the Internet through a proxy server, select this option.
Proxy Host. Enter the name of the proxy server host
Port. Enter the port number for the proxy host.
Authentication. Select this box if you want to enable proxy authentication to allow Sugar to connect to the company’s proxy server.
User Name. Enter the user name.
Password. Enter a password for the user.
|
2.
|
|
3.
|
Select this option to integrate your organization’s self-service portal with Sugar. This enables your customers to access Sugar records such as Notes and Cases.
|
1.
|
Select the Enable self-service portal integration box.
|
|
2.
|
|
3.
|
|
1.
|
Select the Enable SkypeOut integration box.
|
|
2.
|
|
3.
|
If you have installed the Sugar Plug-in for Microsoft Word, this option allows you to perform a mail merge with Word documents. For example, you can merge contact information from Sugar with form letters created in Microsoft Word.
|
1.
|
Select the Enable mail merge box.
|
|
2.
|
To restore the previous setting, click Restore. To exit the System Settings page without saving your changes, click Cancel.
Enable this option if you would like all users to use the Sugar application on their local machines without connecting to the Sugar server. If not, you can enable specific users to use the Offline Client.
Validate user IP address: Select this option to validate, for security purposes, the IP addresses of users who log into Sugar.
Log slow queries. Select this option to log the system’s slow responses to user queries in the sugarcrm.log file. This information is for performance tuning investigation.
Maximum upload size. Enter the maximum file size, in bytes, that users are allowed to upload.
Portal Session Timeout. Enter the maximum time, in seconds, for a SugarPortal session. The session will timeout when the time limit is reached.
Log memory usage. Select this option to record memory usage in the sugarcrm.log file.
Slow query time threshold. Specify the threshold, in milliseconds, that defines slow queries. Queries that take longer than the threshold time are logged in the sugarcrm.log file. This information is for performance-tuning investigation. If you have enabled the Tracker Queries option on the Tracker Settings page, you can run the pre-defined Slow Queries report to view slow queries.
Display stack trace of errors. When you select this option, if an error occurs when users are running the application, the system displays where the error occurred in the application’s stack trace. This information is for debugging purposes.
Developer Mode. Select this option to disable caching so that you can immediately view changes made to language, vardefs, and template files.
|
2.
|
|
3.
|
To restore the previous settings, click Restore; to exit the System Settings page without saving your changes, click Cancel.
|
The Sugar Logger logs events that occur in the Sugar application. By default, the logs are written to sugarcrm.log in the Sugar root directory.
When you upgrade to Sugar 5.2, Sugar automatically parses your Logger settings from the log4.php properties file of your previous Sugar version and populates the Logger Settings sub-panel with the information.
|
•
|
debug: Logs events that would help to debug the application.
|
|
•
|
info: Logs informational messages.
|
|
•
|
warn: Logs potentially harmful events.
|
|
•
|
error: Logs error events in the application.
|
|
•
|
fatal: Logs severe error events that leads the application to abort. This is the default level.
|
|
•
|
security. Logs events that may compromise the security of the application.
|
|
•
|
off. The logger will not log any events.
|
When you specify a logging level, the system will create log files for the specified level as well as higher levels. For example, if you specify ‘Error’, the system creates log files for ‘error’, ‘fatal’, and ‘security’.
Log File Name. Specify a name for the log file.
Extension. Enter the file extension. The default is .log.
Append After File Name. From the drop-down list, select a time period to append to the file name. This makes it easier to identify the log that you want to view.
Log Level. From the drop-down list, select the event level that you want to capture in the log file. The default is fatal.
Default Date Format. Enter the default date format for the log file. This format must be supported by strftime. The default is %c.
Maximum Number of Logs. Specify the maximum number of log files to save. When the number of log files exceed this limit, Sugar deletes the log file that was created first. The default is 10 logs.
|
1.
|
Click All to view the whole log.
|
|
2.
|
Click Mark Point to show the log from that point onward. When you click Refresh From Mark, the log displays actions that occurred since the time you clicked Mark Point.
|
|
3.
|
To search the log by keyword, enter it in the Search box; to search the log by a regular expression, enter it in the Search box and check the Reg Exp box. Press Enter on your keyboard to search the log.
|
Use this option to schedule jobs such as monitoring email in-boxes, running reports, and dispatching campaign emails.
The Scheduler integrates with external UNIX systems and Windows systems to run jobs that are scheduled through those systems. You can schedule the following types of jobs:
Process Workflow Tasks. This job processes workflow events. If you set a timed trigger for an event, for example, when a lead is a week old, then it finds the predefined workflow actions and fires them when appropriate.
Run Report Generation Scheduled Tasks. This job runs reports and emails them to the assigned user as per the schedule specified for a given report. The reports are sent to the user through an email from a PHP script that runs at regular intervals to send out the emails at the appropriate time. The user can choose which reports to receive and how often to send the reports in the Reports module of the Sugar application.
Prune Tracker Tables. This job deletes older activity data.
Check Inbound Mail Accounts. This job monitors inbound emails in active mail accounts that you set up using the Inbound Email option in the Email panel of the Admin page.
Run Nightly Process Bounced Campaign Emails. This job polls any mail account in which, the “Possible Actions” parameter is set to “Bounce Handling”. This is an essential component of monitoring mass email campaigns.
Run Nightly Mass Email Campaigns. This job processes the outbound email queue for your organization’s mass campaign emails.
Prune Database on 1st of Month. This job reads all the tables in your Sugar database, finds records that have been soft-deleted (deleted = 1), creates a large SQL file, and physically deletes those records on the 1st of every month. It is mostly a performance job, and is not essential to the use of Sugar. The backup files are placed in cache/backups with time-stamped filenames.
Update Tracker Session Tables. This job sets the status of timed-out sessions.
For UNIX and Linux systems, you will need to add a new cronjob to your Crontab. For Microsoft Windows, you can use the Task Scheduler.
|
1.
|
At the command prompt, type crontab -e.
|
* * * * * cd /path/to/sugar/crm; php -f cron.php > /dev/null 2>&1
|
3.
|
Ensure that the /path/to/ is correct for your instance.
|
In a properly configured virtual host environment provided by your host, Apache will run as your Login user ID for files in your virtual directory. If you are unsure, contact the Customer Service department for your host.
|
a.
|
Search for a file named httpd.conf. Typically, this file is located in the /etc folder. It will vary with the distribution.
|
|
b.
|
Open the file using a text editor and locate a line that starts with “User”. The word(s) that follow it directly is the name of the User that Apache will run as on your system.
|
The Sugar Scheduler is designed to work with PHP and its extensions; specifically the database connector, the IMAP libraries, and the cURL libraries.
|
a.
|
Type which php. On most correctly configured PHP installations, you will find the binary in /usr/bin or /usr/local/bin. If so, move on to Step 3.
|
|
b.
|
Type find / -name php. Typically, this command will return a long list. Parse through the list to find an executable file named php.
|
|
c.
|
If you cannot find the PHP binary, scroll down to the Troubleshooting Tips at the end of this section and read item No. 2.
|
|
3.
|
Create a cronjob for the Apache user
|
|
a.
|
Type crontab -e -u [the Apache user].
|
* * * * * cd /path/to/sugar/crm; php -f cron.php > /dev/null 2>&1
|
c.
|
To fine tune this job, change the first two “*”. The first is the “Minutes” value, the second is the “Hours” value.
|
"*/3 * * * * cd /path/to/sugar/crm; php -f cron.php > /dev/null 2>&1
|
a.
|
At a terminal prompt, copy and paste the command for your cronjob, and run it; the logic here is that if the command will execute successfully when run manually, the crontab will be able to execute successfully as well.
|
* * * * * cd /var/www/html/sugarcrm; php -f cron.php > /dev/null 2>&1
This folder should contain the cron.php file.
If your system has a 4.x version of PHP, the PHP-CGI binary is named php.exe and is typically located in the root folder of your PHP install folder. To allow it to interact with the dynamic libraries, specify the location of the php.ini file. This can vary from system to system. If you are unsure, assuming that php.exe is located in c:\php, enter the following command at the command prompt:
The system will identify the php.ini file and its location.
If your system has a 5.x version of PHP, the PHP-CGI binary is named php-cgi.exe (not php-cli.exe) and is typically located in the root folder of your PHP install folder. To allow it to interact with the dynamic libraries, specify the location of the php.ini file. This can vary from system to system. If you are unsure, enter the command described above.
The system will identify the php.ini file and its location.
|
a.
|
At the bottom of the default screen, you will see the contents of the commands you need to add to a batch file.
|
b.
|
Open notepad.exe, copy and paste what Sugar’s recommendation into a blank file.
|
|
Note:
|
This is only a recommendation. It may not work for your particular instance. Check the folder paths because they are often the cause for problems with the Scheduler.
|
|
a.
|
Click Start and navigate to Control Panel/Scheduled Tasks/Add Scheduled Task.
|
|
c.
|
Schedule a daily job, and ensure that you select Open advanced properties for this task when I click finish.
|
|
d.
|
|
e.
|
Check off Repeat task to enable the fields below it, and select Every Minute or specify the interval you think is appropriate.
|
|
1.
|
Job Name. Enter a name for the job.
Status. From the drop-down list, select Active to run the job at the specified intervals; select Inactive if you only want to save the job schedule information but not run the job.
Job. Select a job from the drop-down list. The OR field is not used.
Interval. Specify the time interval to check for new scheduled jobs.
|
3.
|
For advanced options, click the Advanced Options link below the Job field.
|
The Advanced Options sub-panel displays below.
Execute If Missed. Select this box to run any jobs that the scheduler missed.
Date & Time Start. Click the Calendar icon and select the start date for the job; select the time, in hours and minutes, from the adjacent drop-down list.
Date & Time End. Click the Calendar icon and select the end date for the job; select the time, in hours and minutes, from the adjacent drop-down list.
Active From. From the drop-down list, select the time, in hours and minutes, when the job becomes active.
Active To. From the drop-down list, select the time, in hours and minutes, when the job becomes inactive.
|
5.
|
|
6.
|
To export one or more scheduler definitions in a .csv file format to a local machine, select them from the list and click Export.
|
|
1.
|
The Schedule List page displays on the page.
|
2.
|
Select any job from the job list to view its settings or the Job log. You can edit, duplicate, or delete the settings. You can also delete a job by clicking the del icon corresponding to the job in the Schedule list.
 |
|
3.
|
|
4.
|
Make the necessary changes and click Save to update the settings; click Cancel to exit the page without saving your changes.
|
|
1.
|
The Sugar Scheduler fails to run even though the cron.log file shows that the crontab is triggering the new job.
|
|
•
|
The Apache user's PATH does not include the location of the php.ini file, and thus the external libraries (such as mod_mysql and mod_imap) are unavailable at run time.
|
|
•
|
Change the crontab entry to include a PHP switch to explicitly define a php.ini to use as shown below.
|
* * * * * php -c /path/to/your/php.ini -f cron.php > /dev/null 2>&1"
|
•
|
Determine if this is an option at this time by finding either “curl” or “wget” on your system. This is done with the commands “which curl” and “which wget”.
|
If you use cURL, your crontab entry should look as follows:
* * * * * curl --silent http://yourdomain/yoursugarcrminstance/cron.php
If you use wget, your crontab entry should look like:
* * * * * wget -q http://yourdomain/yoursugarcrminstance/cron.php
|
Note:
|
Both curl and wget have numerous switches that do not always map to different versions on different platforms. Experiment in the terminal until you find the “perfect” line, and add it as the line for your crontab entry.
|
|
1.
|
The most common problem is that the PHP binary does not have the proper libraries available at run time. As a result, it cannot make calls to your database or to your Email server. To force PHP to be aware of these libraries, it needs to access the php.ini file, which in turn tells it where to find everything that is available.
|
|
a.
|
Locate the php.ini file: if you are unsure, run the following command:
|
The system identifies the php.ini file and its location.
|
2.
|
The second most common breakage is incorrect paths to the extensions that PHP needs; a map is useless if the information is bad.
|
|
a.
|
Open php.ini in your favorite text editor.
|
|
c.
|
The pertinent entry is “extension_dir”.
|
|
d.
|
Keeping in mind that this file piggybacks on Window's $PATH$ variable, double-check the paths listed.
|
|
e.
|
Correct any errors - sometimes giving an absolute path solves hard-to-diagnose problems, for example, full path listing from c:\... onwards.
|
|
f.
|
Open your php.ini file in a text editor.
|
|
i.
|
Make sure that the necessary extensions are uncommented (no “;” preceding the line). The bare minimum for Sugar Scheduler to run is to have php_curl, your database connector, typically php_mysql (for PHP5), and php_imap.
|
Use this option to capture system configuration for diagnostics and analysis. The diagnostic tool pulls up system information and stores it in a zip file on the server for download. When you send a help request to Customer Support, you can attach the file because it summarizes all the basic information required to resolve the problem.
|
1.
|
|
2.
|
To capture specific configuration information, click the Advanced link below the Execute Diagnostic button.
|
The system displays a list of system configuration files. By default, the system captures configuration information for all the selected files.
SugarCRM Config.php - Copies the config.php file from the root directory after replacing the DB password with asterisk for security purposes.
SugarCRM Custom directory - Copies the custom directory to a zip file to enable Customer Support to know what has been customized through the Layout Editor.
phpinfo() - Executes phpinfo and stores it in a file.
MySQL - Configuration Table Dumps - copies a few tables from the database and replaces sensitive information with asterisk for security purposes.
MySQL - All Tables Schema - writes the schema for all tables to an HTML file.
MySQL - General Information - Pulls up some general information, like MySQL version, character sets, etc.
MD5 info - Runs md5 checks on all files in the sugar directory and compares it against a stock Sugar installation’s md5s. This enables Customer Support to learn which, if any, files have been manually customized.
BeanList/BeanFiles files exist - If a custom module has been loaded, and the author did not define these references correctly, it can cause problems. This action checks all the references to ensure they are correct.
SugarCRM Log file - copies the log file.
Sugar schema output (VARDEFS) - copies the Sugar database schema.
|
3.
|
Deselect the ones you do not want to view and then click Execute Diagnostic.
|
|
4.
|
To view the file, click the Download the Diagnostic file link at the bottom of the page; to delete the file, click the Delete the Diagnostic file link.
|
|
5.
|
If you choose to download the file, the File Download dialog box displays on the page. To view its contents, click Open, and click the file you want to view. To save the zip file contents, click Save, and select a location on your local machine.
|
When you obtain the Sugar upgrade .zip file from Sugar, you can save it to your local machine and upload it into Sugar using the Upgrade Wizard. For more information, see the Sugar Upgrade Guide.
Use this option to backup the Sugar configuration files. Note that this option does not backup the database.
|
1.
|
|
2.
|
In the Directory field, specify a directory that is writable by the same user as the Apache process.
|
|
4.
|
To ensure that backup can be performed, click Confirm Settings.
|
|
5.
|
Click Run Backup to create the .zip file of your Sugar application files.
|
|
Note:
|
Use this option to upgrade and rebuild data from a previous version of Sugar for the current version of the program. You also use this option to convert a Sugar installation to offline mode.
Upgrade Teams: Scans all users to ensure that they each have a personal team, and that they are members of the global team, automatically fixing any discrepancies after an upgrade. It may also be useful to restore all users' personal teams if they become corrupted or are removed for any reason.
Quick Repair and Rebuild: Repairs and rebuilds the database, extensions, vardefs, Sugar Dashlets, and so on for selected modules. Click this option, select the modules you want to repair, and click Repair. You also use this option to clear any custom Sugar Feed link types from the cache.
Repair Database: This option is applicable to MYSQL databases only. It repairs your Sugar database based on values defined in the vardefs. You can choose to display the SQL that will be executed on the screen, export it, or execute it.
Clear Chart Data Cache: Removes cached data files that charts use.
Clear Template Data Cache: Removes cached template files. Click this option, select the modules you want to repair, and click Repair.
Clear Vardefs Data Cache: Removes vardefs from the cache. Click this option, select the modules you want to repair, and click Repair.
Rebuild .htaccess file: Rebuilds the .htaccess file to limit access to certain files directly.
Rebuild Audit: Rebuilds the audit table.
Rebuild Config File: Rebuilds the config.php file by updating the version and adding defaults when not explicitly declared. Click this option to check the file and if, necessary, click Rebuild.
Rebuild Extensions: Rebuilds extensions including extended vardefs, language packs, menus, and administration
Rebuild Relationships: Rebuilds relationship metadata and drops the cache file.
Rebuild Schedulers: Rebuilds your out-of-the-box Scheduler Jobs. Click this option and then click Rebuild.
Rebuild Sugar Dashlets: Rebuilds the cache file for Sugar Dashlets.
Rebuild Workflow: Rebuilds the workflow cache and compiles plug-ins.
Rebuild Javascript Languages: Rebuilds Javascript versions of language files.
Rebuild JS Compressed Files: Copies original Full JS Source files and replaces existing compressed JS files.
Rebuild JS Grouping Files: Re-concatenates and overwrites existing group files with latest versions of group files.
Rebuild Minified JS Files: Copies original Full JS Source Files and minifies them, then replaces existing compressed files.
Repair JS Files: Compresses Existing JS files - includes any changes made, but does not overwrite original JS Source files
Repair Teams: Rebuilds private team membership based on user reporting hierarchy. Click this option, select one or all of the following: Global team, Private team, and team hierarchy, and click Rebuild.
Repair Roles: Repairs roles by adding all new modules that support access control as well as any new access controls to existing modules.
Repair Indexes: Validates and, optionally, repairs database indexes against definitions in vardef files.
Repair Oracle VARCHAR2 Columns: Changes the semantics of VARCHAR2 columns from byte to char; necessary for UTF-8, MBCS support.
Repair Inbound Email Accounts: Repairs Inbound Email accounts and encrypts account passwords.
Remove XSS: Removes XSS Vulnerabilities from the database. Click this option, select a module, and click Execute. If any XSS strings are found, the system lists them in the Object(s) found field below.
Repair Activities: Repairs Activities (Calls, Meetings) end dates.
Check Reports: Checks whether reports are still valid after an upgrade and lists any invalid reports that are found during the check.
Enable/Disable Seed Users: Enables or disables seed users populated during demo installation. Click this option, and if the seed users are enabled, click Deactivate to disable them. If the seed users are disabled, click Activate to enable them.
For each new currency that you define, enter the name, symbol (for example, $), conversion rate to the US $, the currency code (such as CDN for the Canadian dollar). Set the Status to Inactive if you do not want users to use this currency for transactions.
Use this option to set system-wide default formats for date, time, language, name, and currency. If you are using MySQL, you can also specify the collation order for records in the application.
Default Date Format. From the drop-down list, select a date format for all records such as Quotes and Contracts. Users can override the default format by setting a different date format in their My Account page.
Default Time Format. From the drop-down list, select a time format to display in all records such as Cases. Users can override the default format by setting a different time format in their My Account page.
Default Language. From the drop-down list, select the default language for the Sugar User Interface. Users can select a different language from the login page, provided they have installed the appropriate language pack.
Default Name Format. Enter the default salutation and name format to display in list views and detail views. You can specify any combination of salutation first name, and last name. For example: Mr. John Smith, Mr. Smith, or John Smith. Users can override the default format by setting a different time format in their My Account page.
Use this sub-panel to override the default currency that you set during installation. On the My Accounts page, users can override the default currency that you specify in this panel.
Currency. Enter the name of the currency that your organization uses to conduct business.
Currency symbol. Enter the symbol for the currency.
ISO 4217 Currency Code. Enter the ISO code for the currency.
1000s Separator. Specify a delimiter to separate thousands when users specify a numeric value for the amount.
Decimal Symbol. Specify a default decimal symbol.
Use this panel to specify export settings such as the delimiter used to separate data in export files and the default character set used to export data from Sugar. The settings you specify here apply to all users in the organization. However, users can define a different default export character set on their My Account page to export data from Sugar.
By default, Sugar uses UTF-8 to store data and CP1252 to export data. For locales that use character encoding other than CP1252, you must specify the appropriate default character set. This ensures that the character set used by the Sugar system to create the exported file is mapped to the correct character set on the user’s machine. For example, MS Windows uses SJIS in Japan. So, for users in this locale, you will need to select SJIS as the default export character set.
By default, both users and administrators can export files from Sugar. However, you can prevent users from exporting files.
Export Delimiter. Specify the delimiter, such as a comma or a period, to use while exporting data.
Default Export Character Set. The default is CP 1252. For locales other than US and Western Europe, select the appropriate character set from the drop-down list.
Disable export. Select this option if you want to prevent end users and users with administrative privileges from exporting data.
Admin export only. Select this option to allow only users with administrative privileges to export data.
This sub-panel displays only if you are using the MYSQL database. You can select the desired collation order from the drop-down list. The default is utf8_general_ci.
Use this option to enable the system to track user actions and other information for Sugar modules, including custom modules.
Sugar uses this information to create tracker reports. For information on tracker reports, see the Sugar Enterprise User Guide.
Tracker actions. By default, this option is enabled to allow you to track user actions such as modules accessed on a particular day and the actions performed in those modules such as viewing or editing records.
Tracker sessions. Enable this option to track a user's session data such as session round trips, start and end dates.
Tracker performance. Enable this option to track performance-related information such as database access, file access, server response time, and memory usage.
Tracker queries. Enable this option to track SQL queries that exceed the slow_query_ time_msec limit set in the config.php file. If any query exceeds the number of milliseconds defined in this setting and the Log Slow Queries option is enabled on the System Settings page, then the query will be logged in the database.The queries tracked will substitute the runtime SQL values with the ‘?’ character so that the SQL pattern is treated as a single slow query entry.
Log Slow queries. Enable this option to log slow queries. This information is for performance-tuning investigation. If you have also enabled the Tracker Queries option, you can run the pre-defined Slow Queries report to view slow queries.
Number of days of Tracker data to store when Scheduler prunes the tables. Enter the number of days of data to be retained after the Prune Tracker Tables scheduler is run.
Slow query time threshold. Specify the threshold, in milliseconds, that defines slow queries. Queries that take longer than the threshold time are logged in the sugarcrm.log file. This information is for performance-tuning investigation. If you have also enabled the Tracker Queries option, you can run the pre-defined Slow Queries report to view slow queries.
|
2.
|
Click Save to save the settings.
|
|
Note:
|
In order to obtain data on memory usage, your PHP system must support the memory_get_usage function.
|
For information on installing and setting up the Sugar Offline Client, see the Sugar Offline Client Installation Guide.
You can change the status of an offline client in the Set Status column in the Offline Clients list. To change the status of multiple offline clients or to delete them, use the Mass Update sub-panel.
Select this option to enable the Sugar Feed functionality for your organization. Sugar Feed enables users to be informed as soon as a team member creates a new contact, lead, opportunity, or case. Team members are also notified of status updates when a lead is converted, when a case is closed, and when an opportunity is closed. When a user performs any of these actions, Sugar displays a message in the My Sugar Feed dashlet on the Home page of team members.
You can activate Sugar Feed for one or more of the following modules: Leads, Cases, Opportunities, and Contacts.
Additionally, you can enable User Feed to allow users to post status updates, external links, images, and YouTube videos. Your organization can also create custom link types. These posts can be viewed only by members of the specified team.
|
1.
|
In the System sub-panel, click Sugar Feed Settings.
|
|
2.
|
|
3.
|
To enable users to post status updates, images, links, and YouTube video, select Activate User Feed.
|
|
5.
|
Click Save.
|
|
6.
|
To delete all existing entries in the Feed, click Delete Feed Entries and click OK to confirm your action.
|
Sugar Feed entries for images, links, and YouTube videos are automatically deleted after two weeks. If you add custom link types, you can clear them from the cache using the Repair - Quick Repair and Rebuild option.
Use this option to manage connectors to external data sources. When you enable connectors for a Sugar module, users can search external data sources for new information from within a Sugar record in the module. Users can view the external data or merge it with the existing information in the Sugar record. For example, they can update addresses and phone numbers for an account. For information on merging data, see the Sugar Enterprise User Guide.
Though you can enable connectors for any standard module or custom module that displays in Studio, they are designed for company-type or person-type modules such as Accounts, Leads, and Contacts. The module must also have a standard Detail View layout. For example, though the Knowledge Base module is listed in Studio, you cannot enable connectors for it because it does not have a standard Detail View layout.
The connectors that Sugar provides are Hoover’s, Jigsaw, and LinkedIn. Developers in your organization can create connectors to other data sources, and you can upload them into Sugar using the Module Loader. You can also search for other available connectors on Sugar Forge at http://www.sugarforge.com and Sugar Exchange at http://www.sugarexchange.com.
You can choose the connector fields by which users can search a data source as described in “Setting Connector Search Fields” on page 53. You can also map connector fields to fields in Sugar as described in “Mapping Connector Fields” on page 54.
To activate the Jigsaw and Hoover’s connectors, you will have to enter the API keys for those services on the Connector properties page. Sugar ships with introductory API keys for these two connectors.
|
1.
|
|
1.
|
Click The Set Connector Properties page displays tabs for the connectors that Sugar provides. Tabs for any other connectors that you install also display on this page.
For connectors to Jigsaw and Hoover’s, you must have API keys from those services in order to connect the data source. Sugar ships with introductory API keys for both these connectors. For LinkedIn, no API key is required. However, users must be logged into LinkedIn using their LinkedIn account in order to view LinkedIn data within Sugar.
The Jigsaw connector tab displays a WSDL URL. The Hoover’s connector tab displays a WSDL URL and an EndPoint URL.
|
•
|
WSDL URL: This is the location of the Web Service Definition Language needed to create the client objects that allow Sugar to communicate with the data source’s Web Services.
|
|
•
|
Endpoint URL: This is the location that will service your SOAP calls.
|
|
3.
|
For Jigsaw, to change the number of results per page, enter the number in the Maximum Number of List Results field. The default value is 20 results per page.
|
|
4.
|
To ensure that data source is correctly configured, click Test Connector.
|
If the configuration is correct, Sugar displays a message stating that the connection was successful.
|
5.
|
|
1.
|
This page displays tabs for the available data source connectors. Each tab displays a column for connector-enabled modules and a column for connector-disabled modules. By default, connectors are disabled for all modules.
|
2.
|
To enable a connector for a module, on the connector tab, drag the module from the Disabled list to the Enabled list.
|
To disable a connector for a module, on the connector tab, drag the module from the Enabled list to the Disabled list.
|
3.
|
Click Save to saving the settings.
|
You can choose the fields by which users can search a data source. However, your choices are limited by the Search parameters that the data source supports. The table below lists the supported and default Search fields for Jigsaw and Hoover’s.
|
Default Search Fields
|
||
|
Note:
|
|
1.
|
|
2.
|
To use a field in Connector Search for a module, drag it from the Available list to the Default list.
|
|
3.
|
Click Save to save the settings.
|
You can map connector fields to fields in a Sugar module to determine how the data is merged from the data source into the Sugar record. For the connectors that Sugar provides, field mappings are set by default. You can change these mappings and also map additional fields.
For each data source, you can map a module field to only one connector field. The connector fields that appear in the Data List View are determined by which connector fields are mapped. However, some of the connector fields display data in the Data Merge form but not in the List View. Other connectors may or may not display data in the List View or Merge Form.
The table below lists the fields that display in the Data List View, Additional Details Pop-up window, and the Data Merge Form for Jigsaw and Hoover’s.
|
Additional Details Pop-up/Data Merge Form Fields
|
||
|
Company name, City, State, Country, Phone, SIC code, Annual revenue, Annual revenue estimate, Ownership, Website, Jigsaw website, Primary industry, Stock symbol, Stock exchange, Date profile created, Employee count, Headcount range
|
||
|
City, Country, Company ID, Annual Sales, Company Name
|
City, Country, Company ID, Annual Sales, Company Name
|
|
1.
|
Each connector tab displays a list of fields in the connector and a corresponding drop-down list of fields in connector-enabled Sugar modules.
|
2.
|
To change a default mapping or to add a new mapping, select the Sugar field from the drop-down list corresponding to the field in the connector.
|
|
3.
|
Click Save to save the mappings.
|
|
Note:
|
Developers in your organization can customize the Sugar code to change the order in which connectors are prioritized when using the Smart Copy feature during data merge.
|
If a data source connector supports pop-up windows to display data, then Sugar also uses these field mappings to determine which fields display the pop-up window for the data source. For example, the mapped field for LinkedIn displays the LinkedIn icon. When users point the cursor at this icon, a pop-up window displays the LinkedIn data for the field.
|
|
|
|
|
Copyright 2004-2008 SugarCRM Inc.
Enterprise License