Question
UHG
US
Last activity: 20 Jul 2016 10:42 EDT
Issue with customizing the fields in Report Editor tool
Hi,
I am trying to customize the fields displayed in the report Editor tool. There are a few issues I am facing while doing that. I followed the steps in the below link from pdn.
https://pdn.pega.com/customize-lists-properties-and-calculations-available-report-editor
1) I click on "Add Report" and I see different values under "Case Type" dropdown listed in the "Create New Report" dialog. I want to customize it and show only one entry in the dropdown. I could not do anything with that. I tried to change my workpool in my access group but I see a lot of other "CaseType" values in the dropdown. Please let me know if there is anything I could do to customize it.
2) I click on the "More" link from Report Editor and I could see a list of of unwanted pages/properties like "pxAssignedOperatorInfo","pxCreateOperatorInfo" etc. I want to customize it and show only a few entries in that like the "Operator information" (exposed fields from Data-Admin-OperatorId). Please let me know if there is a way to do it.
Hi,
I am trying to customize the fields displayed in the report Editor tool. There are a few issues I am facing while doing that. I followed the steps in the below link from pdn.
https://pdn.pega.com/customize-lists-properties-and-calculations-available-report-editor
1) I click on "Add Report" and I see different values under "Case Type" dropdown listed in the "Create New Report" dialog. I want to customize it and show only one entry in the dropdown. I could not do anything with that. I tried to change my workpool in my access group but I see a lot of other "CaseType" values in the dropdown. Please let me know if there is anything I could do to customize it.
2) I click on the "More" link from Report Editor and I could see a list of of unwanted pages/properties like "pxAssignedOperatorInfo","pxCreateOperatorInfo" etc. I want to customize it and show only a few entries in that like the "Operator information" (exposed fields from Data-Admin-OperatorId). Please let me know if there is a way to do it.
2) I want to show only the exposed fields from my database to the users so that they can create and apply filter for the reports on these fields only. My work table (table that stores my work objects) has fields exposed from my "FW" classes and a few from "@baseclass" too. I tried to follow the steps mentioned in the above mentioned link from pdn. I am able to see the fields only from my Implementation class (where "pyReportEditorProperties" Data transform is defined) and not from the classes above that i.e. I included properties from "FW" classes and "@baseclass" but was unable to see the properties reflected in the Report Editor. Please let me know if I am missing anything.
Thanks,
Venkat
Updated: 14 Apr 2016 2:52 EDT
Pegasystems Inc.
IN
Hi Venkat, Good morning!
>>> I click on "Add Report" and I see different values under "Case Type" dropdown listed in the "Create New Report" dialog. I want to customize it and show only one entry in the dropdown. I could not do anything with that. I tried to change my workpool in my access group but I see a lot of other "CaseType" values in the dropdown. Please let me know if there is anything I could do to customize it.
- we may need to customize step #1 using Data transform rule [pyRBNewReportClasses] in OOTB RULE-OBJ-ACTIVITY CODE-PEGA-LIST PZGETNEWREPORTCLASSES available in Pega-Reporting:07-10-13 [Pega 7.1.6]
- again, it would append to the case type list available but may not support removing/restricting the list to one.
- having a security access role to create reports on the specific case type might help.
>>> I click on the "More" link from Report Editor and I could see a list of of unwanted pages/properties like "pxAssignedOperatorInfo","pxCreateOperatorInfo" etc. I want to customize it and show only a few entries in that like the "Operator information" (exposed fields from Data-Admin-OperatorId). Please let me know if there is a way to do it.
Hi Venkat, Good morning!
>>> I click on "Add Report" and I see different values under "Case Type" dropdown listed in the "Create New Report" dialog. I want to customize it and show only one entry in the dropdown. I could not do anything with that. I tried to change my workpool in my access group but I see a lot of other "CaseType" values in the dropdown. Please let me know if there is anything I could do to customize it.
- we may need to customize step #1 using Data transform rule [pyRBNewReportClasses] in OOTB RULE-OBJ-ACTIVITY CODE-PEGA-LIST PZGETNEWREPORTCLASSES available in Pega-Reporting:07-10-13 [Pega 7.1.6]
- again, it would append to the case type list available but may not support removing/restricting the list to one.
- having a security access role to create reports on the specific case type might help.
>>> I click on the "More" link from Report Editor and I could see a list of of unwanted pages/properties like "pxAssignedOperatorInfo","pxCreateOperatorInfo" etc. I want to customize it and show only a few entries in that like the "Operator information" (exposed fields from Data-Admin-OperatorId). Please let me know if there is a way to do it.
- the PDN link shared by you should be helpful. https://docs-previous.pega.com/customize-lists-properties-and-calculations-available-report-editor
>>> I want to show only the exposed fields from my database to the users so that they can create and apply filter for the reports on these fields only. My work table (table that stores my work objects) has fields exposed from my "FW" classes and a few from "@baseclass" too. I tried to follow the steps mentioned in the above mentioned link from pdn. I am able to see the fields only from my Implementation class (where "pyReportEditorProperties" Data transform is defined) and not from the classes above that i.e. I included properties from "FW" classes and "@baseclass" but was unable to see the properties reflected in the Report Editor. Please let me know if I am missing anything.
- by disabling the option 'Display unoptimized properties in data explorer' under data access tab of report definition rule should list only the exposed column properties.
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
IN
>>> I am able to see the fields only from my Implementation class (where "pyReportEditorProperties" Data transform is defined) and not from the classes above that i.e. I included properties from "FW" classes and "@baseclass" but was unable to see the properties reflected in the Report Editor
- could we quick test by enabling the option 'Report on descendant class instances' under data access tab of report definition rule and learn the behavior, please?
we may need to customize step #1 using Data transform rule [pyRBNewReportClasses] in OOTB RULE-OBJ-ACTIVITY CODE-PEGA-LIST PZGETNEWREPORTCLASSES available in Pega-Reporting:07-10-13 [Pega 7.1.6]
- again, it would append to the case type list available but may not support removing/restricting the list to one.
- having a security access role to create reports on the specific case type might help.
Just a small correction, if pyRBNewReportClasses is customized we'll only populate the dropdown with entries from it. So if you customize pyRBNewReportClasses with 1 entry, there will only be 1 entry in the dropdown.
Pegasystems Inc.
IN
Thank you MIke.
My bad. yes - there is a jump step [local.customFound=="true"] to exit activity on transition step. missed it. Thanks again!
Pegasystems Inc.
IN
Hi Phani Sahukaru,
I followed this post and I am trying to customize the 'New Report' filter. I think the first step is to create a new DT in 'Code-Pega-List' with the name 'pyRBNewReportClasses'. I am unable to create this DT, it is giving me error. Am I missing something?
Pegasystems Inc.
IN
Hi Pankaj,
- this is a known issue (addressed in latest MLs)
- the only work-a-round at the moment is to comment the validation [Page-Set-Messages] and continue the save.
- also could we quick check the save and functioning of the rule when saved in @baseclass?
- the only work-a-round at the moment is to comment the validation [Page-Set-Messages] and continue the save.
Thank you!
psahukaru
Pegasystems Inc.
IN
Thanks! I got it, I followed the following work-around for resolving this issue.
Open Decision-Table 'pzReservedNameAllowed' in private-edit, return true in otherwise instead of false. And try to save the rule again.
