Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Developing for webMethods OneData | OneData Hooks | How are hooks used in OneData? | Hook Invocation Modes and Triggering Events
 
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 OneData, not with the user.
iHook interactivity can be directly with the user or with the system.
*OneData interactive mode. 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 OneData user interface.
*User interactive mode. OneData uses a wizard to elicit user responses. The iHook may interact with OneData data management engine.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.