I might have stumbled across an issue in the interpretation of actually escaped (single and double) RegEx line breaks “
\n” in all Rule Engine Filter / Splitter Nodes. Maybe even in all as it’s too late to test all scenarios.
When you have to work with data i.e. extracted from PDF, it often can contain line breaks. Whilst I know about a workaround it’s an unnecessary step and, when working with large data sets, has significant performance implications.
Factoring in line breaks in a rule node like so
$Content$ MATCHES "^0000 (.|\n)+ 007F$" => TRUE results in the issues shown in the screenshot below.
Here is the corresponding workflow:
Cheers & Good Night