Exit Block Routing

Use to terminate the workflow or to return control back to calling workflow in case of a subworkflow (subroutine). Every strategy flow must have at least one Exit block (multiple Exit blocks are allowed, such as when using the Branching block). Composer generates a validation message if an Exit block is missing. If a workflow does not perform target selection and reaches the Exit block, the call is default routed to the default destination in Configuration Server, which is a configured DN. For more information, see option default_destination in the Universal Routing 8.1 Reference Manual. The Exit block has the following properties:

Name Property

The Name property is present in all blocks in Composer. The Name property is the first property for all blocks.

• Use the Value field beside in the Name property row of the block's property table to name the block. Block names should conform to ECMAScript and SCXML identifier naming conventions, and they are limited to a maximum of 255 characters.
• Names may consist only of numbers, letters, or initial underscores (_).
• Names should only begin with a letter or underscore.
• Names can end only with a letter or a number.
• Except for the Entry and Exit blocks, you should give all blocks a descriptive name. For example, if an Input block asks the caller to input an account number, then the name of the block could be Input_Account_Number.
• The name of the block is used as the Name of the <form> tag that gets generated for that block.

To provide a name for a block:

1. Select the Name row in the block's property table.
2. In the Value field, type a block name that conforms to the restrictions above.

Block Notes Property

Find this property's details under Common Properties.

Condition Property

Find this property's details under Common Properties.

Logging Details Property

Find this property's details under Common Properties.

Log Level Property

Find this property's details under Common Properties.

Enable Status Property

Find this property's details under Common Properties.

Interaction ID Property

Set to a meaningful value or keep the default value, which is the system variable InteractionId. Can be used for "interaction-less" processing for scenarios where the InteractionId variable is not automatically initialized, but instead must wait for an event. An example would be an SCXML application triggered by a Web Service that does not add an interaction.   Background: Previous to 8.1.1, Composer did not expose an Interaction ID property.  Instead, when ORS started processing an interaction, a generated SCXML application automatically initialized the system variable, InteractionId. This variable was then used internally by Routing and certain eServices blocks when interacting with ORS. With the introduction of support for Interaction-less processing, you can now define a specific event (IPD Wait For Event property) to initialize InteractionId, or not define an event at all. For scenarios with an interaction (IPD Diagram/Wait For Event=interaction.present for example), you may keep the default value for the Interaction ID property. The default value is the system variable InteractionId, which is initialized automatically in this case. For other scenarios (any scenario where the system variable InteractionId is not set), you may choose to:

1. Not use blocks that require an Interaction ID
2. And/or set the Interaction ID property to a meaningful value
3. And/or assign a meaningful value to the InteractionId  system variable

Return Values Property

This property is visible only for subworkflows. Use to specify the variable(s) whose value(s) will be returned once the Exit block is executed. To select return variables:

1. Click the Return Values row in the block's property table.
2. Click the button to open the Return Values dialog box.
3. Select individual variables, or click Select all or Deselect all as needed.
4. Click OK to close the Return Values dialog box.

Single Session Treatments

When using the Play Application, Play Sound (Music and ARM Types) Exit, and Disconnect blocks, voice applications can now optionally use a single VXML session on Media Control Platform to play/run multiple treatments instead of using one session per treatment. This enables DTMF buffering between multiple MSML treatments. For more information, see Single Session Treatments.