You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
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".
The text was updated successfully, but these errors were encountered: