Hi guys, I’m trying to create a template for library projects. It’s not yet fully supported so I just made a library project and edited the isTemplate value in the project.json to ‘true’. Now after restarting the project I can publish it as a template to Orchestrator, but when I do that it won’t publish the xaml’s in the project, looks like only the project outline. Anyone seen this before or know to publish the project correctly so that I can have a valid and working template for library projects?
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Watch the videos on our official YouTube channel for more visual tutorials.
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
Im Currently with the same problem.
Only the option to create a template for a process is enabled:
@evangemert, you could try to publish this library offline on Settings->Locals on UiPath, and the use a VC System like Git, And for each new library do a fork of the template repository. It will be the workflow I will follow from now on.
Yeah I’m using the same workaround… Glad to hear I’m not the only one facing this problem
Its normal everytime we gain a new functionality, another one is lost hahaha It’s appears that UiPath determined a threshold of possible functionalities, anything after that they charge more with Studio Pro