Robotics Studio field list only includes OOTB properties
When working with Pega Robotics Studio after creating a Robot activity within my global container and providing the class name (i.e, xxx-yyy-Work-MyClass), I am able to select from 8 out of the box properties as shown in the attached image (Case ID, Label, etc...). I have defined several other properties via the case designer for this class, but I am unable to view them from pega robotics studio.
In pega server, navigating to Designer Studio > Application > Inventory > Relevant Records and entering my class name xxx-yyy-Work-MyClass, I can see both out of the box properties as well as the ones I defined in the case designer.
Manually browsing to http://<myHostName>/prweb/api/v1/data/D_pxRuleResolvedRelevantRecords?ContextClass=<xxx-yyy-Work-MyClass>&RecordType=Rule-Obj-Property only yields the same 8 out of the box properties as described above (as expected, since this is means by which robotics studio also pulls these records). However, if I instead reference the D_pxRelevantRecords data page in the url (http://<myHostName>/prweb/api/v1/data/D_pxRelevantRecords?ContextClass=<xxx-yyy-Work-MyClass>&RecordType=Rule-Obj-Property) Then I can see the fields I have defined specific to my case.
When working with Pega Robotics Studio after creating a Robot activity within my global container and providing the class name (i.e, xxx-yyy-Work-MyClass), I am able to select from 8 out of the box properties as shown in the attached image (Case ID, Label, etc...). I have defined several other properties via the case designer for this class, but I am unable to view them from pega robotics studio.
In pega server, navigating to Designer Studio > Application > Inventory > Relevant Records and entering my class name xxx-yyy-Work-MyClass, I can see both out of the box properties as well as the ones I defined in the case designer.
Manually browsing to http://<myHostName>/prweb/api/v1/data/D_pxRuleResolvedRelevantRecords?ContextClass=<xxx-yyy-Work-MyClass>&RecordType=Rule-Obj-Property only yields the same 8 out of the box properties as described above (as expected, since this is means by which robotics studio also pulls these records). However, if I instead reference the D_pxRelevantRecords data page in the url (http://<myHostName>/prweb/api/v1/data/D_pxRelevantRecords?ContextClass=<xxx-yyy-Work-MyClass>&RecordType=Rule-Obj-Property) Then I can see the fields I have defined specific to my case.
Is there any way to get Robotics studio to reference the second data page D_pxRelevantRecords? Or, more ideally, any way to modify my custom defined properties to so that they appear within the D_pxRuleResolvedRelevantRecords data page and in turn appear within robotics studio?
D_pxRuleResolvedRelevantRecords is defined in the Pega-Desktop:07-10-23 ruleset and sourced from the activity pxLoadRuleResolvedRelevantRecords. I am using Pega 7.2.2 and Robotics Studio 8.0.1045.0 (downloaded from academy training course).
Thanks in advance!
Accepted Solution
Ruletek LLC
US
We discovered that our issue required a 2-part solution:
1.) The pega user defined in StudioConfig.xml under RDA_Credentials was using access group <myAccessGroup>. This access group needed to have "PegaRULES:PegaAPI" added under its available roles.
2.) The case properties we defined needed to be exposed. This was achieved by right-clicking one of the properties in question under the App Explorer and selecting "Optimize For Reporting"
Step through the following wizard until it is completed. The custom fields should now appear alongside the OOTB properties in Robotics Studio.
NA
SA
In addition to those,
Open api service package in localhost.
1. Check requires authentication field.
2. Disable TLS/SSL for REST services in this package
This should work..!
Tech Mahindra
CA
Hi Team,
I got the same issue with Pega Robotic studio, tried the below things :
Updated the access roles in Access groups
Unchecked the SSL/TLS in the service package
Added the Pega URL under Studio.config and runtime.config files.
But no luck, still i am getting the same issue : Error while retreiving data from Pega
Please help me