Feedback

  • Contents
 

System Initialization initiator

Use the System Initialization initiator in handlers that need to be executed when Interaction Processor (IP) subsystem starts.

If there are multiple handlers containing the System Initialization initiator when IP starts, IP will execute them all. The order of execution of those handlers is undefined. (If you have a set of procedures that requires a certain order, create subroutines and call them in order from a single System Initialization handler.)

This initiator has no input or output parameters.

Note: If you need to call a subroutine or your operations are going to be very long, sending a custom notification and doing all of the work in a Custom Notification Handler is best. IP waits for all System Initialization handlers to complete, so long tasks done with this can hold things up. The Custom Notifications are not processed until all handlers, including subroutines, have been loaded.