Best practice in modern experience to export from TEST to PROD tenant and use in rpa project

Help Document Understanding
1

Hello, I want to know what is the best practice when we have two are more tenants ?
We created our modern DU project in TEST tenant with a DU performer in studio.
When OK to go in production we export package to recreate process in PROD as usual. But when exporting trained dataset in DU and creating project back in PROD, how to avoid changing the studio project by specifing DU Project and Extractor version in Extract Document Data ?
Developers have no access to PROD tenant so we need to connect remotely to Robot machine to make the change, it is very annoying.

I was thinking that it would be as easy as integration service connection, selected in process parameters directly in orchestrator.

Thanks for your insights, it will help a lot my understanding.

2

Hi @Matt67,

Steps to use modern DU project across different tenants:

  1. Create App ID and Secret in Admin > External Applications.
  2. Save App ID and Secret in Orchestrator assets.
  3. Use the credentials asset in DuAppExtractor activity

Note: You can create your modern DU project in the prod tenant in the first place.

image
image450×162 4.44 KB