i am unable to see case details after upgrading from 8.5.5 to 8.6.4

User Experience
, , , , ,
1

i am unable to see case details after upgrading from 8.5.5 to 8.6.4

we see the follwing error in the logs

[8/16/22 15:00:15:842 EDT] 000000cd SystemOut O 2022-08-16 15:00:15,812 [ WebContainer : 6] [UserPortal] [
] [ SPC:01.01.01] (ternal.mgmt.StreamBuilderTools) ERROR pegauat.saifg.rbc.com|uapg2au10 192820330 - Problem appending
stream null
com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException
at com.pega.pegarules.priv.runtime.jsp.StreamBuilderBase.handleError(StreamBuilderBase.java:161) ~[prpublic.jar:?]
at com.pegarules.generated.html_section.ra_stream_casedetails_b0c9f537721d7a9609a0d98b81c045a5.execute(ra_stream_casedeta
ils_b0c9f537721d7a9609a0d98b81c045a5.java:176) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.StreamBuilderTools.appendStreamKeepProperties(StreamBuilderTools.java:786) ~[
prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.IncludeStreamRuntime.getStream(IncludeStreamRuntime.java:339) ~[p
rprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.IncludeStreamRuntime.emitIncludeStreamReference(IncludeStreamRunt
ime.java:255) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.AutoStreamRuntimeImpl.emitIncludeStreamReference(AutoStreamRuntim
eImpl.java:433) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.emitIncludeStream(ContextPro
cessor.java:1434) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.executeSection(ContextProces
sor.java:1220) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.processSection(ContextProces
sor.java:1182) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.processSection(ContextProces
sor.java:1463) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.RuntimeContextTree.loadSection(RuntimeContext
Tree.java:515) ~[prprivate-session.jar:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.buildSection_6(ra_stre
am_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6642) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.sectionBodyIncludeInCe
ll_6(ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6648) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.pzLayoutBodyWrapper_4(
ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6627) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.pzLayout_4(ra_stream_p
ycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6703) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.simpleLayoutTemplateCe
ll_4(ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6854) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.simpleLayout_2(ra_stre
am_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6945) ~[?:?]
at com.pegarules.generated.html_section.ra_stream_pycasemaininner_53b6196929af079b31fe4e18d073afb5.pzLayoutBody_2(ra_stre
am_pycasemaininner_53b6196929af079b31fe4e18d073afb5.java:6616) ~[?:?]

Exception in : RULE-HTML-SECTION RBC-SPC-WORK-CMTMANUALCASECREATION CASEDETAILS #20210728T140210.174 GMT

Caused by: com.pega.pegarules.pub.generator.UnresolvedAssemblyError: Exception in : RULE-HTML-SECTION RBC-SPC-WORK-CMTMANUALCASECREATION CASEDETAILS #20210728T140210.174 GMT

at com.pegarules.generated.html_section.ra_stream_casedetails_b0c9f537721d7a9609a0d98b81c045a5.execute(ra_stream_casedetails_b0c9f537721d7a9609a0d98b81c045a5.java:136) ~[?:?]

2

@MarkB6885 Can you confirm whether there were any errors during the upgrade steps?

Did you carry out the steps in the Keeping Current - Testing updates documentation?

Could you please try to Revalidate and Save the CASEDETAILS section?

Check out the following support document: Troubleshooting Rule Utility Function issues for more info about these types of issues.

3

@MarijeSchillern we get following error "Validate failed for the key ‘RULE-HTML-SECTION RBC-SPC-WORK-CMTMANUALCASECREATION CASEDETAILS #20210728T140210.174 GMT’ # property definition open failed for RULE-OBJ-PROPERTY WORK- PYRESOLVEDUSERID #20180713T131937.511 GMT

4

@MarkB6885 if my suggestions above did not help and if there are no other forum user comments, then I would suggest that you log a support incident for this.

Please can you provide the INC reference here so that we can help track it?

5

@MarijeSchillern INC-237513 was opened

6

@MarkB6885 there is one thing you could check whilst we wait for support to pick this up.

My investigation shows there was a change made to the pyWorkStatus property in Pega 8.3.4

The error in your log shows the pzInsKey and it is trying to open an old rule that was in Pega-ProcessArchitect:08-01-01.

" property definition open failed for RULE-OBJ-PROPERTY WORK- PYRESOLVEDUSERID #20180713T131937.511 GMT"

This seems to suggest that the dictionary cache still contained a reference to the old version of pyWorkStatus after the patch install. So the application is trying to open the old version of the pyWorkStatus property from the dictionary cache.

The updated pyWorkStatus property is in the Pega-ProcessArchitect:08-03-05 ruleset.

It looks like the dictionary cache is perhaps not rebuilt after the patch was applied and the servers restarted.

Next Steps

Run the BulkValidateSave activity for the pyWorkStatus property and check if the issue is resolved.

Let me know if that makes any difference.

7

@MarijeSchillern

Hi Marije,

We ran the BulkValidateSave activity and tried again the bulk revalidation tool - it looks like we are still observing the same failure.

8

INC-237884 was open because the last ticket hat the wrong environment

9

@MarkB6885 I can see that the support ticket was closed with the following explanation:

t seems that on upgrade to 8.6.4, your environment did not have the latest rule PYRESOLVEDUSERID.

This rule has been updated and on re-saving this rule, casedetails section renders correctly.

Please could you mark this as Accept Solution so that users are aware how this can be fixed for possible future scenarios?

10

Thank you @MarkB6885!

I’ve linked this Question to your Support Case: INC-237884 for engineer review.