Create a document classification use case

Create a use case record to begin defining the classes or categories that you want to apply to a type of document or pages within the document.

Important:

Starting with the Zurich release, Document Intelligence is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details, see the Deprecation Process article [KB0867184] in the Now Support Knowledge Base. Instead, you can extract information from documents using the Now Assist in Document Intelligence application. For more information, see Now Assist in Document Intelligence.

Before you begin

Role required: sn_docintel.manager

Procedure

1. Navigate to All > Document Intelligence > Document Classification > Use Cases.
2. Select New.
3. On the form, fill in the fields.

   Table 1. Use case form

   Field	Description
   Display Name	The name for the use case as it appears in the Document Intelligence workspace.
   Document Type	Type of document to be processed for the use case.
   Document Config	Configuration of the document to be processed for the use case.
   Autofill Threshold	DocIntel only auto-fills the classes (fields) if the confidence score of the top recommendation is at or above the percentage you define. Fields with a confidence score lower than the threshold are left empty in the Document Intelligence workspace, and the recommendation mode is available to extract these fields. This field is available only if the Auto-fill mode is enabled.
   Fully Automated Threshold	Confidence score threshold for document classifications, which enables a document task to be fully automated in the Fully Automated (Straight Through Processing) mode.
   Warning Threshold	DocIntel shows a warning for empty fields and auto-filled fields with a confidence score at or below the percentage that you define. This field is available only if the Auto-fill mode is enabled.

4. Select Submit.

What to do next

After creating a use case, finish setting it up by adding fields to create document classes. Then, train the use case.