Critical Vuln Count evaluates in Analysis and local client Fixlet Debugger - this same relevance does not evaluate correctly in a fixlet in the console

Content Authoring
1

this relevance below evaluates correctly as true or false in the fixlet debugger and as a separate Analysis in BigFix :

number of relevant fixlets whose(exists values whose(“Important” = it OR “Critical” = it) of headers “X-Fixlet-Source-Severity” of it AND not exists values whose(it contains " (Superseded)") of headers “Subject” of it AND exists (current date - it) whose(it > 30 * day) of (it as date) of values whose(exists it as date) of headers “X-Fixlet-Source-Release-Date” of it) of sites whose(“Fixlet Site” = type of it AND exists names whose(it starts with "Updates for " OR it starts with “Patches for” OR it = “Enterprise Security”) of it) > 5

When this same relevance is used in a fixlet whose action is to send out a message, it does not evaluate correctly

2

That’s expected behavior. I think the original intent is to prevent a fixlet’s result from making itself relevant (as an example). The ‘fixlet’ inspector can be used in an Analysis or in a running action script, but not in Fixlet relevance evaluation.

3

https://developer.bigfix.com/relevance/reference/fixlet.html

The <fixlet> inspectors can provide important information about the fixlets at any site. These inspectors only work in the context of property evaluation, not Fixlet evaluation.
4

Thank you very much. I appreciate the quick response.

5

Ran into the same issue myself some years ago. You also cannot use it in computer group relevance for the same reason.

It could be used in ActionScript, though,for instance to run a daily probe task and change a client setting if the count is above some number, and then use that client setting to assign a group membership.