Question
Rabobank
SE
Last activity: 25 Jan 2019 7:20 EST
Error when creating Case via File Listener
While creating case via File listener, getting this below error in logs.
Problem evaluating When condition: The reference .pyDisplay().pyUIActive(1).pyStreamName is not valid. Reason: invalid subscript for non-list property pyUIActive - Error 1
Section 'pyCaseMainInner' execution error on page 'pyWorkPage' of class '{Work Class}'.
com.pega.pegarules.pub.PRRuntimeException: Error evaluating visible when ' - Error 2
Section 'pyCaseMain' execution error on page 'pyWorkPage' of class '{Work Class}'.
java.lang.RuntimeException: Component stack mismatch {"whenId":"663babf22e9b4f6f29932063521a4fcb328c908c_6","pyName":"pxVisible"}!!!!===={"paramName":"EXPANDEDSubSectionpyCaseMainBBB","liveUI":"data-ui-meta=\"{'type':'Layout','subType':'SECTIONINCLUDE','pgRef':'.pySections(3)'}\"","sectionIndex":"3","isSectionIncl":"true","pxWhenIdentifiers":{"pyVisibilityWhenId":"6fbb3c0a05e711f37c4c7929d5f4a672b116ff8d_6"},"pyName":"pxLayoutContainer","pyTemplates":[{"pxReferencedId":"6fbb3c0a05e711f37c4c7929d5f4a672b116ff8d_5","pyName":"pxSection"}]} - Error 3
While creating case via File listener, getting this below error in logs.
Problem evaluating When condition: The reference .pyDisplay().pyUIActive(1).pyStreamName is not valid. Reason: invalid subscript for non-list property pyUIActive - Error 1
Section 'pyCaseMainInner' execution error on page 'pyWorkPage' of class '{Work Class}'.
com.pega.pegarules.pub.PRRuntimeException: Error evaluating visible when ' - Error 2
Section 'pyCaseMain' execution error on page 'pyWorkPage' of class '{Work Class}'.
java.lang.RuntimeException: Component stack mismatch {"whenId":"663babf22e9b4f6f29932063521a4fcb328c908c_6","pyName":"pxVisible"}!!!!===={"paramName":"EXPANDEDSubSectionpyCaseMainBBB","liveUI":"data-ui-meta=\"{'type':'Layout','subType':'SECTIONINCLUDE','pgRef':'.pySections(3)'}\"","sectionIndex":"3","isSectionIncl":"true","pxWhenIdentifiers":{"pyVisibilityWhenId":"6fbb3c0a05e711f37c4c7929d5f4a672b116ff8d_6"},"pyName":"pxLayoutContainer","pyTemplates":[{"pxReferencedId":"6fbb3c0a05e711f37c4c7929d5f4a672b116ff8d_5","pyName":"pxSection"}]} - Error 3
Section 'Review' execution error on page 'pyWorkPage' of class '{Work Class}'.
java.lang.RuntimeException: Component stack mismatch {"whenId":"663babf22e9b4f6f29932063521a4fcb328c908c_6","pyName":"pxVisible"}!!!!===={"scrollClass":"","centerInspectorData":"data-ui-meta=\"{'type':'Panel','subType':'CENTER'}\"","ariaLabelCenterPanel":"Center Panel","startWrapperDiv":"true","endWrapperDiv":"false","pyName":"pxWorkAreaContent","pyTemplates":[{"pxReferencedId":"417de4788427dbaa6acaa946e63986d886ca7d90_4","pyName":"pxSection"}]} - Error 4
This does not occur when we manually create case or create case by running the Service file.
I even tried to create cases by changing the AG to the one which was defined in the Service Package but not able to reproduce it.
Any insight on this ?
American Express Services Europe Ltd
GB
Optimum solution
IN
Hi,
We also facing the same issue when we opening the work object.
Below is the error, anyone can help on this
ERROR Proprietary information hidden| Proprietary information hidden testuser1 - Section 'Perform' execution error on page 'pyWorkPage' of class 'Work class'.
14:32:03,897 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) java.lang.RuntimeException: Component stack mismatch {"NTId":"1547015523386000","NTRef":"bfb5128620823b78f2c8f6c94b3418e1_38","pyName":"pxNonTemplate"}!!!!===={"scrollClass":"","centerInspectorData":"","ariaLabelCenterPanel":"Center Panel","startWrapperDiv":"true","endWrapperDiv":"false","pyName":"pxWorkAreaContent","pyTemplates":[{"pxReferencedId":"b2a9f06a1337744c57409cd272178119_4","pyName":"pxSection"}]}
Pegasystems Inc.
AU
Hi,
Could you please check if you have any service package and the operators have configured with the same access group? Because we might see this in such scenario's where the system pages are not loaded again for the performance considerations.
Regards,
Basavaraj
Hi,
The same errors are coming in our application as well but different scenario. When the case comes to last assignment in the screen flow, the harness is failing and we see similar errors in the logs.
We have upgraded from 7.3 to 8.1.1. Appreciate if anyone has any resolution on this.
Thanks,
Veera