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

Undefined class "SearchTemp" refreshing browser CSFSSYSADMIN



In the Research Interaction, on refreshing the browser and switching to another tab, a Display error occurs and unable to navigate further.

Error Messages

Display error:

Action that failed:-For class:Data-Portal-Current operator:CSFSSYSADMIN
Object key:- Read/Write:true
Error message:Problem invoking function: pega_processengine_workutilities.pzHasAccessToWorkPool--(String), Undefined class "SearchTemp"
[egaRULES-MasterAgent] [STANDARD] [shared] [ ] (internal.async.Agent) INFO - System date:  Total memory: 7'824'474'112 Free memory: 5'551'299'400 Requestor Count: 14 Shared Pages memory usage: 0% Current number of threads: 122
[http-nio-8080-exec-3] [TABTHREAD3] [shared] [PegaCSFSSample:07.31] (nternal.library.LibraryRuntime) ERROR bfl-wfl-001|11.111.111 CSFSSysAdmin - Problem invoking function: pega_processengine_workutilities.pzHasAccessToWorkPool--(String)
java.lang.IllegalArgumentException: Undefined class "SearchTemp"
at com.pegarules.generated.pzHasAccessToWorkPool_071017_k_68hYobMy083oKDB11lxg.pzHasAccessToWorkPool07_10_17( ~[?:?]
at com.pegarules.generated.pzHasAccessToWorkPool_071017_k_68hYobMy083oKDB11lxg.invoke(pzHasAccessToWorkPool_071017_k_68hYobMy083oKDB11l

at org.apache.coyote.AbstractProtocol$ConnectionHandler.process( ~[tomcat-coyote.jar:8.5.33]
at$SocketProcessor.doRun( ~[tomcat-coyote.jar:8.5.33]
at ~[tomcat-coyote.jar:8.5.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$ Source) [?:1.8.0_181]
at org.apache.tomcat.util.threads.TaskThread$ ~[tomcat-util.jar:8.5.33]
at Source) [?:1.8.0_181]

Steps to Reproduce

  1. Log in as CSFSSYSADMIN user.
  2. Search for any individual or organization.
  3. In the results list, select the StartResearch option from the Context menu.
  4. When the interaction loads, refresh the browser and switch back to the Search Results tab.

Root Cause

A defect or configuration issue in the operating environment. 

Pega does not support reloading a temporary work object.


The issue occurs due to a refresh on a screen where a case which is not yet persisted is displayed. Reloading a temporary work object is not supported. Hence, a static harness message after a  reload must be included to state, 'Reloading temporary work object is not supported'.

In Pega 7.4, in the pzpega_ui_dynamicContainer_lite.js file, the replaceHistory method is modified and includes a new harness, pyTempWorkObjectErrorMessage, to configure the message to display when reload fails.


Published October 10, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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