Why I should use DU template in Studio when modern project there?

Help Document Understanding
1

What is the use of DU template in Studio when we have modern project in DU cloud ? What benefits I get if i define taxonomy again in studio as a classic project

2

Hello @suripaleru,

If you’re on modern DU with cloud taxonomy, stick to it. You get central management, scalability, and easy retraining.

Only define taxonomy again in Studio (classic DU template) if you must integrate with legacy extractors, run offline, or handle hybrid scenarios.

3

@suripaleru,

Both approaches have their own pros and cons and which works for your use case you should be using it.
Here is quick comparison by LLM about it [Validated by me].

Why Use the DU Template in Studio (Modern Project)?

Even if you’re leveraging DU cloud capabilities (like ML models, Document Manager, etc.), the DU template in Studio provides:

:white_check_mark: Local Development & Testing

  • You can simulate the entire DU workflow locally: classification, extraction, validation.
  • Useful for debugging, custom logic, and integration testing before deploying to Orchestrator.

:white_check_mark: Custom Workflows

  • You can extend or customize the DU process with additional logic (e.g., business rules, exception handling).
  • Easier to integrate with other systems (SAP, databases, etc.) during development.

:white_check_mark: Offline Taxonomy & Flexibility

  • You can define a local taxonomy for testing or for documents that don’t need cloud processing.
  • Useful when working with confidential documents that shouldn’t be uploaded to cloud.

:package: Benefits of Defining Taxonomy Again in Studio (Classic Project)

If you define taxonomy again in a classic project, here’s what you gain:

:counterclockwise_arrows_button: Backward Compatibility

  • Some legacy components (like IntelligentOCR activities) still rely on classic taxonomy definitions.
  • Useful if you’re migrating older workflows or integrating with older systems.

:test_tube: Fine-Grained Control

  • You can manually control the taxonomy structure, field types, and validation logic.
  • Helpful for complex document types or when cloud taxonomy doesn’t support certain features.

:toolbox: Custom Extractors

  • Classic taxonomy allows easier integration with custom extractors or regex-based logic.
  • You can mix ML and rule-based extractors more flexibly.

:rocket: Best Practice Recommendation

If you’re using modern projects with DU cloud, you typically:

  • Define taxonomy in Document Manager (cloud).
  • Use DU template in Studio for local testing, validation station, and orchestration.
  • Avoid duplicating taxonomy unless you need legacy support or offline processing.
4

Hi @suripaleru

The DU template in Studio is useful when you need offline testing, legacy compatibility, or full control over taxonomy, extractors, and classifiers.
Even if you’re using DU Cloud in a modern project, defining taxonomy again in Studio as a classic project allows deeper customization, manual extractor tuning, and support for older workflows. It’s ideal for hybrid setups or when cloud features don’t fully meet your document processing needs.

Reference: UiPath Document Understanding

If helpful, mark as solution. Happy automation with UiPath