Custom VBScript Code - Call logging into textfile

Summary:

With SwyxWare v4.0 it is possible to define own custom scripts with the Graphical Script Editor (GSE). To create scripts using the GSE you have to license the Option Pack - Extended Call Routing.

This articles describes, how to implement a simple Call logging into a text file.

Other articles in this series are:

• Custom VBScript Code - Call logging into database
• Custom VBScript Code - Caller verification in database
• Custom VBScript Code - Check for Bank Holiday

Further informations about the new features within the Graphical Script Editor can be found in the article:

• Changes in Graphical Script Editor (Update from 3.20 to 4.00)

Information:

Installation of the example rule

Download the complete example code usig the link at the end of this article and copy all included files into the

c:\gse_demo

To load the LogFile.rse file as rule into your Call Routing Manager i.e. Graphical Script Editor please follow these steps:

• Open the Call Routing Manager.
• Click the New... button.
• Select Graphical Script Editor and click on Ok.
• Within the GSE open the File | Import... menu.
• Select the LogFile.rse. The rule will be imported and your GSE will look like this:
  
  
                                                                Graphical Script Editor
• Save the new rule using the File | Save menu.
• Close the GSE.
• Activate the rule by moving it to the right list box of the CRM.
  
  
                                                        Call Routing Manager

How it works

Custom code can only be added to the Start rule. All consts, variables and functions you'll define here are available all over the script, i.e. can be used in all blocks e.g. the Evaluate block. Please note, that the final script being created by the GSE places the VBScript statement option explicit to the top of the script. This forces all variables to be used within the script to be declared properly.

        
                             Properties - Start rule

As you will see in this example a function will be defined within the custom code in the Start rule, which will later be used within a Set Variable block. This is a small trick: we don't need the new defined variable, we use it just to call our function.

                                 Properties - Insert Call into File

The function InsertCallIntoFile opens a text file and appends the caller id together with the current date and time to it. This is how the code looks like:

1. ' FileOpen iomode Values
2. Const fsoForReading = 1
3. Const fsoForWriting = 2
4. Const fsoForAppending = 8
5.  
6. Const fsoCreateIfNotExist = True
7.  
8. Function InsertCallIntoFile( ByVal callerID)
9.  
10.     Const filename = "c:\gse_demo\test.txt"
11.  
12.     Dim fso
13.     Dim file
14.  
15.     ' Create FileSystemObejct
16.     fso = CreateObject("Scripting.FileSystemObject")
17.  
18.     ' Open text file
19.     file = fso.OpenTextFile(filename, _
20.       fsoForAppending, fsoCreateIfNotExist)
21.  
22.     ' Write (append) CallerID into file
23.     file.WriteLine("""" & callerID & """,""" & _
24.       CStr(now) & """")
25.  
26.     file.Close()
27.  
28.     file = Nothing
29.     fso = Nothing
30.  
31. End Function

After activating this rule all incoming calls with be recorded within the text file. Note that we exit the script using the Rule skipped block. This will enable us to use other rules after this one within our call routing.

Notes

• All callrouting scripts, and therefore also your code, runs under the SwyxWare Service Account. Please make sure that this account has the needed priviliges to access the file/database.

• The script in this example does contain no Error Handling. If an error occurs at runtime, e.g. when trying to access a database, this error will not be handled, the script will stop and the call get lost. If you have enabled Server Tracing for SvrScript on level Info3 you will find the original Microsoft Script Engine error message within the server trace file.

  To get your own error handling you have to disable the standard error handling by the Script Engine:

  On Error Resume Next

  
  Place this line of code at the beginning of your function. Now you have to check for error at every potential place and do your own error handling:

  ' Open connection to Database

  db.Open sDsn

  If Err <> 0 then

  'do something, e.g.:

  FunctionName = False

  Exit Function

  End If

   

References:

• Custom Scripts in GSE (Examples)
  kb2285-Bank_Holiday_Check.zip

This Swyx Forum Wiki article documents the GSE build in functions.

• Swyx Forum - GSE build in functions
  https://www.swyx-forum.com/forum/151-gse-build-in-functions/

This Swyx Forum Wiki article documents the SwyxServer Script API.

• Swyx Forum - Server Script API
  https://www.swyx-forum.com/forum/150-server-script-api/

This Swyx Forum Wiki article documents all VBScript build in functions.

• Swyx Forum - VBScript functions
  https://www.swyx-forum.com/forum/152-vbscript-build-in-functions/

The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.