Mining, it is recommended that users provide a minimum of 25 pinned examples per label to ensure proper training and accurate predictions by the machine learning models. This number allows the platform to have a sufficient variety of examples to generalize and make reliable predictions for each label in real-world scenarios.

The minimum number of pinned examples per label is crucial because it enhances both precision and recall, helping the model effectively differentiate between labels and improving overall model performance. If fewer examples are provided, the model may struggle with generalization and might not perform well in distinguishing between similar or overlapping categories.

This standard of 25 pinned examples is outlined in several UiPath documentation sections and best practices for training models in Communications Mining​

UiPath Documentation

​

UiPath Documentation

​

UiPath Community Forum

For further details, refer to UiPath’s official Communications Mining User Guide on their documentation portal.

To configure the Classification Station as an attended activity in UiPath, certain inputs are mandatory for proper functionality. These include:

Taxonomy: The schema that defines the structure of document types and fields.

Document Path: The file path of the document to be classified.

Document Object Model (DOM): Generated from the document using the Digitize Document activity, this is a structured representation of the document.

Document Text: The extracted text of the document, also an output from the Digitize Document activity.

These inputs allow the Classification Station to review and validate the classification results, either manually or based on automatic suggestions from previous processes.

 A label taxonomy is a hierarchical structure of concepts that you want to capture from your communications data, such as emails, chats, or calls. Each label represents a specific concept that serves a business purpose and is aligned to your objectives. A label taxonomy can have multiple levels of hierarchy, where each child label is a subset of its parent label. For example, a parent label could be “Product Feedback” and a child label could be “Product Feature Request” or “Product Bug Report”. A label taxonomy is used to train a machine learning model that can automatically classify your communications data according to the labels you defined1.

One of the best practices for designing a label taxonomy is to ensure that each label is clearly identifiable from the text of the individual verbatim (not thread) to which it will be applied. A verbatim is a single unit of communication, such as an email message, a chat message, or a call transcript segment. A thread is a collection of related verbatims, such as an email conversation, a chat session, or a call recording. When you train your model, you will apply labels to verbatims, not threads, so it is important that each label can be recognized from the verbatim text alone, without relying on the context of the thread. This will help the model to learn the patterns and features of each label and to generalize to new data. It will also help you to maintain consistency and accuracy when labelling your data2.

The Sentiment Analysis out-of-the-box model in UiPath is used to interpret and classify the emotional tone within text data. It is particularly useful for analyzing product reviews, customer feedback, social media posts, and emails to understand customer sentiment and emotional responses, helping businesses make informed decisions based on these insights.(Source: UiPath Sentiment Analysis model documentation

In this scenario, the rules defined in the Taxonomy Manager are as follows:

IsNotEmpty: Ensures that the field is not empty.

EndsWithUSA: Checks if the extracted address ends with "USA".

ContainsNY: Ensures that the extracted address contains "NY".

The address extracted in this case is: "42 W 80th St. West New York, NJ 1234, USA". While the address ends with "USA" (passing the EndsWithUSA rule), it includes "West New York, NJ", which satisfies the ContainsNY rule even though "NY" is part of "New York". However, the exact behavior of the Contains rule can generate a warning message because "NY" is part of a larger string ("New York"). Since this does not constitute an error but simply a rule conflict, the validation can proceed.

Therefore, the most accurate outcome would be a warning, but validation can still be performed

When creating a data labeling session in UiPath AI Center, the key pieces of information required are:

The data labeling session name: A unique identifier for the session.

The dataset: The data that will be used in the labeling session.

For more details, refer to:

UiPath AI Center Documentation: Data Labeling Sessions

The End Process is the final stage of the Document Understanding Process, which is a fully functional UiPath Studio project template based on a document processing flowchart. The End Process is responsible for setting the queue transaction status, logging the results, and performing any post processing or cleaning actions if needed. The End Process sets the queue transaction status as Successful if the document was processed without any exception, and as Failed if an exception occurred, either a Business Exception (such as invalid data) or a System Exception (such as network failure). The End Process also adds the extracted data and the validation status as output arguments to the queue transaction. The End Process also logs the processing statistics, such as the number of documents processed, the number of exceptions, the average processing time, and the accuracy rate. The End Process also performs any post processing or cleaning actions, such as deleting temporary files, closing applications, or sending notifications1.

Comprehensive and Detailed Explanation From Exact Extract:

Processes that undergo frequent business logic changes require frequent updates to automation scripts, resulting in high maintenance effort and potential breakdowns in unattended execution.

Stable, rules-based processes are preferred for long-term, low-maintenance automation.

UiPath Academy Reference: RPA Developer Foundation – “Process Assessment and Selection” Module

According to the UiPath documentation, the recommended number of documents per vendor to train the initial dataset is 10. This means that for each vendor that provides a specific type of document, such as invoices or receipts, you should have at least 10 samples of their documents in your training dataset. This helps to ensure that the dataset is balanced and representative of the real-world data, and that the machine learning model can learn from the variations and features of each vendor’s documents. Having too few documents per vendor can lead to poor model performance and accuracy, while having too many documents from a single vendor can cause overfitting and bias1.