Hidden scenarios
Location path
| Path in the assembly catalog | Assignment |
|---|---|
|
A shared catalog within which the structure is arbitrary. |
|
Recommended location path for hidden scripts. |
Overview
The contents of hidden scripts located in files.
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.
Types of scenarios: ivr, svc.
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.
{
"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.
Application options
-
For the integration channel types set in the assert file webservices.json.
-
To hide business logic.
See also
-
Entity integration point