See this earlier post. It's long, I have to warn you. 

--------
From: Rabi Tripathi <[EMAIL PROTECTED]>         
To: [email protected]
Date: Fri, Oct 12, 2007 at 3:30 PM
Subject: Re: ITSM 7: "On-Call" and "Shift"
Functionality question...RESOLVED

I have resolution(s)...kind of.

Yes, the intended design is that once a group's "On
Call" flag is set to "Yes", when an Incident is
assigned to that group:
1) only on call pages go out. Emails/alerts and even
pages about assignment, based on member's preference
on their profile STOP.
2) on-call pages do not honor any setting on on-call
member's profile. only the pager address is used
3)'Pager Email' is not used, only real pager address.
4)you can NOT get around this by doing anything on the
SYS:CFG-NotificationPreferences form. The "System
Default" and "User" records there are ignored,
contrary to what I said in earlier email.
5)one caveat: while looking for on-call members to
page about assignment, in case system fails to find at
least one person to page (say the only on call
person's pager address is missing), system will try to
be helpful and WILL trigger the regular
emai/alert/page notifications.

If you are testing this stuff, you will be thrown off
by 5 above and also by the fact that notifications
take upto something like 11 minutes to get to
"NTE:Notifier Log" form and will take longer to get to
inbox, pagers. And by various other settings that
drive notifications.

If you want regular emails/alerts/pages to go out
based on member's preferences, in addition to on-call
pages, disable these three filters:
NTE:NTG:NoOnCall_260_Group
NTE:NPC:GroupNotification_051
NTE:NTG:OnCall_105

Shift functionality is unfinished, so useless, as
somebody mentioned before. Better to hide it on
notification preference pop up.

You wish this were the end of the story, don't you?
Hang on, this is ACT I, Scene I.

ACT II Scene I
What happens if an incident is assigned to an on-call
group and also to a member at the same time? No
on-call page to the individual. Also no
email/alert/page based on his/her notification
preference. I am still processing this one in my mind.
Doesn't seem logical. The guy needs to be yanked out
of bed. Who's going to do that?

ACT II Scene II
Having a twisted mind, I also asked myself: what
happens if incident is assigned to a group only now,
and LATER assigned to a person?

The answer is bad. It pages ALL currently on-call
members of the group saying "incident has been
assigned to YOU". Imagine a group of people in
pajamas, eyes barely open, getting all mad.

A bug report has been created: SW00278274
This is a really bad one and is going to be very
common, so I need to fix this myself.

ACT II Scene III
On some of my tests, Owner group and/or Owners were
paged. I haven't been able to reproduce this recently.
The intended design, I am told, is that Assignees
receive on-call pages, not owners. Fine by me, if
that's how the code behaved.

Finally, there's a bug so that group assignment pages
(regular or on-call) do not go out properly to people
with numeric pages. Fix is to modify this filter
HPD:INC:NTAsgGrp_805_SetTag to have this included in
its set field: z1D NT Pager Message Numeric =
$Incident Number$
I haven't reported this one yet.

<the curtain finally comes down, for now, as the
audience decide to withhold applause>

----- Original Message ----
From: Rabi Tripathi <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, September 19, 2007 11:15:25 AM
Subject: Re: ITSM 7: "On-Call" and "Shift"
Functionality question

I agree with your current understanding, with one
exception. See my comments below starting with "::::"

> I think the
> notification filter processes must be checking first
> for an on call
> notification during the on call schedule (and like
> you say, ignoring ALL
> other factors),
:::: Agree

>then looking for a custom
> notification and trying to use
> that under it's specific parameters - AND IF the
> Default Notify
> Mechanism and Notification Availability of the
> Profile are E-mail/Yes
> (mine are),
::::agree, it checks group member's user defined
setting on NTE:NotificationEvents form and if it finds
one, then takes into account his/her notification
preferences on CTM:People form

>and last it looks for a system default
> notification and
> tries to use that,
::::My installation does NOT do this--never--if the
group is flagged as on call. But you're right, it
would be logical if it did.


>and whichever one the filters
> find first they
> execute, and the process stops without looking
> further.
::::This would be logical, but it does not do this in
my installation.

This is what happens.

Scenario (A) Group flagged as on call:

1)On call page settings for the group on "CTM:Support
Group On-Call" are processed. Pages go out if
appropriate, regardless of member's preferences on
"CTM:People". Only thing used from CTM:People is the
paging address.
2)No matter 1 results in pages or not, checks group
memebr's "user" notification settings on
NTE:NotificationEvents. Any resulting notifications DO
take into account member's CTM:People preference on
Notifications tab.
3)No matter what happens in (2), does NOT look for
System Default records on NTE:NotificationEvents form.


So, if any On-Call group's member hasn't defined a
personal setting in "NTE:NotificationEvents" form, no
emails to her EVER for incident assignment to that
group.

Scenario (B) If group is NOT flagged as on call

1) will of course not apply
2) Applies the same way as above, processes "user"
settings on NTE:NotificationEvents
3) Applies, meaning does look at "system default"
settings for that group, contrary to what happens in A
above.

(B) is logical.
(A) breaks down, in my mind, when it gets to (3).

What's this kinetic training about?

Regards.

--- David Sanders
<[EMAIL PROTECTED]> wrote:

> The On Call notifications feature in ESS controls
> who notifications are sent
> to for support team notifications outside normal
> business hours.
> 
> First, each support Team can be associated with
> Business Time records to
> define their normal operational hours.  If the
> application generates a
> notification to Team members in working hours, it is
> processed normally.  If
> it is outside normal working hours the notification
> is only sent to people
> in an On Call role, by email, pager, voice
> notification, or whatever
> mechanism is defined for that notification/person.
> 
> Isn't that how ITSM7 is meant to work??
> 
> David Sanders
> Remedy Solution Architect
> Enterprise Service Suite @ Work
> ==========================
> ARS List Award Winner 2005
> Best 3rd party Remedy Application
>  
> See the ESS Concepts Guide
>  
> tel +44 1494 468980
> mobile +44 7710 377761
> email [EMAIL PROTECTED]
>  
> web http://www.westoverconsulting.co.uk
>  
> 
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Rabi
> Tripathi
> Sent: Wednesday, June 18, 2008 4:44 PM
> To: [email protected]
> Subject: Re: On-Call notification/assignment config
> question
> 
> On-Call feature delivers a lot less than meets the
> eye
> or I should say suggests the name.
> 
> On-Call feature is about who in a group is paged
> when
> a ticket is assigned to the group, but to no
> individual (assigned person is blank). That's it.
> Nothing more. Even when doing this much, there are
> caveats and weirdest bugs as of the last time I
> checked.
> 
> Picking a person within a group for assignment,
> based
> on the on-call info for the group...well, that would
> be where your customization expertise comes handy.
> 
> In other words, OOB, there is no connection between
> picking assigned person and the on-call feature.
> On-call feature only does exactly what I stated
> above.
> 
> 
> Lesson I learned after a long analysis: don't
> extrapolate and imagine that it does what you or
> anybody else would have the feature do, if you were
> building it, or what the name implies.
> 
> Regards.
> 
> 
> --- William Rentfrow <[EMAIL PROTECTED]>
> wrote:
> 
> > I haven't messed around with the on-call paging
> etc
> > much yet in IM so
> > this question may be dumb, but anyway...
> >  
> > I am not sure what I'd like to do is possible.
> > Ideally I want to be able
> > to:
> >  
> > 1.) Assign cases to people based off AE rules
> (round
> > robin, capacity, #
> > assigned)
> > 2.) Have this work when personal business time/on
> > call time is in effect
> > 3.) Not assign cases if the person is not on-call
> at
> > the time of
> > Incident creation.
> >  
> > I can get 99% of the way there if I do not use the
> > assignment engine and
> > put people in on-call groups and then do
> > notifications based off of
> > group assignment + on-call times....but it doesn't
> > assign down to the
> > individual that way.
> >  
> > Anyone have some pointers?
> >  
> > William Rentfrow, Principal Consultant
> > [EMAIL PROTECTED]
> > C 701-306-6157
> > O 952-432-0227
> >  
> > 
> >
>
____________________________________________________________________________
> ___
> > UNSUBSCRIBE or access ARSlist Archives at
> > www.arslist.org
> > Platinum Sponsor: www.rmsportal.com ARSlist:
> "Where
> > the Answers Are"
> > 
> 
> 
> 
>       
> 
>
____________________________________________________________________________
> ___
> UNSUBSCRIBE or access ARSlist Archives at
> www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where
> the Answers Are"
> 
>
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at
> www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where
> the Answers Are"
> 



      

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to