In version 22.1 Appian released support for executing stored procedures out-of-the-box using a!executeStoredProcedureForQuery(), a!executeStoredProcedureOnSave(), or the Execute Stored Procedure Smart Service. With this release, the Execute Stored Procedure plug-in was deprecated. Below is a guide for how you can upgrade the deprecated plug-in function calls and smart service nodes to the fully supported features. Note that this guide does not guarantee the success of your updates. All updates should be tested thoroughly.
When upgrading, keep in mind the following backwards compatibility considerations:
Appian Execute Stored Procedure Behavior
Plug-in Execute Stored Procedure Behavior
Result sets exceeding the max result set size of 1000 rows are truncated.
No maximum result set size.
For stored procedures that return multiple result sets, results exceeding the cumulative max size of 10,000 rows are truncated.
No maximum cumulative result set size.
Error returned when duplicate or empty column names are found.
Columns with duplicate names are silently truncated. Empty column names are allowed.
Error returned when IN or INOUT parameters are not passed in inputs.
Missing IN and INOUT parameters are defaulted to null.
Supports data source connected systems and admin console data sources.
Supports only admin console data sources.
Optionally, the fully supported Appian Execute Stored Procedure functions and smart service can be used with data source connected systems, which allow you to apply role map security to your data sources. Migrating from an admin console data source to a data source connected system is simple. From the Appian designer click to create a new connected system object, copy the connection details, and apply security. To execute stored procedures using the new data source connected system you’ll also need to create a connected system constant.
To find each instance that the Execute Stored Procedure plug-in is used, follow these steps:
Like the plug-in function, a!executeStoredProcedureForQuery should not be used to execute stored procedures that modify data. Doing so can have unintended side effects! If you’re relying on this unsupported behavior to execute a stored procedure that modifies data, we’re excited to introduce you to the new a!executeStoredProcedureOnSave smart service function. Using this function, you can safely execute stored procedures that modify data from an interface.
Upgrading to the Appian execute stored procedure functions is super easy. In most cases it will be as simple as changing the function name.
To upgrade execute stored procedure process model nodes, we recommend copying the properties from the process model documentation in a separate window and following the instructions below: