ML Skill Change/Modify after moving to Production

Hi ,

We are in the process of creating our first Document Understanding Project. We have created a ML Skill for invoices. However once I move the code to Production, how do we change the ML Skill, Package and test for any changes without impacting the Production process.

Hi @nanmishra

If you want to train more documents even after moving to production, you just need to import the documents in data labelling section, train and export. No need of changing ML skill, it will be updated automatically and you need to create pipeline as well again.

Regards,
Chandrika.

@nanmishra,

Move your ML Package with this and create new ML Skill for it.

Thanks,
Ashok :slight_smile:

No I am not asking about training or creating pipelines.
We do not have a separate Dev/Prd environment in UiPath Orchestrator or in AI Center.

In the Orchestrator for all other codes we differentiate using different parameter in the code to check for Prd and Dev and point all folders accordingly.

However I am not able to understand how we can do that for AI Center ML Skill that we have created now. For example I have now created a skill MS_Invoice and made it public. I am calling that skill in my code. Once this code is deployed into Orchestrator and used for Production I will not be able to add/modify any fields in the MS_invoice as this is automatically be reflected in the Production code.

Is there any way to stop this.

I don’t have any direct experience with these things, but it sounds like you need one skill for QA and one for prod ie MS_Invoice_QA and MS_Invoice_Prod

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