Hey all,
I have to do a proof of concept for some call centre software, and need some advice on the following :
1) They have Service Level Agreements over n minutes depending on the severity of the call and need to follow up on calls over n period of time. Now the question is, has anybody used a timer control within Pro-Iv to popup screens, do updates etc ?
2) Has anybody got Global Lscalls to work dynamically ?
I.E. $FUNCT = 'TESTFUN'
GLOBAL_LSCALL($FUNCT)
By my logic, this is similiar to @LFUNCT = 'TESTFUN' and should therefore work the same way ?
Click the link below to see the new game I'm developing!
ActiveX and Global Lscalls
Started by
Neil Hunter
, Aug 19 2005 07:51 AM
9 replies to this topic
#2
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 19 August 2005 - 08:45 AM
Hi,
2) No you cannot use 'dynamic' global function calls. It would be good if we could, but currently you must hard code the name in logic.
Rob D.
2) No you cannot use 'dynamic' global function calls. It would be good if we could, but currently you must hard code the name in logic.
Rob D.
#5
CSuarezdelReal
-
- Members
-
- 91 posts
Advanced
- Gender:Not Telling
Posted 07 September 2005 - 02:55 PM
It might not be the nicest way, but I ran batch jobs every hour or so (scheduled from the OS) that performed several ProIV updates and sent email based on its findings... No popups or exact time message delivery, but pretty good for our purpose.
Claudio Suarez del Real "It is not the strongest of the species that survive, nor the most intelligent, but the ones most responsive to change."
#6
Joseph Bove
-
- Members
-
- 756 posts
ProIV Guru
- Gender:Male
- Location:Ramsey, United States
Posted 07 September 2005 - 03:58 PM
Neil,
You've probably thought of this, but:
CASE $FUNCT
WHEN 'TEDIOUS': GLOBAL_LSCALL(TEDIOUS, 123)
WHEN 'NOT_FUN': GLOBAL_LSCALL(NOT_FUN, 124)
ETC.
hth,
Joseph
2) Has anybody got Global Lscalls to work dynamically ?
I.E. $FUNCT = 'TESTFUN'
GLOBAL_LSCALL($FUNCT)
You've probably thought of this, but:
CASE $FUNCT
WHEN 'TEDIOUS': GLOBAL_LSCALL(TEDIOUS, 123)
WHEN 'NOT_FUN': GLOBAL_LSCALL(NOT_FUN, 124)
ETC.
hth,
Joseph
#7
Richard Bassett
-
- Members
-
- 707 posts
ProIV Guru
- Gender:Not Telling
- Location:Rural France
Posted 07 September 2005 - 06:16 PM
You could also consider wrapping that CASE statement ina a global logic - that at least keeps all the mess in one place.
BE WARNED that [last time I tried on V4.6 anyway] arguments in a GLOBAL_LSCALL interface in a global logic that are arrays and/or are the subject of an EXTERN simply do not work properly. (Search forum for previous posts)
If your global functions do not pass data via interfaces though, this could well work for you.
BE WARNED that [last time I tried on V4.6 anyway] arguments in a GLOBAL_LSCALL interface in a global logic that are arrays and/or are the subject of an EXTERN simply do not work properly. (Search forum for previous posts)
If your global functions do not pass data via interfaces though, this could well work for you.
Edited by Richard Bassett, 07 September 2005 - 06:17 PM.
Nothing's as simple as you think
#8
Neil Hunter
-
- Members
-
- 420 posts
ProIV Guru
- Gender:Male
- Location:Johannesburg, South Africa
Posted 08 September 2005 - 05:34 AM
Joseph, Thats exactly what i'm doing now, but thanks for the suggestionNeil,
2) Has anybody got Global Lscalls to work dynamically ?
I.E. $FUNCT = 'TESTFUN'
GLOBAL_LSCALL($FUNCT)
You've probably thought of this, but:
CASE $FUNCT
WHEN 'TEDIOUS': GLOBAL_LSCALL(TEDIOUS, 123)
WHEN 'NOT_FUN': GLOBAL_LSCALL(NOT_FUN, 124)
ETC.
hth,
Joseph
CSuarezdelReal, I need to have interaction on the user side rather than from the server side. IE Call gets logged, SLA dictates that call must be attended to within 30 minutes of logging, so after 30 minutes an event/process must get fired that alerts the user that the call is outstanding etc. And it all has to be within Pro4, so no e mailing
#9
Richard Bassett
-
- Members
-
- 707 posts
ProIV Guru
- Gender:Not Telling
- Location:Rural France
Posted 08 September 2005 - 10:03 AM
Um.. Neil,
Wouldn't it nevertheless be a lot better to drive timer-for-SLA stuff from the server-side if possible given that a particular client PC might be "down" far more often than the server or might be unattended - in which case should the system escalate the issue to someone/where else?
Just a thought.
Wouldn't it nevertheless be a lot better to drive timer-for-SLA stuff from the server-side if possible given that a particular client PC might be "down" far more often than the server or might be unattended - in which case should the system escalate the issue to someone/where else?
Just a thought.
Nothing's as simple as you think
#10
Neil Hunter
-
- Members
-
- 420 posts
ProIV Guru
- Gender:Male
- Location:Johannesburg, South Africa
Posted 08 September 2005 - 11:06 AM
Its all from a centralised server over a WAN. But yes your logic is spot on, user may be sitting at their workstation doing absolutely nothing for longer than a prescribed period. This is one of the reasons that I wanted to do it from the client side, so that a user would not have to interact with the server eg. check calls every x minutes to see whats happening.
Or in another case, yes you run an update server side by cron or scheduled task. Then what ? Some sort of user intervention would be required
Unless my logic is flawed ?
Or in another case, yes you run an update server side by cron or scheduled task. Then what ? Some sort of user intervention would be required
Unless my logic is flawed ?
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
