Policy Guide › Categorizing Events › Set Up New Categorization Triggers

Set Up New Categorization Triggers

CA DataMinder event categorization is policy-based. This ensures that emails or files are successfully categorized, regardless of how they were captured or imported.

1. Configure a categorize control action. Your categorization triggers reference this control action in step 5. Specifically, you must specify a Categorize option for the Intervention setting. For email control actions and Data In Motion control actions, there are two Categorize options:

   Categorize: Single category only

   This displays a single-select Categorize dialog. The user can only select a single category for their email or file.

   Categorize: Multiple categories allowed

   This displays a multi-select Categorize dialog, permitting the user to select multiple categories.

   Note: Because of control action precedence, we recommend that you designate the lowest possible control action number as your categorize action. For example, if you designate Control Action 1 as your categorize action.

2. Set up your categorization trigger(s). These can be any email or file control triggers. Set up the triggers to detect the emails or files you want to categorize.

   How you set up the triggers depends on various factors. For example, if you are using Outlook or Notes client agents to detect emails and you want to permit users to manually categorize their emails, you can set up a single trigger that specifies multiple possible categories, each with a low category score.

3. Configure the Smart Tags trigger setting to save the final email or file category or categories—whether selected automatically by CA DataMinder or chosen by the user—as smart tags.

   Important! You must add a smart tag to store the email category, otherwise the category details will not be saved on the CMS.

   When you add a new smart tag, you must set its name (or value) to include a categorization variable such as %category% (this variable is populated with the category 'label' specified by the <smart tag> parameter in the Message To Users setting—see step 4). Note also:

   • If you have multiple triggers that specify categories, you must configure the smart tags identically in each trigger.
   • To make the smart tags readily identifiable in the iConsole, we recommend that you prefix the variables with text labels. For example:

     Category: %category% 
     

   • Smart tags are case-sensitive.
4. Specify the associated category or categories. To do this, you edit the Message To Users trigger setting. Use the correct syntax!

   Briefly, the message must include the following elements:

   <message text>

   Specifies the explanatory message shown in the Categorize dialog or (for files detected by the FSA) replacement stub files.

   <category>

   Specifies a category name that is listed in the Categorize dialog.

   <score>

   Is the category score.

   <smart tag>

   Specifies a category 'label' that gets converted to a category smart tag.

   As with smart tags in Step 3, if you have multiple triggers that specify the same category, you must specify the category name and label identically in each trigger. This prevents variations in spelling or capitalization being stored as separate category smart tags for the same event.

5. Point each categorization trigger at the same control action.

   Specifically, set the Control Action trigger setting to point to the categorize control action you specified in Step 1.

More information:

Add Categorization to Existing Triggers

Syntax for Specifying Categories

Example Category Definitions