Join Angel Hermira (HERMA) in this Ask the Expert session (2nd - 13th March) on Robot Manager, Robotics & Platform Integration!
Meet Angel: Angel is a Product Manager in Robotics. He joined Pega in 2018 as SSA and has grown in his knowledge through LSA and PSA roles in Professional Services. For two years, he led the Robotics services team in Europe and helped clients to architect their solutions extracting the best of Pega Platform and Robotics technologies creating Intelligent Automations before recently moving into the Robotics Product team.
Message from Angel: Hi all, I’d like to take this opportunity to share my passion and experiences creating solutions with Pega. I hope you find it as fascinating as I do.
I have a question about Deployment levels. We have 3 different Pega Robot Manager Environments Dev, Test and Prod.
I am successfully able to assign packages and select configurations.
But I am still seeing development as highlighted in Test and Production environments and on top it, I need to change configurations to test/prod in dev deployment level to run bot with correct configurations.
Test and Prod deployment level are picking up
Not sure why it is doing like that, Could you tell what is best practice to move deployment levels to next envs, assign packages and select configs
Pega Robot Manager was initially conceived as a solution to orchestrate the packages' assignments across all environments. This was when the deployment levels were created and why are there. Still some clients use it as this allows them to control which packages are assigned to who on each deployment level.
The functionality within Pega Robot Manager has evolved since and clients now typically use one Pega Robot Manager per environment as you describe or one for Development and Testing and another one for Production. The deployment levels are still useful to group the assignments on these cases but have lost a bit the purpose when there is one Pega Robot Manager per environment. However, a usage that clients use of this and I found very valuable is to control and test initial deployments (Smoke testing) on restricted users and then assigning to the wider group when certain the release has been successful.
I hope that this answers your question but happy to elaborate further.
You should verify that the bot is registered in the right Work Group and have access to the Work Queue as first step. Aside from the roles required for the robot to connect and load the package it needs access to the work assignments and should have the application's case worker role at minimum to process these.
Bots use Get Next Work Pega's algorithm function to get the assignment from the robotic work queues. The bot needs access to process the work assignment. A potential solution could be to define different roles for the different work queues and assign these to the different bot as required.