Question
RBC
CA
Last activity: 12 May 2025 11:44 EDT
Pega Robot Studio: move mulitiple 19.1 projects to asset based solutions
My org has numerous 19.1 projects that we combine into solutions like:
top level: solution
middle level: WinApp & Web app projects
bottom level: commonUtility library project
Using the conversion utility 19->22 it creates one solution for the top level with all the code pulled together. that breaks our portability/reuse of the middle level. turning the projects into assets seems the way to go, but how do I maintain "import" mapping when recombining the separate asset project into each other and top level v22 solution. Looking for suggestions/articles..
Pegasystems Inc.
US
@RobIsTheName The way to do this is to upgrade the lowest level projects as assets first. Once all the child projects have been upgraded and deployed as assets, then upgrade your main project and select "Use Project Assets". This will find the ones you've deployed (either into Robot Manager or into your %AppData%\Pegasystems\Assets folder) and use those instead of the project code.
Let me know if you'd like me to put together an example. If so, please send me a diagram showing your current project relationships, as I can build something from that to replicate.
Updated: 12 May 2025 10:26 EDT
RBC
CA
Hi @ThomasSasnett,
Our understanding is that if we add the asset to the main project, it becomes "read-only". How can developers troubleshoot in the main project if the asset doesn't work as planned? Any ways, the developer can temporary modify the asset code for troubleshooting purpose before updating the asset project?
Regards,
Fiona
Pegasystems Inc.
US
@FionaCherryIt is best to think of an asset like a finished product. You can troubleshoot it as much as you wish but changing it would defeat its purpose as a separate, tested and deployed entity. If you wish to modify the asset, you would need to check the code out of source control.
I would make sure that your asset is tested and complete before you elect to publish it. Once it has passed all of your unit testing, then your other developers would be able to use it in its stable state. If they determine it lacks something or has a bug, then the owner of the asset should be responsible for changing it, testing it, and then re-deploying the asset.
RBC
CA
Hi @ThomasSasnett,
It makes sense if it's a brand new build. With all the legacy/existing codes in v19.1, it could be challenge for us to manage those after the version uplift.
Do you have any recommendation?
Regards,
Fiona
Pegasystems Inc.
US
@FionaCherry Presumably, your project that you wish to convert to an asset is working now. If so, then you should upgrade it and perform unit testing on it. If it passes the unit testing, then deploy it as an asset to be used in the larger project. Do this for each of your assets as you reconstruct your main project with these assets. If that doesn't meet your needs, you can always convert to assets later, albeit at an added labor effort. It is best to decide now, so that you can avoid as much technical debt as possible.