Document Understanding
Banner background image
Document Understanding
Last updated Dec 19, 2023


Release date Document Manager On-Premises: 23 May 2022

Stay up to date with all the latest news regarding Document Manager by going through the next list of changes that have occurred since the last LTS release until now.

What's New

Data Manager changes its name to Document Manager.

A new option is available, allowing you to permanently delete individual files. The option can be found in the drop down that also contains the download option.

You now have the option to rename previously created fields.

Search inside a document is now possible, allowing you to search for words in your current document.

Data gathered from importing a dataset is now integrated into the JSON files of the subset field, meaning that if you manually modify the file or delete it completely from the dataset, it does not have an impact over the training of the model.

Deleted documents are now excluded from deduplication, meaning that you can now import the same document twice. Deleted documents are also excluded from searching or filtering, so it only searches non-deleted documents unless you are using the deleted keyword.

Document view has received new getting started tips.


An on-premise deployment that is using SQL Server installation with the full-text search option disabled, requires, at installation time, a restart of the full-text search service to enable it. This can be done by running the EXEC sp_fulltext_service 'restart_all_fdhosts' command by a DBA with the appropriate permissions on the server.

When using the Predict functionality along with Document Manager, tagged data that was not manually edited by the user is replaced with the values received from the model.

Added more descriptive tooltips on Training, Validation, and Evaluation document types.

The edit field dialog box for column and regular fields has been restructured. Post processing, Multi page, Scoring, and Color options have been moved to the Advanced tab. The rest of the options can be found in the General tab.

Speed improvement on import for duplicate documents.

Classification fields now appear in the order they're created.

Bug Fixes

  • Fixed a known issue that was causing the search or the download of a document which contained characters that require URL encoding (&, ,, +, #, ') in its file name to fail with an invalid query.
  • Fixed a bug that caused the Predict functionality to fail on documents with very dense text.
  • Removed the 2000 documents import limit per session. Now you can have more than 2000 documents in a session, considering the limit of 2000 pages per import.
  • Fixed a bug that was not allowing you to select more than 3 boxes when pressing ctrl or shift.
  • Fixed a bug that caused an import to hang in processing until being timed out after the pod was restarted but the job did not resume.
  • Fixed a bug that prevented the Predict function from extracting data from the entire document. Please note that the 10 page limit when using the function with Public Endpoints is still in place.
  • Fixed a bug for Microsoft Read OCR where endpoints matching the * subdomains were throwing an OCR endpoint is not valid error.
  • Fixed a bug that caused the Document Manager dataset import to mix up pages on documents with more than 10 pages.
  • Fixed a bug that caused the download or the export of an empty dataset or only a small subset of the full dataset when the All labelled option was selected.

Known Issues

  • Maximum import size decreased from 2GB or 2000 pages to 1GB or 2000 pages.
  • Searching or downloading a document containing characters that require URL encoding (&, ,, +, #, ') in its file name fails with invalid query.

For more details about all changes that occurred in Document Manager, please consult the previous Release Notes.

3 June 2022

Known Issues

  • Some PDF files that contain Type3 fonts can result in high memory usage for the Digitizer Service. When this occurs, import operations from Document Manager are degraded. The mitigation for this is to manually delete the kubernetes pods that have high memory usage (constantly above 70%).
  • What's New
  • Improvements
  • Bug Fixes
  • Known Issues
  • 3 June 2022
  • Known Issues

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.