Basically Robot Manager consists of PegaRoboticAutomationConsole application which is built on AutomationPackageManager application which is built on PegaRULES application. Let's say, we have following application structure which is pretty simple and standard hierarchy - where exactly should we add PegaRoboticAutomationConsole application to?
<RM v5.1 configuration>
This way, PegaRULES application shows up twice in a diagram. Also, When Robotics UI is displayed, UI-Kit is not applied (Why didn't product team include UI-Kit just like Pega Express does)? I am feeling this could be a bit better but is this really the correct configuration that product team would expect? I actually wanted to have PegaRULES and UIKit under Robotics so it looks more straightfoward but Robotics application is locked and I was not able to change the stack.
Add the PegaRoboticAutomationConsole (latest version) to your application definition. Screenshot attached. Your UIKit is defined on your application. You then provide access to the robotic console through your access groups.
I am not sure what the ask is here. If you asking how to make the Robot Console portal available, the documentation should outline fairly well. Its a matter of adding the necessary roles, and then adding the portal to the Access Group.
The post from SIMMR-1 is correct. Just simply the PegaRoboticAutomationConsole application layer as a built-on of your top-level app (MyApp). Then, add pyRoboticConsole to the list of availale portals on your access group.