Hook Invocation Modes and Triggering Events

Hook Processing Actions

There are two types of hooks: standard hooks and iHooks. Both types use a similar framework but have different attributes.

Standard Hooks. You can invoke standard hooks (known simply as, hooks) during data manipulation when no user interaction is required. You can trigger a standard hook from on a pre-processing or post-processing event.

Event-Driven Hooks. Triggered by an event such as an insert, update, or delete before (pre-process) or after (post-process) a data manipulation event.

Command Hooks. Triggered by an action on a record from a Data Manager or Workflow Details screen.

iHooks (Interactive Hooks). iHooks require user interaction and are triggered only after receiving user input. iHooks provide the framework for XML interaction. You can trigger iHooks from a pre-processing or post-processing event.

Note:
If the iHook is triggered from a post-process event, the iHook interacts with webMethods OneData, not with the user.

iHook interactivity can be directly with the user or with the system.

webMethods OneData interactive mode. webMethods OneData interacts with the data management engine to ensure that iHook actions adhere to the same rules, auditing, and workflow as changes made through the webMethods OneData user interface.

User interactive mode. webMethods OneData uses a wizard to elicit user responses. The iHook may interact with webMethods OneData data management engine.