My RPA team has strictly used studio desktop to make all of our automations, but with the new AI tools and API workflows on the web, we want to start getting comfortable with the Studio Web and other features. I decided to create a really simple serverless background RPA workflow on Studio Web to test it out. I clicked “Create - RPA Workflow” and it created a whole solution. The only way I have found to publish the process is as a solution which creates a whole new folder in orchestrator. This is such a simple process I was hoping to just create a package and process in another all encompassing folder via the Studio Web.
Is there a way to create a simple RPA workflow in Studio Web and not publish it as a solution, or am I doing something wrong?
Also can’t find any way to connect that process to GitHub either, is that possible from Studio Web?
A solution is a wrapper around a nuget package, it can contain multiple nuget packages and things like assets, queues etc.
The need to skip this, and just publish a single artifact from a solution as a nuget package is something I’ve been asking the product team for a while, as there is often a need for it. As of yet they are sticking to the Solution wrapper.
Jon’s right on the architecture, solutions are the wrapper and theres currently no way around that from Studio Web itself
on your GitHub question, thats a real gap right now, Studio Web doesnt have native source control integration the way desktop Studio does (Git, TFS, SVN panel). The practical workaround is using “Open in Studio Desktop” on your Studio Web project, that pulls it into regular Studio where you get full Git support and can also publish it as a plain package instead of a solution if you want to skip the wrapper entirely for that one process. Theres actually another recent thread here about that button not working for some people, worth checking if you run into issues with it too
on the new folder thing, before assuming its forced, check the deployment step for the solution again, when you deploy it usually lets you pick an existing Orchestrator folder as the target instead of only creating a brand new one, its easy to miss since the wizard defaults to creating fresh. If it genuinely only lets you create new folders every time in your case, that would be worth flagging as feedback too since it doesnt match how it behaves for solutions with multiple processes
so short version, for now if your team wants the old single package single folder workflow with Git, bouncing through desktop Studio is the practical path until Studio Web catches up on both fronts.
Regarding the GitHub integration - we DO have it!
You need to use the Local Workspace however - store your files locally, not in the cloud.
After doing that you may use either the git client from the browser or any locally installed git clients.
