Ever thought of an "output iterator"? It would start by executing a program of some type, then iterating over each line of output. It would make it easy to have a very simple filter. For example today I wanted to filter out the output of the "dir /s" command, ditching any line with "(DIR)", "File(s)", or a blank line.
Of course, I could achieve the same result by writing the result to one file, then doing a file contents iterator to write it to another file, then delete the original. But not as elegant or cute, eh? 
Steve
what about using a List Iterator? You could set the Log to Variable to a variable, and then use that variable in the List Iterator action. It’s not as elegant as an action that does the whole thing, but is better than writing to a file and then reading it back in
.t8
Hey, I didn’t know you could “Log to Variable”. That’s pretty nifty.
Steve