NextGen Knowledge Center

Iterator Filter Rule

This is a special type of rule that allows you to decide whether to filter a message or not by iterating through an array or list of XML nodes. The child rules underneath the Iterator determine the accept/filter behavior of the overall rule. For additional information, see Working With Iterators.

Item NameDescription
Iterate OnThe element to iterate on. This may be a list of E4X XML nodes, or a Java / JavaScript array.
Index VariableThe index variable to use for each iteration.
Accept Message IfDetermines how to logically combine each iteration into the overall accept / filter behavior.
  • At Least One: If the logical combination of the child rules returns true for at least one of the iterations, the overall Iterator behavior will be to accept the message.
  • All: If the logical combination of the child rules returns true for all of the iterations, the overall Iterator behavior will be to accept the message.
Break EarlyIf this is enabled, the iterator loop will terminate as quickly as possible. For example if "At Least One" is chosen above, the loop will terminate as soon as the first iteration returns true.
Drag-and-Drop SubstitutionsWhen drag-and-dropping values into the children underneath this Iterator, the index variable (e.g. "[i]") will be injected after any of these prefixes.

For example if your index variable is i and you have msg['PID'] in the Drag-and-Drop Substitutions table, when you drag the value msg['PID']['PID.3']['PID.3.1'].toString() from the Message Trees Tab into a child rule, it will automatically be replaced with msg['PID'][i]['PID.3']['PID.3.1'].toString().