SUPPORT / SAMPLES & SAS NOTES
Problem Note 68466: A SAS® Anti-Money Laundering alert disposition fails with the error "...Expression operands do not match..."
 |  |  |  |  |
When an alert is generated, a standard product feature is that you can create a routing rule to control which queue an alert ends up in. However, if your routing rule contains any blank fields, the disposition fails when you disposition an alert that is using the rule.
In your svi-alert log, you also see an error that is similar to the following:
ERROR 2021-09-01 23:17:21.773 [sas-svi-alert] - Alerting event processing exception - Alerting Event ID: AlertingEventID199919
com.sas.fcs.tdc.exceptions.TDCUnhandledServerException: Expression operands do not match. [0:AlertingEventID199919 1:com.sas.fcs.tdc.exceptions.TDCUnhandledServerException: Expression operands do not match.]
com.sas.fcs.tdc.exceptions.TDCUnhandledServerException: Expression operands do not match. [0:AlertingEventID199919 1:com.sas.fcs.tdc.exceptions.TDCUnhandledServerException: Expression operands do not match.]
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
This issue is also fixed in the SAS® Visual Investigator 10.8 update for February 2022.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Linux for x64 | 8.2 | Viya | ||