printing this e-mail
Joe Martin D'Souza jdso...@shyle.net
Sent by: Action Request System discussion list(ARSList)
arslist@ARSLIST.ORG
03/12/2012 10:36 PM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: ResetKickbackCount Escalation question out of the box
to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: ResetKickbackCount Escalation question out of the box escalation
seems to be updating every incident older than 31 days
**
I completely agree that bypassing the application layer is never a good
idea unless
the environment before printing this e-mail
Jose Huerta jose.hue...@sm2baleares.es
Sent by: Action Request System discussion list(ARSList)
arslist@ARSLIST.ORG
03/13/2012 08:45 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: ResetKickbackCount Escalation question
I have a report the looks for all Incidents modified in the last 10 days that
runs and the escalation called HPD:INC:ResetKickbackCount is killing my report
since it modifies all incidents. Does anyone know any thing about kick back.
is not AR_ESCALATOR.
Joe
-Original Message-
From: John Atherly
Sent: Monday, March 12, 2012 3:13 PM Newsgroups:
public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Subject: Re: HPD:INC:ResetKickbackCount Escalation question out of
the box escalation seems to be updating every
I ran into a similar problem in the past. My solution was to apply this:
http://theremedyforit.com/2012/02/avoid-ar_escalator-in-last-modified-by-field/
Then you can use your modified date as a feed for your reports.
Regard,
Jose M. Huerta
Project Manager**
Movil: 661 665 088
Telf.: 971 75
Sent: Monday, March 12, 2012 3:13 PM Newsgroups:
public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Subject: Re: HPD:INC:ResetKickbackCount Escalation question out of
the box escalation seems to be updating every incident older than 31 days
I have a report the looks for all
: public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Subject: Re: ResetKickbackCount Escalation question out of the box
escalation seems to be updating every incident older than 31 days
** I think that change a set action to a direct SQL to avoid normal ARS
behavior is a bad practice and you'll pay
Verson Info:
ARS 7.5 running on Oracle 10g
ITSM 7.6 patch 1
Problem:
There is a escalation called HPD:INC:ResetKickbackCount that has a
qualification:
'Closed Date' ($TIMESTAMP$ - 2678400)
I.e. - if the closed date is less than 31 days from the current timestamp
(only runs at the 1st
I set up a very robust scheduler application. I made it act a bit
like the Windows Task Scheduler. You can set up a very specific
schedule at which you want something to happen/trigger...every 2nd
Saturday of the month, for instance. It works by calculating when the
first trigger time will be.
I have been trying to figure out a way to make an Escalation run on the
Second Saturday of every month. I know you can schedule it to run at
during a specific Hour of the Day, or Day of the Month or even a Week
Day but none of these options allow you to run it on a specific day of
the Month where
). This
filter does whatever you wanted the escalation to do.
Good luck,
Dwayne Martin
James Madison University
Original message
Date: Tue, 3 Feb 2009 12:00:17 -0600
From: Pruitt, Christopher J christopher.pru...@eds.com
Subject: Escalation question
To: arslist@ARSLIST.ORG
, Michael E Jr. CTR USAF
AFRL/SNOD
Sent: Monday, January 29, 2007 9:59 AM
To: arslist@ARSLIST.ORG
Subject: Escalation question
Importance: High
**
Remedy Newby here -
I have an escalation that I want to fire for all records with a status of
'Working' and that have not had a diary entry posted
(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E Jr. CTR USAF
AFRL/SNOD
Sent: Monday, January 29, 2007 10:59 AM
To: arslist@ARSLIST.ORG
Subject: Escalation question
Importance: High
Remedy Newby here -
I have an escalation that I want to fire for all records with a status
Mike,
I would create a working date field on the form, and set it to $TIMESTAMP$
every time there is an entry made to the worklog, then with your escalation,
you can check Status = 'Working' and Last Worklog Entry $TIMESTAMP$ - 129600
Hope this helps.
Rem
Date: Mon, 29 Jan 2007 11:58:55
Cheers
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
- Original Message
From: Cupp, Michael E Jr. CTR USAF AFRL/SNOD [EMAIL PROTECTED]
To: arslist@ARSLIST.ORG
Sent: Monday, January 29, 2007 11:58:55 AM
Subject: Escalation question
**
Remedy Newby here -
I have
Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E Jr. CTR USAF
AFRL/SNOD
Sent: Monday, January 29, 2007 10:59 AM
To: arslist@ARSLIST.ORG
Subject: Escalation question
Importance: High
**
Remedy Newby here -
I have an escalation that I want to fire
Subject: Re: Escalation question
**
I'm not sure if you can parse through that with an escalation, but you
might consider setting a hidden timestamp field through a filter each
time the diary field is modified, that way your escalation can just look
at that timestamp field
: Escalation question
**
How can I check in the filter to see if the diary field has been updated?
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]
On Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Monday, January 29, 2007 12:11 PM
To: arslist@ARSLIST.ORG
Subject
19 matches
Mail list logo
