James, you're right; I want it to also notify if the timing changes to
emergency or expedited. I've used something very similar to what you suggested:
(('TR.Change Timing' != 'DB.Change Timing') AND (('TR.Change Timing' =
"Emergency") OR ('TR.Change Timing' = "Expedited")))
Thank you for your help... sometimes I just draw blank!
Marcelo
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of jham36
Sent: Thursday, November 12, 2009 1:54 PM
To: [email protected]
Subject: Re: new notifications for emergency expedited changes
Why not have your filter fire only on Submit?
If you want to also notify if the Change Type is changed to expedited
or emergency, let it run on submit and modify.
Then just enter a Run If qualification: 'Change Type' != "DB.Change
Type" AND ('Change Type' = "Emergency" OR 'Change Type' =
"Expedited")
James
On Nov 12, 2:38 pm, "Martinez, Marcelo A" <[email protected]> wrote:
> Notifications are working, the theory checks out. The only problem now is
> that since my filters fire on submit and modify, a notification is created
> every time there is a change to the emergency or expedited ticket.
> My question is: How are filters for other "People Support Staff" configured?
> How do these other filters not create multiple notifications?
>
> I suppose I could have the filter write to a temp field on the CHG form and
> have the filter fire is this field is null. But I rather implement this how
> it is supposed to and not rig the system.
>
> Thanks
> Marcelo Martinez
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Schon, Stuart
> Sent: Wednesday, November 11, 2009 5:23 PM
> To: [email protected]
> Subject: Re: new notifications for emergency expedited changes
>
> Not sure about change, but the theory is correct.
>
> Create a new notification template in sys:notification messages
>
> Create two filters in the 800 range (at least that's the number used in
> incident) against the Change form. One looks up to see if the template and
> notification event exists (for the expedited and emergency changes only) and
> the other writes the data to nte:sys-nt process control. The rest should just
> work. It only gets complicated if you need to add new fields to the
> notification engine.
>
> regards
>
> Stuart Schon
> Team Leader
>
> FUJITSU AUSTRALIA LIMITED
> Level 3, 2 Julius Avenue, North Ryde, NSW 2113, Australia
> T 02 9113 9435 M 0439 475 240
> [email protected]
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Martinez, Marcelo A
> Sent: Thursday, 12 November 2009 09:27
> To: [email protected]
> Subject: new notifications for emergency expedited changes
>
> Hello All,
> I am working on implementing new notifications for change management. The
> purpose of the notification would be alert the change mgmt team when an
> emergency or expedited change is entered into the system.
> From what I've seen, it looks like I have to create a new notification event
> on many of the NTE forms, is this correct? The forms I've identified are the
> following:
> NTE:CFG-Notification Events
> NTE:LoadCFGNotificationEvents
> NTE:Notifier
> NTE:Notifier Log
> NTE:SYS-Define NT Events
> NTE:SYS-Group NT Control
> NTE:SYS-Individual NT Control
> NTE:SYS-NT Process Control
>
> Additionally, I have to create 2 filters. One filter to set a value when the
> change is expedited or emergency. The second filter reads the value and calls
> the notification process.
>
> Also, I have to create a new notification message in SYS:Notification
> Messages that the notification process will use for sending the emails.
>
> Can someone verify that my theory is correct?
>
> Thank you,
>
> Marcelo Martinez
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visithttp://www.messagelabs.com/email
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visithttp://www.messagelabs.com/email
> ______________________________________________________________________
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
