Support Article

Failed to find instance:@baseclass.CaseSearch

SA-38043

Summary



User migrated the application from PRPC 6 to Pega 7.2.

When user perform an access the Search page, click on the CaseNumber which opens in a new window, close it and on the Search page, filter the search option and Search records, user observes below error.


Error Messages



Error trying to process..Access that failed CaseSearch.
Error message: Failed to find instance @baseclass.CaseSearch of type Rule-HTML-Harness.


Steps to Reproduce



1. Access the Search page.
2. Click on the CaseNumber which opens in a new window, and close it.
3. Access the Search page, filter the search option and Search records.

Actual Behavior: Error observed with below message:
Failed to find instance @baseclass.CaseSearch of type Rule-HTML-Harness.
Expected Behavior: Search page should be accessible.


Root Cause



It was observed that when the custom Activity is called while child window is launched, it removes all the custom pages from the clipboard.

These pages gets recreated in PRPC 6 (using gadgets in Fixed portal) and not in Pega 7(using Accordions in Composite portal).

A custom activity creates such custom pages in Clipboard.

In Pega 7, these pages do gets created when user clicks on the respective usecase (implemented as Accordion);

Resolution



To know where and when custom activity (to recreate the pages) needs to be called, run a use case in PRPC 6 and Pega 7 application, trace it and compare the tracer. Figure out the activity called and configure accordingly in Pega 7.

Avoid removing the custom user pages from clipboard through custom Activity, to resolve the reported behavior.




Published May 16, 2017 - Updated June 2, 2017

Have a question? Get answers now.

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