Templates (Composite Nodes)

Working with the Call Flow Editor > Getting Familiar with Nodes to Build Applications > Templates (Composite Nodes)

	Templates (Composite Nodes)

The Templates (Composite) Nodes contain preset functionality and options, which are used as templates. These nodes are easier to use than the Application Items (basic nodes), but they are also intended to be more limited in scope.

Think of a composite node as being a template for a predetermined use. These nodes are actually Form nodes that Dialog Designer populates with one or more form items, in ways that make it easier to create speech application projects. For example, a Prompt and Collect node consists of:

A Form node with a nested Prompt item

A speech Input item

A selection of event handlers

On the Call Flow Editor palette, Dialog Designer displays the composite nodes as the Templates group. Composite Nodes have a predefined structure in the node editor, and the following properties:

Name - Should reflect the central purpose of the node. Use naming conventions for Java components. See Naming Java Components.

Comments - Can be anything to add as a reminder or description of the purpose or content of the node. Can also be left blank.

Dialog Designer uses whatever text entered in this property field for the pop-up hint that appears when the cursor hovers over the node icon in the workspace. If left blank, Dialog Designer uses the name of the node for the pop-up hint.

Location - (Read-only) Displays the location of the node graphic in the workspace.

For more information, including complete and detailed descriptions of the composite nodes (Templates), see Detailed Node Descriptions.

Note:

A deleted node will have a marker in the Task Tab and the associated Java class will be marked with a warning marker. The task may be deleted if you want to keep the Java code in the project. Be aware that the Java code will not be regenerated by Dialog Designer and you may encounter Java errors in future upgrades if the Dialog Designer runtime API changes. In such cases, you will have to manually fix the Java errors.