EvidenceCounter content control counts the number of instances of Evidence associated with a specific
Issue on a specific
Node. Yes, the
EvidenceCounter is a real specialist! But, it can help you answer interesting questions like, "how many times does this Issue impact this Node?"
EvidenceCounter control is so specialized, you'll need to make sure that it is always wrapped in a Node content control and also in an Issue content control. Without both of them, the
EvidenceCounter control will not populate.
This page contains:
The simplest report template with an
EvidenceCounter content control would look something like this:
If we have an example project that contains just 1 Issue (e.g. Insufficient cross-site request forgery (CSRF) protection) with 3 instances of Evidence, we can use the
EvidenceCounter content control to understand how many times each Node is affected.
This sample project will export into the simple report template like:
We can filter our
EvidenceCounter content control if we want to count just a subset of our instances of Evidence.
If you haven't already, now would be a good time to review the Filtering and sorting page of this guide for more on the different filtering options available.
In the example above, you can see that one of the instances of Evidence contains a
#[Report]# field with the value Yes. We can filter the
EvidenceCounter control as shown below to only capture the instances of Evidence that have the Report field set to Yes:
Next help article: Methodology content control →