I also had problems with @URLdecode and long strings (messages in webforms... -> bad)
I submitted the @Urldecode limit to IBM (PMR 62259 SGC 724) and they say it's not a limitation in @URLDecode but in evaluate: @explode will have the same problem. So you could add the value to field in a temp document and call @URLdecode(field) with the tempdoc as context (haven't tried yet).
To split the string correctly, you need to split it at an encoded value which begins NOT with the bytes 10xx xxxx (see http://en.wikipedia.org/wiki/UTF-8 -> table). Also not yet sure how to do that, but I think I will go that way in my websession bugfix...
I also had problems with @URLdecode and long strings (messages in webforms... -> bad)
I submitted the @Urldecode limit to IBM (PMR 62259 SGC 724) and they say it's not a limitation in @URLDecode but in evaluate: @explode will have the same problem. So you could add the value to field in a temp document and call @URLdecode(field) with the tempdoc as context (haven't tried yet).
To split the string correctly, you need to split it at an encoded value which begins NOT with the bytes 10xx xxxx (see http://en.wikipedia.org/wiki/UTF-8 -> table). Also not yet sure how to do that, but I think I will go that way in my websession bugfix...
Lots of fun...