E.g. string parsing and manipulation in Config Change Template scripts, to improve NCM capability and therefore reduce the need for external scripting
Would this happen to include access to custom properties? I've found that a custom property defined in NPM as an integer (numeric data) is copied to the NCM database as text. I'd like to be able to run mathmatic calculations against a custom property so the fact that it comes across as text doesn't allow for that. In my situation I'm defining a custom property that identifies the LAN address space for a site/node and I'd like to be able to add a number to the custom property and end up with a specific host address.
