Validation Regex not working

Hi,

We have the following regex placed in one of our DCT.

 "^[\sA-Za-z0-9!~`@#\$%\^\&amp;\*\(\)\_+\-=\{\}\|\[\]\\:';"<>?,./]{0,4000}$"

The issue is earlier when we were on TS 6.1 it was working all fine, however after migration to TS 6.7.1 SP 1... somehow it stopped working and accepting only upto 300 chars.

Does anyone know, if it is a known bug in TS 6.7.1 SP 1 or something is not correct as per regex is concerned??

Thanks.

Find more posts tagged with

Comments

ISCBorisB

Hi,

We have the following regex placed in one of our DCT.
 "^[\sA-Za-z0-9!~`@#\$%\^\&amp;\*\_+\-=\{\}\|\[\]\\:';"<>?,./]{0,4000}$" 
The issue is earlier when we were on TS 6.1 it was working all fine, however after migration to TS 6.7.1 SP 1... somehow it stopped working and accepting only upto 300 chars.

Does anyone know, if it is a known bug in TS 6.7.1 SP 1 or something is not correct as per regex is concerned??

Thanks.

Unescaped forward slash *may* be an issue, see if escaping it helps.
I've also used " instead of ", depending on your DCT Syntax that may or may not be needed.
In either case, 'apos' and 'quote' Entities are parts of DCT XML, not regex proper

"^[\sA-Za-z0-9!~`@#\$%\^\&\*\_+\-=\{\}\|\[\]\\:';"<>?,.\/]{0,4000}$"

kaalraa

Unescaped forward slash *may* be an issue, see if escaping it helps.
I've also used " instead of ", depending on your DCT Syntax that may or may not be needed.
In either case, 'apos' and 'quote' Entities are parts of DCT XML, not regex proper

"^[\sA-Za-z0-9!~`@#\$%\^\&\*\_+\-=\{\}\|\[\]\\:';"<>?,.\/]{0,4000}$"

Still the same. Not allowing to put more than 300 chars.

ISCBorisB

Still the same. Not allowing to put more than 300 chars.

That "300" limit just seems too round to be arbitrary. Perhaps you have some other validation with FormAPI,
callServer, what have you? If that's the case, some custom configuration or Environment setting may be missing in
the 67 so that 61 works correctly and 67 applies "300" as a default.

kaalraa

That "300" limit just seems too round to be arbitrary. Perhaps you have some other validation with FormAPI,
callServer, what have you? If that's the case, some custom configuration or Environment setting may be missing in
the 67 so that 61 works correctly and 67 applies "300" as a default.

I had investigates all of the surrounding cases of javascript, inline etc.

Apart from that, i had created a small DCT to check the issue and it is also behaving in same manner.

ISCBorisB

I had investigates all of the surrounding cases of javascript, inline etc.

Apart from that, i had created a small DCT to check the issue and it is also behaving in same manner.

Then you just have to build your case for the Support request. We do not know which Java Pattern Class IWOV developers
used in 61 and 67 to implement validation regex functionality, it is certainly possible that something changed.

You already have rudimentary DCT without any inline/FormAPI scripting. Apply simple validation regex like "^a{0,4000}$"
and see if that allows no more 300 a's. If you've got the problem manifested you have your case and code to submit to
Support. If not - complicate regex a little and repeat the cycle, etc...

kaalraa

Then you just have to build your case for the Support request. We do not know which Java Pattern Class IWOV developers
used in 61 and 67 to implement validation regex functionality, it is certainly possible that something changed.

You already have rudimentary DCT without any inline/FormAPI scripting. Apply simple validation regex like "^a{0,4000}$"
and see if that allows no more 300 a's. If you've got the problem manifested you have your case and code to submit to
Support. If not - complicate regex a little and repeat the cycle, etc...

I am thinking off to open a support case with Iwov.

Any Interwoven guy had any suggestion????

Adam Stoller

That "300" limit just seems too round to be arbitrary. Perhaps you have some other validation with FormAPI,
callServer, what have you? If that's the case, some custom configuration or Environment setting may be missing in
the 67 so that 61 works correctly and 67 applies "300" as a default.

This is a good point, which I ran into a couple of projects ago - in 671 text fields default to maxlength="300" - so if you want to allow more than 300 characters in a text field you need to explicitly state as much in your DCT.

Textareas do not, I believe, have any such hard-coded value because I don't believe textareas have a maxlength attribute - frankly, if you're expecting more than 300 or 500 characters - it makes more sense to use a textarea instead of a text field (some might even say that this would apply if you're expecting more than 100 characters...)

kaalraa

This is a good point, which I ran into a couple of projects ago - in 671 text fields default to maxlength="300" - so if you want to allow more than 300 characters in a text field you need to explicitly state as much in your DCT.

Textareas do not, I believe, have any such hard-coded value because I don't believe textareas have a maxlength attribute - frankly, if you're expecting more than 300 or 500 characters - it makes more sense to use a textarea instead of a text field (some might even say that this would apply if you're expecting more than 100 characters...)

Thanks Adam. maxlength = '4000' worked.