report and then sending the report as the email notification. The steps
consisted of the following: 1) created a report that contains the
information that I wanted to send (which in my case was a ticket information
report), having it send the output to a file; 2) created a macro to run this
report and send the report to a text file named xxxxx.rpt (where xxxxx is
the ticket number); 3) setup a script file to call the command-line version
of aruser to run this macro and then send the resulting file as email
(passing in the filename and email address as parameters to the script file)
using the UNIX mailx command; 4) setup the notification active link to run
the script file as a process, passing in the ticket number and email address
as parameters to the script file.

-----Original Message-----
From: Roger Medsker [mailto:roger-medsker@UIOWA.EDU]
Sent: Monday, August 23, 1999 5:21 PM
To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
Subject: Re: How can I get email notifications to be bigger than 255
character s?


Hi Sara. If you are using ARS 3.2 or 4.x you can do this with an extra
schema, a display only field, and an active link.

Create a new schema to hold the notification message that the support group
wants. Just use the core fields and add a single character field with input
length of zero (unlimited length) or whatever length you want.

Add a field to your support call schema to match the field you created
above. Make the field hidden and the entry mode "display only".

Then create an active link that fires on display of your support group
schema. Use a Set Fields action to set the display only field to the value
in the notification message schema. Then when you perform the notification
include this field.

This has the added benefit of allowing your customer support group to edit
the notification message with the user tool and not bother you.


ARS 4.0.2; Oracle 7.3.4; AIX 4.3.
-------------------------------------------------------------------
Roger Medsker | e-mail: roger-medsker@uiowa.edu
Remedy Project Manager |
The University of Iowa | Phone: 319-335-5487
448 NWB | Fax: 319-335-6385
Iowa City, IA 52242-1000 |

At 01:48 PM 8/23/99 -0700, you wrote:
>Hi,
>
>I have just implemented the Remedy/Exchange integration and I am working on
>finding a way to make the mail notifications bigger than 255 characters.
>What I need is every time a new support call is submitted to our support
>call schema an email notification is sent to the customer the call is
logged
>for. This notification is longer than 255 characters, and is what our
>support group wants sent out every time a call is entered.
>
>I called Remedy tech support and they said to put the long message into a
>field on that schema and just include that field in the Notify action.
>Well, this would require that I take up DB space on every record in that
>table just to hold that notification message so I wanted to see if I could
>come up with a different solution.
>
>The solution I tried was as follows:
>
>I made a reference schema (Form Replies Holder) that would hold the
response
>message and have open variable fields. Then when a new call is submitted
in
>Tech. Support Call a piece of workflow pushes the customer's email to the
>Form Replies Holder schema. That triggers a filter that sends a
>notification to the email address received and the only thing in the Text
>box of the Notify action is the field name of the field holding the
message.
>
>All the workflow worked, but the email message still cut off at 255
>characters.
>
>Anyone know of a way to get around this? Or do all my automated
>correspondences with my customers have to be limited to 255 characters or
>less?
>
>Thanks,
>
>Sara Betts
>Echelon Corp
>
>---------------------------------------------------------------------------
>To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
>with a body of "signoff arslist". The subject line is ignored.

Roger

---------------------------------------------------------------------------
To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
with a body of "signoff arslist". The subject line is ignored.

---------------------------------------------------------------------------
To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
with a body of "signoff arslist". The subject line is ignored.