VoiceGuide IVR Software Main Page
Jump to content

The Scope Of The Cleanup Script

Recommended Posts

I use many scripts during a call. I have to go to the Edit - Script properties - "Script to run when call is finished" and choose the path of the cleanup script.

 

In your help file 3.Script design - Call finish page says:

“This is how we would set the script "C:\My Scripts\Update Databases.vgs" to be called when the CURRENTLY EDITED SCRIPT is finished:…”

 

What is the real scope of a cleanup script definition?

Do I have to enter the same path of the cleanup script in each and every script i use?

Or is it enough to enter in the first script and then it remains valid until the end of the call (even if many scripts are used) or until I change it in another script or using the $RV[RUNAFTERHANGUP] variable in an Evaluate Expression module or Vbscript module?

Share this post


Link to post

Right now the 'After Hangup' script is a script-related paramter.

 

When call ends VG looks to see if the script running at that time has an 'After Hangup' associated with it and if so then VG runs that script.

 

If at the time of hangup the current script does not have an 'After Hangup' script associated with it then VG will not run any script.

Do I have to enter the same path of the cleanup script in each and every script i use?

Yes. (If you want an after hangup script to run)

Or is it enough to enter in the first script and then it remains valid until the end of the call

No.

 

We know some users would like to have the 'After Hangup' setting to be a bit smarter then that. Right now there are however quite a few items higher on the "ToDo" priority list...

Share this post


Link to post

This “After Hangup” problem is part of a bigger problem. The scripts that are used during a call are not integrated well in a script system used during a call.

Another example for this is that I have to enter the script names and module names by hand, instead of choosing them - in cases when the path points to another script. Also, unlike paths pointing to a module in the same script, paths pointing to a different script are not automatically updated when I change the referred name. That’s rather inconvenient.

 

Last time I spent a day to figure out that I incorrectly assumed an automatic update in the SAME script. First I used a module name called GetLanguage. Then I used the $RV[GetLanguage] result variable in the Evaluate Expression section of an Evalute Expression module in the same script. Later I changed the name of the module name from GetLanguage to Language and there was not automatic update in the Evaluate Expression from $RV[GetLanguage] to $RV[Language].

 

Please consider putting these concerns to your ToDo list. I guess these upgrades are not too time consuming and they could improve the integrity of this VG software significantly.

Share this post


Link to post

Only the local paths will be updated if the module name is changed.

 

If a path points to another script then that path will not be altered if the other script is renamed/deleted.

 

Similar with the Result Variables. RVs referring to a renamed module will not be updated - after all the user may want to create another module with the same name - and the simple process of deleting the module should not result in changes behind the scenes that the user is not made aware of. Such changes behind the scenes tend to just create confusion rather then aid in efficient design.

 

You may want to look into using a text editor to edit the .vgs files directly. This would give you the flexibility of global search and replace etc.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×