Cross tenant action item creation and resume on du item validated

I am processing the documents using DU in tenant A where the robot is connected. My requirement is to create action items in tenant B for user validation. Is it possible to create cross tenant DU action item and suspend the job, so that after the action item task is validated the job needs to be resumed.

@aravindbalineni123

I dont think so you can do something of that sort directly…

As create form task creates a task in same tenant as robot is connected and not in anaother tenant and there is no configuration that is available as such

One thing you can do is connect robot to tenant B and access the ai center of tenant1 using api so that tenant A model is accessed via api using du as service and as robot is connected to tenant B it works as you need

Cheers

So as per client requirement we can’t connect robot to client B. So we need to find a possibility without that.

Update: AI Center I am using as public so it is accessible through api key.

@aravindbalineni123

If you need to create action in tenant B then robot id should be from tenant B only

Alternately there is a create form task api which can be used for creating form task…

And for resuming you need to have your logic or can use webhooks to trigger when approver or rejected

Cheers

Hi Anil,

I was on the same thought but do you what can be implemented so that if the action task is complete it should do a api call to the tenant to resume the bot

@aravindbalineni123

Webhooks can be configured with listner

If not toyou need to do get and check if it is completed or not and if not completed check again else proceed

Cheers

Yea that’s right but how can we link the webhook to Action task. If action task completed it should initiate webhook… how can we achieve this?

@aravindbalineni123

My bad…

I just checked webhooks and for action completion we dont have a webhook that we cna configure

So only way is to add the created tasks to queue…and then postpone it by few hours and add queue trigger…

And when it triggers check if the task is completed or not…if completed move forward …if not postpone it again so that it can be checked again

Cheers