Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Threading issue when using secondary portal



We're trying to debug an issue in our 'appeal manager' portal but when I try to to test the issue with the portal launced from the developer portal, I get this error: Failed to find instance @baseclass.CreateManualAppeal for non personal RSLH db9118f507ab04d9f8637e88d048a6e1 Top App Hash RDSAdmin!en_US_!RDSSysAdmin!03.21$dafba12263ca16bf8a23da130eaa438c of type Rule-Obj-HTML.

Error Messages

Failed to find instance @baseclass.CreateManualAppeal for non personal RSLH db9118f507ab04d9f8637e88d048a6e1 Top App Hash PegaAdmin!en_US_!PegaSysAdmin!03.21$dafba12263ca16bf8a23da130eaa438c of type Rule-Obj-HTML.

Steps to Reproduce

1. log into developer portal
2. launch secondary portal (appeal manager)
3. Click on Process Work and try to create manual appeal
4. fill out the data for the appeal and click on 'create appeal'
5. submit failed with error on screen

Root Cause

The root cause of this problem is a defect in customer application code/rules. The customized HTML is missing the thread name which is causing the issue.  We observedthese findings when looking at the information returned in Fiddler. 


The explanation for this behavior is as follows:  This information was provided to address the issue. 
Introduction to JavaServer Page tags
JavaServer Page tags à see URL
One possible change would include the addition of the <pega:url /> JSP tag so the URL includes the thread which seems to be missing. So in looking at the HTML snippet
<form style="margin:0px;padding:0px" onsubmit="return CheckRequiredManualAppealFields('CreateManualAppeal', 'AppealType;AppealSource;InitialDetermination;AppealRequestorID;AppealReasonTxt')"
name="CreateManualAppeal" ENCTYPE="multipart/form-data" method="POST" action="/prweb/PRServlet?&pzFromFrame=&pzPrimaryPageName=pyWorkPage">
    <input type="hidden" name={=pzAuth=} value="guest">
    <input type="hidden" name={=AppealEntry=} value="2">
    <input type="hidden" name="SelectedAppealType" id="SelectedAppealType" value="{Param.AppealType}"/>
    <input type="hidden" name="SelectedAppealSource" id="SelectedAppealSource" value="{Param.AppealSource}"/>
    <input type="hidden" name="SelectedAppealReason" id="SelectedAppealReason" value="{Param.InitialDetermination}"/>
    <input type="hidden" name="SelectedAppealRequestedBy" id="SelectedAppealRequestedBy" value="{Param.TmpAppRequestorID}"/>
    <input type="hidden" name="SelectedAppealDocExpected" id="SelectedAppealDocExpected" value="{Param.AppealDocExpected}"/>
Replaced by action="<pega:url value="pyActivity= RDS-Work-EPS-Appeal-.CreateManualAppeal”</pega:url>&pzFromFrame=&pzPrimaryPageName=pyWorkPage

Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us