Ordering application event actions

A single application event handler can include multiple event actions. When you define an event action, you must assign an action sequence number in the Action Sequence field of the Event Actions form. You can assign any number you want in that field and the system automatically sorts the actions in the correct sequence on the Event Handlers form. When the event handler executes, the system uses this Action Sequence number to determine the order in which the actions execute.

The only exception to this rule is that, if you select a particular action (other than 1) in the Initial Action field of the Event Handlers form, then processing of the event actions begins with the designated action and proceeds from there. So, for example, if you have four actions associated with a handler, and you later decide that you want action number 3 to be the starting point, you would select 3 in the Initial Action field. In this case, only actions 3 and 4 execute. The system skips over actions 1 and 2. You can later execute these actions by using a Branch action type or a Goto action type, with one of these actions (1 or 2) as the destination.