Contents

Email - Run Subroutine

This node passes the current email object to a custom handler. The processing that the subroutine performs occurs is up to the handler author. This node is sometimes called "Subroutine Initiator", since it allows a custom handler to take over processing of an interaction. The custom handler usually accomplishes functionality outside of the scope of Attendant's built-in nodes.

Important: Before using Run Subroutine in Interaction Attendant, you must modify the CustomSubroutineInitiatorRouter handler using Interaction Designer. See Modify CustomSubroutineInitiator.ihd for procedural details. Interaction Designer's online help provides comprehensive information about handlers and subroutines.

Node Characteristics frame

Options in this frame name the node, and establish whether or not it is active, logged, or tracked for reporting purposes.

Name field

The label you enter here becomes the name of the node in the tree structure.

Active check box

By default, forms are "on", or "active", which means that Interaction Attendant will process them. If you uncheck a form's Active check box, the name of the node turns gray in the tree to indicate that the form is inactive. Interaction Attendant and its handlers will thereafter ignore the form and its children. Use this feature to save a configuration that you are testing. Inactive forms are invisible to callers. When a node is inactive, it appears grayed out in the tree view.

Enable IVR Reporting

This option determines whether or not reporting data will be collected when control passes through this node. Several IVR Reports summarize this information. IVR Reporting is disabled by default. Enable it to capture the date, time and duration of time that the call remained in the node and its children. This option is hidden when Attendant is connected to a server that does not have reporting installed. For more information about this feature, see IVR Reporting Option.

Add entry to the Interaction log

When this option is enabled, information about this node is appended to the call's Interaction Log when the call enters this node. This helps track the path that a call took through Attendant. The Interaction Log is maintained for reporting purposes. See View the Interaction Log for details.

Subroutine Name

Subroutine name field

Type the name of the subroutine to run in this field. Attendant does not validate this entry, so be careful to enter a valid subroutine name. At runtime, the Subroutine Initiator will pass the interaction's identifier and the supplied subroutine name to a handler named CustomSubroutineInitiatorRouter, which in turn, invokes the subroutine.

Once control is passed to the subroutine, it does not return to Attendant. From Attendant's point of view, the interaction ends once the email is passed to the handler.

Related Topics