Message-
From: Rod Harris [mailto:r...@smapps.com.au]
Sent: Thursday, November 19, 2009 12:13 AM
Subject: Re: Duplicate notifications on helpdesk modify
Hi Robert,
ITSM has some rather complex workflow and quite often it will do two
updates on the ticket for one user update. You have to exclude
There was a bug in the email engine that generated duplicate messages. What
version of the email engine are you using?
Dave
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Robert Fults
Sent: Wednesday, November
Hi Robert,
I think you have to replace the ORs with ANDs.
If 'Last Modified By' is e.g. AR_ESCALATOR then 'Last Modified By' !=
'Assignee Login ID' is true
Br,
Norbert
Am 18.11.2009 um 17:37 schrieb Robert Fults:
**
I set up a filter to fire a notification on Modify of the HPD:HelpDesk
]
Sent: Wednesday, November 18, 2009 11:40 AM
Subject: Re: Duplicate notifications on helpdesk modify
**
There was a bug in the email engine that generated duplicate messages. What
version of the email engine are you using?
Dave
From: Action Request System
Hi Rob,
Do you have a development server? If so, make sure the email on development is
configured for development and not your production service. Same with your
ar.conf. If these settings get copied over from production email do exactly
that - send two emails.
Tom Lamy
UNH
From:
respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Duplicate notifications on helpdesk modify
**
Hi Rob,
Do you have a development server? If so, make sure the email on
development is configured for development and not your production service.
Same with your ar.conf
; herd-dispa...@lists.stanford.edu
Subject: RE: Duplicate notifications on helpdesk modify
Hi Rob,
Do you have a development server? If so, make sure the email on development is
configured for development and not your production service. Same with your
ar.conf. If these settings get copied over
Hi Robert,
ITSM has some rather complex workflow and quite often it will do two
updates on the ticket for one user update. You have to exclude the
second update. One thing you could try is to exclude the second update
caused by syncing the worklog by adding ('z1D Action' !=
SYNC_WORKLOG to your
8 matches
Mail list logo
