How to remove specific record types, such as incidents automatically created from system events from the Similarity Solution definitions, so that they are excluded from showing in the Similarity Examples after training the solutionSummaryWhen training a Similarity Solution definition, it is possible to add filter conditions to the Word Corpus, and the table from which the similarity results are retrieved, but it is not possible to add any conditions to the table that is used for comparison, the Test Table in the Similarity Solution definition. This is a challenge to exclude specific record types from the Similarity models, so that they are not shown as Similarity Examples. The Test Table is only used to generate the Similarity Examples, and is automatically limited to 100,000 most recent test records. However, it will only generate a sub-set of Similarity Examples from the 100,000 test records, and not for all test records. Reviewing the Similarity Examples will enable you to determine the optimal Confidence Threshold for you Similarity solution. However, when re-training the Similarity solution, the Confidence Threshold will be automatically set back to "80" in the [ml_solution] record.InstructionsYou can remove for example incidents auto-created from system events via the Similarity Solution definition by using a database view on the Test Table and adding additional filters on the Word Corpus, as per the Community article on how to improve Similarity results, as follows - 1. Word Corpus with additional filters to remove unwanted vocabulary from the Word Corpus associated with incidents auto-created from system events. The community article has further suggestions for improving Similarity results - Tuning Predictive Intelligence Models (part 3) – Improving Similarity Results using the Word Corpus. Note: With Washington+, the Word Corpus is no longer used, as we use a pre-trained Word Corpus using the Google Universal Sentence Encoder (GUSE), and so this step is no longer required, as the Word Corpus field has been removed from the solution definition form. 2. Create a database view that removes the incidents auto-created from system events and have the [incident] table in the database view configuration with the lowest Order, so that it shows the Incident number in the Similarity Examples on the trained Similarity Solution when using the database view as the Test Table. If you only need to one table as the Test Table, then you only need to create 1 entry for the View table, as follows - 3. You will then need to create a Before Query Business Rule (BQBR) on the database view with the encoded query to filter the required records for the Test Table, as per KB0719186: Filtering using the 'Where clause' in database views. Further information on Encoded Queries can be found on the ServiceNow Developer site - Simplify queries with Encoded Queries TIP: To generate an Encoded Query, open the List View on the table, and complete the filter configuration to filter the desired records for the Test Table. Now right-click the end of the filter breadcrumb and select the Copy query menu item, and copy it into your BQBR. For example, if you want to restrict incident data created on the last 6 months, you can use the following encoded query - var query = "inc_sys_created_onONLast 6 months@javascript:gs.beginningOfLast6Months()@javascript:gs.endOfLast6Months()";current.addEncodedQuery(query); Note: A Test Table in the Similarity solution will automatically be limited to 100,000 most recent test records, if you do not limit it in the encoded query. 4. Finally, in the Similarity solution definition, you select the database view as the Test Table, and now it will only use selected incidents, based on your BQBR to generate Similarity Examples from.