Yes: Enables ActiveX viewer for Crystal reports.

No: Disables ActiveX viewer for Crystal reports.

Crystal is not currently supported by Sage CRM. This setting remains for backward compatibility for customers using unsupported versions of Crystal.

Parameters used when calling the Adobe converter program. %1 and %2 are placeholders for the source and destination file names and should not be removed. -q enables quiet mode, which suppresses information messages. Error messages are still displayed.

The full path and file name of the Adobe converter program.

To allow the upload of executable files, set this option to Yes and add the file name extensions of executable files to Allow file name extensions for upload.

To detect an executable file, Sage CRM checks the file's header to determine its true type. This makes Sage CRM capable of detecting an executable file even if its file name extension has been changed.

Populate this option with the file name extensions that can be uploaded to Sage CRM. Omit full stop from the file name extensions. Use a comma as a separator.

The default value in this option is:

doc, docx, rtf, xls, xlsx, ppt, pptx, pdf, csv, xml, txt, jpg, jpeg, bmp, gif, png, svg, zip

If a file name extension in this option belongs to an executable file, you must also set Allow executable files to be uploaded to Yes.

Sage CRM treats the following file types as executable:

com, cpl, dex, dll, exe, fon, mz, scr, sys, iec, ime, rs, tsp

The path to the IIS virtual directory required for Crystal viewer support.

Crystal is not currently supported by Sage CRM. This setting remains for backward compatibility for customers using unsupported versions of Crystal.

The version of Crystal reports installed on the web server.

Crystal is not currently supported by Sage CRM. This setting remains for backward compatibility for customers using unsupported versions of Crystal.

The path to the directory where mail merge templates are stored.

The size limit in kilobytes of the report for desktop clients. This is an approximation; it counts the size of the XML rather than the HTML output. It prevents very large reports running and taking all the bandwidth.

If you regularly run large reports, you should set this to 60 MB (61 440 Kb). It must not exceed 120 MB (122 880 Kb).

The name of the server where documents are stored if different to Sage CRM.

The type of users that can view the Export Group to file action button. For more information, see Export Group to File.

The size limit for each file that can be uploaded. The value in this option applies when a user:

• Selects the Add File button or uses the Drop files here to attach them area to upload files.

• Selects the Import Emails button to import emails with attachments. When an email attachment exceeds the file size limit set in this option, the email is imported without the attachment.

The maximum number of files per upload. For example, set to 10 to allow a user upload up to 10 files in a single transaction.

The value in this option applies when a user selects the Add File button or uses the Drop files here to attach them area to upload files.

The alias for the directory where mail merge documents are stored. This is set up in IIS. This is a legacy field that’s no longer used.

The web server port number.

The login ID of the local machine administrator which Sage CRM uses to save files to the server. The impersonated user login ID and the impersonated user domain are required for a valid logon.

The domain of the impersonated user.

The password of the impersonated user.

The maximum amount of time, in seconds, that Sage CRM waits for a mail merge to complete before a timeout error is displayed. If users frequently receive timeout errors during mail merges, you can increase this value. The default value is 300 seconds (5 minutes).

The maximum amount of memory allocated to the mail merge process. The default setting is 1024MB (1GB) but can be increased.

The amount of memory required for mail merge depends on the number of records merged and the size of the template (the number of graphics and amount of text).

The number of users who can perform concurrent mail merges. The default is 5. If you increase this value, you must also increase the value of Max mail merge memory because more memory is required.

The number of mail merge and Excel report generation processes that are carried out concurrently. New processes can start before the previous process has completed. For example, one user’s mail merge runs at the same time as another user’s Excel report output.

Set to 1 to carry out processes sequentially.

The path to the directory where mail merge documents are stored. The path must end in a backslash (\).

The size limit in Kb of the report for mobile clients. This is an approximation; it counts the size of the XML rather than the HTML output. It prevents very large reports running and taking all the bandwidth.

The maximum amount of memory allocated to the report generation process. The default setting is 1024MB (1GB).

Yes: Administrators can run a report of any size.

No: The value in Desktop size limitation is used when a report is run. Use No if you regularly run large reports.

The maximum amount of time, in seconds, that Sage CRM waits for a report to build before a timeout error is displayed.

Yes: All users can export reports to PDF or spreadsheet format and view reports on screen.

No: Only a user with info manager or full system administrator rights can export reports to PDF or spreadsheet format. All users can view reports on screen.

This setting relates to reports run from the Reports menu and does not affect summary reports. Enable access to summary reports in Summary reports enabled.

The maximum amount of time, in seconds, that Sage CRM waits for a report to run before a timeout error is displayed.

The path to the directory where reports are stored.

The type of users that can view the Send Email action button. For more information, see Send Email.

Yes(default): An image produced by a graphic, chart, or organizational chart is retained in memory and streamed to the client.

No: An image produced by a graphic, chart, or organizational chart is saved to the server's hard disk and then relayed to the client. This option is disabled by default.