User Guide

Please email for omissions or errors.

Legacy Control - Database Get

Change Type
Version Number
System Change
Database Get control is included in the legacy control pack, rather than being issued on new installations.  This control can still be used by existing users, but will no longer be included in the training material.  Please use the curent Data Controls instead.
Legacy Control - Database Get
The Database Get control can be used to return a single, unique record to a script.  It can also be used to insert, update, and delete data from a database.  A unique value must be passed to the select statement from the script.  The database get control runs on page load or page refresh, so the field or variable being passed to the control must be established on a previous page, or by carrying out a page refresh once the data has been captured.
For outbound calling the Database Get can also be used to populate the Do Not Call table - see Populating the DNC Table for further information.
In the following example, a unique passport ID number is collected in a text field called [IDNumber] on the first page, which is then referred to in the select statement which returns the data to the script fields on the second page.

Field Name

1. Field Name
Change the field name if required

Field Help

2. Field Help
Enter help on completing this field if required

Advanced Properties/Setup Wizard

3. Advanced Properties/Setup Wizard

Step 1

Choose the data source type to link to.  The example that follows shows an Excel spreadsheet being used, the following steps will vary slightly depending on the data source type selected.  In most instances it is best to use the CallScripter database (this will allow users to update information by using a Database Get if necessary, and will not give any performance issues if many agents are accessing the data).

Step 2

Create the link to the data source:
Choose the data source type to link to.  In the example that follows, an Excel Spreadsheet connecting using OLEDB is used.  Ideally the SQL table should be queried directly as many agents accessing the same spreadsheet can cause performance issues. The following steps will vary slightly depending on the data source type selected.
  • SQL Server:
If connecting to a SQL server the server name  is needed.  Use Windows Authentication, or SQL Authentication with a username and password.
  • ODBC:
If connecting to an ODBC data source, users will have either set up a system DSN or enter the ODBC Connection String for the data source.
  • OLEDB:
If  connecting to Excel, browse for the file and upload it.  The connection string will be populated automatically.
  • CallScripter:
If connecting to the CallScripter database itself, a username and password with the appropriate permissions to access the data is needed.  If a default username and password has been configured for the system, it will be automatically entered and this section of the wizard will be skipped.

Step 3

Change the text identifier if required.  Ordinarily this can be left as it is.

Step 4

Enter the query to return the data as required:
Note that all fields and variables used in the script can be included in the select statement.  This control can also be used to insert or update data in a table, see Populating the DNC table for an example.

Step 5

Enter a test value that exists in the data source.

Step 6

Map the script fields (appearing in the drop down lists) to the data fields (appearing as bold headings above the drop down box).  Variables and fields can be mapped.
Overwrite:  Check this option to allow the agent to go back and pick a different record from a second search.
Click Finish at the bottom of the mapping window to complete the configuration of the Database Get control.