Hi everyone,

We have recently started using the Pega Platform to explore insights with the Traditional UI, while rendering landing pages with the Constellation UI. We've encountered several challenges, beginning with Group content security policy issues, which we managed to resolve. However, there are still many unresolved issues. We are reaching out to those who have successfully implemented insights and replaced Report definitions.

Here are a few open questions we have:

1. Scenario: An insight is defined in a Work- class with a report definition that reports on all descendant classes. The data retrieval preference is set to "Use search data (if available)." There are several descendant classes, each configured with its own database table (concrete classes). When we launch this specific insight from the Explore Data landing page, we receive a "Something went wrong. Please try again later." message at the top, but it still provides results. The same message appears for a chart-type data drill down. Upon tracing and debugging, it seems to be due to default association rules like pxCreateOperator, pxUpdateOperator, etc., automatically added to the insights (We have not explicitly defined any associations).

   Has anyone experienced this behavior and found any solutions?

2. Scenario: For the same scenario above, we couldn't see a few fields in the available fields pane. For example, pyID wasn't available for selection, even though it is by default optimized, marked as relevant, and active for the class. However, the same field is available for use in other implementation classes. So, the question is, is insight recommended for the above-mentioned scenario? Considering there are OOTB insights available in the Work- class, but they don't have reporting on descendant classes enabled.