I haven't checked, but I doubt that it's changed....32k is fairly large for a text field...you of course could change it on your end, but ensure that you also change any 'follow-on' fields as well...anywhere that the body of the message goes needs to be enlarged as well....I would personally suggest that the user not send such a large email to Remedy
1 of 1 people found this helpful
Field length is not changed in 18.05 too. it remains at 32000 bytes.
We created an overlay and set it to 0 (unlimited) - we didn't encounter any issues so far.
Hi, it's not the user fail. Normally, it works like this.:
User creates a new ticket in our system. Then some support staff wrote an Work Info to the ticket, so user is notified about the work info. And then, user makes an REPLY to this email, and replies to remedy. So, for example, the first reply is a 2000bytes long. But, because the request needs a too many consultations, there are more than 10 work info entries in it. And because some support staff people also reply to these emails, they are getting bigger. So you can imagine, if you do a RE: RE: RE :RE :RE ....... more than 10x , the email gets a log of characters, more than 32 000. And then this error occurs.
I'll try the Overlay and set it to 0, as mentioned by Juergen below
Thanks, I was thinkig about the same, to make it to 0. Because I didnt find any workflow working with that "Field Values" field afterwards.