Joe, What you've described in my high point of frustration with Remedy 4, 5, 6. Notify limited to 255 characters, and truncates if that number is exceeded. Had heard a rumor this would be expanded under 7.something but when we moved to 7.6.04, it's still there. Sigh
Like Fred says, need to do the push. Mark From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Tuesday, March 04, 2014 3:49 PM To: arslist@ARSLIST.ORG Subject: Re: ARERR 8976 ** We use the Push to the AR System Email Messages form with no problems Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Castleman Sent: Tuesday, March 04, 2014 1:40 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: ARERR 8976 ** Greetings, We're occasionally seeing ARERR 8976, "The CC list of the email notification message cannot exceed 255 bytes." Indeed sometimes (not always) the data we're trying to put in 'CC' exceeds 255 bytes; I'm trying to decide what to do about it. This system runs ARS 8.0, Build 001 201211030845 (I recall that might actually mean "Build 2"); it's all custom ARS with no OOTB apps. We have a number of forms that employ similar workflow, whereby a filter's notify action takes data from a temp field (where the input length = 0 bytes), in the form of one or (usually) more email addresses, and uses this string for "CC:". ($USER$ goes into "User:", so that will always be exactly one recipient.) On the AR System Email Messages form, the 'CC' field (ID 18088) has input length set to 32000 bytes. (Elsewhere, email addresses are defined as 64 bytes or less.) None of these specify (nor exceed) 255 bytes, but sure enough, if I go find the problematic Outgoing message in AR System Email Messages, the data in 'CC' is truncated to 255 bytes, so I guess this is the built-in ARS workflow (and not input lengths etc.). I see in the online documentation "Creating a notify action" that the User parameter is limited to 255 bytes, but it doesn't say anything about CC or BCC. I am guessing, though, that CC and BCC are subject to the same limitations as User. (It's hard to find documentation on the BMC website after years of knowing how to find it in the hard copy books, but that's neither here nor there, except to say that I haven't yet found what ARS says about CC and BCC.) Anyone else seen this? If so, were you able to get around it? For now, at least, I can tell the users (or devise a pop-up message etc.) that if they need to send to more than 4 or so recipients, then they'll need to do it via multiple distributions. But I'd like to devise a permanent solution if possible and get around the 255 byte limitation. I'm wondering about using a Push Fields action instead of Notify, and pushing the data to AR System Email Messages -- unless there's a central setting somewhere that I can change this for the entire ARS. Thanks, Joe Castleman _ARSlist: "Where the Answers Are" and have been for 20 years_ ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
