Specify the records used to train a classification solution, what fields trigger a prediction, and how often you want to retrain your solution.

1. Navigate to Agent Intelligence > Classification > Solution Definitions.
2. On the ML Solution Definitions list, click New.
3. On the blank ML Solution Definition form, configure these field values per the following guidance.

   Field	Value
   Solution Template	Select the Classification Template. By default, Agent Intelligence offers these solution templates, which have some field values pre-assigned. Classification Template Incident Assignment Template Incident Category Template Incident Priority Template For example, the Incident Assignment Template selects the Incident table and creates a filter that selects resolved or closed incidents within the last 12 months. Note: This field cannot have a value of None.
   Active	Select this check box so that the system uses your solution definition record to train your solutions. You can only train active solution definition records.
   Label	Enter a name for the solution record.
   Name	The system generates the value of this read-only field based on the Label value that you entered.
   Table	Select the table containing the target records that you want the system to predict.
   Output Field	Select the field whose value you want the predictive model to set. The system provides a default output field when you select a Solution Template. In general, a good output field has these characteristics. The field is a choice field or a string field with a finite set of possible values. The field has some causal connection to the input fields. For example, the Incident Category Template selects the Category field.
   Domain	On instances where domain separation is active, select the domain whose target records you want to predict. Create a separate solution definition record for each domain whose field values you want to predict.
   Input Fields	Select the input fields you want the solution to use to generate a prediction. The system provides default input fields when you select a Solution Template. In general, good input fields have these characteristics. The fields are available to users when creating records. Configure the form to show all input fields. The field data type can be string, reference, choice, or HTML. The more information a field provides, the more often a solution can make a prediction, and the more often predictions are accurate. The field has a default value. The field should not have a blank value. For example, all default solution definitions use the Short description field as the input field.
   Filter	Select the conditions you want to apply to the training records. To train a solution, the filter must return at least one record. If your filter returns no records, update it until it returns records for training. Note: The recommended number of records for training a good solution is from 30,000 through 300,000. If you submit more than 300,000 records, the most recent 300,000 records are used to train the solution. Use only authentic records from the database. The system provides a default filter when you select a Solution Template. A solution is only as good as the data you use to train it. In general, a good filter has these characteristics. The training records are inactive and have task states that represent completing work within your standard process such as resolved or closed. The training records only contain correct values for the target field. Filter out records with unreliable target field values. For example, if you are predicting the assignment group/category and you have assignment groups/categories in your historic incident data that are no longer used, add a filter to remove such incident records from the training. The training records contain multiple examples of each target field value you want the solution to predict. The training records include common variations of the input fields. For example, the Incident Category Template creates a filter with these conditions. [Created][on][Last 12 months] AND [Active][is][false] AND [State][is one of][Resolved | Closed] Do not use hard-coded dates as filters, as these filters are not updated when the solutions are retrained unless you update them manually before every retraining. Instead, use relative date filters, such as last 3 months, last 6 months, and last 12 months.
   Processing Language	Select the dominant language of the dataset you are training on the solution definition. If the dataset language is English only, you can choose None, as English processing is applied to all datasets by default. For example, if you select Dutch, data is processed in both English and Dutch. Note: The term “processing” indicates some of the language-specific steps used as part of training a solution. For example, tokenizing words, removing stop words, and stemming.
   Training Frequency	Select how often the system regenerates the solution based on records matching the Filter. Options include: Run Once Every 30 days Every 60 days Every 90 days Every 120 days Every 180 days By default, the system runs training once. This practice provides you time to review and update the solution definition as needed until it provides acceptable coverage and precision values. When your solution definition is fairly stable, consider scheduled trainings, as data can age over time, thus degrading the accuracy of your prediction model.

4. Click the appropriate button for your solution definition.

   Option	Description
   Save	Save your solution definition record so that you can return to it later.
   Submit & Train	Create your solution definition record and train it.

5. If you submitted the solution for training, click OK on the Training Activation window to confirm.
   The system schedules the solution for training with the nearest training service. The system sends you a notification when the training completes, including any are errors that may have occurred in the training. Any other users can subscribe to the Agent Intelligence Notifications category. When training is complete, the system uploads the solution as an Attachment record.