- Contents
Interaction Designer Help
Manage Handlers notebook
In the Manage Handlers notebook you can activate and deactivate Primary and Monitor handlers. All published handlers are listed here. Once you publish a handler, it appears in the Inactive Handlers list, unless it is already an actively running handler. CIC begins to use Activated handlers as soon as another event occurs for which the handler is registered. If Interaction Processor is currently running older versions of the handler, those threads finish before the new handler is used. Any threads running on handlers you deactivate continue until the thread is finished.
Caution: CIC cannot differentiate between primary and monitor handlers in the Manage Handlers Notebook. This is why the lists of inactive handlers are identical on the Primary Handlers and Monitor Handlers page. Make sure you don't activate a primary handler on the Monitor Handlers page, or vice versa.
Note: You can also manage handlers in Interaction Administrator's Server Configuration container.
Primary and Monitor Handlers
Primary handlers are generally handlers that act directly on objects such as calls within the system. Only one primary handler can be activated for a given initiator. For example, you cannot activate two primary handlers that both start with the Incoming Call initiator. Only one handler can act on the incoming call. This prevents two handlers from performing disparate actions on a single object. If you attempt to activate two handlers that start with the same initiator, CIC generates an error message in the event log.
Monitor handlers do not actively manipulate or modify objects in the system. Typically they retrieve call attributes and write that information to a database for reporting purposes, although they are not limited to reporting. CustomCallDisconnectMonitor determines if a call was recorded, and if so, where to send a copy of that recording. Since monitor handlers are not acting on objects, more than one monitor handler can use the same initiator. For example, CallDisconnectMonitor and CustomCallDisconnectMonitor both use the Call Monitor Initiator configured to start when a call disconnects.
Activating and Deactivating Handlers
Click on one of the links below for more information on activating primary and monitor handlers.