Data page running issue in Pega 7.3.1
Could you, please, help with the data page problem detailed below?
In Pega 7.3.1, after running a data page, the results cannot be seen on the screen. For example, please see the image below:
Moreover, the results cannot be found on the Clipboard or in the Tracer.
In Pega 7.3.0, running the same data page works as expected:
Many thanks in advance!
***Updated by moderator: Lochan to update platform capability***
Accepted Solution
Saltech Consulting
GB
The Load Balancer was the root cause of the problem:
'RESOLUTION
Accessing the node directly bypassing the Load Balancer does not cause the issue.
User has been suggested to check the Load Balancing configuration.'
Anamata
NL
Can you post the trace output of the entire run?
Regards,
Michel Kraaij - van den Berg
Valori ~ Innovation starts with testing
Saltech Consulting
HU
There is nothing in the tracer if you trace the datapage only.
If you trace everything then still nothing related to the datapage.
Merkle
GB
Have you trace everything? Could you please check DataPage option and select all rulesets in tracer. Hope you will find something in tracer.
Regards,
Gopesh
Merkle
GB
Hi,
Could you please share the screen shot of the Data page rule and the trigger activity?
Need to understand mote about the implementation. There should be some entries in tracer.
Thanks & Regards,
Gopesh
Saltech Consulting
GB
Hi Gopesh,
Please take a look at the attached images. Please note that the Tracer window remains empty only if I click on the Tracer button in the 'Run' popup. Alternatively, I could launch the Tracer using the link at the bottom of the Designer Studio screen. In the latter case, the Tracer window does not remain empty. But the results of the data page are still missing from the (non-empty) Tracer window.
Many thanks,
István
Anamata
NL
Both warnings in screenshot 1 can be ignored. They are irrelevant.
I've ran the same rule in my Pega 7.3.1. instance and it's working fine. So it is a isolated issue on your end. The only thing I can think of is a difference in authorizations. Can you verify that your user is correctly authorized?
Regards,
Michel Kraaij - van den Berg
Valori ~ Innovation starts with testing.
Saltech Consulting
GB
Thanks for the info and your reply! I created a new operator ID and set its Access Group to PRPC:Administrators, and then to PegaCRM-SFA:SysAdmin. Unfortunately, the situation is still the same in both cases.
Best regards,
István
Merkle
GB
Hi István,
Thanks for sharing those screen shots, few things I would suggest, could you please try?
1. Un-check the 'Reload once per interaction' option from datapage 'Load management' tab.
2. Try to run the activity stand alone and see if the results is coming correctly(trace that)?
3. Try with some other operator might be 'vashv'.
4. If you are able to run the activity stand alone and get the details, then validate the page response with the D_Page setup.
Regards,
Gopesh
Saltech Consulting
GB
Hi Gopesh,
Thanks for your reply!
1. Un-check the 'Reload once per interaction' option from datapage 'Load management' tab.
Un-checked it. The problem persists.
2. Try to run the activity stand alone and see if the results is coming correctly (trace that)?
I can run and trace the pxGetOperatorDetails activity in itself without any problems. It works perfectly.
3. Try with some other operator might be 'vashv'.
I created a new operator ID and set its Access Group to PRPC:Administrators, and then to PegaCRM-SFA:SysAdmin. Unfortunately, the problem is still the same in both cases.
4. If you are able to run the activity stand alone and get the details, then validate the page response with the D_Page setup.
Yes, this is an option: running and tracing the data source activity (report, etc.) work perfectly, as it was mentioned earlier.
Best regards,
István
Merkle
GB
That's really strange! From this we found the D_Page working fine, but the issue is with stand alone run!
Have you try to create a new data page with new name? Though don't think the name would be a problem, but sometime in my case, I found the recreation of the rule resolve some issue!
Thanks and best wishes!
Gopesh
Saltech Consulting
GB
Thanks for your reply! I created another data page from scratch. It calls the same activity (pxGetOperatorDetails). Unfortunately, the situation is still the same.
Best regards,
István
Accepted Solution
Saltech Consulting
GB
The Load Balancer was the root cause of the problem:
'RESOLUTION
Accessing the node directly bypassing the Load Balancer does not cause the issue.
User has been suggested to check the Load Balancing configuration.'