Insights created from a Data Page sourced by a Report Definition are not displayed in Web Portal

[MaleeshaW (Maleesha Wilfred)]

I need to create an Insight that displays the average time an operator takes to complete an action.

The required historical data is available in the History-ABC-ABC3-Work-Orchestration class, specifically properties such as:

• .pxTaskElapsedTime
• .pyPerformActionTime

To achieve this, I created the following:

1. A Data Page D_PerformanceMetrics in the ABC-ABC3-Work-Orchestration class.
2. The Data Page is sourced from a Report Definition GetPerformanceMetricsList in the History-ABC-ABC3-Work-Orchestration class.
3. The Report Definition retrieves the required historical properties and data.
4. From App Studio, I created an Insight and selected D_PerformanceMetrics as the data source.
5. I configured the Insight to calculate/display the required performance metrics.

However, I am facing the following issues:

• The Insight created from App Studio does not appear when I launch the Web Portal.
• I am also unable to add this Insight to any of the available dashboards.
• As an alternative, I tried creating the Insight directly from the Web Portal → Explore Data option. However, I cannot find the properties that are being populated by my Report Definition/Data Page.

Question

Is this behavior a known limitation in Pega Platform Infinity ’26.1 regarding Insights using a custom Data Page/Report Definition as the data source, particularly when the underlying data comes from a History-* class?

If so:

• Is there a supported way to expose the fields returned by the Report Definition/Data Page to Explore Data/Insights?
• Can a custom Data Page sourced from a Report Definition be used as a data source for an Insight that is consumable in the Web Portal and added to dashboards?
• Is there a recommended alternative approach for this use case?

Any guidance on this would be appreciated.

[RameshSangili]

Ideally, it should work from Report defintion as well.

I hope you can directly configure the Insights from Work History (screenshot below for your reference).

[MarcCheong]

@MaleeshaW there is a lot to unpack here. Perhaps Some insights into Insights (and Explore Data) might help.

A few ideas off the top of my head.

1. Did you try logging out and logging back in? Caching on the newly created insight might cause issues
2. Is the data page Constellation friendly? (this might also answer question 4 as that controls which area the data page shows)
   1. The Data Page must have a List structure and be queryable.
   2. The Allow querying any column option on the Data Page definition controls whether it is exposed to the reporting/query mechanism
3. Is the class of your data object in your application definition? By default, only data objects in your app would be shown in Explore Data
4. Are you running the Insight against the data object OR the data page? Its a fine line between the two but:
   1. One is on the object
      1. 
   2. The other is in Data Pages

      1. 
         

5. Did you add the insight as “Admin - App Author Only” for visibility, that could block things
   1. 

When you say its not visible, are you talking about in Explore Data or inside Dashboards? Some screenshots might help.

Finally, have you ever added objects to your Explore Data landing page?

Once you start adding them here, you are telling the system to lock it down just to those objects, so if anyone has started adding to this list, it might not be visible.

Last Resort

I mention this as a last resort as I would prefer to fix the underlying issue why it isn’t showing. However, you can use things like pyGetDataPagesForInsightSource mentioned in https://docs.pega.com/bundle/platform/page/platform/reporting/missing-data-objects-reporting.html to specify things that are missing.

However, as you are specialising OOTB rules, it does mean you need to assess this on updates to ensure we haven’t made any changes to it that you need to take.

It does also mention some other troubleshooting steps you may want to consider:

If your Data Page is valid, but still does not appear in the dropdown, consider the following options:

• Ensure that the Index-DPParameters declare index is populated for your Data Page.
• Ensure that the Index-DataSources declare index is populated for your Data Page.
• Ensure that the number of results does not exceed the number specified in the pyGetDataPagesForInsightSource report definition on the Data Access tab. Otherwise, the system limits the number of results.

[MaleeshaW (Maleesha Wilfred)]

@RameshSangili and @MarcCheong Thanks for your insights.

We raised INC-D46480 regarding this issue.

These are the resolution steps we received and it worked!

The issue was resolved by registering the Data Page used by the Insight in the Web Portal configuration.

The following configuration was verified:

• The Data Page is a List structure and is sourced from a Report Definition.

• Allow querying any column is enabled on the Data Page.

• The Data Page is marked Available with the API option enabled.

• Most importantly, the Data Page (D_PerformanceMetrics) was added under Application → Channels and interfaces → Web Portal → Landing pages → Explore data → Objects.

• The Insight visibility was also verified to ensure it was accessible.

After registering the Data Page under the Web Portal’s Explore Data configuration, the Insight became visible and could be used as expected.

Key takeaway: For an Insight based on a Data Page to be available in the Web Portal, the Data Page must be explicitly registered under the Web Portal’s Explore Data → Objects configuration.