Re: Overwriting Attachments

Thu, 31 Aug 2006 08:57:41 -0700

**
I got this response from Matt Reinfeld's site:
 
"This is a bug i also run into. I already reported it to remedy. If they fix it and in which version is not clear until now.

The biggest problem is that the user can change the attachment and you could not prevent him from that (i have Filter which prevent change if user is not editor of the ticket).

The workaround for this is to store the names of the attachment in seperate character fields and use them for the comparision. I guess the better way is to store the attachments in a seperate form and handle add and modify actions over an dialog. In this case you have more control and the number of attachments is dynamic."
-------------------------------
 
So what I did was created 3 active links. 1 to put the attachment name into a character field, another one to NULL this field out if the attachment is being deleted and the third one is to compare the character field to the attachment field and if they are different, then set an error message that in order to do an overwrite they will have to delete the attachment first, save the record, then add the new attachment.  This may be a little overkill, but it works!
 
Lisa
 
 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 4:10 PM
To: [email protected]
Subject: Re: Overwriting Attachments

**
Thats is correct as when you remove the attachment, as also when there is actually no value in the field, TR would both be NULL so you cannot really differentiate between the two conditions..
 
So to specifically isolate the condition where there was a db value and it has been removed what you stated in your last statement is good..
 
DB.Field != NULL and Field = NULL
 
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.


----- Original Message ----
From: "McKenzie, James J C-E LCMC HQISEC/L3" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 3:29:48 PM
Subject: Re: Overwriting Attachments

**
Joe:
 
Let me see if I understand you:
 
If you modify an attachment, the modification will not be reflected in the TR.<fieldid> if the action taken was to remove the attachment.  I know this is true thus I use the following to check if a field was changed and not set to NULL:
 
field != $NULL$ and TR.field != $NULL$
 
So, checking for the empty field should take this:
 
'DB.Field' != $NULL$ AND 'Field' = $NULL$
 
This should detect that the current value in the field is empty and that the field in the database does contain something.  YOU CANNOT USE TR.Field AS IT WILL NOT BE RELIABLE IN THIS CASE.
 
James McKenzie
L-3 GSI

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 12:07 PM
To: [email protected]
Subject: Re: Overwriting Attachments

**
James,
 
I meant transactional value is always null when there is no modification done on a field, even though there might be a database value other than null in that field... so even though you see a value in that field that value is the db value and not transactional if you haven't dirtied that field during the transaction..
 
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.


----- Original Message ----
From: "McKenzie, James J C-E LCMC HQISEC/L3" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, August 30, 2006 2:59:28 PM
Subject: Re: Overwriting Attachments

**

Joe:
 
You mean not equal to $NULL$ even if you did not change the field as long as another field was changed.
 
James McKenzie
 

________________________________

From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe DeSouza
Sent: Wednesday, August 30, 2006 11:51 AM
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

**
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


________________________________

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


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

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

Reply via email to