I just downloaded version 2.0.0.3 of the relevance debugger. It says BES version 7 on the About page. Should this work with a computer running the existing 6.0.21.5? When I evaluate the following in a single clause tab it works fine, but when I evaluate it in the graphical breakdown it returns “eval error”. Is this a bug or just my ignorance?
The expression I’m testing is
node value of attribute “value” of last child of select “root/command” of xml document of file “C:\Program Files\Dell\Dell Client Configuration Utility\Client\Packages\DCCUResults.xml”
The relevance debugger you have does include a few inspectors that are only available to 7.0. We decided to publish a version of the relevance debugger that supports the new inspectors a little bit before we actually release 7.0 because there are some nice new features in the debugger we thought would be useful to release as soon as possible. When 7.0 is officially released (Real Soon Now ™), we will publish a full change list that includes the new inspectors. In practice you’re unlikely to end up using the 7.0 inspectors by accident since they aren’t documented yet.
That’s a long way of saying, “I don’t think the version of the relevance debugger you have is affecting the outcome of your query.”
There should be no difference between evaluating on the graphical tab vs. the single clause tab. Is it possible that you had part of the query selected when you evaluated on the graphical tab? One of the features of the relevance debugger is that, if you select a section of relevance and hit evaluate, it will only evaluate the selected portion instead of the whole clause.
That’s my guess, let us know if you are seeing something different.
I went through it some more. I was careful to confirm I have the same statement in both tabs, and didn’t have anything selected. Also tried it with everything selected. Same strange mismatched result.
A bit more detail about the result. In the graphical view of the result tab, it shows this s) under the file “path” on the far right and
That looks like a bug to me. We’re very close to the 7.0 release date and this is a relatively minor issue, so I can’t promise that a fix will make it in to 7.0, but usually the relevance debugger is also released separately on support.bigfix.com, so a fix could show up there.
Just so there’s some feedback, both bugs have been fixed in 7.0. (The xml inspectors not working in the graphical view, and the current selection evaluation not working in the graphical view).