The standard JDBC syntax looks like the following:

{ call procedure-name ( parameter1 parameter2 parameter3 ... ) }

If you are using this syntax with Rule-Connect-SQL, it is important to escape the curly braces (using the backslash character), so that PegaRULES does not interpret them as part of one of its own directives. So your call would look like the following:

\{ call procedure-name (parameter1 parameter2 parameter3 ... ) \}

Note that in a stored procedure call, there is not usually a place to put a Class directive. It is therefore important that the Rule-Connect-SQL be defined on a class that is mapped to the database to which the query should be submitted.

Specifying Parameters:

If you had a stored procedure named my_proc that took no parameters, a call to this procedure in Rule-Connect-SQL would look as follows:

\{ call my_proc \}

If your stored procedure takes input parameters, and the value of those parameters will come from a clipboard property, then you may use standard PegaRULES RDB property directives for the values of the stored procedure parameters. For example, assume your stored procedure takes one string-type input parameter, and assume that the value of that parameter should come from the MyProperty property defined on MyPage. Your call might look like the following:

\{ call my_proc ( {MyPage.MyProperty} ) \}

I believe (I have seen in one of the Pega forum) that one can use UDB and DB2 stored procedures with rule-connect-sql.