Explore Data Is throwing error even after enabling Hybrid option in App Landing Page

User Experience
, , ,
1

I am trying to explore the Insights feature that Pega released in 8.6 in my personal edition. As stated in the PDN article, Insights can be created from Explore Data landing page. But when I am clicking on the landing page I am getting the following error “There has been an issue; please consult your system administrator.”.

I followed the steps in the below article to make my Landing Pages support React.

  1. Enabled “Server rendered UI” in the Advanced section and saved application rule but stills it’s throwing the same error.

Can someone assist on how to achieve this.

2

@KotaC382 Team I need assistance on this.

3

@KotaC382 I also have the same issue, but I’m using the Pega 8.6 community edition (trial).

I also enabled “Use react-based landing pages” and then proceed to create a case with reference to a couple Data objects, still when I go to the Explore Data landing page, it says: “No case or data types to explore yet”.

Application with React settings.png
Application with React settings.png659×413 18.5 KB

After trying to confirm everything is Ok on the Pega side, I noticed a bunch of errors in the Browser’s console:

Explore data console errors.png
Explore data console errors.png1920×774 60.7 KB

All of them, I think are related to the Constellation service… and start with a bad request error (400) to this URL:

https://si0v6zlf.pegace.net/prweb/sso/app/delivery_/api/application/v2/data_objects

(In my case my application is called “delivery”)

I wonder if we need to do something else from the Pega side to expose the Application’s data objects or case types to be accessible to the Constellation service…

Hopefully this can give a little bit more of context to this Insights error.

Thanks,

-Jose

4

@josenavas yes, i’ve been playing around too and came across the same issues.

On top of ticking ‘React based UI’ on your application rule, you may also need to setup the Constellation Service via the correct DSS.

5

@josenavas Hi Jose,

In your scenario, Constellation seems to be setup correctly as we are actually seeing some of the Constellation UI in your screenshot.

The failures you are seeing, with the various DX API’s not working, are generally caused by the URL of your application not being correct (appending an underscore). I notice the url in your application had an underscore after the application name (in the url it should be “delivery” instead of “delivery_”).

Can you double check that you are logging into your app with a url that doesn’t have an underscore? It should work after that. There is a bug fix to help with that, which has gone into the current release that our engineering group is working on… but for now manually removing the underscore should help.

Regards,
-Meghan

6

@josenavas Thanks for taking time and stating the analysis for me also I saw the same issue and also the issue that is stated by @MeghanAtkins . Once I remove the underscore from the app alias URL the issue is resolved. I am able to see the page with data.