Ephesoft 'Classify Document' activity returns incorrect classification and confidence

When using the ‘Classify Document’ activity from the ‘UiPath.Ephesoft.Activities’ package, some documents (between 2-5%) are returning different results compared to all the other methods I am aware of. This includes

  1. The ‘test classification’ function on transact,
  2. The API (/rest/ocrClassifyExtract),
  3. The document review function.

Is it possible to explain how the document classification confidence score is calculated?

The documentation mentions it’s a Lucene score? This seems to suggest it’s linked to the Search Classification plugin but this is disabled in the batch class we are using and when manually tested, provides a significantly different result.

For Example: When the same document is run through the various pathways the results are:

  1. Expected: Unknown (confidence = 0%)
  2. Test Classification: Unknown (0%)
  3. API: Unknown (0%)
  4. Review: Unknown (0%)
  5. Test Classification (with search classification plugin enabled): Type A (24%)
  6. This activity: Type A (88%)



Hello @zanekearney!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

@zanekearney - Fancy seeing you here. Should we post the solution up for this so others can benefit?