We are using Pega provided "Banker Pro sample application". We have done all the configuration as mentioned.
Issue: Robot or VM is not creating for Account work group, screen shot attached "VM issue.png". Please help.
In earlier version of Pega robotic studio, In Project properties, we use to set "Robot Work Queue". which is not there in latest version attached screen shot "New Account Product.png". can some explain or guide us.
Can someone provide the Pega robotic studio solution for "Banker Pro sample application" for cross verify the configuration in Pega robotic studio.
Thanks in Advance!
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
The workgroup and baseurl are now defined in the commonconfig located in the %programdata% directory. I have attached a screenshot of what the entry should look like. Be sure that the access group for the operatorID that you will be using to register the robot has the following roles:
I believe that the BankingAdministrator operator ID comes by default with these roles applied to its access group.
If you are not using the packageserver I please enable AllowRunWithNoPackage otherwise Runtime will close because it has no package assigned to it.
Do we have to manually create Operator i.e. robotic automation Virtual Machine (VM)? No, this is generated automatically once the Robot registers successfully.
I am using Pega 7.3 and Pega Robotics Studio 8.0.1059.0. Could you please explain "If you are not using the packageserver I please enable AllowRunWithNoPackage otherwise Runtime will close because it has no package assigned to it": The package server is a new feature that was added in version 8.0.1058 that allows you to deploy a package to the RobotManager and assign it to a workgroup. This should allow the robot to download the package on start up and begin work without someone having to upload the deployment files. If there is no package assigned and Runtime is trying to connect to the server it will shut itself down.
The issue that you are seeing may be related to the decision table. By default the "Get AccessGroup for Robot by WorkGroup" decision table should point to the following access group: "BankerPro:Administrators" and would not contain the workgroup you entered in the commonconfig.
Please add the workgroup to the decision table and the accessgroup for the operatorID that you are trying to register the robot with.