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

NullPointerException during execution of pxTransferAssignment

SA-11070

Summary



In trying to transfer an assignment, you sometimes encounter a NullPointerException.
Investigation of the stack trace shows that the error is originating in step 9 of the activity "pxTransferAssignment", in the When condition that is using the Rule-Utility-Function hasMessages.


Error Messages



java.lang.NullPointerException
    at com.pegarules.generated.hasMessages_060201_NkIYplDb9nAuJCnpX0y43A.hasMessages06_02_01(hasMessages_060201_NkIYplDb9nAuJCnpX0y43A.java:110)
    at com.pegarules.generated.hasMessages_060201_NkIYplDb9nAuJCnpX0y43A.invoke(hasMessages_060201_NkIYplDb9nAuJCnpX0y43A.java:84)
    at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:131)
    at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:108)
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:7910)
    at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
    at com.pegarules.generated.pega_rules_default.hasMessages(pega_rules_default.java:1924)
    at com.pegarules.generated.activity.ra_action_pxtransferassignment_1a6f197486cae3e21e65cb247a71a0c8.step9_circum0(ra_action_pxtransferassignment_1a6f197486cae3e21e65cb247a71a0c8.java:981)


Steps to Reproduce



Run any flow that executes the pxTransferAssignment activity.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. The When condition on step 9  must be changed from @hasMessages(TransferWorkPage) to @(Pega-RULES:Default).PageExists("TransferWorkPage", tools) && @hasMessages(TransferWorkPage). This prevents an NPE when TransferWorkPage does not exist.

TransferWorkPage does not exist, when and only when, a previous step to open the work object failed. This failure prevents the creation of the TransferWorkPage.


Resolution



This issue is scheduled to be resolved in  Pega 7.1.9.
Suggest Edit

Published June 29, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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