Question
Bradesco Seguros
BR
Last activity: 31 Oct 2023 8:54 EDT
Change stage create cases instances empty
Hello ,
I'm facing a problem that seems very strange to me in my version 8.6.1
I have a case that when it advances to the stages, it creates instances of the same case in the work table - but they are empty.
In one of these stages I execute a flow, where depending on the decision, it triggers a stage change through the Change Stage shape.
However, it changes stage, but the case screen disappears, remaining empty.
This stage he moves to, he just has the idea of solving the case. There's no flow or anything, you just enter the internship and solve the case.
I noticed that even if I change my strategy and add an assignment flow, the screen appears for my user, he can close the case, however, I noticed that he continues to generate empty instances of the same case in the corresponding work class.
I got the following error logs on my pdc:
Error evaluating visible when ' o2&& o2&& o2&& wxpzIsTabbedScreenFlow o2> rxpyFlowData.pxNodeCount ci1 o1! wxpxIsOfflinePackaging o1! wxpzIsCaseWideAction' .
Hello ,
I'm facing a problem that seems very strange to me in my version 8.6.1
I have a case that when it advances to the stages, it creates instances of the same case in the work table - but they are empty.
In one of these stages I execute a flow, where depending on the decision, it triggers a stage change through the Change Stage shape.
However, it changes stage, but the case screen disappears, remaining empty.
This stage he moves to, he just has the idea of solving the case. There's no flow or anything, you just enter the internship and solve the case.
I noticed that even if I change my strategy and add an assignment flow, the screen appears for my user, he can close the case, however, I noticed that he continues to generate empty instances of the same case in the corresponding work class.
I got the following error logs on my pdc:
Error evaluating visible when ' o2&& o2&& o2&& wxpzIsTabbedScreenFlow o2> rxpyFlowData.pxNodeCount ci1 o1! wxpxIsOfflinePackaging o1! wxpzIsCaseWideAction' .
(root cause) Type com.pega.pegarules.pub.PRRuntimeException Message Error evaluating visible when ' o2&& o2&& o2&& wxpzIsTabbedScreenFlow o2> rxpyFlowData.pxNodeCount ci1 o1! wxpxIsOfflinePackaging o1! wxpzIsCaseWideAction' . Stack at com.pega.pegarules.session.internal.mgmt.autostreams.AutoStreamRuntimeImpl.handleEvaluateWhen(AutoStreamRuntimeImpl.java:1275) at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.updateWhenInContextData(ContextProcessor.java:2437) at
(top level exception) Type com.pega.pegarules.pub.PRRuntimeException Message Section 'pyActivityPage' execution error on page 'pyWorkPage' of class 'BS-RetencaoSPG-Work-Retencao'. : Error evaluating visible when ' o2&& o2&& o2&& wxpzIsTabbedScreenFlow o2> rxpyFlowData.pxNodeCount ci1 o1! wxpxIsOfflinePackaging o1! wxpzIsCaseWideAction' .
com.pega.pegarules.pub.PRRuntimeExceptioncom.pega.pegarules.session.internal.mgmt.autostreams.AutoStreamRuntimeImpl.handleEvaluateWhen!1275:com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.ContextProcessor.updateWhenInContextData!2437:com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.RuntimeContextTree.executeVisibleWhen!356:com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.context.RuntimeContextTree.beginVi...
attached the log detail
Accepted Solution
Bradesco Seguros
BR
@KotaC382 I found out that they made a specialization for the application class of a section rule called pyActivityPage that was impacting the completion of the case. Once I started using the native one in the work class, the problem was solved. Thank you for sharing an investigation idea, this helped me identify other possible gaps
Cognitonic Systems Australia
AU
@GuiValino1984 Based on the error what I can understand is it is trying to access some when rule in the context of pyWorkPage which PEGA is not able to identify. Due to which pyWorkPage might be becoming class less or and empty page is recreating with the class and getting saved during the change stage. Because of this reason empty work instances might be getting created.
Try to identify the when condition that is failing and save it the level where it gets identified. This should resolve your problem. Do not include any explicit commit when you are doing the change stage, as the commit happens as part of the process.
Regards,
Naga.
Bradesco Seguros
BR
@KotaC382 Thank you very much for your return. It seems to make sense to me, because previously there was a when code in the decision shape that led to the stage change call and it was decided to use a Boolean expression. I will check this and perform further tests.
Accepted Solution
Bradesco Seguros
BR
@KotaC382 I found out that they made a specialization for the application class of a section rule called pyActivityPage that was impacting the completion of the case. Once I started using the native one in the work class, the problem was solved. Thank you for sharing an investigation idea, this helped me identify other possible gaps