Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consider appending quantity of scan terms matched #42

Open
cgrayson opened this issue Jul 31, 2017 · 0 comments
Open

consider appending quantity of scan terms matched #42

cgrayson opened this issue Jul 31, 2017 · 0 comments

Comments

@cgrayson
Copy link
Contributor

When scanning for multiple terms, it's not straightforward to determine how many of the scans (whether required or forbidden) matched. As discussed in internal AP Slack, it might be a nice enhancement to append data that can be easily evaluated in subsequent rules.

Of what was discussed, I think something like a field called how_many_matched, with possible values "none", "some", and "all" would work well. Opening this issue to discuss, and track future needs for this.

The workaround used by support in this instance, where they needed to make sure none were matched, was this filter rule: "TrustedForm Scans Found * is blank".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant