Contents
- Introduction
- Scenario Builder Application
- Scenario Blocks
- Accept
- Add to Calling List
- Answer
- Attached Data
- Collect Digits
- Comment
- Connect Call
- Connect Chat
- 1 DB Execute
- Exception Handler
- Exit
- Fetch URL
- Find Agent
- Get Next Record
- Get Statistics
- Get User Configuration
- Goto
- If
- Log
- Menu
- Play Prompt
- Record
- Request Callback
- Request Input
- Request Skill or Service
- RightNow Create Object
- RightNow Screen Pop
- RightNow Search
- RightNow Select Account
- RightNow Update
- Salesforce.com Delete
- Salesforce.com Insert
- Salesforce.com Screenpop
- Salesforce.com Search
- Salesforce.com Update
- Save Survey Response
- Self-Service Provided
- Search Directory
- Send Message
- Set Agent State
- Set Disposition
- Set Priority
- Set Prompt Language
- Set Variable
- Start Another Scenario
- Stop Prompt
- Voicemail
- Wait
- Web Screen Pop
- Zendesk Create Object
- Zendesk Screen Pop
- Zendesk Search
- Zendesk Select Account
- Zendesk Update
- Variables and Expressions
- Voice Segment Types
- Scenario Example
DB Execute
This block provides a way for a scenario to execute SQL statements on a specified database.
Note that this block can be used to share data between scenarios.
Conditional Exits
- Failed – Error occurred during SQL statement execution. No error details are provided.
- No Data – The SELECT statement successfully executed but did not return any records.
Settings
- Title text - The name of the block instance.
- DB Connection – The desired database connection. See below for details.
- SQL Statement – The SQL statement to be executed. SQL statements may use scenario variables. For example: SELECT id, name FROM customers WHERE phone=’$(item.from)’
- Recordset name – For SELECT statements, the name of the retrieved recordset should be specified. This allows scenarios to have more than one recordset and to choose the recordset to iterate on.
- The columns of the first retrieved record (if any) are stored in the scenario variables <recordset_name>.<column_name>, for example, RS.id.
- The number of returned records is stored in variable <recordset_name>.__count__, for example RS.__count__. (Note the double underscores in front and after count; they are used to reduce the chance of confusing the name of this variable with a column name in a recordset.)
- To iterate through the recordset use the Get Next Record block.
- The number of records in the retrieved recordset is limited to 25.
The database connection is selected from a list of connections. Click the Manage DB connections button. The pop-up window will display all database connections defined in this scenario. For each connection the following data should be defined:
- Name – The name of the database connection. This name is shown in the DB Execute block connection selection menu.
- JDBC driver and connection string – Specify the JDBC driver and connection string that will be used to access this database. Note that templates are provided for some widely used DBMS systems.
- Database user name and password – Specify database access credentials.
The database connection selector allows the following operations:
Add a new connection (Add New button)
Edit and save the selected connection (Save button)
Delete the selected connection (Delete button)
Select the connection to be used in the DB Execute block (Select button)
Clear the connection selected for the DB Execute block (Select None button)
Close the window without changing the DB Execute block connection (Close button)