Is it possible to Call Stored Procedure to get some data in SAIL Interface or Expression Rule?

Hi - Yes, you can invoke a Stored Procedure directly from a SAIL interface, as well as from in Process. You'll need to install the following plug-in if you haven't already:

https://community.appian.com/b/appmarket/posts/execute-stored-procedure

You will then have access to fn!executestoredprocedure() which you can call within a SAIL interface.

Pros:

• you do not have to leave the SAIL interface (e.g. call a Process Model) to conduct transactions with a Database

Cons:

• depending on the complexity and risks associated with your database integration you may end up writing some complex logic (which ends up looking very process-like) in your SAIL interface to handle "non-happy-path" results (i.e. exceptions/errors) - for example: how are you going to notify your Support team that there's been an error? How is that error surfaced to the End User?

Other schools of thought exist, but I would err towards using Stored procs for read-only purposes AND very simple updates (e.g. toggling the value of a Boolean field), where there are no down-stream implications of the transaction failing.

Hi - Yes, you can invoke a Stored Procedure directly from a SAIL interface, as well as from in Process. You'll need to install the following plug-in if you haven't already:

https://community.appian.com/b/appmarket/posts/execute-stored-procedure

You will then have access to fn!executestoredprocedure() which you can call within a SAIL interface.

Pros:

• you do not have to leave the SAIL interface (e.g. call a Process Model) to conduct transactions with a Database

Cons:

• depending on the complexity and risks associated with your database integration you may end up writing some complex logic (which ends up looking very process-like) in your SAIL interface to handle "non-happy-path" results (i.e. exceptions/errors) - for example: how are you going to notify your Support team that there's been an error? How is that error surfaced to the End User?

Other schools of thought exist, but I would err towards using Stored procs for read-only purposes AND very simple updates (e.g. toggling the value of a Boolean field), where there are no down-stream implications of the transaction failing.