Is there a way to pass variables (i.e. custom properties for the node) into the string matching section (similar to what you can do in NCM scripting ${Custom_Property_Name}? We want to be able to check for site specific routes on core switches and it seems this feature is lacking in the string matching section.
↧