Component Start

Table of Contents

Description

The component that starts the execution of a script or a detached branch of a script.

Table 1. System Characteristics

Index

101

Short title

start

Types of scenarios

All of them

Starter module

r_script_component_start

Mode

Synchronous

Icon

101

Branching pattern

Non-branching

Properties

Table 2. Properties
Specification Description

Title: Start Type
Code: type
Visibility: no
Default: `Start'

Script Start Type.
Possible values:

  • Start - the main mode of the script execution. Code: default. Id: 0.

  • Post-processing - script execution mode in case the main branch is terminated for one of the possible reasons. Code: stopping. Id: 1.

Title: Startup Parameter
Code: startParam
Visibility: yes
Default: empty

Field for specifying the variable to which the value from the first run parameter will be written startparam1.

Title: Initialize variables
Code: defineVars
Visibility: yes;
Default: `Yes'

Switch to set all script variables to default values of the appropriate type.

Title: Transition Option
Code: transitionOption
Order: 3
Visibility: yes;
Default: All

The reason for the failure of the main branch of the script execution, upon the occurrence of which a chain of components following the current START component will be executed as part of post-processing.
Possible values:

  • All (all, 0) - any reason to terminate the scenario.

  • Correct termination (normal, 1) - the scenario is terminated with components that have no transition branches (Stops, Transitions, etc.).

  • No transition branch (transfer_not_set, 2) - the required transition property is not assigned to the main scenario branch component.

  • External stop (stop, 3) - the script is forcibly terminated (via the API).

  • Timeout (timeout, 4) - not used.

  • Component Error (error, 5) - critical component execution error.

  • Owner disconnect (ownerdown, 6) - termination of a related owner process, such as FSM call dialog for IVR scenario (for IVR scenario including caller-side disconnect).

  • Component count limit (maxcount, 7) - reaching the limit on the number of executed components set for domaina.

  • Execution Time Limit (maxduration, 8) - Reaches the script execution time limit set for the domain.

Title: Time of execution of the entire scenario
Code: implementedTime
Visibility: yes;
Default: 60000

Limit on script execution within the post-processing branch, in milliseconds.
When it expires, the script will forcibly terminate.

See also