Okay, thanks - I see that I can take it to 7999 without CLOBbering it, but 1500 is more reasonable. We'll discuss it here first.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Schon, Stuart Sent: Monday, August 08, 2011 10:28 PM To: [email protected] Subject: Re: Incident 7.6.04 WorkLogs ** Hi Yep we found the same thing and were forced to increase its size. To prevent users from adding data that should be an attachment we restricted the size to 1500, big enough for almost all text needed to be explained in the WL but forces long email trails to an attachment. We also check all the other apps to see if they had the same issue and adjusted accordingly Stuart Schon Team Leader Fujitsu Australia Limited 2 Julius Avenue, North Ryde NSW 2113, Australia T +61 2 9113 9435 M +61 458 592 245 [email protected]<mailto:[email protected]> au.fujitsu.com<http://au.fujitsu.com> [file:///C:\DOCUMENTS%20AND%20SETTINGS\SCHONST\Application%20Data\Microsoft\Signatures\Fujitsu_files\fujitsuemailsignature.gif] From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of strauss Sent: Tuesday, 9 August 2011 12:13 To: [email protected] Subject: Incident 7.6.04 WorkLogs ** Another interesting complaint today. Apparently the WorkLog Notes field (Notes: 304247080 z1D_Note) is resisting editing and limiting entry on the Incident form, where it is limited to 255 characters. The underlying field on HPD:WorkLog is 0 length (Notes 1000000151 Detailed Description), and the equivalent field on HPD:Help Desk Dialogs is also 0 length (Notes 301398800 z1D_Details). One of the problems is that the HPD:WorkLog form contains many records where this field is already populated well beyond 255 characters - throwing an error when you view and try to edit one of them through the Incident form. The disconnect between HPD:Help Desk and HPD:Help Desk Dialogs is even more puzzling, although the latter is Display Only and stores no data so 0 length comes cheap. I'll be forced to consider lengthening it on the Incident form overlay, and if it gets big enough to require a BLOB then I might as well go for unlimited. The helpdesk also complained that it would not accept carriage returns when typing inside the text box; I'm not sure what that's all about, or how to correct it. Of course this did not show up in testing since no one bothered entering anything lengthy in a test ticket. Any comments from anyone who has already gone down this road? Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
