Stored procedures in Jitterbit App Builder

Overview

Stored procedures are imported when importing metadata from a relational database (SQL Server and Oracle).

Input parameters can be passed to the stored procedure.

Outside of a true/false or a thrown error, the output of the stored procedure is ignored. If your stored procedure raises an error, it will be presented to the user like an error message.

Your stored procedure cannot return a table of data and have this rendered in App Builder.

The execution timeout can be set for each stored procedure. See steps to configure below.

When you trigger a stored procedure in an action, you bind columns from your data object to the input parameters.

You cannot create / edit stored procedures from within App Builder, but App Builder can use release management to ship stored procedures from development to quality assurance and production environments.

To configure execution timeout on stored procedures

Execution timeout can be set per stored procedure. If no value is configured, App Builder will use the exception timeout value set at the data source level. If you wish to set an execution value for a stored procedure, enter the numeric value of seconds which represent how long you expect the procedure to run.

1. Navigate to the App Workbench > Data Sources
2. Select the Data Source
3. Click the Procedures button
4. Click the pencil icon for the Stored Procedure you wish to edit
5. Enter the desired execution timeout value in seconds in the Timeout field
6. Click the checkmark icon to save the setting

Calling stored procedures across data sources

Stored Procedures can be used across Data Sources, meaning you can call a stored procedure in Data Source B from an event running in Data Source A. To call Stored Procedures across Data Sources, first mark the Stored Procedure as Public in the Data Source you will call it from (in this example, Data Source B) to add it to your Event in another Data Source (Data Source A).