Question
Accenture
SG
Last activity: 2 Sep 2018 1:47 EDT
IndeterminateConditionalException: in RULE-ACCESS-WHEN condition
Hi Team,
Agent run is failing in production environment and none of the cases are updating for that particular agent. And its working fine in Lower environment.
Version - PRPC 7.2
Error ::
com.pega.pegarules.pub.PRRuntimeException: Error at com.pegarules.generated.activity.ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.step1_circum0(ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.java:231) at
..
...
Hi Team,
Agent run is failing in production environment and none of the cases are updating for that particular agent. And its working fine in Lower environment.
Version - PRPC 7.2
Error ::
com.pega.pegarules.pub.PRRuntimeException: Error at com.pegarules.generated.activity.ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.step1_circum0(ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.java:231) at
..
...
Caused by: com.pega.pegarules.pub.runtime.IndeterminateConditionalException: in RULE-ACCESS-WHEN UBS-FW-HRHUB-WORK-JML-JOINER NOTASSIGNEDORRELATEDTOME #20170116T030821.572 GMT: Problem invoking function: pega_rules_expressionevaluators.evaluateWhen--(String), com.pegarules.generated.evaluateWhen_071017_fEZlwEOzA7GDwvcV_fMPMw at com.pegarules.generated.when.ra_when_notassignedorrelatedtome_997d09be657c7fbae4dbaf406acf8cbc.evaluate(ra_when_notassignedorrelatedtome_997d09be657c7fbae4dbaf406acf8cbc.java:59) at com.pega.pegarules.session.internal.mgmt.Executable.evaluateWhen(Executable.java:4229) at com.pega.pegarules.session.internal.mgmt.Executable.evaluateWhen(Executable.java:4133) at com.pega.pegarules.exec.internal.basic.dictionary.AccessInfoConclusion.evaluateConditions(AccessInfoConclusion.java:936) at com.pega.pegarules.exec.internal.basic.dictionary.AccessInfoConclusion.evaluate(AccessInfoConclusion.java:797) at com.pega.pegarules.session.internal.authorization.access.AccessEvaluator.haveAccess(AccessEvaluator.java:179) at com.pega.pegarules.session.internal.authorization.access.AccessEvaluator.haveAccessWithFrame(AccessEvaluator.java:599) at com.pega.pegarules.session.internal.authorization.Authorization.haveAccessWithFrame(Authorization.java:1932) at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:4656) at com.pegarules.generated.activity.ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.step1_circum0(ra_action_establishcontext_248d42905b4016024e8caa73040dbcc4.java:220) ... 37 more Caused by: com.pega.pegarules.pub.runtime.LibraryFunctionNotFoundException: Problem invoking function: pega_rules_expressionevaluators.evaluateWhen--(String), com.pegarules.generated.evaluateWhen_071017_fEZlwEOzA7GDwvcV_fMPMw at com.pega.pegarules.generation.internal.library.LibraryMetadataCache.getFunctionInstance(LibraryMetadataCache.java:338) at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:124) at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:110) at com.pega.pegarules.generation.internal.library.LibraryFunctionUtilityImpl.resolveMethodCall(LibraryFunctionUtilityImpl.java:3136) at com.pega.pegarules.session.internal.mgmt.Executable.resolveMethodCall(Executable.java:11018) at com.pegarules.generated.when.ra_when_notassignedorrelatedtome_997d09be657c7fbae4dbaf406acf8cbc.evaluate(ra_when_notassignedorrelatedtome_997d09be657c7fbae4dbaf406acf8cbc.java:50) ... 46 more </pxStackTrace><pxObjClass>Embed-QueueErrorDetails</pxObjClass><pxErrorMessage>Error</pxErrorMessage><pyAttempt>1</pyAttempt>
Please let me know the root cause of the issue.
Regards,
Yasmin
***Edited by Moderator Marissa to update platform capability tags***
CollabPartnerz
IN
Might be issue with your when condition NOTASSIGNEDORRELATEDTOME,
Could you please check below link.
https://community.pega.com/support/support-articles/indeterminateconditionalexception
Accenture
SG
Hi,
The cases were created long back suppose August 2017 and October 2017 and 3 releases happened after that.
And for every old cases if they were trying to update the value, the changes were not reflected in the portal. This has to be update by Agent. I don't have any new cases in production to check whether the data has been refreshed and the agent able to update it or not.
And my question is why this Access when rule NOTASSIGNEDORRELATEDTOME is not affecting in lower environment. I am not getting any evidence how this rule is affecting.
Do we have any method to resolve this issue for old cases or to handle this situation.
Also, after re-trigger the case from Broken queue item, data was getting refreshed but there is no logged in the audit log for the in-flight cases.
Regards,
Yasmin
