Understanding hooks in server-side business rules

Hooks indicate a specific activity when the business rule must fire. The hooks have names that are indicative of the activity. For example, Route on ER Submit. ER Submit is the activity and Route on is a modifier. This indicates that the hook is used by a server-side business rule for routing purposes.

There is a standard set of hooks already defined in the application. The set of hooks correspond to the most common activities in any implementation. In each implementation there is customer specific activities. Hooks must be defined if a server-side business rule is required for such an activity. The Implementation team can decide on the name of such hooks.