Best Practices for Defining Taxonomies in Document Understanding

Help Document Understanding
1

I’m currently revisiting UiPath’s Document Understanding.

I remember that in the past, it was common to define fields and taxonomies manually using the Taxonomy Manager within UiPath Studio. Is this approach still widely used today, or is it considered outdated?

The reason I ask is that when I recently used Document Understanding again, I noticed that it’s now possible to create projects directly on Automation Cloud, and documents like invoices and purchase orders can be classified automatically. This made me wonder whether defining everything within Studio has become an old-fashioned method.

The image shows the Document Understanding interface in UiPath with options for building and managing document types such as Invoices, Purchase Orders, and W9 forms. (AI によるキャプション)
The image shows the Document Understanding interface in UiPath with options for building and managing document types such as Invoices, Purchase Orders, and W9 forms. (AI によるキャプション)2959×836 139 KB

If there are clear differences or recommended use cases between the traditional Studio-based approach and the newer Automation Cloud project management method, I would appreciate it if you could explain those as well.

Best regards,

2

@mkt.scott4,

I would suggest if starting up new project, go with modern approach which is from Automation cloud

If working on older project, keep it using classic approach.

3

@mkt.scott4

please check this

cheers

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.