Hook Processing Actions
You can invoke hooks during different points of data manipulation to perform necessary processing:
Pre-processing. Validate data before adding it to the repository. Pre-process hooks call an external program to verify data consistency and to apply business rules. Data management cannot be performed with pre-processing hooks.
Post-processing. Perform actions on the data that has been written to the repository. After data is written to the repository, the post-processing hook calls an external program to run subsequent event processing in a different repository.
User interaction trigger. Hooks that are triggered from a Data Manager or Workflow Details screen when a specific event occurs.
The following table shows the data manager actions and the type of processing available.
Note:
You cannot use hooks to delete data in objects that have multi-select columns. Multi select columns are not shown as part of grid display in hooks. Multi select columns are displayed only on the insert and edit screens.
Note:
In the iHook pop up, data grid is displayed using ShowableRowset.
Data Manager Actions | Pre-process |
Insert | No |
Update | No |
Data Manager Actions | Pre-process | Post-Process | User Interaction |
Insert | No | Yes | Yes |
Update | No | Yes | Yes |
Delete | No | No | Yes |
Restore | No | No | Yes |
Purge | No | No | Yes |
The following diagram shows the different ways that hooks can be invoked.