Configuring the parameter values
You can configure the parameters for custom SQL, Select, Update, Insert, Delete actions and Stored Procedures or configure parameters for Batch Insert and Batch Update operations.
Create, retrieve, update, and delete actions, and stored procedures
Procedure
Provide details to the parameters.
- Query Time Out
- Type or Select the query time out value in seconds. This field specifies the number of seconds
the database connection waits for an SQL statement.Note: Leave blank when you do not want to specify the Query timeout.
- Maximum Row
- Type the number of rows to be retrieved from a database table.Note:
- Leave blank when you do not want to specify a limit on the number of rows retrieved.
- The parameter is available in custom SQL and Selects actions.
- Row Count Field Name
- Type the field name of the Row Count Field. The field specifies the name of the output field
whose value contains the number of affected rows during SQL query execution.Note: This parameter is not available in Stored Procedures.
- Row Count Field Type
- Select the data type of the Row Count Field.Note: This parameter is not available in Stored Procedures.
Batch operation
Procedure
Provide the required details.
- Query Time Out
- Type or Select the query time out value in seconds. This field specifies the number of seconds
the database connection waits for an SQL statement to run.Note: Leave blank when you do not want to specify the Query Time Out.
- Query Time Out
- Type the output name of the Batch Result Output Name. The output of the batch operation is a
string list. Elements in the list appear in the order in which you add the Insert SQL queries for
execution in the batch mode. Depending on the JDBC driver you use, the elements in the list contains
one of the following values. that are mentioned after this.
- A number greater than or equal to 0. It indicates the insert SQL query is successfully run and returns the number of rows that are affected in the database.
- A value of -2. It indicates that the insert SQL query was run successfully but the number of rows that are affected is unknown.|