I have a UiPath tenant dedicated to Production, with only Production runtime available. I have set up the UiPath Assistant and connected the machine successfully. However, the folder created is empty, and I don’t see any packages or processes available.
How can I add a process in this setup? Where should I upload or deploy the required packages?
Click on Publish button and provide necessary information
Or
If you are having NUPKG file go to Orchestrator follow below steps
Regards,
If you are Choosed publish option to Orchestartor Tenant Process Feed then it’ll appear in package (Like step 4)
If you choose option to custom, then you have to perform all steps to upload pkg from local to tenant.
If you found helpful, mark as a solution.
Happy Automation
On this system I don’t have the licence to install the UiPath studio. I’ve only production (unattended) runtime licence. I’ve other 2 tenants dedicated for dev and uat.
You have to check with developer or admin to check whether you have to access of that folder they had published the package or not.
Or share the screenshot , might be we can help better.
Thanks
I have 3 tenants dedicated to Dev, UAT, and PROD. In Dev and UAT, I have an Automation Developer license, so I can set up UiPath Studio and publish my workflows.
However, in PROD, I only have a Production (Unattended) Runtime license, which means I can only install UiPath Assistant.
My question is: How can I get the workflow in PROD without UiPath Studio? Do I need to manually upload the package?
Screenshot is here:
Yes , you have add process and upload .nupkg file.
then each time when i publish the workflow from Dev i should re upload the package? How this will work in CI/CD ?
Yes you can configure CI/CD:,
Or check belo link,
Yes, we also follow the similar process with a little difference.
We have 2 orchestrator instances prod and non-prod and non-prod one further have 2 tenants dev and uat.
Dev is only for development purposes.
Uat is used literally for Uat with business stakeholders and once the approval is gained from business on a particular process, then the package version which we have got approval from business is locked and then our Primary Process Owner does the package move manually to prod orchestrator.
Developers are not allowed to move packages into prod directly. This avoids uploading of any unwanted packages into the prod and ensures the agreed version goes into prod.
However, if you are looking for a quicker way to move resources from lower environments to a prod environment in a controlled manner, kindly give a read to the below thread on solutions management, might be helpful.
Regards
Sonali
Thank you @sonaliaggarwal47 and @prashant1603765 for providing useful info and links.
@manjula_rajendran great to hear!
Please mark as a solution tick & Close the thread.
Thanks, Happy Automation
I would recommend you take a look at Solution Manager:
I would say it’s the step between manually uploading the .NUPKG and CI/CD.
It allows you to group Processes, Assets, Queues, any artifact really - in order to deploy it from Environment A to Environment B.
It’s a much cleaner way of managing deployments, and keep control of asset values in the process.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
