1 of 1 people found this helpful
"Extended Object:Stupid test//hostname/*"."Value1 as String (All OS)" or something like that ... since there isn't matching data for Value 1 where Name is profile.
I tried this using the FQDN of the server as it appears in the server inventory, but same results.
Any time I add anything concerning the value, it takes away all of my operators and gives me an error. If I run these rules against a global EO, I have values to select in addition to Name and Path and everything works fine.
Thank you for the help.
if you add the local EO to the parts list of the template and enable the EO for 'browse' you should be able to live browse one of the components of the template and see what the output looks like or if it's even working. i believe in a later version of 8.x we made it possible to browse the local objects in the rule editor, but in 8.0 you are kind of stuck.
what you could do is create a global EO (w/ a different name) so you can figure out how to write the rule condition, then simply manually replace the name of the EO in the rule w/ the local one and delete the global EO.
The correct answer was to use "Extended Object Entry" and the //* wildcard that Jae pointed out.
"Extended Object Entry:Stupid test//*"."Value1 as String (Windows OS)"
Thank you all for the help.