Enabling a case for analytics

When you create a case, analytics is not enabled by default. The reason for this is that you may need to provision and control the SQL Server resources that are necessary for analytics, and these may not be immediately available. After you enable a case for analytics, case items including content, attachments, and item metadata such as subject, recipients and other attributes, are fetched into the customer database. If you have already built analytics rules for a case before you enable it, the automatic categorization of items begins soon after collection starts.

Before you enable a case for analytics, note the following:

To enable a case for analytics

  1. Click the Cases tab in the Discovery Accelerator client.

  2. In the left pane, select the case that you want to enable for analytics.

  3. Click the Analytics tab.

  4. If you want to define any case-specific review marks or tags before you enable the case for analytics, click the appropriate hyperlink and then enter the details.

  5. If you want to define any rules for automatically categorizing the items in the case, click the Define rules hyperlink and then set up the required marking rules and tagging rules.

  6. Click Enable.

    Initially, the case's status changes to "Enabling analytics" while the collection of data is prepared. Subsequently, the status changes to "Analytics enabled" and the collection and indexing of data and the automatic categorization of items begin.

More Information

About review marks

About analytics rules

Monitoring the progress of analytics data collection

About the Discovery Accelerator permissions

Analytics Data Collection configuration options

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.