I have a baseline that only has content created in the month of July and I need relevance for the baseline to say that if the server doesn’t have applicable content from July then it’s not relevant for the overall baseline.
I tried this but it’s not working 
and I know I’ve probably spent way too long looking at it so fingers crossed I’ve just missed something stupid.
exists ((bes fixlets) whose (source release date of it >= (now - 1*month) AND source release date of it < now)) whose (exists applicable computer of it AND globally visible flag of it AND relevant flag of it)
That’s Session Relevance, so it’s useful in the REST API, Web Reports, or Dashboards, but a client cannot evaluate that to determine baseline relevance. You’d need something that works purely in Client Relevance.
Using the GUI, what we would normally do is to use the “Baseline will be relevant” checkbox on the baseline components. In your case, you’d only check the box for the July components, and un-check the box for anything. The baseline will only be relevant to the machines that are relevant to at last one of the checked components.
If that meets your needs and you need to figure out how to “check the box” for API imports or something let me know and we can investigate.
Jason - I can’t even believe I was trying to use session relevance in there - it’s only Monday and it feels like my brain is mush already - so stupid of me.
1 Like
OK so I’ve updated the baseline and removed the ticks where required but because the baseline is auto created via the API I’m assuming I just need to mark IncludeInRelevance=“true” as IncludeInRelevance=“false”
1 Like
Exactly right! The IncludeInRelevance attribute is the right one to change.
Normally a Task has this as ‘false’ and a Fixlet has the ‘true’ value but those can be customized.
1 Like
