For instance, can I create a rule within string pattern matching like 'Config file must contain string "Hostname=${NodeCaption}" ?
You first create the rule, then the policy. Under the Policy you can use node caption as criteria but it's regular wildcard matching. You can mix and match rules assigning them to various policies.
I hope this answer helps, let me know if I need to elaborate further!
Thanks Tim but I'm looking to use, if possible, NCM node variables in rule string pattern matching, not the policy. I need to confirm a statement in a device configuration is correctly configured with the hostname of the device. I would like to be able to specify ${NodeCaption} in a rule string pattern and NCM substitute the corresponding NCM nodename when the policy/rule is tested against the configuration. Hope this better clarifies.