Policy Guide › Data Lookup › Complex Data Lookup Commands › OR and <fallguy> Handling

OR and <fallguy> Handling

If you combine multiple lookup commands, CA DataMinder quits evaluating as soon as a subcommand returns a True or False value that allows the overall command to be unambiguously resolved. This is a deliberate optimization designed to minimize delays when processing outgoing emails.

But for commands linked with an OR operator, it could mean, in certain circumstances, that the <fallguy> variable only returns recipients identified by one subcommand (because, with a True value already returned, there is no logical need to evaluate the other subcommands).

For example, a combined lookup command detects emails sent to the London office (subcommand A) OR members of the Sales team (subcommand B). It evaluates subcommand A first. If it successfully detects a London recipient, the overall command must also be True so there is no logical need to evaluate subcommand B. This means that no Sales recipients are written to the <fallguy> variable. If this variable is included in a notification dialog, shown when the control trigger activates, the message to users may contain an incomplete list of ‘triggering’ recipients.