Working with Command Hooks
Command hooks are external routines that you can manually execute in OneData to perform an action on several records at a time. The routines can be stored database procedures or Java code that can be executed locally or by calling a remote method. You may use a command hook, for example, when you need to customize and update data manually on several records.
Command hooks are standard on iHooks and can be configured to be invoked manually. If there are three or fewer command hooks associated with the object, then the hook name is displayed as a menu option. Otherwise, OneData displays the Command Hook field, which lists all hooks associated with the object that can be executed for the associated role.
Hooks are available in the staging schema and can be configured with security privileges. Event driven hooks are executed for configured actions.
The Execute Command Hook field displays different hooks in conceptual objects depending on the display mode:
In Default mode,
OneData displays the hook assigned to the root node.
In Nova mode, if the network recursive conceptual objects are configured, and the objects have secondary axis objects, you can directly execute the command hooks configured for the secondary axis objects.
OneData displays the hook command menu along with the secondary axis menu. Any data manipulation executed within the hook is part of the conceptual object transaction.
In Nova mode, configured command hooks appear in the main menu of Advanced Parent-Child conceptual objects. You can execute these hooks on different objects in a conceptual object by moving the command hooks to the required objects in the tree.
To execute a hook, you must select the records according to the cardinality of the hook. If the cardinality is 0, you do not need to select a record and can execute the hook by clicking on the hook name. If the cardinality is 1, you must select a record. Any number of records can be selected for cardinality n before executing the respective hooks.
In objects that are SOX compliant, the Request Info and Delegate to actions are not available. In these objects, only the user who created the object is allowed to update records.
For more information on hooks, see Developing for webMethods OneData.
To manage assigned workflow items
1. On the Menu toolbar, click Manage > My Workflow Inbox.
2. Enter search criteria to narrow the list of workflow items that display, if desired, and click Next.
OneData returns the records with pending workflow actions.
3. Select the pending records to manage.
Tip:
To view only the requested record actions for one object, select the object and then the pending records. For conceptual objects, click Expand /Collapse All to view the complete object hierarchy.