Add Regular Expression-type feature to Processing Rules

[#1]

The current features (starts with, contains, ends with, etc) are nice, but having actual Regular Expressions would be even better!

If this isn't possible, one great improvement would be to allow for IP Address ranges to be used. For example:

Instead of creating a Processing Rule defined as:

Starts with:

129.32.34.15

129.32.34.16

129.32.34.17

129.32.34.18

129.32.34.19

129.32.34.2

Et cetera.

It'd be much more powerful to define the rule as:

129.32.34.15-255

[#2]

Regex capability within processing rules would be very useful and have multiple use cases for us. For example: Creating alternative campaign attribution models. Say you wanted to have a new eVar that will serve as an alternative marketing attribution variable to the "campaign" variable, but not including certain traffic types. The "contains" conditional operator just isn't powerful enough. I want to be able to write a regex against the campaign value to only copy campaign to the new eVar when certain regex conditions are or are not met.

[#3]

Couldn't agree more.  Processing rules would be much better with regex support!

[#4]

Thanks for the promotes guys!

Tag Manager needs the same regex support: http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/Add-Regular-Expressions-to-H ost-Match-and-Path-Match-in-Tag/idi-p/6791

[#5]

 I agree.  Providing regex support for processing rules will make this functionality very powerful!