Lisa,
Another method that is slightly more involved is to
generate and store an MD5 value each time the attachment field is
changed. MD5 values can be generated from a run process, SQL Server and
many programming languages http://userpages.umbc.edu/~mabzug1/cs/md5/md5.html.
After generating the MD5 value a filter's Run If
qualification like this 'Attachment MD5'
!= 'DB.Attachment MD5' should
work.
As a general rule, try
to accomplish what you want completely using ARS. I only mention this
approach in case it may be useful to you or others.
HTH
Stephen
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 3:12 PM
To: [email protected]
Subject: Re: Overwriting Attachments
Yes that would definitely qualify if you have deleted an attachment during
a given transaction...
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
-----
Original Message ----
From: "Kemes, Lisa" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 2:59:58 PM
Subject: Re: Overwriting Attachments
**
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 2:51 PM
To: [email protected]
Subject: Re: Overwriting Attachments
**
__20060125_______________________This
posting was submitted with HTML in it___ __20060125_______________________This
posting was submitted with HTML in
it___
From: "Kemes, Lisa" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 2:59:58 PM
Subject: Re: Overwriting Attachments
**
You're right! I changed my delete action to: (
'DB.First Attachment' != $NULL$ ) AND ( 'First Attachment' = $NULL$
)
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 2:51 PM
To: [email protected]
Subject: Re: Overwriting Attachments
And you realize that TR.FirstAttachment will be $NULL$ on modification of a
ticket, even if you haven't touched the current attachment field during
that transaction right????
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
-----
Original Message ----
From: "Kemes, Lisa" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 2:32:22 PM
Subject: Re: Overwriting Attachments
**
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 2:31 PM
To: [email protected]
Subject: Re: Overwriting Attachments
**
From: "Kemes, Lisa" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 2:32:22 PM
Subject: Re: Overwriting Attachments
**
More info:
I do a 'TR.FirstAttachment' = $NULL$, this is a
delete. And I do a 'FirstAttachment != 'DB.FirstAttachment', and this captures
an add action, but not an overwrite....isn't that weird???
Lisa
Lisa
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 2:31 PM
To: [email protected]
Subject: Re: Overwriting Attachments
I've noticed you need to remove, edit and readd the attachment and then
save the record.. it then takes the new one in...
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
-----
Original Message ----
From: Lisa Kemes <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 1:46:19 PM
Subject: Overwriting Attachments
From: Lisa Kemes <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 1:46:19 PM
Subject: Overwriting Attachments
I'm trying to capture add and delete actions of an attachment pool to a
history form. Add and deletes are easily captured, but what if someone
adds overwrites an attachment? A window pops up asking if you would like
to overwrite it, but then it seems like Remedy does not recognize this as
a "change." Is there a way to capture this?
Lisa Kemes
history form. Add and deletes are easily captured, but what if someone
adds overwrites an attachment? A window pops up asking if you would like
to overwrite it, but then it seems like Remedy does not recognize this as
a "change." Is there a way to capture this?
Lisa Kemes
