AM" and if so, it displays an error message telling them to input the
correct time. They are populating the field via the drop down calendar, so
the format would be mm/dd/yy hh:mm:ss AM.
-----Original Message-----
From: Woyton, Chris [mailto:CWoyton@PINACOR.COM]
Sent: June 08, 1999 1:57 PM
To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
Subject: Re: Escalation Qualification ....HELP!
Ahhhh....here's an idea...
Are your customers entering the date in mm/dd/yy hh:mm:ss format? If they
supply just the date, Remedy will assume 12:00 AM on that date. It could be
causing miscalculations with the time.
Perhaps?
-Chris
> -----Original Message-----
> From: Black, Dulcy A. [SMTP:Dulcy_Black@DEN.INVESCO.COM]
> Sent: June 08, 1999 12:30 PM
> To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
> Subject: Re: Escalation Qualification ....HELP!
>
> This Date&Time field is NOT automatically populated by the database. It
> is
> a date the user would put in upon submission of a ticket. The date and
> time
> can be anywhere in the future.
>
> -----Original Message-----
> From: Woyton, Chris [mailto:CWoyton@PINACOR.COM]
> Sent: June 08, 1999 12:52 PM
> To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
> Subject: Re: Escalation Qualification ....HELP!
>
>
> Dulcy,
>
> If you're referring to a field set by the database, then the 'Date&Time'
> field has already been set when you compare against it, thus, it is in the
> past.
>
> $TIMESTAMP$ is the time on the server when the escalation performs its
> comparison so it is larger than (future to) the 'Date&Time' field.
>
> Does that make any more sense?
>
> -Chris
>
>
>
> > -----Original Message-----
> > From: Black, Dulcy A. [SMTP:Dulcy_Black@DEN.INVESCO.COM]
> > Sent: June 08, 1999 11:40 AM
> > To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
> > Subject: Re: Escalation Qualification ....HELP!
> >
> > I thought that $TIMESTAMP$ is now, and the 'Date&Time' field is always
> in
> > the future (which would seem like it would be a bigger integer value),
> so
> > that $TIMESTAMP$ would be less than the 'Date&Time' field instead of the
> > other way around. What am I missing with this logic?
> >
> > -----Original Message-----
> > From: Jim Caruso [mailto:James_P_Caruso@ETCSCAN.COM]
> > Sent: June 08, 1999 11:21 AM
> > To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
> > Subject: Re: Escalation Qualification ....HELP!
> >
> >
> > Dulcy,
> >
> > a couple of things...
> >
> > 1.) You are generating negative numbers because your timestamp is
> greater
> > than
> > your date time field.
> > 2.) Generally, you would want to subtract the off set from you timestamp
> > and
> > then do a >= evaluation versus the date time field as it is more
> > efficient...
> > so try this one:
> >
> > (( 'Status' = "New") OR ( 'Status' = "Scheduled") OR ( 'Status' =
> > "Coordinating")) AND ( 'Date&Time' >= ($TIMESTAMP$ - 7200))
> >
> > :)
> >
> > Jim C
> >
> >
> >
> >
> >
> > "Black, Dulcy A."
on 06/08/99 10:13:54
> >
> > Please respond to "Action Request System discussion list(ARSList)"
> >
> >
> > To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
> > cc: (bcc: James P Caruso/ETC/Deluxe Corporation)
> > Subject: Escalation Qualification ....HELP!
> >
> >
> >
> >
> > I am trying to create an escalation that performs a run process action
> > (which works) but it appears that my qualification is the part that is
> not
> > working. I want it to check a date/time field against the time now and
> if
> > the difference is two hours or less and the status is any one of three
> > states, to do the run process. Here's what I'm using:
> >
> > (( 'Status' = "New") OR ( 'Status' = "Scheduled") OR ( 'Status' =
> > "Coordinating")) AND (( 'Date&Time' - $TIMESTAMP$) <= 7200)
> >
> > This appears to be running at every time interval, regardless of the
> time
> > portion of the qualification (the status part seems to work). Can
> anyone
> > see what I'm doing wrong?
> >
> >
> --------------------------------------------------------------------------
> > -
> > To unsubscribe from this list, send mail to
> listserv@listserv.buffalo.edu
> > with a body of "signoff arslist". The subject line is ignored.
> >
> >
> --------------------------------------------------------------------------
> > -
> > To unsubscribe from this list, send mail to
> listserv@listserv.buffalo.edu
> > with a body of "signoff arslist". The subject line is ignored.
> >
> >
> --------------------------------------------------------------------------
> > -
> > To unsubscribe from this list, send mail to
> listserv@listserv.buffalo.edu
> > with a body of "signoff arslist". The subject line is ignored.
>
> --------------------------------------------------------------------------
> -
> To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
> with a body of "signoff arslist". The subject line is ignored.
>
> --------------------------------------------------------------------------
> -
> To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
> with a body of "signoff arslist". The subject line is ignored.
---------------------------------------------------------------------------
To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
with a body of "signoff arslist". The subject line is ignored.
---------------------------------------------------------------------------
To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
with a body of "signoff arslist". The subject line is ignored.
Previous Topic
Index