Question
Wipro
US
Last activity: 14 Aug 2015 6:44 EDT
Custom fields are not populating for a new report from report browser
Hi,
I need to present customized properties list for a new report using the data trasform pyReportEditorProperties as suggested in below article.
As per my understanding, this data transform will be called from the OOTB activitypzPrepareReportExplorerFieldNames.
But this activity has precondition to execute this transform and the condition is like operator should not be allowed check out.
For create a new report end user should be able to check out the rules otherwise he can not create a report.
This is contradicting with each other.
Can anyone please clarify me on this.
Note: I am using Pega 7.1.6.
Thanks,
Shivakumar Singani.
Accepted Solution
Pegasystems Inc.
IN
Hello,
I think this support article talks about the same kind of issue : https://collaborate.pega.com/discussion/user-enhancements
What i understand that you can follow the PDN article but you have to ensure the test is completed using a 'user' instead of a 'developer' operator and that 'user' does not have the "Allow rule checkout" option enabled.
Wipro
US
Thanks Santanu, I am testing it with end user having allow rule checkout disabled.
But I missed to uncheck the check out option in design time configuration ruleset. that is why it is not picking the data transform.
Thanks.
Wipro
US
Hi Santanu,
It is working but still I have some other issue.
I am still confused why we there is dependency on check out option for presenting custom fields where as there is no such dependency in creating a new report.
Generally we have minimum of 2 design time configuration rulesets, one for delegated rules and other for reports.
This disabling check out option from operator id works for reports, but it will not for delegated rules as we need to have that so that no one can modify any rule by mistake.
Can anyone please clarify me on this.
Thanks,
Shivakumar Singani.
Pegasystems Inc.
IN
Hi Shivkumar,
Sorry for delay in reply, Let me do some analysis in my lab system . I will get back to you in few days with my observation and opinion.
Pegasystems Inc.
IN
Hi Shiv,
The question that you have is really great.
So basically you have two scenarios :
1.One where you want your end user ( typically manager ) to be able to delegate rules and use it as per their need
2.Another where you want to restrict the user from seeing all the data on the data explorer while editing any report.
For requirement number 2, you need to have the "Allow rule check out " disabled .
For requirement number 1 you asked that how you can proceed with "Allow rule check out" disabled ?
I was going thru multiple help article on PDN to understand the different option available for rule delegation and this PDN Help article https://community.pega.com/sites/default/files/help_v71/howto/howto2/howtodelegatedrulev5.htm gave a nice pointer which I believe can give you the answer.
The article ( under "A best practice" stanza ) says :
Hi Shiv,
The question that you have is really great.
So basically you have two scenarios :
1.One where you want your end user ( typically manager ) to be able to delegate rules and use it as per their need
2.Another where you want to restrict the user from seeing all the data on the data explorer while editing any report.
For requirement number 2, you need to have the "Allow rule check out " disabled .
For requirement number 1 you asked that how you can proceed with "Allow rule check out" disabled ?
I was going thru multiple help article on PDN to understand the different option available for rule delegation and this PDN Help article https://community.pega.com/sites/default/files/help_v71/howto/howto2/howtodelegatedrulev5.htm gave a nice pointer which I believe can give you the answer.
The article ( under "A best practice" stanza ) says :
So having that particular ruleset ( used for delegation ) , and keeping the require check out option disabled. i think , will help you to take care of the requirement !
Wipro
US
Thanks for the response Santanu.
But the restriction for custom fields is also on the check out option in operator id.
as you mentioned the requirements, what if both should be handled by one operator?
Pegasystems Inc.
IN
Hi Shiv,
That's an wonderful question ! I will keep this thread open for further discussion by other SME on this community !
Wipro
US
Hi Santanu,
It is working but still I have some other issue.
I am still confused why we there is dependency on check out option for presenting custom fields where as there is no such dependency in creating a new report.
Generally we have minimum of 2 design time configuration rulesets, one for delegated rules and other for reports.
This disabling check out option from operator id works for reports, but it will not for delegated rules as we need to have that so that no one can modify any rule by mistake.
Can anyone please clarify me on this.
Thanks,
Shivakumar Singani.