Similarity Check Logic

Before you proceed with the analysis of the Generated Knowledge, take a moment to familiarize yourself with the Knowledge Generation & Similarity Check logic in order to establish a correlation with its functionality.

When you click the Generate Knowledge button, the following two processes take place:

1. Knowledge for the cluster representatives is generated, followed by

2. The similarity of the representatives is verified and compared with the committed knowledge (in other words, comparing with knowledge repository that are available for downstream consumption)

Here is the process that tickets undergo during knowledge generation

Similarity check logic

The logic will analyze all the cluster representative documents and compare them against the committed knowledge repository available in the knowledge module.

If no duplicates are found, they will be automatically approved and committed, and will be directly accessible under the knowledge module for fulfillments.

However, if any documents are found to be duplicates, they will not be automatically committed or approved.

You can view the duplicate documents and decide whether to commit or delete the generated document. We will delve deeper into the functional requirements in the next section.