When using the datasource "Text File Content" and in particular the field "Text File Name" - you want to wildcard the file name, either wildcard or use regex. This actually works when using a query but using the same logic in a check, the check (as part of a CCS standard) fails to find the files.
Control Compliance Suite for Windows 11.5 SCU 2016-1 and earlier does not support wildcards or regex for datasource "Text File Content" and in particular the field "Text File Name" when used in checks.
As of SCU 2016-2 you can use .* (dot star) as a wildcard (full regex is still not supported).
The following CCS check logic works:
Text File Line Contains 'abc' Where Text File Name Matches Pattern 'abc.*.txt' AND Text File Path Equal To 'c:\test' with Missing Data Outcome being 'Manual Review' and Multiple Data Operator being 'AND'
When that is run (using a system on CCS11.5 - SCU 2016-2) on the following set of files:
Directory of c:\test
09/27/2016 02:34 AM <DIR> .
09/27/2016 02:34 AM <DIR> ..
09/27/2016 02:28 AM 3 abc123.doc
09/27/2016 02:28 AM 3 abc123.txt
09/27/2016 02:29 AM 3 abc456.doc
09/27/2016 02:29 AM 3 abc456.txt
09/27/2016 02:29 AM 3 abc789.txt
09/27/2016 02:34 AM 24 abc999.txt
09/27/2016 02:29 AM 3 xyz123.txt
09/27/2016 02:29 AM 3 xyz456.txt
8 File(s) 45 bytes
With various files having the pattern abc in it and some don't, a C-E-R job shows/reports on only those files starting with abc and ending with .txt, which is in line with: Text File Name Matches Pattern 'abc.*.txt'