Import Existing Automation/Adapter Project into a New Project in 22.1
Hi, I'm trying to import an existing Automation Project into another Automation project. In 19.1 we had the option to import "Existing Project" but doesnt seem like this option exists in 22.1. I can add an existing file but this seems a really long winded approach if I need to add into multiple projects/adapters with their own GCs, Automations etc. I quick work around would be to start a new project in 19.1, add the existing projects and then use the Import 19.1 functionality in Robot Studio - but not useful long term if upgrading an existing automations functionality.
Accepted Solution
Updated: 20 Jun 2025 4:31 EDT
Pegasystems Inc.
US
@BenT8604In 22.1, you can simply copy the files into the folder and then load the project. This is nice for when you have an entire folder of items that you want to bring in. It will detect all new files. You will need to make sure that these are truly new files though, as you'd get errors if any of those files were already present in the project. You also need to think about anything global, as you can't easily merge the Globals from different projects. Be sure to check that the files you are copying in are self-contained and do not use anything in their global container. You can mitigate this by having your automation accept parameters instead of relying on global items or return data that could then be copied into a global item.
If you truly want reusable parts (a la projects in 19.1), you can convert your project to an Asset and import that. Let me know if you'd like more information on Assets.
Nationwide Building Society
GB
@ThomasSasnett Amazing, thank you very much Thomas for the quick and thorough response. Yes if you could elaborate on Assets I'd appreciate that. Thanks
Pegasystems Inc.
US
@BenT8604 Here is the main link below. Essentially an Asset is a reusable piece of automation. Generally, it is either a Project Asset, a Utility Asset, or an Application Asset. The latter two have an interface tab that allows you as the developer to define what is visible to the developers who use the Asset. The Project Asset does not but is otherwise similar in functionality.
A Utility Asset is generally used for a collection of automations that do not involve any interrogated applications. Usually, they would contain a UI of some sort and then whatever automations you've built in support of that UI.
An Application Asset is used to encapsulate the automations around a single interrogated application. The idea here is that you can build a robust set of functionalities, build unit tests for that functionality, and then deploy that asset to other developers to make use of.
A project Asset lets you deploy a collection of automations, applications, UIs, etc. as an entire more complex project.
For the developers that consume them, Assets are read-only. This means that they can be used without worrying that other developers will modify them causing your automation code to become overly customized. The idea is that you build them once, and then use them wherever needed.
@BenT8604 Here is the main link below. Essentially an Asset is a reusable piece of automation. Generally, it is either a Project Asset, a Utility Asset, or an Application Asset. The latter two have an interface tab that allows you as the developer to define what is visible to the developers who use the Asset. The Project Asset does not but is otherwise similar in functionality.
A Utility Asset is generally used for a collection of automations that do not involve any interrogated applications. Usually, they would contain a UI of some sort and then whatever automations you've built in support of that UI.
An Application Asset is used to encapsulate the automations around a single interrogated application. The idea here is that you can build a robust set of functionalities, build unit tests for that functionality, and then deploy that asset to other developers to make use of.
A project Asset lets you deploy a collection of automations, applications, UIs, etc. as an entire more complex project.
For the developers that consume them, Assets are read-only. This means that they can be used without worrying that other developers will modify them causing your automation code to become overly customized. The idea is that you build them once, and then use them wherever needed.
Nationwide Building Society
GB
@ThomasSasnett Thanks for the information Thomas. That all makes complete sense. Thanks again for the help. Ben