Souza
Sent: Tuesday, July 14, 2009 4:35 PM
To: arslist@ARSLIST.ORG
Subject: Re: Read-only Remedy
**
True, he may need to keep in mind API's that create tickets but have
exceptions for whatever is the true source for creation of these
tickets. Since he didn't mention the source of creation
about what he does with a
creation prevention filter. You do not want to prevent 'too much'.
Joe
From: "Nichols, Wesley D CTR USAF AFMC 72 CS/SCBAF"
To: arslist@ARSLIST.ORG
Sent: Tuesday, July 14, 2009 4:24:47 PM
Subject: Re: Read-only Re
)
[mailto:arsl...@arslist.org] On Behalf Of Joe DeSouza
Sent: Tuesday, July 14, 2009 3:19 PM
To: arslist@ARSLIST.ORG
Subject: Re: Read-only Remedy
**
Or even better still an Active Link that closes a New Window and opens a
Search instead with a message saying that they can only Modify an
existing ticket. That
know that they cannot
create a ticket..
Joe
From: LJ Longwing
To: arslist@ARSLIST.ORG
Sent: Tuesday, July 14, 2009 4:11:07 PM
Subject: Re: Read-only Remedy
**
Create a filter that fires on Submit that throws an error, that'll stop them
from creatin
o: arslist@ARSLIST.ORG
Subject: Read-only Remedy
**
Howdy, listerz.
We have Remedy 6 on Windows 2003.
Is there any clever way to prevent users from creating NEW tickets, but
allow them to annotate & resolve their EXISTING ticke
slist@ARSLIST.ORG
Subject: Read-only Remedy
**
Howdy, listerz.
We have Remedy 6 on Windows 2003.
Is there any clever way to prevent users from creating NEW tickets, but
allow them to annotate & resolve their EXISTING tickets...
Howdy, listerz.
We have Remedy 6 on Windows 2003.
Is there any clever way to prevent users from creating NEW tickets, but
allow them to annotate & resolve their EXISTING tickets...?
thanks --
---
The information con
7 matches
Mail list logo
