Stored Procedure Hooks

You can invoke a stored procedure using either standard hooks or iHooks. OneData uses XML to communicate with the iHook stored procedure. A stored procedure hook can complete successfully if it does not execute a raise_application_error command.

If an event-driven hook (pre-processing or post-processing) invokes the stored procedure and it returns an error, the entire transaction rolls back. For example, when you insert a new record in OneData, if the post-processing stored procedure returns an error, OneData does not insert the new record in the repository.

Property	Description
Hook Name	Name of the hook.
Hook Description	Type an appropriate description for the hook.
Hook execution mode	The OneData mode in which the hook should be executed: Default Nova
Hook Type	Select the Stored Procedure hook type.
Connection	Select the connection to the database where the stored procedure is available.
Program Name	Name of the external program to be executed.
Default Parameters	Parameters used for invoking the stored procedure. For more details about default parameters, see Default Parameters in a Stored Procedure Hook.
Is Interactive Hook?	Indicates if the hook is an iHook. This property is selected by default and cannot be changed.
Hook Cardinality	Execution parameter that determines when to execute the external program. The hook executes the program based on the number of rows changed: 0. Hook executes when no rows are changed. 1. Hook executes when one row is changed. n. Hook executes when more than one row is changed.