DPS: transform attribute value - more than sub-string - more like awk/sed

Question

We have been working on using DirProxy to transform telephoneNumber from "(XXX) YYY-ZZZZ" format to a "Y-ZZZZ" for our VoIP call manager and and have been successful.
How we find out that our VoIP phones have feature that lets users search by phone number. The problem is that there is no way to input a dash (-) character on the phone so we would like to be able to translate from the "(XXX) YYY-ZZZZ" format that is stored in LDAP to "YZZZZ",
Anyone have suggestions on how to do this? (We know we can create a local attribute in the LDAP master in the format YZZZZ and have DPS return that attribute as telephoneNumber, but we are hoping we can do the transformation on the fly.)
Thanks.

Answer 1

I'm on the roads for a few weeks and have limited bandwith but here is what I did recently with the DPS version not released yet. Hope this works with DPS 6.3
I created 3 transformations and associated them with the dataview, assuming phoneNumber looks like (XXX) YYY-ZZZZ
In the example below, reworked number is returned in attr yz
- step1 : extract trailing Y
- attribute name : y // temp attr
- model : mapping
- transformation: add value
- viewValue : substring(${phoneNumber}, 7, 8)
- internalValue: ${xxxx} // dont care
-step2 : extract ZZZZ
- attribute name : z // temp attr
- model : mapping
- transformation: add value
- viewValue : substring(${phoneNumber}, 10)
- internalValue: ${zzzz} // dont care
- viewValue : substring(${phoneNumber}, 7, 8)
- internalValue: ${xxxx} // dont care
-step3 : reconstruct
- attribute name : xz // temp attr
- model : mapping
- transformation: add value
- viewValue : ${y}${z}
- internalValue: ${y}${z}
Note that this would work for searches only, and when the reworked attr is not present in the search filter.
Hope this helps
-Sylvain