Understand the Pre-Hook Type and Post-Hook Type properties

A single middleware event can either execute a stored procedure or invoke an assembly for a pre-hook and a post-hook. No other types besides the following are allowed in the current release.

• Stored procedure. Indicates that the configured hook type is a stored procedure. In other words, the name configured in the corresponding Pre-Hook Name or Post-Hook Name column is considered to be a stored procedure. Therefore, the configured custom stored procedure in the MES database is invoked before or after the middleware call depending upon the pre-hook or post-hook configuration.

• Assembly. Indicates the configured hook type is an assembly. In other words, the name configured in the corresponding Pre-Hook Name or Post-Hook Name column is considered to be an assembly. Therefore, the configured custom assembly is invoked before or after the middleware call depending upon the pre-hook or post-hook configuration.