Use of Parameters or System Properties in Insights
Hello Team,
Request your inputs on the following scenario which is a blocker.
I am trying to create a simple insight for our use case and filter cases for which the requester is the create operator, however I am unable to add properties from Operator page or requester page.
How can I achieve this without hardcoding ?
In the filters I get two options for RHS. Text Value and Another Field but when I select another field, I see field references from the same case which doesnt make sense.
Pega has done this OOTB in one of the existing insight. 'List of Work Items Entered by the Current Operator' where the RHS of the param is pxRequester.pyUserIdentifier. But when I try to do the same in my insight it doesn't work neither can I 'save as' this existing insight because as soon as I change its type to my case type, the filters are lost.
How can we achieve this, or parameterize insights ? A Workaround for us is to do the the longer way of Data page/ RD and list it on the dashboard.
Insights seems to be powerful but if we cannot do these basic things in insights such as parameterize or use system page properties in filters, then it would not help us achieve even the basic of use cases. Therefore requesting for some assistance on this topic.
***Edited by Moderator Marije to add Enhancement Request FDBK-111445***
Updated: 11 Mar 2024 8:22 EDT
Pegasystems Inc.
GB
@BraamSmithCLSA as you have been involved in documenting CLSA Community Meetup: Gain insight on Insights (May 2022) would you be able to provide some insight into the above question?
@MeghanAtkins and @SidduAdusumalli as you have both recently run the Ask the Expert - Reporting: Explore Data and Insights with Meghan Atkins and Siddu Adusumalli session would you be able to provide some help on this question?
Pegasystems Inc.
IN
Currently, we expose a third option "Parameter" on the RHS for a limited set of fields:
This option is enabled just for User reference fields and some pre-defined system fields that are known to correspond to operator info. When the parameter option is selected, the filter is applied using the corresponding property on the pxRequestor page.
The intention was to avoid showing this option for regular text fields like, say State/Product/..., and cause confusion. That said, we understand the need for generalizing the feature more. We'll take this feedback and plan for this.
Thanks a lot for reaching out.