** Carey
I can understand your horror! but the way the app was designed, and it was done in version 3 to start with,
create a SQL table in the db
execute a SQL statement that writes to this table a command
execute a process that runs every 1 minute that then executes the command written in the SQL table.

now try to run this virtually constantly and see what the results are!!

like i said i did not design the app, i am just working on it.
My intention is to take all the SQL out and use Push fields, although i am considering using API for just the creation of tickets and Push fields for modifications. Trying to decide whether a Push fields will create a record faster than an API.

kind regards
shafqat

Carey Matthew Black <[EMAIL PROTECTED]> wrote:
Shafqat,

I understand the problem at hand. But I have to question only one part
of your explanation:

"
> in the olden days since it was
> being done via SQL there could be a delay of upto 30 to 40 minutes before
> the new entry showed up(sometimes, but it had happened).
"


Given what I know of how the ARS server Push action works. I can not
imagine that under a normal operating condition (barring bugs in the
design implementation) that even a delay of 1 minute would be
possible. Now if your actually using an Escalation to create the
"consolidated" record then I can see how such a delay would be
possible. But that seems like a poor way to design this feature in my
mind. As Michiel pointed out, use Push actions from Submit and Modify
to create/update/remove these consolidated records and the timing
should be almost instantaneous to the action done on the "source"
records.

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.







Shafqat Ayaz


Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2ยข/min with Yahoo! Messenger with Voice. __20060125_______________________This posting was submitted with HTML in it___

Reply via email to