Support Article

Poor performance when browsing through data classes

SA-33128

Summary



Start with a data page with connect REST being data source. Then start from the data type underneath the name of the connector and continue to navigating through various data type. The time taken for result to come back will increase for each data type and eventually the below error screen is thrown..

Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID No ID available
Timestamp Thu Jan 12 17:29:34 UTC 2017
Engine Version PegaRULES 7.20 ML1 (coreAssemblyCached_721_916)


Error Messages



Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID No ID available
Timestamp Thu Jan 12 17:29:34 UTC 2017
Engine Version PegaRULES 7.20 ML1 (coreAssemblyCached_721_916)


Steps to Reproduce



Navigate through various data type starting from data page.

Root Cause



In the data designer, we have Visulaizer feature which shows the class relationships in a graph. For each node in the graph an RD is executed to get the reference properties. This is defer loaded. So, after we open the Resource, since it has large number of page/pagelist properties, the data is still being loaded in the background for the visualizer and in the meantime when we click on BodySite, since the graph loading is still in progress, the BodySite Data type is not opened.


Resolution



Apply HFix-31470

Published January 31, 2017 - Updated February 11, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.