Regular Expression In Pipeline Does Not Work As Per Specifications (Doc ID 1308838.1)

Last updated on JULY 29, 2015

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 29-July-2015***

Symptoms

Regular expression in Pipeline does not work as per specification, i.e., as described in BRM docs - see here for instance:

BRM Documentation -> Setting Up Pricing and Rating -> Pricing Center Help -> Pipeline rate plans -> Getting started with pipeline rate plans -> Using regular expressions


We identified following issues with regular expression in Pipeline:

1) not able to backslash metacharacters
We are unable to check for e.g. \. or \+. It does not even work if we use ASCII code, e.g. \043

2) {m, n} - does not work at all if m equals to 0

We were able to verify this not working in:

a) Input format "pattern"

Pattern = "(GPRS|VOICE|CSD|SMS|SMSC);[0-9]{0, 40};[\-\+]?[0-9]{4};.*\n";

This would not work.

b) iRule

Condition with =~ "[0-9]{0, 40}" or "[\-\+]?[0-9]{4}" or \043[0-9]{4} would not work.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms