We should be able to use regular expressions when defining policies. Especially policies that validate a Specific Property. The current method is very limited on ensuring that the content being provided in a particular field matches what the customer wants. For example, it is better to try and validate a phone number with something like ((\(\d{3}\) ?)|(\d{3}-))?\d{3}-\d{4} then ###-###-####. The second limits you to only 313-444-9801, where as the first allows for (313) 444-9801 or 313-444-9801. You would also be able to be more or less restrictive with regular expressions where the current method is overly restrictive and does not provide a lot of variety.
by: Richard M. | over a year ago | Configuration
Comments
Hi Richard, thanks for this suggestion. This is a valid request and one that I'd encourage other customers to respond to and/or vote on.
This is aligned to our roadmap for policy expression, and will be addressed over the next two releases.
We are currently exploring this feature and determining where to place on an upcoming road map and release