We are using a rule in exception in a user input task. When I test the expression in the expression editor it returns true or false. But the process on testing is giving the following info "ERROR:EVAL:@reason=index"Have any of you experienced this error? Any input is greatly appreciated.
Discussion posts and replies are publicly visible
is this issue resolved ?
soujanya B, this is a known limitation of Appian which is documented:"Passing arguments by keyword is not supported when creating rules for the Web Content Channel, process reports, or events. If used, it will cause the process or task to pause by exception."
My requirement is to get the SLA dynamicamically from DB and for that I created rule and calling it in Escalation timer event .
I am getting this error when calling an expression rule from escalation tab.
When i harcode the value in expression rule and calling from escalation tab of User input task , its wokring.
Is this limitation been relaxed? or is there any alternative? In our case it was working with queryEntity inside a Timer event, but failed when we turned it into a query record.
This limitation has not been relaxed, given queryRecordType requires arguments for the record type reference, I don't believe they are supported in these expressions.
© 2022 Appian. All rights reserved.