Default Scenarios

Table of Contents

Location path
Overview
Default scenario structure
See also

Location path

Path in the assembly catalog

Path in the assembly catalog
`/era_dc/priv/default_scripts/<SCRIPT_TYPE>/<SCRIPT_CODE>.scr`

/era_dc/priv/default_scripts/<SCRIPT_TYPE>/<SCRIPT_CODE>.scr

Overview

Applies if a reference to a script code is present in a domain, but a script with that code does not exist in the domain itself or in any of its root domains up to the master.

For example, voicemail and parking services are available via susces featurecode, which set fixed script codes. By default, these services use basic scripts.

Basic scenarios are not available for modification through the API. In order for the service to use a script specifically configured by the domain administrator, it must be saved with a code that matches the default script code. This way the created script will be applied instead of the default script for all domains in the child tree.

The format is identical to the JSON value of the scriptdata field of entities ivrscript, svcscript. Creation of a hidden script file can be performed according to the following algorithm:

In the script editor web application, a script is created and saved to the domain.
The body of the script is pulled from the domain via API requests .
The value of the scriptdata field is saved to a file with encoding UTF-8.
The file is named, placed in the assembly directory of the process CI.

Format:

{
  "objects": array<object>,
  "variables": array<object>,
  "scriptVersion": 170105
}

objects – list of scenario components with filled fields.
variables – a list of the script variables used.
scriptVersion – file format version.