The routing query is implemented via an IVR object with the following properties.
The functionality of the object is as follows:
Installed and configured Oracle Instant Client on the jtel server, for production (minimum) and test database (optional) See also Oracle ODBC Driver.
The following system parameters influence the operation of the object:
Parameter | Meaning | |
---|---|---|
Nexus.RIS.DSN.Production | Name of the ODBC data source, for production calls. | |
Nexus.RIS.DSN.Production.Connect | ODBC connection string for the connection to the production database. Example:
| |
Nexus.RIS.DSN.Test | Name of the ODBC data source, for test calls. | |
Nexus.RIS.DSN.Test.Connect | ODBC connection string for the connection to the test database. Example:
|
Parameter | Meaning | |
---|---|---|
Tenant ID | The ID of the client that is used for the parameter x (client ID) for the call to EXEC pkg_rtma.set_mandant(x). This call is made transparently in the object itself. | |
Variable Prefix | A prefix that precedes all variables from the query return. For example, if the query returns a field "ISVIP" and "nexus" is used as a prefix, the object declares a variable named nexus.ISVIP | |
Query | The query to be executed. For example:
|
All fields returned from the query are stored in variables. Only the first record is saved if multiple hits are returned.
From the example above, the following variables are declared:
Note: Oracle always returns field names in uppercase via ODBC. The variables are accordingly created with capital letters, regardless of how they are written in the query itself.
Output | Use when |
---|---|
Found | 1 or more data sets returned by the query |
Not found | 0 data sets returned by the query. |
Error | An error occurred in the query or the connection to the database. |