How many projects can be added to a single solution.
How many projects can be added to a single solution in Pega Robotics Automation?
I have 80 projects to be added to one single solution and rest 3 projects as Reusables that support all other 80 Projects. Kindly help me with the right way to go with solution.
Pegasystems Inc.
US
@RumanB313 In Pega Robotics 22.1 there are no more solutions. When you upgrade a 19.1 project, it will create a separate folder for each 19.1 project and will group the entire solution together as one project. In 19.1, there is no hard limit that Pega places on your ability to add new projects, however that many seems very excessive.
The more projects you have the longer it takes to open, build, and load a solution. Our best practice in 19.1 is to use an architecture where the majority of your projects are "adapter" projects and contain an adapter and all associated automations and artifacts that you wish to use with a given adapter. Each project is created as a separate project, because you want to be able to test it independently and re-use it in other solutions. Above the "adapter" projects (or other asset projects) is a controller project. This is where your business logic would lie and would essentially tie the other projects together. Above this might be your naming project. This allows you to re-use your controller since the naming project is really just an initializer for the controller and the project that actually gets deployed to Pega Robot Manager (or as a deployment package with a specific ID you place on your Runtime machines).
@RumanB313 In Pega Robotics 22.1 there are no more solutions. When you upgrade a 19.1 project, it will create a separate folder for each 19.1 project and will group the entire solution together as one project. In 19.1, there is no hard limit that Pega places on your ability to add new projects, however that many seems very excessive.
The more projects you have the longer it takes to open, build, and load a solution. Our best practice in 19.1 is to use an architecture where the majority of your projects are "adapter" projects and contain an adapter and all associated automations and artifacts that you wish to use with a given adapter. Each project is created as a separate project, because you want to be able to test it independently and re-use it in other solutions. Above the "adapter" projects (or other asset projects) is a controller project. This is where your business logic would lie and would essentially tie the other projects together. Above this might be your naming project. This allows you to re-use your controller since the naming project is really just an initializer for the controller and the project that actually gets deployed to Pega Robot Manager (or as a deployment package with a specific ID you place on your Runtime machines).
If you'd like to share your solution architecture, I could certainly provide some suggestions on it. Since I can't likely see the actual solution, I would need to see a diagram explaining how each project references or is referenced by other projects and what each project does (e.g., is it an adapter, a UI, a connector, a helper, etc.).
Below is a recent webinar where we discuss application assets in 22.1.
https://support.pega.com/discussion/pega-community-events-new-pega-robotics-application-assets
Achmea
NL
I would also strongly advise not import all 80 projects in one solution.
As Thomas said, the more projects you import, the longer it takes to open, build and load a solution.
In the past, we experimented with about 20 projects in one solution. The developer working on the solution would lose hours every week, just by waiting for the solution. With 80 projects, the waiting times will be even longer. You'll lose efficiency that way, and a situation like this might become frustrating for both the stakeholders and the developers.
Pegasystems Inc.
US
@RobinT51 This is a great point. I would add though that in 22.1, loading and running of the project is much faster since there isn't really a compilation step as there is in 19.1. In addition, the loading only starts the things that are needed as they are needed.
Evoke Technologies
IN
I have Implemented the Pega Robotics with more then 80+ projects in once single solution. and said @ThomasSasnett I created the main business Controller project and the Re-useable project referenced other 80+ projects with it.
My experience:
1) It take quite lot of time to compile the bot. - but managed how to make it fast.
2) All reference has to be crossed checked with main project integration.
3) Had to work on the bot stability and proper functioning.
4) faced a lot challenges but finally made a way through.
5) Got to learn and took up the challenge and made it work as per the client requirements.
The bot is in production and is up and working fine(Business Function). Only prod support for Website Page changes and controls changes.
Thank you @RobinT51 and @ThomasSasnett for support!