I'm receiving the following error when configuring an escalation timer: "ERROR:EVAL:@reason=index". I saw a corresponding knowledge base article indicating that I should not have a load() in a rule within the escalation timer, but even after removing that load(), and even directly inputting my expression into the expression editor, I'm still receiving this error. Has anyone experienced this issue before or have any insight? Code is below:
caladdhours( rule!XXXX_getXXXX( caseId: ri!case.id, statusId: ri!case.statusTypeId, pagingInfo: a!pagingInfo( startIndex: 1, batchSize: 1, sort: a!sortInfo(field: "createdOn", ascending: true) ) ).data.createdOn, rule!XXXX_getREFXXXX( id: ri!case.xxxxTypeId ).data.slaBusHrs, "XXXX")
Discussion posts and replies are publicly visible
is this issue resolved? I am facing the same issue in19.2 version
Keywords cannot be used in escalation events, timer expressions, etc. 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."
© 2022 Appian. All rights reserved.