Support Article
InvalidReferenceException when instantiating tab for ThreadIndex
SA-97677
Summary
InvalidReferenceException is generated in the log on refreshing the Pega portal.
Error Messages
Error: Error occurred while instantiating tab for the thread index:1 com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference TABTHREAD3/ACPRIMARY_0 is not valid. Reason: invalid property name: 'TABTHREAD3/ACPRIMARY_0' at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.updatePropertyInStream(ClipboardPageImpl.java:2493) at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putStringOverride(ClipboardPageImpl.java:2393) at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putStringOverride(ClipboardPageImpl.java:2349) at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putString(ClipboardPageImpl.java:2329) at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putString(ClipboardPageImpl.java:2324) at com.pega.pegarules.session.internal.mgmt.autostreams.DynamicContainerDataModel.updateCustomTabHeader(DynamicContainerDataModel.java:240)
Steps to Reproduce
- Launch the Pega Customer Service (CS) Interaction portal.
- Create an Interaction.
- Launch a Service Intent.
- Click F5 (Refresh).
Root Cause
A defect in Pegasystems’ code or rules.
The error occurs only when the pzCustomDCTabHeader (pyEnableCustomTabHeaders) and the AjaxContainer are configured in the document during the Refresh usecase.
The CustomTabHeader recreation (DynamicContainerDataModel.updateCustomTabHeader) must be skipped for the AjaxContainer because the CustomTabHeader is applicable only to the top level dynamic container document and not to the AjaxContainer document.
Resolution
This feature is implemented in the following:
- Pega Platform 8.2.6
- Pega Platform 8.3.2
- Pega Platform 8.4
Published July 15, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.