i think the problem is that you need to specify the "Name" of the Key were you are trying to check the Values from.
But as you probably won't like to specify all possible pathes to Patrol you should be able to use:
"Extended Object Entry:BPPM Version//*"."Value1 as String (All OS)"
So the //* is the bit to add to your existing Compliance Rule.
Let me know if that helps !
Thanks for the solution. I had a similar issue where the EO used in compliance rule gave same error shown above. Tried using //* as you mentioned and it worked.
I would like to understand what this //* mean here.
// is the separator between the config file or extended object name and the entry - so:
Extended Object: EO Name//EO Entry.
the * gets all entries, a ** would recurse through multiple levels of entries.