Sqlcursor

Submits a SQL (Structured Query Language) statement to a database server and returns a multi-row result.

Dependencies

• Use Sqlcursor for the same purpose as Sqlselect when multiple rows are expected.
• This action does not retrieve all the rows at once. Instead, the dataset is opened and kept open for repetitive access.
• As with Sqlcursor, each column is stored in a variable with the same name as the column. Initially, the first record will be fetched. To fetch consecutive records, execute Sqlnext repeatedly until Sqlnext triggers its End of Dataset branch condition.
• If the script does not need to continue fetching all records, place the Sqlclose action after the End of Dataset branch condition. This will manually close the dataset. This ensures that the database memory is released and potential record locks will not be left active.

Supported Script Types

Generic	Email	Chat	Phone	Voicemail	Work Item	SMS

Input Properties

These properties define data that the action uses when executing.

Property	Description
Add Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon.
SQL Query	The SQL statement that will be submitted to the database server. This statement should be expected to return records.
Global Variables	Not used.
Publish	Publishes a variable and value from the last name that is retrieved. For example, if there were 3 names retrieved, only data from the last name would be published.
Timeout Sec	The number of seconds the action waits to execute before timing out. The value must be between 0 and 60.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition	Description
Default	Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
NoRecords	Path taken if there are no values for the specified properties.
Error	Path taken when the action fails to execute properly. For example, when there is an unexpected problem such as poor connectivity, syntax errors, and so on. The _ERR variable, with a single underscore character, should be populated with a condensed explanation of the problem.