In order to address updating laptops and PC’s that don’t support WOL after hours, I send out a blank/empty action with a message with something like “Please leave computer powered on and at the CTRL+ALT+DEL screen tonight as updates are ready to be applied.”
Then, in the relevance I put the relevance lanquage of the fixlet I want to apply… IE: I will copy / paste the relevance for XP SP3 and put it into my blank “message” action and it will automatically pop the message up on PC’s that need XP SP3 and let them know to leave their PC’s on… Then I create another action to actually install the patch…
What I was wondering was if there was a way in my “message” fixlet for the relevance to be something as easy as “If applicable FixletID 13501”…
This would be a lot easier then going into each fixlet / patch I want to deploy and copy the relevance out of them…
I just want to make sure you know that when you copy the Relevances a Fixlet, you should right-click and do a “Create Custom Copy”. The Relevance tab allows you to copy the combined Relevance statement, rather than having to piece the fragments together.
Back to your original question, this statement should work:
exists values whose (it = "1004619") of
headers "X-Fixlet-ID" of relevant fixlets of
sites whose (name of it = "Enterprise Security")
Note that the Fixlet ID plus the Site will make it unique, so we need to include the Site filter.
Enterprise Security is equivalent to “Patches for Windows (English)”. The other site names should be straight forward.
Ok, so I ran the below relevance in the client api tester and it came back true, however, in the actual fixlet it’s showing 0 computers as relevant…
Here it is:
exists values whose (it = “38117”) of headers “X-Fixlet-ID” of relevant fixlets of sites whose (name of it = “Enterprise Security”) OR exists values whose (it = “56201”) of headers “X-Fixlet-ID” of relevant fixlets of sites whose (name of it = “Enterprise Security”) OR exists values whose (it = “29213”) of headers “X-Fixlet-ID” of relevant fixlets of sites whose (name of it = “Enterprise Security”)
Action 10345 is the action with the relevance… I copied and pasted the exact relevance in the client API tester that I pulled the above log for and it comes back TRUE.
You’ve run into a limitation of the ‘relevant fixlets’ inspector. It can be used in a property that the client can evaluate, but not in fixlet relevance. Trying to use it in this fashion creates a potential chicken and egg scenario where the client has to be able to say which fixlets are currently relevance, while trying to determine if the current fixlet is relevant. So that’s why it won’t work.