DCI rules provide the ability to make element decisions based on conditionals, for example:
#####################
userString != ".*-2800-.*"
{
setPoll ("No");
}
#####################
However, this "no match" conditional does not allow to make decisions like:
setSysContact ("$1-$2")
In order to take advantage of the data before and after the matching condition, a positive match is needed, for example:
#####################
userString != ".*-2800-.*" and
userString matches ".*-.*-.*" :
{
setSysContact ("$1-$2");
}
#####################
In this way, the "no match" conditional provides the exclusion desired, while the "match" provides regular expression access to the data in the given DCI field.
Related Issues/Questions:
How to match an element based on negative logic using DCI rules
DCI rules
Problem Environment:
eHealth
(Legacy KB ID CNC TS19100 )