MAS - CA - Add Node Dialog Box

This topic describes how to use the Add Node dialog box to create a new application (action) node. This is a child node of a caller application or another application (action) node.

Callers can interact with the system in a more complex fashion than a simple menu, when application (action) nodes are used. A caller application may have many nodes, however, for reasons of usability, Avaya recommends that you limit a caller application to three or four menu levels.

Launching the Screen

In the Modular Messaging Caller Applications window, click on a

caller application node that you have created or on an existing

application (action) node.

For more information on these nodes, see MAS - CA - Caller Applications Node and MAS - CA - Application (Action) Node.

Click the

Action > New > Application Node icon or menu command. The system displays Add Node dialog box.

Configuring the Screen Controls

Name Enter a name for the node.

The Caller Application Editor uses this name to identify the node in various node and application displays.

Action type Select the type of action you want to assign to the node.

Note: You can amend this setting, if necessary, when you are configuring the application node’s properties via the General tab of the node’s Properties dialog box.

Menu (Default) Select this option to present the caller with a menu. A menu usually plays a prompt and then provides the caller with a series of single digit numbered choices.

Transfer Select this option to transfer the caller to either the operator, a mailbox or an extension number, when a caller presses the associated key

Goto Select this option to route the caller directly to another application node or another caller application. This can be useful when you have a common action that you want to reuse in your system.

Conditional goto Select this option to route the caller directly to another application (action) node, using criteria specified by a schedule.

Send message Select this option to allow callers to send a message to a subscriber without having to listen to the subscriber’s greeting.

Termination Select this option to terminate the current caller application. It either disconnects the caller from the system or re-routes the caller back to the system Automated Attendant.

Key press Select the touchtone key (also known as the access key) that callers must press to activate the action assigned to this node. If you wish, you can select the keyless option so that there are no TUI key bindings.

Note: You can change the access key at any time via the Action > Change Access Key menu. See MAS - CA - Change Key Dialog Box.

Description (Optional, but recommended) Enter a short description of the caller application.

This description provides the text that the system displays with the application properties. It can be useful, especially when designing large applications.

After Configuring the Controls

Once you have configured the fields in the Add Node dialog box and pressed OK, you should configure the new application (action) node’s properties, via the Properties dialog box. See MAS - CA - Properties Dialog Box.

The icon for the new application (action) node varies, depending on its current status. These example icons show key press 1 but they can show any valid key press number.

You will see this display, when the application (action) node is configured correctly so far but ideally needs some additional settings before the caller application is saved.

You will see this display, when the application (action) node is not configured correctly. It also ideally needs some additional settings before the caller application is saved.

You will see this display, when the application (action) node is not configured.

Note: Until this is corrected, you cannot save the caller application successfully.

You will see this display, when the application (action) node is fully configured and the caller application has been saved.

The green arrow attached to the icon indicates this node is the start of the caller application.

Note: The caller application node is set as the start point by default. The start point can be set to a different node via the Action > Set application start menu command.